**************************** ECO SUMMARY INFORMATION **************************** Release Date: 6-MAY-2004 Kit Name: DEC-AXPVMS-VMS73_FIBRE_SCSI-V0700--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3 Approximate Kit Size: 4640 blocks Installation Rating: INSTALL_2 Required Features: Fibrechannel SCSI Superseded Kits: VMS73_FIBRE_SCSI-V0600 Mandatory Kit Dependencies: VMS73_UPDATE-V0300 VMS73_PCSI-V0200 Optional Kit Dependencies: None. VMS73_FIBRE_SCSI-V0700.PCSI-DCX_AXPEXE Checksum: 563715354 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS73_FIBRE_SCSI-V0700 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 1 KIT NAME: VMS73_FIBRE_SCSI-V0700 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2: To be installed by all customers using the following feature(s): - Fibrechannel - SCSI This installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) 2.2 Reboot Requirement: Reboot Required. HP strongly recommends that a reboot is performed immediately after kit installation to avoid system instability. If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.3 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - VMS73_FIBRE_SCSI-V0600 Page 2 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS73_PCSI-V0200 - VMS73_UPDATE-V0300 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None. 5 FILES PATCHED OR REPLACED: o [SYSHLP.UNSUPPORTED]FC$CP.EXE (new image) Image Identification Information image name: "FC$CP" image file identification: "X-2" image file build identification: "X9UH-0060010048" link date/time: 2-FEB-2004 16:33:13.70 linker identification: "A11-50" Overall Image Checksum: 684656946 o [SYSLIB]FC$SDA.EXE (new image) Image Identification Information image name: "FC$SDA" image file identification: "X-12A3" image file build identification: "X9UH-0060010048" link date/time: 2-FEB-2004 16:33:16.96 linker identification: "A11-50" Overall Image Checksum: 1070098524 o [SYSLIB]IOGEN$FIBRE_CONFIG.EXE (new image) Image Identification Information image name: "IOGEN$FIBRE_CONFIG" image file identification: "X-16A1" image file build identification: "X91Y-0060010003" link date/time: 14-MAY-2002 06:53:40.68 linker identification: "A11-50" Overall Image Checksum: 2782898312 Page 3 o [SYSHLP.UNSUPPORTED]MSA_UTIL.EXE (new image) Image Identification Information image name: "MSA_UTIL" image file identification: "X-2" image file build identification: "X9UH-0060010048" link date/time: 2-FEB-2004 16:33:20.39 linker identification: "A11-50" Overall Image Checksum: 3062080939 o [SYSLIB]SMI$OBJSHR.EXE (new image) Image Identification Information image name: "SMI$OBJSHR" image file identification: "X40-A8" image file build identification: "X9UH-0060010015" link date/time: 18-FEB-2004 09:55:04.79 linker identification: "A11-50" Overall Image Checksum: 2443932942 o [SYS$LDR]SYS$DKDRIVER.EXE (new image) Image Identification Information image name: "SYS$DKDRIVER" image file identification: "X-12" image file build identification: "X9UH-0060010048" link date/time: 2-FEB-2004 16:29:07.06 linker identification: "A11-50" Overall Image Checksum: 791549300 o [SYS$LDR]SYS$FGEDRIVER.EXE (new image) Image Identification Information image name: "SYS$FGEDRIVER" image file identification: "X-55A11" image file build identification: "X9UH-0060010048" link date/time: 2-FEB-2004 16:32:42.37 linker identification: "A11-50" Overall Image Checksum: 1218086152 o [SYS$LDR]SYS$GKDRIVER.EXE (new image) Image Identification Information image name: "SYS$GKDRIVER" image file identification: "X-40A2" image file build identification: "X9UH-0060010048" link date/time: 2-FEB-2004 16:29:40.37 linker identification: "A11-50" Overall Image Checksum: 2607564359 Page 4 o [SYS$LDR]SYS$MKDRIVER.EXE (new image) Image Identification Information image name: "SYS$MKDRIVER" image file identification: "X-12" image file build identification: "X9UH-0060010048" link date/time: 2-FEB-2004 16:29:25.25 linker identification: "A11-50" Overall Image Checksum: 4156830116 o [SYS$LDR]SYS$PGADRIVER.EXE (new image) Image Identification Information image name: "SYS$PGADRIVER" image file identification: "X-44A6" image file build identification: "X9UH-0060010048" link date/time: 2-FEB-2004 16:32:28.51 linker identification: "A11-50" Overall Image Checksum: 201396747 o [SYS$LDR]SYS$PKADRIVER.EXE (new image) Image Identification Information image name: "SYS$PKADRIVER" image file identification: "X-12A2" image file build identification: "X9UH-0060010048" link date/time: 2-FEB-2004 16:32:07.46 linker identification: "A11-50" Overall Image Checksum: 2735408374 o [SYS$LDR]SYS$PKQDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKQDRIVER" image file identification: "X-10A3" image file build identification: "X9UH-0060010048" link date/time: 2-FEB-2004 16:31:42.46 linker identification: "A11-50" Overall Image Checksum: 248352204 o [SYS$LDR]SYS$PKSDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKSDRIVER" image file identification: "X-9" image file build identification: "X9UH-0060010048" link date/time: 2-FEB-2004 16:30:52.94 linker identification: "A11-50" Overall Image Checksum: 3918213893 Page 5 o [SYS$LDR]SYS$PKWDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKWDRIVER" image file identification: "X-29A2" image file build identification: "X9UH-0060010048" link date/time: 2-FEB-2004 16:31:54.41 linker identification: "A11-50" Overall Image Checksum: 3141587115 o [SYSLIB]FC$GLOBALS.STB (new file) o [SYS$LDR]SYS$CONFIG.DAT (new file) 6 PROBLEMS ADDRESSED IN THIS KIT 6.1 New problems addressed in the VMS73_FIBRE_SCSI-V0700 kit 6.1.1 INCONSTATE bugcheck at SYS$FGEDRIVER+12968 6.1.1.1 Problem Description: The system can crash with an INCONSTATE bugcheck at SYS$FGEDRIVER+12968. Crashdump Summary Information: ------------------------------ Bugcheck Type: INCONSTATE, Inconsistent I/O data base Current Process: NULL Failing PC: FFFFFFFF.8053A968 SYS$FGEDRIVER+12968 Failing PS: 10000000.00000804 Module: SYS$FGEDRIVER (Link Date/Time: 27-MAR-2003 06:17:59.15) Offset: 00012968 Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE 6.1.1.2 CLDs, and QARs reporting this problem: 6.1.1.2.1 CLD(s) None. Page 6 6.1.1.2.2 QAR(s) 75-13-1126 6.1.1.3 Problem Analysis: The fg$fcp_fp_ring_attention did not recognize the XRI_ABORTED_CX command. 6.1.1.4 Release Version of OpenVMS that will contain this change: V7.3-1 6.1.1.5 Work-arounds: None. 6.1.2 Backup operations can take three times longer or more when using SDLT tapes. 6.1.2.1 Problem Description: Backup operations can take three times longer or more when using SDLT tapes. Images Affected: - [SYS$LDR]SYS$MKDRIVER.EXE 6.1.2.2 CLDs, and QARs reporting this problem: 6.1.2.2.1 CLD(s) 70-3-7295,70-3-7564 6.1.2.2.2 QAR(s) None. 6.1.2.3 Problem Analysis: With skip-file, routine io_skip_file_reverse is called if the skip count is negative. However, this routine only skips by record. This causes unnecessary tape motion and degrades performance. Page 7 6.1.2.4 Release Version of OpenVMS that will contain this change: The next release after V7.3-2 6.1.2.5 Work-arounds: None. 6.1.3 MCR SYSMAN IO AUTO command causes INVEXCEPTN crash in SYS$FGEDRIVER 6.1.3.1 Problem Description: The MCR SYSMAN IO AUTO command can cause a system crash with an INVEXCEPTN at SYS$FGEDRIVER+0BE48 bugcheck. Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE 6.1.3.2 CLDs, and QARs reporting this problem: 6.1.3.2.1 CLD(s) None. 6.1.3.2.2 QAR(s) None. 6.1.3.3 Problem Analysis: A partially configured fabric can trigger the crash because the partial configuration leaves lsdb$ps_fid null, while fg$validate_fc_la() expects this pointer to be valid. 6.1.3.4 Release Version of OpenVMS that will contain this change: The next release after V7.3-2 Page 8 6.1.3.5 Work-arounds: None. 6.1.4 Frequent mount verification on SCSI disks attached to KZPCA/KZPCM controllers 6.1.4.1 Problem Description: Under heavy IO loads, SCSI disks attached to KZPCA/KZPCM controllers experience frequent mount verifications. The error log will contain SCSI timeout errors. Images Affected: - [SYS$LDR]SYS$PKWDRIVER.EXE 6.1.4.2 CLDs, and QARs reporting this problem: 6.1.4.2.1 CLD(s) 70-3-7263,70-3-7264,70-3-7268 6.1.4.2.2 QAR(s) None. 6.1.4.3 Problem Analysis: o The driver/script-code handshaking algorithm had timing problems that showed up under heavy IO loads. The script would miss the fact that it had been given a new IO. o Non-queued commands had a disconnect timeout value too small for heavy loads. o Broken devices could reselect the script and start using an IO that had already been completed. 6.1.4.4 Release Version of OpenVMS that will contain this change: The next release after V7.3-2 Page 9 6.1.4.5 Work-arounds: None. 6.1.5 SS$_DATAOVERRUN errors with odd-byte transfers. 6.1.5.1 Problem Description: SS$_DATAOVERRUN errors with odd-byte transfers. Images Affected: - [SYS$LDR]SYS$PKWDRIVER.EXE 6.1.5.2 CLDs, and QARs reporting this problem: 6.1.5.2.1 CLD(s) None. 6.1.5.2.2 QAR(s) None. 6.1.5.3 Problem Analysis: If the transfer count is odd, and the read buffer is xfer count + 1 then the wrong byte count is returned. 6.1.5.4 Release Version of OpenVMS that will contain this change: The next release after V7.3-2 6.1.5.5 Work-arounds: None. 6.1.6 SYSMAN IO FIND_WWID command generates AUDIT security messages Page 10 6.1.6.1 Problem Description: After execution of a SYSMAN IO FIND_WWID command, a channel remains assigned to a PGxx (Fibre Channel Protocol) device. If security auditing has been setup in such a way that usage of privilege is logged, a number of security messages, like the one below, may be generated if the SYSMAN IO FIND_WWID command is given from other processes than the one doing the original assignment: %%%%%%%%%%% OPCOM 22-JAN-2004 11:20:11.44 %%%%%%%%%%% Message from user AUDIT$SERVER on NODE1 Security alarm (SECURITY) on NODE1, system id: 11111 Auditable event: Privilege used Event information: SHARE used to assign a channel to a non-shared device ($ASSIGN) Event time: 22-JAN-2004 11:20:11.43 PID: 21400228 Process name: SysDamager Username: USER1 Process owner: [SUPPORT,USER1] Terminal name: TNA11: Image name: $7$DISK3:[SYS0.SYSCOMMON.] [SYSEXE]SYSMAN.EXE Device name: _UTRA41$PGA0: Privileges used: SHARE Posix UID: -2 Images Affected: - [SYSLIB]SMI$OBJSHR.EXE 6.1.6.2 CLDs, and QARs reporting this problem: 6.1.6.2.1 CLD(s) CFS.104447 6.1.6.2.2 QAR(s) None. 6.1.6.3 Problem Analysis: See Problem Description Page 11 6.1.6.4 Release Version of OpenVMS that will contain this change: The next release after V7.3-2 6.1.6.5 Work-arounds: None. 6.1.7 Users of the ABS tape library management software encounter backup positioning errors. 6.1.7.1 Problem Description: Users of the ABS tape library management software encounter backup positioning errors. Images Affected: - [SYS$LDR]SYS$MKDRIVER.EXE 6.1.7.2 CLDs, and QARs reporting this problem: 6.1.7.2.1 CLD(s) 70-3-7709,70-3-7710,70-3-7144 6.1.7.2.2 QAR(s) None. 6.1.7.3 Problem Analysis: Some versions of ABS (and probably other 3rd party librarians) use io$_diagnose to move tape and then update ucb$l_record to keep MKDRIVER's positioning bookkeeping accurate. This depended on a UCB field, ucb$l_prev_tm, that was not part of these products' bookkeeping. 6.1.7.4 Release Version of OpenVMS that will contain this change: The next release after V7.3-2 Page 12 6.1.7.5 Work-arounds: None. 6.2 Problems addressed in the VMS73_FIBRE_SCSI-V0600 kit 6.2.1 The system can crash with an INCONSTATE bugcheck at SYS$FGEDRIVER+1100C. 6.2.1.1 Problem Description: The system can crash with an INCONSTATE bugcheck at SYS$FGEDRIVER+1100C. Crashdump Summary Information ----------------------------- Bugcheck Type: INCONSTATE, Inconsistent I/O data base Failing PC: FFFFFFFF.8041500C SYS$FGEDRIVER+1100C Failing PS: 08000000.00000804 Module: SYS$FGEDRIVER (Link Date/Time: 19-FEB-2003 11:27:30.09) Offset: 0001100C Stack Pointers: KSP = FFFFFFFF.EF119E08 ESP = FFFFFFFF.E6431000 SSP = FFFFFFFF.E641B000 USP = FFFFFFFF.E641B000 Failing Instruction: SYS$FGEDRIVER+1100C: BUGCHK Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.3 CLD(s) None. 6.2.1.4 QAR(s) 75-83-999 Page 13 6.2.1.5 Problem Analysis: The error checking code does an INCONSTATE for all unknown errors returned from kernel$register_address() in both adr$register_plogi() and adr$pdisc_rsp(). 6.2.1.6 Work-arounds: None. 6.2.2 Mis-leading errors when mounting tape drive 6.2.2.1 Problem Description: A hardware error is logged any time a tape is mounted on a tape drive, such as a TLZ09, that does not support the Read Write Error Recovery Page (SCSI Mode Page 01h). The error does not prevent the drive from mounting and OpenVMS Release Notes state that this behavior does not indicate a problem with the drive and can be ignored. However, ignoring errors is not a satisfactory answer for customers. Customers cannot distinguish this error from an actual error. This change will disable error logging for this error. Images Affected: - [SYS$LDR]SYS$MKDRIVER.EXE 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.3 CLD(s) CFS.96327,CFS.97599,CFS.98783,CFS.99263,CFS.99951 6.2.2.4 QAR(s) None. 6.2.2.5 Problem Analysis: See Problem Description 6.2.2.6 Work-arounds: None. Page 14 6.2.3 Provide Additional error logging 6.2.3.1 Problem Description: Provide additional error logging to help diagnose systems with unavailable or missing fibre channel storage. Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE - [SYSLIB]FC$SDA.EXE 6.2.3.2 CLDs, and QARs reporting this problem: 6.2.3.3 CLD(s) None. 6.2.3.4 QAR(s) None. 6.2.3.5 Problem Analysis: See Problem Description 6.2.3.6 Work-arounds: None. 6.2.4 Display of some controller and device identifiers missing in some SHOW commands. 6.2.4.1 Problem Description: The display of some controller and device identifiers that correspond to OpenVMS unit numbers was missing in some of the SHOW commands. Images Affected: - [SYSHLP.UNSUPPORTED]MSA_UTIL.EXE Page 15 6.2.4.2 CLDs, and QARs reporting this problem: 6.2.4.3 CLD(s) None. 6.2.4.4 QAR(s) None. 6.2.4.5 Problem Analysis: See Problem Description. 6.2.4.6 Work-arounds: None. 6.2.5 The system can crash with an INCONSTATE bugcheck at SYS$FGEDRIVER+12968 6.2.5.1 Problem Description: The system can crash with an INCONSTATE bugcheck at SYS$FGEDRIVER+12968 Crashdump Summary Information: ------------------------------ Bugcheck Type: INCONSTATE, Inconsistent I/O data base Failing PC: FFFFFFFF.8053A968 SYS$FGEDRIVER+12968 Failing PS: 10000000.00000804 Module: SYS$FGEDRIVER (Link Date/Time: 27-MAR-2003 06:17:59.15) Offset: 00012968 Stack Pointers: KSP = FFFFFFFF.892ABDD0 ESP = FFFFFFFF.892AD000 SSP = FFFFFFFF.892A7000 USP = FFFFFFFF.892A7000 Failing Instruction: SYS$FGEDRIVER+12968: BUGCHK Images Affected: - [SYS$LDR] SYS$FGEDRIVER.EXE Page 16 6.2.5.2 CLDs, and QARs reporting this problem: 6.2.5.3 CLD(s) None. 6.2.5.4 QAR(s) 75-13-1126 6.2.5.5 Problem Analysis: The fg$fcp_fp_ring_attention did not recognize the XRI_ABORTED_CX command. 6.2.5.6 Work-arounds: None. 7 INSTALLATION INSTRUCTIONS 7.1 Compressed File This kit is provided as a DCX compressed kit. To expand this file to the installable PCSI file, run the file with a RUN file_name command. When the file is run you will see the following output: $ RUN VMS73_FIBRE_SCSI-V0700.PCSI-DCX_AXPEXE FTSV DCX auto-extractible compressed file for OpenVMS (AXP) FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT Copyright (c) Digital Equipment Corp. 1993 Options: [output_file_specification] [input_file_specification] The decompressor needs to know the filename to use for the decompressed file. If you don't specify any, it will use the original name of the file before it was compressed, and create it in the current directory. If you specify a directory name, the file will be created in that directory. Decompress into (file specification): If you want the file to be expanded into a different directory, enter the directory specification. DO NOT enter a new file name. The expanded file must retain the original name. If you want to expand the file via batch, the command file must contain an answer to the Decompress into "(file specification)" question, either a or an alternate Page 17 directory specification 7.2 Installation Command Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS73_FIBRE_SCSI /SAVE_RECOVERY_DATA [/SOURCE=location of Kit] The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. The kit location may be a tape drive, CD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 7.3 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following logical name definitions and commands: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE o To avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT TRUE o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of that operation. There is no need to also save files as *.*_OLD: $ DEFINE/SYS ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V7.0/SAVE_RECOVERY_DATA Page 18 o De-assign the logical names assigned For example, a sample command file to install the VMS73_FIBRE_SCSI kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/SYS ARCHIVE_OLD NO $! $ PROD INSTALL VMS73_FIBRE_SCSI/PRODUCER=DEC/BASE=AXPVMS- /VER=V7.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2004 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.