**************************** ECO SUMMARY INFORMATION **************************** Release Date: 4-DEC-2003 Kit Name: DEC-AXPVMS-VMS73_UPDATE-V0300--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3 Approximate Kit Size: 154352 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - rolling reboot Superseded Kits: VMS73_UPDATE-V0200 Mandatory Kit Dependencies: VMS73_PCSI-V0100 Optional Kit Dependencies: None VMS73_UPDATE-V0300.PCSI-DCX_AXPEXE Checksum: 4111319137 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS73_UPDATE-V0300 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 1 KIT NAME: VMS73_UPDATE-V0300 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1 : To be installed by all customers. 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: Yes 3 KITS SUPERSEDED BY THIS KIT: - VMS73_UPDATE-V0200 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-V0100 Page 2 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 [SYSEXE]ALPHA_MACRO.EXE (new image) Image Identification Information image name: "ALPHA_MACRO" image file identification: "V4.1-15-3381U" image file build identification: "X91Y-0060010003" link date/time: 8-FEB-2002 10:19:15.79 linker identification: "A11-50" Overall Image Checksum: 2847515790 o [SYSLIB]ALPHA_XFC$SDA.EXE (new image) Image Identification Information image name: "ALPHA_XFC$SDA" image file identification: "V1.0" image file build identification: "X91Y-0060010009" link date/time: 7-MAR-2003 15:31:52.34 linker identification: "A11-50" Overall Image Checksum: 1566881438 o [SYSEXE]APB.EXE (new image) Image Identification Information image name: "APB" image file identification: "X-8" image file build identification: "X91Y-0060010002" link date/time: 25-JUL-2002 00:28:54.97 linker identification: "A11-50" Overall Image Checksum: 230135085 o [SYSEXE]AUDIT_SERVER.EXE (new image) Image Identification Information image name: "AUDIT_SERVER" image file identification: "X-9" image file build identification: "X91Y-0060010000" link date/time: 21-SEP-2001 09:40:04.12 linker identification: "A11-50" Overall Image Checksum: 2412702625 Page 3 o [SYSEXE]BACKUP.EXE (new image) Image Identification Information image name: "BACKUP" image file identification: "AXP73R0022" image file build identification: "X91Y-0060010009" link date/time: 19-NOV-2002 10:38:49.45 linker identification: "A11-50" Overall Image Checksum: 745114801 o [SYSLIB]BACKUPSHR.EXE (new image) Image Identification Information image name: "BACKUPSHR" image file identification: "AXP73R0022" image file build identification: "X91Y-0060010009" link date/time: 19-NOV-2002 10:38:31.03 linker identification: "A11-50" Overall Image Checksum: 2503525503 o [SYSEXE]CIA.EXE (new image) Image Identification Information image name: "CIA" image file identification: "X-21" image file build identification: "X91Y-0060010016" link date/time: 29-MAY-2002 02:41:47.40 linker identification: "A11-50" Overall Image Checksum: 1933164138 o [SYSMSG]CLIUTLMSG.EXE (new image) Image Identification Information image name: "CLIUTLMSG" image file identification: "X-3" image file build identification: "X91Y-0060010002" link date/time: 11-APR-2002 14:01:18.83 linker identification: "A11-50" Overall Image Checksum: 2048500973 o [SYSEXE]CONFIGURE.EXE (new image) Image Identification Information image name: "CONFIGURE" image file identification: "X-7" image file build identification: "X91Y-0060010000" link date/time: 2-DEC-2001 01:53:47.48 linker identification: "A11-50" Overall Image Checksum: 3229994207 Page 4 o [SYSEXE]CONVERT.EXE (new image) Image Identification Information image name: "CONVERT" image file identification: "X-8" image file build identification: "X91Y-0060010008" link date/time: 10-JUN-2002 16:38:38.88 linker identification: "A11-50" Overall Image Checksum: 977659709 o [SYSLIB]CONVSHR.EXE (new image) Image Identification Information image name: "CONVSHR" image file identification: "X1-012" image file build identification: "X91Y-0060010008" link date/time: 10-JUN-2002 16:38:29.93 linker identification: "A11-50" Overall Image Checksum: 417998174 o [SYSEXE]CREATE.EXE (new image) Image Identification Information image name: "CREATE" image file identification: "X-10" image file build identification: "X91Y-0060010016" link date/time: 29-MAY-2002 02:41:59.85 linker identification: "A11-50" Overall Image Checksum: 1821220121 o [SYSEXE]DCE$DCED.EXE (new image) Image Identification Information image name: "DCE$DCED" image file identification: "DCE V3.0-020410" image file build identification: "" link date/time: 11-APR-2002 05:50:01.53 linker identification: "A11-50" Overall Image Checksum: 1643545434 o [SYSLIB]DCE$LIB_SHR.EXE (new image) Image Identification Information image name: "DCE$LIB_SHR" image file identification: "DCE V3.0-020926" image file build identification: "" link date/time: 26-SEP-2002 19:46:38.43 linker identification: "A11-50" Overall Image Checksum: 2121334521 Page 5 o [SYSLIB]DCE$SOCKSHR_IP.EXE (new image) Image Identification Information image name: "DCE$SOCKSHR_IP" image file identification: "DCE V3.0-0060010003" image file build identification: "" link date/time: 11-APR-2002 05:42:30.56 linker identification: "A11-50" Overall Image Checksum: 4046392146 o [SYSEXE]DCL.EXE (new image) Image Identification Information image name: "DCL" image file identification: "X-18" image file build identification: "X91Y-0060010016" link date/time: 11-FEB-2003 14:13:09.53 linker identification: "A11-50" Overall Image Checksum: 748087898 o [SYS$LDR]DDIF$RMS_EXTENSION.EXE (new image) Image Identification Information image name: "DDIF$RMS_EXTENSION" image file identification: "X-3" image file build identification: "X91Y-0060010002" link date/time: 2-DEC-2001 01:45:55.05 linker identification: "A11-50" Overall Image Checksum: 2571139415 o [SYSLIB]DEBUGSHR.EXE (new image) Image Identification Information image name: "DEBUGSHR" image file identification: "V7.3-01R" image file build identification: "X91Y-0060010002" link date/time: 9-APR-2003 14:37:11.57 linker identification: "A11-50" Overall Image Checksum: 1573687623 o [SYSEXE]DEBUG_APB.EXE (new image) Image Identification Information image name: "DEBUG_APB" image file identification: "X-8" image file build identification: "X91Y-0060010002" link date/time: 25-JUL-2002 00:33:49.61 linker identification: "A11-50" Overall Image Checksum: 2623798498 Page 6 o [SYSEXE]DECW$DWT_FONT_DAEMON.EXE (new image) Image Identification Information image name: "DECW$DWT_FONT_DAEMON" image file identification: "V1.1-015" image file build identification: "X91Y-0060010001" link date/time: 10-APR-2002 15:28:06.87 linker identification: "A11-50" Overall Image Checksum: 2773465063 o [SYSLIB]DECW$OPENGLPEERRI.EXE (new image) Image Identification Information image name: "DECW$OPENGLPEERRI" image file identification: "V1.0" image file build identification: "0060010003" link date/time: 26-APR-2002 15:54:29.31 linker identification: "A11-50" Overall Image Checksum: 2014734255 o [SYSLIB]DECW$OPENGLSHR_V11.EXE (new image) Image Identification Information image name: "DECW$OPENGLSHR_V11" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010003" link date/time: 26-APR-2002 14:08:35.94 linker identification: "A11-50" Overall Image Checksum: 175122433 o [SYSLIB]DECW$OPENGLUSHR_V11.EXE (new image) Image Identification Information image name: "DECW$OPENGLUSHR_V11" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010003" link date/time: 26-APR-2002 14:08:55.90 linker identification: "A11-50" Overall Image Checksum: 4202316089 o [SYSLIB]DECW$OPENGLUTSHR.EXE (new image) Image Identification Information image name: "DECW$OPENGLUTSHR" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010003" link date/time: 26-APR-2002 14:09:18.61 linker identification: "A11-50" Overall Image Checksum: 2920365815 Page 7 o [SYSLIB]DECW$OPENGLWIDGETSHR_V11.EXE (new image) Image Identification Information image name: "DECW$OPENGLWIDGETSHR_V11" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010003" link date/time: 26-APR-2002 14:09:14.23 linker identification: "A11-50" Overall Image Checksum: 3434109192 o [SYSLIB]DECW$OPENGL_PROTOCOL_V11.EXE (new image) Image Identification Information image name: "DECW$OPENGL_PROTOCOL_V11" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010003" link date/time: 26-APR-2002 14:08:39.57 linker identification: "A11-50" Overall Image Checksum: 700711074 o [SYSLIB]DECW$SERVER_DDX_GB.EXE (new image) Image Identification Information image name: "DECW$SERVER_DDX_GB" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010002" link date/time: 26-APR-2002 15:53:31.59 linker identification: "A11-50" Overall Image Checksum: 1609608708 o [SYSLIB]DECW$SERVER_DDX_GZ.EXE (new image) Image Identification Information image name: "DECW$SERVER_DDX_GZ" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010002" link date/time: 26-APR-2002 14:03:24.04 linker identification: "A11-50" Overall Image Checksum: 2627762684 o [SYSLIB]DECW$SERVER_DDX_P2.EXE (new image) Image Identification Information image name: "DECW$SERVER_DDX_P2" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010001" link date/time: 26-APR-2002 14:03:22.34 linker identification: "A11-50" Overall Image Checksum: 3207650232 Page 8 o [SYSLIB]DECW$SERVER_DDX_P3.EXE (new image) Image Identification Information image name: "DECW$SERVER_DDX_P3" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010001" link date/time: 26-APR-2002 14:03:25.72 linker identification: "A11-50" Overall Image Checksum: 3733979569 o [SYSLIB]DECW$SERVER_DIX.EXE (new image) Image Identification Information image name: "DECW$SERVER_DIX" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010001" link date/time: 26-APR-2002 13:39:14.22 linker identification: "A11-50" Overall Image Checksum: 958771402 o [SYSLIB]DECW$SERVER_RIDDGL.EXE (new image) Image Identification Information image name: "DECW$SERVER_RIDDGL" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010002" link date/time: 26-APR-2002 15:54:09.00 linker identification: "A11-50" Overall Image Checksum: 1269402964 o [SYSEXE]DECW$SETSHODIS.EXE (new image) Image Identification Information image name: "DECW$SETSHODIS" image file identification: "DW V7.3-020507" image file build identification: "X91Y-0060010001" link date/time: 7-MAY-2002 08:34:35.33 linker identification: "A11-50" Overall Image Checksum: 1479532716 o [SYSLIB]DECW$SVEXT_DEC_PEER_GLX.EXE (new image) Image Identification Information image name: "DECW$SVEXT_DEC_PEER_GLX" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010002" link date/time: 26-APR-2002 15:54:47.71 linker identification: "A11-50" Overall Image Checksum: 597273345 Page 9 o [SYSLIB]DECW$SVEXT_GLX_P350.EXE (new image) Image Identification Information image name: "DECW$SVEXT_GLX_P350" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010001" link date/time: 26-APR-2002 13:43:59.85 linker identification: "A11-50" Overall Image Checksum: 494920341 o [SYSLIB]DECW$TRANSPORT_COMMON.EXE (new image) Image Identification Information image name: "DECW$TRANSPORT_COMMON" image file identification: "DW V7.3-020507" image file build identification: "X91Y-0060010003" link date/time: 7-MAY-2002 08:33:49.23 linker identification: "A11-50" Overall Image Checksum: 168829087 o [SYSLIB]DECW$TRANSPORT_DECNET.EXE (new image) Image Identification Information image name: "DECW$TRANSPORT_DECNET" image file identification: "DW V7.3-020507" image file build identification: "X91Y-0060010003" link date/time: 7-MAY-2002 08:34:01.95 linker identification: "A11-50" Overall Image Checksum: 1466157999 o [SYSLIB]DECW$TRANSPORT_LAT.EXE (new image) Image Identification Information image name: "DECW$TRANSPORT_LAT" image file identification: "DW X1.5-930406" image file build identification: "X91Y-0060010000" link date/time: 31-JUL-2001 05:43:11.43 linker identification: "A11-50" Overall Image Checksum: 2794535021 o [SYSLIB]DECW$TRANSPORT_LOCAL.EXE (new image) Image Identification Information image name: "DECW$TRANSPORT_LOCAL" image file identification: "DW V7.3-020507" image file build identification: "X91Y-0060010003" link date/time: 7-MAY-2002 08:34:13.55 linker identification: "A11-50" Overall Image Checksum: 3061270449 Page 10 o [SYSLIB]DECW$TRANSPORT_TCPIP.EXE (new image) Image Identification Information image name: "DECW$TRANSPORT_TCPIP" image file identification: "DW V7.3-020507" image file build identification: "X91Y-0060010003" link date/time: 7-MAY-2002 08:34:14.40 linker identification: "A11-50" Overall Image Checksum: 138712639 o [SYSEXE]DELETE.EXE (new image) Image Identification Information image name: "DELETE" image file identification: "X-05" image file build identification: "X91Y-0060010000" link date/time: 16-OCT-2001 01:54:28.08 linker identification: "A11-50" Overall Image Checksum: 677373511 o [SYSEXE]DIRECTORY.EXE (new image) Image Identification Information image name: "DIRECTORY" image file identification: "A10-02" image file build identification: "X91Y-0060010002" link date/time: 15-JUL-2002 16:07:49.68 linker identification: "A11-50" Overall Image Checksum: 3418066618 o [SYS$LDR]EXCEPTION.EXE (new image) Image Identification Information image name: "EXCEPTION" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:51:32.40 linker identification: "A11-50" Overall Image Checksum: 646856264 o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information image name: "EXCEPTION_MON" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:52:16.97 linker identification: "A11-50" Overall Image Checksum: 1697767069 Page 11 o [SYS$LDR]EXEC_INIT.EXE (new image) Image Identification Information image name: "EXEC_INIT" image file identification: "X-8" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:53:22.44 linker identification: "A11-50" Overall Image Checksum: 1503233689 o [SYS$LDR]F11BXQP.EXE (new image) Image Identification Information image name: "F11BXQP" image file identification: "XQP V7.3R-0002" image file build identification: "X9UH-0060010013" link date/time: 4-SEP-2003 21:13:53.81 linker identification: "A11-50" Overall Image Checksum: 31749393 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-0060010045" link date/time: 27-OCT-2003 13:10:13.96 linker identification: "A11-50" Overall Image Checksum: 2300613778 o [SYSLIB]FC$SDA.EXE (new image) Image Identification Information image name: "FC$SDA" image file identification: "X-12A3" image file build identification: "X9UH-0060010045" link date/time: 27-OCT-2003 13:10:15.72 linker identification: "A11-50" Overall Image Checksum: 2737892680 o [SYS$LDR]IMAGE_MANAGEMENT.EXE (new image) Image Identification Information image name: "IMAGE_MANAGEMENT" image file identification: "X-7" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:54:00.01 linker identification: "A11-50" Overall Image Checksum: 753908056 Page 12 o [SYSLIB]IMGDMP.EXE (new image) Image Identification Information image name: "IMGDMP" image file identification: "X-11A1" image file build identification: "X91Y-0060010000" link date/time: 20-OCT-2001 06:06:23.85 linker identification: "A11-50" Overall Image Checksum: 3813432078 o [SYSLIB]INIT$SHR.EXE (new image) Image Identification Information image name: "INIT$SHR" image file identification: "V1.0" image file build identification: "X91Y-0060010000" link date/time: 4-JAN-2002 06:28:49.19 linker identification: "A11-50" Overall Image Checksum: 792549192 o [SYSEXE]INIT.EXE (new image) Image Identification Information image name: "INIT" image file identification: "X-15" image file build identification: "X91Y-0060010000" link date/time: 4-JAN-2002 06:39:17.73 linker identification: "A11-50" Overall Image Checksum: 1384204664 o [SYSEXE]INSTALL.EXE (new image) Image Identification Information image name: "INSTALL" image file identification: "X-26" image file build identification: "X91Y-0060010002" link date/time: 10-JUN-2002 16:38:41.26 linker identification: "A11-50" Overall Image Checksum: 1866724319 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 13 o [SYSLIB]IOGEN$SHARE.EXE (new image) Image Identification Information image name: "IOGEN$SHARE" image file identification: "X-24" image file build identification: "X91Y-0060010003" link date/time: 14-MAY-2002 06:53:16.29 linker identification: "A11-50" Overall Image Checksum: 1471326447 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information image name: "IO_ROUTINES" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:54:50.94 linker identification: "A11-50" Overall Image Checksum: 2224814366 o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) Image Identification Information image name: "IO_ROUTINES_MON" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:56:10.96 linker identification: "A11-50" Overall Image Checksum: 952697098 o [SYSEXE]JBC$JOB_CONTROL.EXE (new image) Image Identification Information image name: "JBC$JOB_CONTROL" image file identification: "X-27" image file build identification: "X91Y-0060010001" link date/time: 19-DEC-2002 16:38:42.04 linker identification: "A11-50" Overall Image Checksum: 1540996535 o [SYSLIB]LIBRTL.EXE (new image) Image Identification Information image name: "LIBRTL" image file identification: "X01-001" image file build identification: "X9UH-0060010010" link date/time: 3-OCT-2003 01:44:00.69 linker identification: "A11-50" Overall Image Checksum: 1625525882 Page 14 o [SYSLIB]LIBRTL_INSTRUMENTED.EXE (new image) Image Identification Information image name: "LIBRTL_INSTRUMENTED" image file identification: "X01-001" image file build identification: "X9UH-0060010010" link date/time: 3-OCT-2003 01:56:07.85 linker identification: "A11-50" Overall Image Checksum: 3480200403 o [SYSEXE]LINK.EXE (new image) Image Identification Information image name: "LINK" image file identification: "A13-00" image file build identification: "X9UH-0060010010" link date/time: 21-AUG-2003 15:22:30.63 linker identification: "A11-50" Overall Image Checksum: 3237819625 o [SYSEXE]LMCP.EXE (new image) Image Identification Information image name: "LMCP" image file identification: "V1.3-X035-X91Y" image file build identification: "X91Y-0060010002" link date/time: 4-JAN-2002 06:42:45.12 linker identification: "A11-50" Overall Image Checksum: 1765590452 o [SYS$LDR]LOCKING.EXE (new image) Image Identification Information image name: "LOCKING" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:57:37.71 linker identification: "A11-50" Overall Image Checksum: 3151480747 o [SYS$LDR]LOGICAL_NAMES.EXE (new image) Image Identification Information image name: "LOGICAL_NAMES" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:58:08.38 linker identification: "A11-50" Overall Image Checksum: 757708653 Page 15 o [SYSEXE]MAIL.EXE (new image) Image Identification Information image name: "MAIL" image file identification: "V1.06" image file build identification: "X91Y-0060010001" link date/time: 6-JUN-2001 17:29:33.64 linker identification: "A11-50" Overall Image Checksum: 1690719321 o [SYSLIB]MAILSHR.EXE (new image) Image Identification Information image name: "MAILSHR" image file identification: "X-4" image file build identification: "X91Y-0060010001" link date/time: 6-JUN-2001 17:29:05.10 linker identification: "A11-50" Overall Image Checksum: 1279149775 o [SYSLIB]MAILSHRP.EXE (new image) Image Identification Information image name: "MAILSHRP" image file identification: "X-4" image file build identification: "X91Y-0060010001" link date/time: 6-JUN-2001 17:29:11.15 linker identification: "A11-50" Overall Image Checksum: 1963234510 o [SYSEXE]MAIL_SERVER.EXE (new image) Image Identification Information image name: "MAIL_SERVER" image file identification: "X-11" image file build identification: "X91Y-0060010001" link date/time: 6-JUN-2001 17:29:56.59 linker identification: "A11-50" Overall Image Checksum: 2189798432 o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) Image Identification Information image name: "MESSAGE_ROUTINES" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:51:06.24 linker identification: "A11-50" Overall Image Checksum: 2019097029 Page 16 o [SYSEXE]MIME.EXE (new image) Image Identification Information image name: "MIME" image file identification: "V1.7" image file build identification: "0060010001" link date/time: 29-MAY-2002 02:03:24.52 linker identification: "A11-50" Overall Image Checksum: 273220078 o [SYSLIB]MONTORSHR.EXE (new image) Image Identification Information image name: "MONTORSHR" image file identification: "V2.0" image file build identification: "X91Y-0060010000" link date/time: 19-MAR-2002 23:31:16.60 linker identification: "A11-50" Overall Image Checksum: 702723265 o [SYSLIB]MOUNTSHR.EXE (new image) Image Identification Information image name: "MOUNTSHR" image file identification: "V1.0" image file build identification: "X91Y-0060010004" link date/time: 10-SEP-2001 12:02:05.00 linker identification: "A11-50" Overall Image Checksum: 2123544474 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-0060010045" link date/time: 27-OCT-2003 13:10:17.09 linker identification: "A11-50" Overall Image Checksum: 1827767317 o [SYS$LDR]MULTIPATH.EXE (new image) Image Identification Information image name: "MULTIPATH" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:58:22.92 linker identification: "A11-50" Overall Image Checksum: 3167939357 Page 17 o [SYS$LDR]MULTIPATH_MON.EXE (new image) Image Identification Information image name: "MULTIPATH_MON" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:58:38.49 linker identification: "A11-50" Overall Image Checksum: 2330454914 o [SYSEXE]NETACP.EXE (new image) Image Identification Information image name: "NETACP" image file identification: "X-18" image file build identification: "X9UH-0060010000" link date/time: 22-OCT-2003 13:05:00.23 linker identification: "A11-50" Overall Image Checksum: 284795048 o [SYS$LDR]NETDRIVER.EXE (new image) Image Identification Information image name: "SYS$NETDRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010000" link date/time: 22-OCT-2003 13:05:02.96 linker identification: "A11-50" Overall Image Checksum: 1572898447 o [SYS$LDR]NET$CSMACD.EXE (new image) Image Identification Information image name: "NET$CSMACD" image file identification: "X-17" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 07:59:54.60 linker identification: "A11-50" Overall Image Checksum: 1883462454 o [SYS$LDR]NET$FDDI.EXE (new image) Image Identification Information image name: "NET$FDDI" image file identification: "X-17" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 07:59:55.44 linker identification: "A11-50" Overall Image Checksum: 2360687297 Page 18 o [SYSEXE]PPPD$UTIL.EXE (new image) Image Identification Information image name: "PPPD$UTIL" image file identification: "X-19" image file build identification: "X91Y-0060010001" link date/time: 25-JUL-2002 00:34:06.87 linker identification: "A11-50" Overall Image Checksum: 466436358 o [SYSMSG]PRGDEVMSG.EXE (new image) Image Identification Information image name: "PRGDEVMSG" image file identification: "X-1K2" image file build identification: "X91Y-0060010000" link date/time: 24-AUG-2001 00:03:34.18 linker identification: "A11-50" Overall Image Checksum: 3984871636 o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:52:18.21 linker identification: "A11-50" Overall Image Checksum: 1537621575 o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT_MON" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:54:51.47 linker identification: "A11-50" Overall Image Checksum: 3778905531 o [SYSLIB]PTHREAD$DBGSHR.EXE (new image) Image Identification Information image name: "PTHREAD$DBGSHR" image file identification: "V3.17-034" image file build identification: "X91Y-0060010007" link date/time: 25-JUL-2002 00:18:47.51 linker identification: "A11-50" Overall Image Checksum: 3898285378 Page 19 o [SYSLIB]PTHREAD$RTL.EXE (new image) Image Identification Information image name: "PTHREAD$RTL" image file identification: "V3.17-034" image file build identification: "X91Y-0060010007" link date/time: 25-JUL-2002 00:18:00.51 linker identification: "A11-50" Overall Image Checksum: 1622283044 o [SYSEXE]QUEMAN.EXE (new image) Image Identification Information image name: "QUEMAN" image file identification: "X-15" image file build identification: "X91Y-0060010016" link date/time: 29-MAY-2002 02:41:52.50 linker identification: "A11-50" Overall Image Checksum: 2795291529 o [SYSEXE]RECLAIM.EXE (new image) Image Identification Information image name: "RECLAIM" image file identification: "X-6" image file build identification: "X91Y-0060010008" link date/time: 10-JUN-2002 16:38:41.66 linker identification: "A11-50" Overall Image Checksum: 1206693227 o [SYSEXE]REG$CP.EXE (new image) Image Identification Information image name: "REG$CP" image file identification: "X-2" image file build identification: "X91Y-0060010004" link date/time: 25-JUL-2002 00:28:22.71 linker identification: "A11-50" Overall Image Checksum: 2058476774 o [SYSEXE]REGISTRY$SERVER.EXE (new image) Image Identification Information image name: "REGISTRY$SERVER" image file identification: "X-7" image file build identification: "X91Y-0060010004" link date/time: 25-JUL-2002 00:31:56.69 linker identification: "A11-50" Overall Image Checksum: 328623843 Page 20 o [SYSEXE]REMACP.EXE (new image) Image Identification Information image name: "REMACP" image file identification: "X-3" image file build identification: "X91Y-0060010000" link date/time: 19-MAR-2002 23:27:42.85 linker identification: "A11-50" Overall Image Checksum: 2835832676 o [SYS$LDR]RMS.EXE (new image) Image Identification Information image name: "RMS" image file identification: "V1.0" image file build identification: "X91Y-0060010019" link date/time: 12-JUL-2002 07:58:46.08 linker identification: "A11-50" Overall Image Checksum: 4080353699 o [SYSEXE]RTPAD.EXE (new image) Image Identification Information image name: "RTPAD" image file identification: "X-9" image file build identification: "X91Y-0060010000" link date/time: 4-JAN-2002 06:40:22.93 linker identification: "A11-50" Overall Image Checksum: 640334932 o [SYSEXE]SCACP.EXE (new image) Image Identification Information image name: "SCACP" image file identification: "X-13" image file build identification: "X91Y-0060010004" link date/time: 12-FEB-2002 09:21:00.17 linker identification: "A11-50" Overall Image Checksum: 3603509609 o [SYSLIB]SDA$SHARE.EXE (new image) Image Identification Information image name: "SDA$SHARE" image file identification: "X-6B1" image file build identification: "X91Y-0060010020" link date/time: 2-MAY-2003 11:28:02.81 linker identification: "A11-50" Overall Image Checksum: 35770327 Page 21 o [SYSLIB]SDARMS$SHARE.EXE (new image) Image Identification Information image name: "SDARMS$SHARE" image file identification: "X-9" image file build identification: "X91Y-0060010019" link date/time: 12-JUL-2002 07:59:16.43 linker identification: "A11-50" Overall Image Checksum: 857424469 o [SYSLIB]SECURESHR.EXE (new image) Image Identification Information image name: "SECURESHR" image file identification: "X-9" image file build identification: "X91Y-0060010012" link date/time: 19-SEP-2001 11:06:06.85 linker identification: "A11-50" Overall Image Checksum: 2916003487 o [SYSLIB]SECURESHRP.EXE (new image) Image Identification Information image name: "SECURESHRP" image file identification: "7-3" image file build identification: "X91Y-0060010012" link date/time: 19-SEP-2001 11:06:03.37 linker identification: "A11-50" Overall Image Checksum: 2821224889 o [SYS$LDR]SECURITY.EXE (new image) Image Identification Information image name: "SECURITY" image file identification: "X-5" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:56:00.19 linker identification: "A11-50" Overall Image Checksum: 1318990505 o [SYS$LDR]SECURITY_MON.EXE (new image) Image Identification Information image name: "SECURITY_MON" image file identification: "X-5" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:56:22.49 linker identification: "A11-50" Overall Image Checksum: 1624999083 Page 22 o [SYSEXE]SET.EXE (new image) Image Identification Information image name: "SET" image file identification: "X01-13" image file build identification: "X91Y-0060010016" link date/time: 29-MAY-2002 02:42:09.08 linker identification: "A11-50" Overall Image Checksum: 295326790 o [SYSEXE]SHADOW_SERVER.EXE (new image) Image Identification Information image name: "SHADOW_SERVER" image file identification: "X-13" image file build identification: "X9UH-0060010021" link date/time: 4-AUG-2003 15:22:15.04 linker identification: "A11-50" Overall Image Checksum: 3371117791 o [SYS$LDR]SHELL8K.EXE (new image) Image Identification Information image name: "SHELL8K" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:57:28.40 linker identification: "A11-50" Overall Image Checksum: 1818027498 o [SYSEXE]SHOW.EXE (new image) Image Identification Information image name: "SHOW" image file identification: "X-9" image file build identification: "X91Y-0060010016" link date/time: 29-MAY-2002 02:41:43.97 linker identification: "A11-50" Overall Image Checksum: 985508605 o [SYSEXE]SHWCLSTR.EXE (new image) Image Identification Information image name: "SHWCLSTR" image file identification: "X-22" image file build identification: "X91Y-0060010016" link date/time: 29-MAY-2002 02:42:07.51 linker identification: "A11-50" Overall Image Checksum: 1846896915 Page 23 o [SYSLIB]SMI$OBJSHR.EXE (new image) Image Identification Information image name: "SMI$OBJSHR" image file identification: "X40-A8" image file build identification: "X9UH-0060010014" link date/time: 12-AUG-2003 10:43:22.31 linker identification: "A11-50" Overall Image Checksum: 2180729159 o [SYSEXE]SMISERVER.EXE (new image) Image Identification Information image name: "SMISERVER" image file identification: "X01-15" image file build identification: "X91Y-0060010006" link date/time: 14-MAY-2002 07:12:19.03 linker identification: "A11-50" Overall Image Checksum: 2594662985 o [SYSLIB]SPISHR.EXE (new image) Image Identification Information image name: "SPISHR" image file identification: "ALPHA X91Y-K5L" image file build identification: "X91Y-0060010000" link date/time: 19-MAR-2002 23:28:27.64 linker identification: "A11-50" Overall Image Checksum: 1943569251 o [SYSEXE]STACONFIG.EXE (new image) Image Identification Information image name: "STACONFIG" image file identification: "X-39" image file build identification: "X91Y-0060010000" link date/time: 2-DEC-2001 01:55:14.07 linker identification: "A11-50" Overall Image Checksum: 4127314954 o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) Image Identification Information image name: "SYS$BASE_IMAGE" image file identification: "ALPHA X91Y-K5L" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:50:17.95 linker identification: "A11-50" Overall Image Checksum: 1607307837 Page 24 o [SYS$LDR]SYS$CLUSTER.EXE (new image) Image Identification Information image name: "SYS$CLUSTER" image file identification: "X-3" image file build identification: "X91Y-0060010012" link date/time: 4-NOV-2002 16:35:36.67 linker identification: "A11-50" Overall Image Checksum: 922157356 o [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE (new image) Image Identification Information image name: "SYS$CPU_ROUTINES_2308" image file identification: "X-1" image file build identification: "X91Y-0060010004" link date/time: 6-SEP-2002 13:16:16.09 linker identification: "A11-50" Overall Image Checksum: 2460679146 o [SYS$LDR]SYS$CPU_ROUTINES_2608.EXE (new image) Image Identification Information image name: "SYS$CPU_ROUTINES_2608" image file identification: "X-1" image file build identification: "0060010000" link date/time: 9-MAY-2001 01:16:29.54 linker identification: "A11-50" Overall Image Checksum: 279173938 o [SYSEXE]SYS$DAYLIGHT_SAVING.EXE (new image) Image Identification Information image name: "SYS$DAYLIGHT_SAVING" image file identification: "TDF V1.0-0" image file build identification: "0060010002" link date/time: 6-DEC-2002 15:42:14.82 linker identification: "A11-50" Overall Image Checksum: 2687838548 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-0060010045" link date/time: 27-OCT-2003 13:09:05.94 linker identification: "A11-50" Overall Image Checksum: 2983306991 Page 25 o [SYS$LDR]SYS$DQDRIVER.EXE (new image) Image Identification Information image name: "SYS$DQDRIVER" image file identification: "X-26A1" image file build identification: "X91Y-0060010004" link date/time: 2-DEC-2001 02:15:47.13 linker identification: "A11-50" Overall Image Checksum: 2559917328 o [SYS$LDR]SYS$DUDRIVER.EXE (new image) Image Identification Information image name: "SYS$DUDRIVER" image file identification: "X-3" image file build identification: "X91Y-0060010008" link date/time: 28-JUN-2002 08:39:15.58 linker identification: "A11-50" Overall Image Checksum: 3699066891 o [SYS$LDR]SYS$DVDRIVER.EXE (new image) Image Identification Information image name: "SYS$DVDRIVER" image file identification: "X-3" image file build identification: "X91Y-0060010000" link date/time: 20-JUN-2001 12:24:01.22 linker identification: "A11-50" Overall Image Checksum: 3622049348 o [SYS$LDR]SYS$EBDRIVER.EXE (new image) Image Identification Information image name: "SYS$EBDRIVER" image file identification: "X-12" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 08:00:15.30 linker identification: "A11-50" Overall Image Checksum: 2193241038 o [SYS$LDR]SYS$ECDRIVER.EXE (new image) Image Identification Information image name: "SYS$ECDRIVER" image file identification: "X-3" image file build identification: "X91Y-0060010005" link date/time: 19-SEP-2001 11:10:32.30 linker identification: "A11-50" Overall Image Checksum: 1994141470 Page 26 o [SYS$LDR]SYS$EIBTDRIVER.EXE (new image) Image Identification Information image name: "SYS$EIBTDRIVER" image file identification: "X-1" image file build identification: "X91Y-0060010004" link date/time: 28-JUN-2002 08:39:11.12 linker identification: "A11-50" Overall Image Checksum: 638682849 o [SYS$LDR]SYS$EIDRIVER.EXE (new image) Image Identification Information image name: "SYS$EIDRIVER" image file identification: "X-25" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 08:00:17.40 linker identification: "A11-50" Overall Image Checksum: 4040503856 o [SYS$LDR]SYS$ERBTDRIVER.EXE (new image) Image Identification Information image name: "SYS$ERBTDRIVER" image file identification: "X-4" image file build identification: "X91Y-0060010004" link date/time: 28-JUN-2002 08:39:35.63 linker identification: "A11-50" Overall Image Checksum: 2277817899 o [SYS$LDR]SYS$ERDRIVER.EXE (new image) Image Identification Information image name: "SYS$ERDRIVER" image file identification: "X-3" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 07:59:11.76 linker identification: "A11-50" Overall Image Checksum: 3016377382 o [SYS$LDR]SYS$ESDRIVER.EXE (new image) Image Identification Information image name: "SYS$ESDRIVER" image file identification: "X-3" image file build identification: "X91Y-0060010005" link date/time: 19-SEP-2001 11:12:26.13 linker identification: "A11-50" Overall Image Checksum: 2442339750 Page 27 o [SYS$LDR]SYS$EW1000A.EXE (new image) Image Identification Information image name: "SYS$EW1000A" image file identification: "X-31" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 08:00:12.85 linker identification: "A11-50" Overall Image Checksum: 4281057669 o [SYS$LDR]SYS$EWBTDRIVER.EXE (new image) Image Identification Information image name: "SYS$EWBTDRIVER" image file identification: "X-4" image file build identification: "X91Y-0060010004" link date/time: 28-JUN-2002 08:39:43.47 linker identification: "A11-50" Overall Image Checksum: 3833398203 o [SYS$LDR]SYS$EWDRIVER.EXE (new image) Image Identification Information image name: "SYS$EWDRIVER" image file identification: "X-3" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 07:59:19.58 linker identification: "A11-50" Overall Image Checksum: 4252214140 o [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image) Image Identification Information image name: "SYS$DE500BADRIVER" image file identification: "X-3" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 07:59:23.29 linker identification: "A11-50" Overall Image Checksum: 4205920813 o [SYS$LDR]SYS$FGEDRIVER.EXE (new image) Image Identification Information image name: "SYS$FGEDRIVER" image file identification: "X-55A10" image file build identification: "X9UH-0060010045" link date/time: 27-OCT-2003 13:10:04.52 linker identification: "A11-50" Overall Image Checksum: 1611378418 Page 28 o [SYS$LDR]SYS$FWBTDRIVER.EXE (new image) Image Identification Information image name: "SYS$FWBTDRIVER" image file identification: "X-1" image file build identification: "X91Y-0060010002" link date/time: 10-SEP-2001 12:03:38.47 linker identification: "A11-50" Overall Image Checksum: 558326001 o [SYS$LDR]SYS$FWDRIVER.EXE (new image) Image Identification Information image name: "SYS$FWDRIVER" image file identification: "X-3" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 07:59:39.72 linker identification: "A11-50" Overall Image Checksum: 1313914530 o [SYS$LDR]SYS$GFDRIVER.EXE (new image) Image Identification Information image name: "SYS$GFDRIVER" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010001" link date/time: 26-APR-2002 13:43:45.62 linker identification: "A11-50" Overall Image Checksum: 320190739 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-0060010045" link date/time: 27-OCT-2003 13:09:18.75 linker identification: "A11-50" Overall Image Checksum: 524387284 o [SYS$LDR]SYS$GYCDRIVER.EXE (new image) Image Identification Information image name: "SYS$GYCDRIVER" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010001" link date/time: 26-APR-2002 13:44:34.19 linker identification: "A11-50" Overall Image Checksum: 2934841390 Page 29 o [SYS$LDR]SYS$GZDRIVER.EXE (new image) Image Identification Information image name: "SYS$GZDRIVER" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010001" link date/time: 26-APR-2002 13:46:07.94 linker identification: "A11-50" Overall Image Checksum: 1592517167 o [SYS$LDR]SYS$GZVDRIVER.EXE (new image) Image Identification Information image name: "SYS$GZVDRIVER" image file identification: "DW V7.3-020426" image file build identification: "X91Y-0060010001" link date/time: 26-APR-2002 13:46:12.80 linker identification: "A11-50" Overall Image Checksum: 472428166 o [SYS$LDR]SYS$IIDRIVER.EXE (new image) Image Identification Information image name: "SYS$IIDRIVER" image file identification: "X-3" image file build identification: "X91Y-0060010000" link date/time: 6-DEC-2002 15:42:14.92 linker identification: "A11-50" Overall Image Checksum: 1152349440 o [SYS$LDR]SYS$IPC_SERVICES.EXE (new image) Image Identification Information image name: "SYS$IPC_SERVICES" image file identification: "V1.3-X03E-X9UH" image file build identification: "X9UH-0060010010" link date/time: 21-AUG-2003 15:22:39.31 linker identification: "A11-50" Overall Image Checksum: 609242701 o [SYS$LDR]SYS$LAN.EXE (new image) Image Identification Information image name: "SYS$LAN" image file identification: "X-3" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 07:58:33.27 linker identification: "A11-50" Overall Image Checksum: 2518434589 Page 30 o [SYS$LDR]SYS$LAN_ATM.EXE (new image) Image Identification Information image name: "SYS$LAN_ATM" image file identification: "X-28" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 07:58:42.85 linker identification: "A11-50" Overall Image Checksum: 398035977 o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image) Image Identification Information image name: "SYS$LAN_CSMACD" image file identification: "X-3" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 07:58:37.93 linker identification: "A11-50" Overall Image Checksum: 2940566715 o [SYS$LDR]SYS$LAN_FDDI.EXE (new image) Image Identification Information image name: "SYS$LAN_FDDI" image file identification: "X-3" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 07:58:52.04 linker identification: "A11-50" Overall Image Checksum: 195370383 o [SYS$LDR]SYS$LAN_TR.EXE (new image) Image Identification Information image name: "SYS$LAN_TR" image file identification: "X-3" image file build identification: "X91Y-0060010010" link date/time: 12-JUL-2002 07:58:55.63 linker identification: "A11-50" Overall Image Checksum: 955540170 o [SYS$LDR]SYS$MCDRIVER.EXE (new image) Image Identification Information image name: "SYS$MCDRIVER" image file identification: "X-59" image file build identification: "X91Y-0060010000" link date/time: 14-MAY-2002 07:04:33.89 linker identification: "A11-50" Overall Image Checksum: 150903747 Page 31 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-0060010045" link date/time: 27-OCT-2003 13:09:13.35 linker identification: "A11-50" Overall Image Checksum: 128458752 o [SYS$LDR]SYS$NTA.EXE (new image) Image Identification Information image name: "SYS$NTA" image file identification: "X-1" image file build identification: "X91Y-0060010001" link date/time: 5-FEB-2002 14:27:46.10 linker identification: "A11-50" Overall Image Checksum: 174685084 o [SYS$LDR]SYS$PBDRIVER.EXE (new image) Image Identification Information image name: "SYS$PBDRIVER" image file identification: "X-28" image file build identification: "X91Y-0060010008" link date/time: 28-JUN-2002 08:39:18.77 linker identification: "A11-50" Overall Image Checksum: 652682089 o [SYS$LDR]SYS$PEDRIVER.EXE (new image) Image Identification Information image name: "SYS$PEDRIVER" image file identification: "X-3" image file build identification: "X91Y-0060010008" link date/time: 28-JUN-2002 08:41:18.19 linker identification: "A11-50" Overall Image Checksum: 1965197194 o [SYS$LDR]SYS$PEDRIVER_MON.EXE (new image) Image Identification Information image name: "SYS$PEDRIVER_MON" image file identification: "X-3" image file build identification: "X91Y-0060010008" link date/time: 28-JUN-2002 08:41:48.43 linker identification: "A11-50" Overall Image Checksum: 427313907 Page 32 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-0060010045" link date/time: 27-OCT-2003 13:10:00.31 linker identification: "A11-50" Overall Image Checksum: 2474049801 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-0060010045" link date/time: 27-OCT-2003 13:09:54.40 linker identification: "A11-50" Overall Image Checksum: 599400494 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-0060010045" link date/time: 27-OCT-2003 13:09:45.68 linker identification: "A11-50" Overall Image Checksum: 2657583703 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-0060010045" link date/time: 27-OCT-2003 13:09:33.74 linker identification: "A11-50" Overall Image Checksum: 2306903856 o [SYS$LDR]SYS$PKWDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKWDRIVER" image file identification: "X-28" image file build identification: "X9UH-0060010045" link date/time: 27-OCT-2003 13:09:50.01 linker identification: "A11-50" Overall Image Checksum: 229263718 Page 33 o [SYS$LDR]SYS$PMDRIVER.EXE (new image) Image Identification Information image name: "SYS$PMDRIVER" image file identification: "X-31" image file build identification: "X91Y-0060010010" link date/time: 12-MAY-2003 15:51:28.65 linker identification: "A11-50" Overall Image Checksum: 3861444456 o [SYS$LDR]SYS$PPPDRIVER.EXE (new image) Image Identification Information image name: "SYS$PPPDRIVER" image file identification: "V1.0" image file build identification: "X91Y-0060010001" link date/time: 25-JUL-2002 00:31:40.77 linker identification: "A11-50" Overall Image Checksum: 68041550 o [SYS$LDR]SYS$SHDRIVER.EXE (new image) Image Identification Information image name: "SYS$SHDRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010021" link date/time: 4-AUG-2003 15:22:27.66 linker identification: "A11-50" Overall Image Checksum: 809706559 o [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE (new image) Image Identification Information image name: "SYS$TRANSACTION_SERVICES" image file identification: "V1.3-X035-X91Y" image file build identification: "X91Y-0060010001" link date/time: 21-SEP-2001 09:40:05.37 linker identification: "A11-50" Overall Image Checksum: 651396111 o [SYS$LDR]SYS$TUDRIVER.EXE (new image) Image Identification Information image name: "SYS$TUDRIVER" image file identification: "X-3" image file build identification: "X91Y-0060010008" link date/time: 28-JUN-2002 08:46:05.09 linker identification: "A11-50" Overall Image Checksum: 2500024329 Page 34 o [SYS$LDR]SYS$VCC.EXE (new image) Image Identification Information image name: "SYS$VCC" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:58:29.07 linker identification: "A11-50" Overall Image Checksum: 1497489579 o [SYS$LDR]SYS$VCC_MON.EXE (new image) Image Identification Information image name: "SYS$VCC_MON" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:58:40.41 linker identification: "A11-50" Overall Image Checksum: 1098820704 o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information image name: "SYS$VM" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:58:18.45 linker identification: "A11-50" Overall Image Checksum: 2582580750 o [SYS$LDR]SYS$XFCACHE.EXE (new image) Image Identification Information image name: "SYS$XFCACHE" image file identification: "V1.0" image file build identification: "X91Y-0060010009" link date/time: 7-MAR-2003 15:29:50.83 linker identification: "A11-50" Overall Image Checksum: 3118376262 o [SYS$LDR]SYS$XFCACHE_MON.EXE (new image) Image Identification Information image name: "SYS$XFCACHE_MON" image file identification: "V1.0" image file build identification: "X91Y-0060010009" link date/time: 7-MAR-2003 15:30:50.01 linker identification: "A11-50" Overall Image Checksum: 1253053662 Page 35 o [SYSEXE]SYSGEN.EXE (new image) Image Identification Information image name: "SYSGEN" image file identification: "X-3" image file build identification: "X91Y-0060010001" link date/time: 28-JUN-2001 02:30:26.79 linker identification: "A11-50" Overall Image Checksum: 2943455964 o [SYS$LDR]SYSGETSYI.EXE (new image) Image Identification Information image name: "SYSGETSYI" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:50:59.95 linker identification: "A11-50" Overall Image Checksum: 87736742 o [SYSEXE]SYSINIT.EXE (new image) Image Identification Information image name: "SYSINIT" image file identification: "X-96" image file build identification: "X91Y-0060010001" link date/time: 2-DEC-2001 01:47:33.82 linker identification: "A11-50" Overall Image Checksum: 3179881459 o [SYS$LDR]SYSLDR_DYN.EXE (new image) Image Identification Information image name: "SYSLDR_DYN" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:51:27.36 linker identification: "A11-50" Overall Image Checksum: 3721416165 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:54:40.14 linker identification: "A11-50" Overall Image Checksum: 4272844087 Page 36 o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES_MIN" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:52:43.45 linker identification: "A11-50" Overall Image Checksum: 2030065290 o [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE (new image) Image Identification Information image name: "SYSTEM_SYNCHRONIZATION" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:57:15.73 linker identification: "A11-50" Overall Image Checksum: 3175624212 o [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE (new image) Image Identification Information image name: "SYSTEM_SYNCHRONIZATION_MIN" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:57:38.89 linker identification: "A11-50" Overall Image Checksum: 1136225464 o [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.EXE (new image) Image Identification Information image name: "SYSTEM_SYNCHRONIZATION_UNI" image file identification: "X-3" image file build identification: "X91Y-0060010054" link date/time: 12-MAY-2003 15:58:00.00 linker identification: "A11-50" Overall Image Checksum: 1691276207 o [SYSEXE]TDF$SET_TIMEZONE.EXE (new image) Image Identification Information image name: "TDF$SET_TIMEZONE" image file identification: "TDF V1.0-0" image file build identification: "0060010002" link date/time: 6-DEC-2002 15:42:21.61 linker identification: "A11-50" Overall Image Checksum: 2457749054 Page 37 o [SYS$LDR]TMSCP.EXE (new image) Image Identification Information image name: "TMSCP" image file identification: "X-3" image file build identification: "X91Y-0060010002" link date/time: 19-FEB-2002 08:35:40.83 linker identification: "A11-50" Overall Image Checksum: 2938325371 o [SYSEXE]TPSERV.EXE (new image) Image Identification Information image name: "TPSERV" image file identification: "V1.3-X035-X91Y" image file build identification: "X91Y-0060010001" link date/time: 21-SEP-2001 09:40:17.54 linker identification: "A11-50" Overall Image Checksum: 415400183 o [SYSEXE]VMOUNT.EXE (new image) Image Identification Information image name: "VMOUNT" image file identification: "X-10" image file build identification: "X91Y-0060010004" link date/time: 10-SEP-2001 12:02:46.52 linker identification: "A11-50" Overall Image Checksum: 1783017413 o [SYSEXE]VPM.EXE (new image) Image Identification Information image name: "VPM" image file identification: "X-5" image file build identification: "X91Y-0060010000" link date/time: 19-MAR-2002 23:32:24.46 linker identification: "A11-50" Overall Image Checksum: 2547940954 o [SYSEXE]VPM_SERVER.EXE (new image) Image Identification Information image name: "VPM_SERVER" image file identification: "V1.0" image file build identification: "X91Y-0060010000" link date/time: 19-MAR-2002 23:33:41.44 linker identification: "A11-50" Overall Image Checksum: 2926046313 Page 38 o [SYSLIB]XFC$SDA.EXE (new image) Image Identification Information image name: "XFC$SDA" image file identification: "V1.0" image file build identification: "X91Y-0060010009" link date/time: 7-MAR-2003 15:31:47.50 linker identification: "A11-50" Overall Image Checksum: 3518494027 o [SYSHLP]SYSBOOT.EXE (new image) o [SYSLIB]BACKUP.CLD (new file) o [SYSEXE]COPY.CLD (new file) o [SYSLIB]DAYLIGHT_SAVINGS.COM (new file) o [SYSEXE]DCE$RPC_STARTUP.COM (new file) o [SYS$LDR]DIRECTORY.CLD (new file) o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXCEPTION_MON.STB (new file) o [SYS$LDR]EXEC_INIT.STB (new file) o [SYSHLP.UNSUPPORTED]F11BXQP.STB (new file) o [SYS$LDR]FC$GLOBALS.STB (new file) o [SYS$LDR]IMAGE_MANAGEMENT.STB (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB (new file) o [SYS$LDR]IPCDEF.STB (new file) o [SYS$LDR]LOCKING.STB (new file) o [SYS$LDR]LOGICAL_NAMES.STB (new file) o [SYS$LDR]MESSAGE_ROUTINES.STB (new file) o [SYS$LDR]MIME$HELP.HLB (new file) o [SYS$LDR]MULTIPATH.STB (new file) o [SYS$LDR]MULTIPATH_MON.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) Page 39 o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) o [SYS$LDR]RMSDEF.STB (new file) o [SYS$LDR]SECURITY.STB (new file) o [SYS$LDR]SECURITY_MON.STB (new file) o [SYSEXE]SHELL8K.STB (new file) o [SYS$LDR]STARLET.MLB (new file) o [SYS$LDR]SYS$CLUSTER.STB (new file) o [SYS$LDR]SYS$CONFIG.DAT (new file) o [SYS$LDR]SYS$STARLET_C.TLB (new file) o [SYS$LDR]SYS$VCC.STB (new file) o [SYS$LDR]SYS$VCC_MON.STB (new file) o [SYS$LDR]SYS$VM.STB (new file) o [SYS$LDR]SYS$XFCACHE.DSF (new file) o [SYS$LDR]SYS$XFCACHE.STB (new file) o [SYS$LDR]SYSGETSYI.STB (new file) o [SYS$LDR]SYSLDR_DYN.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) o [SYS$LDR]SYSTEM_SYNCHRONIZATION.STB (new file) o [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.STB (new file) o [SYSEXE]SYSTEM_SYNCHRONIZATION_UNI.STB (new file) o [SYSLIB]VMS$INITIAL-050_CONFIGURE.COM (new file) o [SYSUPD]VMSKITBLD.DAT (new file) o [SYSHLP]XFC$SDA.HLB (new file) 6 CONSOLIDATION OF PREVIOUSLY RELEASED V7.3 ECO KITS. The VMS73_UPDATE-V0300 kit is a consolidation of previously released OpenVMS V7.3 ECO kits. The following ECO kits are included: VMS73_AMACRO-V0100 VMS73_APB-V0200 Page 40 VMS73_AUDSRV-V0100 VMS73_BACKUP-V0200 VMS73_CLIUTL-V0200 VMS73_CLUSTER-V0200 VMS73_CPU2308-V0100 VMS73_CPU2608-V0100 VMS73_DDTM-V0100 VMS73_DCL-V0300 VMS73_DEBUG-V0100 VMS73_DECW_XTERM-V0100 VMS73_DELETE-V0100 VMS73_DIR-V0100 VMS73_DRIVER-V0300* VMS73_DTSS-V0100 VMS73_DW_MOT_MUP-V0100 VMS73_F11X-V0200* VMS73_FIBRE_SCSI-V0500 VMS73_GRAPHICS-V0100 VMS73_IIDRIVER-V0100 VMS73_INIT-V0100 VMS73_IOGEN-V0100 VMS73_IPC-V0200* VMS73_LAN-V0400 VMS73_LIBRTL-V0300* VMS73_LINKER-V0400 VMS73_MAIL-V0100 VMS73_MANAGE-V0200 VMS73_MEM_CHAN-V0200* VMS73_MIME-V0100 VMS73_MONTOR-V0100 VMS73_MOUNT96-V0100 VMS73_MSCP-V0100 VMS73_NETACP-V0100* VMS73_PPPD-V0200 VMS73_PTHREAD-V0300 VMS73_REGISTRY-V0100 VMS73_REM-V0100 VMS73_RMS-V0400* VMS73_RPC-V0100 VMS73_RTPAD-V0100 VMS73_SHADOWING-V0300* VMS73_SYS-V0600* VMS73_SYSBOOT-V0100 VMS73_SYSINI-V0100 VMS73_SYSLOA-V0300 VMS73_TDF-V0100 VMS73_UPDATE-V0200 VMS73_XFC-V0300 * = New Kits added to UPDATE kit. Following are descriptions of the new functionality introduced, and problems corrected, in the above kits. Note that the VMS73_UPDATE-V0200 kit description can be found in a separate file, [SYSHLP]VMS73_UPDATE-V0200_CVRLET.TXT. 7 NEW FUNCTIONALITY INCLUDED IN THE VMS73_UPDATE-V0300 KIT 7.1 New functionality introduced the VMS73_FIBRE_SCSI-V0600 kit 7.1.1 Dynamically Update SCSI Disk WWIDs Without a Reboot 7.1.1.1 Functionality Description When a disk is mounted, the WWID for the disk is checked. If the WWID in the SUD is different, it is updated with with the new WWID. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE Page 41 8 PROBLEMS INCLUDED IN THE VMS73_UPDATE-V0300 KIT 8.1 Problems addressed in the VMS73_F11X-V0200 kit 8.1.1 System can crash with a "UNXSIGNAL, Unexpected signal name in ACP" bugcheck 8.1.1.1 Problem Description: The system can crash with a "UNXSIGNAL, Unexpected signal name in ACP" bugcheck in routine ACL_BUILDACL. Crashdump Summary Information ----------------------------- Bugcheck Type: UNXSIGNAL, Unexpected signal name in ACP Failing PC: FFFFFFFF.C9114E54 ACL_BUILDACL_C+00594 Failing PS: 20000000.00000000 Module: F11BXQP (Link Date/Time: 24-AUG-2000 07:20:45.47) Offset: 00052E54 Images Affected: - [SYS$LDR]F11BXQP.EXE 8.1.1.2 CLDs, and QARs reporting this problem: 8.1.1.3 CLD(s) CFS.83831,CFS.85044,CFS.88565,CFS.90523 8.1.1.4 QAR(s) None. 8.1.1.5 Problem Analysis: The exception occurs because the XQP tries to access a null FCB, which was loaded from a previous FCB that had FCB$L_EXFCB = 0. 8.1.1.6 Work-arounds: None. Page 42 8.1.2 "%SYSTEM-W-ACCONFLICT, file access conflict" error 8.1.2.1 Problem Description: When using sys$check_access against a file opened in write mode, a "%SYSTEM-W-ACCONFLICT, file access conflict" error is returned. Images Affected: - [SYS$LDR]F11BXQP.EXE 8.1.2.2 CLDs, and QARs reporting this problem: 8.1.2.3 CLD(s) 70-3-6002,CFS.92708 8.1.2.4 QAR(s) None. 8.1.2.5 Problem Analysis: SYS$CHECK_ACCESS uses the FIB option FIB$V_NO_READ_DATA to read the ACL/protection attributes of a file object. When the file is opened to not allow read sharing, this service would return SS$_ACCONFLICT. If the service adds the FIB$V_CONTROL flag this does not occur. The change relaxes the requirement for the need to specify FIB$V_CONTROL, which implies the need write access to the file. This is not the case and FIB$V_NO_READ_DATA prevents the file system from mapping the data in the file. 8.1.2.6 Work-arounds: None. 8.1.3 "UNXSIGNAL, Unexpected signal name in ACP" bugcheck 8.1.3.1 Problem Description: The system can crash with a "UNXSIGNAL, Unexpected signal name in ACP" bugcheck. Crashdump Summary Information: ------------------------------ Bugcheck Type: UNXSIGNAL, Unexpected signal name in ACP Page 43 Current Image: Failing PC: FFFFFFFF.802163C8 EXTEND_C+00B68 Failing PS: 10000000.00000000 Module: F11BXQP (Link Date/Time: 17-MAR-2001 03:16:47.08) Offset: 0001A3C8 Stack Pointers: KSP = 00000000.7AC7EF30 ESP = 00000000.7FFA6000 SSP = 00000000.7FFAB6C0 USP = 00000000.7AB75AF0 Images Affected: - [SYS$LDR]F11BXQP.EXE 8.1.3.2 CLDs, and QARs reporting this problem: 8.1.3.3 CLD(s) None. 8.1.3.4 QAR(s) 75-13-0895 8.1.3.5 Problem Analysis: The crash occurs when, during a header extension, the LAST_FCB value is zero as the last header on disk has not yet mapped to an FCB. 8.1.3.6 Work-arounds: None. 8.1.4 Failing UIC not reported when a diskquota operation fails 8.1.4.1 Problem Description: If a diskquota operation fails, the UIC of the current thread may not reflect the UIC operation on the file created. This may be due to privileges of the thread or the use of Resource Identifiers on a file/directory. Images Affected: - [SYS$LDR]F11BXQP.EXE Page 44 8.1.4.2 CLDs, and QARs reporting this problem: 8.1.4.3 CLD(s) None. 8.1.4.4 QAR(s) None. 8.1.4.5 Problem Analysis: As the ability to create a file with differing resource ownership increased, the failure mechanism did not provide means of determining the failing resource value. 8.1.4.6 Work-arounds: None. 8.1.5 System can crash with an "XQPERR, Error detected by file system XQP" bugcheck 8.1.5.1 Problem Description: The system can crash with an "XQPERR, Error detected by file system XQP" bugcheck: Crashdump Summary Information: ------------------------------ Bugcheck Type: XQPERR, Error detected by file system XQP VMS Version: V7.3-1 Current Process: BATCH_875 Current Image: DSA1:[SYS5.SYSCOMMON.] [SYSEXE]LOGINOUT.EXE Failing PC: FFFFFFFF.80248600 SEARCH_FCB_C+00E70 Failing PS: 00000000.00000000 Module: F11BXQP (Link Date/Time: 18-JUL-2002 19:55:23.70) Offset: 00014600 Images Affected: - [SYS$LDR]F11BXQP.EXE Page 45 8.1.5.2 CLDs, and QARs reporting this problem: 8.1.5.3 CLD(s) CFS.98483,70-3-6831 8.1.5.4 QAR(s) None. 8.1.5.5 Problem Analysis: If a process on one node performs a FID_TO_SPEC operation (ATR$C_FILE_SPEC) on a file, as the operation traces the directory path it may release the serialization on the FCB and, at the same time, increase the REFCNT. If another node, processing this same file for delete, does not notice that the file is locked elsewhere in the cluster, it succeeds with a full delete of the file. With the file now free, another process can create a file with the header and search for the FCB. The FCB in memory references an old header and the system bugchecks with an XQPERR bugcheck (in RES_SEQ_MISMATCH). 8.1.5.6 Work-arounds: None. 8.1.6 "UNXSIGNAL, Unexpected signal" bugcheck 8.1.6.1 Problem Description: Use of the undocumented and unsupported command SET WATCH FILE could result in an ACCVIO or UNXSIGNAL bugcheck if the process P1 space allocation area becomes corrupt. Crashdump Summary Information: ------------------------------ Bugcheck Type: UNXSIGNAL, Unexpected signal name in ACP Current Image: DSA100:[SYS1.SYSCOMMON.] [SYSEXE]COBOL.EXE;3 Failing PC: FFFFFFFF.80040510 EXE$ALLOCATE_C+00070 Failing PS: 00000000.00000000 Module: SYSTEM_PRIMITIVES_MIN (Link Date/Time: 17-OCT-2001 00:50:50.04) Offset: 00012510 Stack Pointers: KSP = 00000000.7B042E70 ESP = 00000000.7B09E0F8 SSP = 00000000.7FFAC100 USP = 00000000.7AE20FA0 Page 46 Images Affected: - [SYS$LDR]F11BXQP.EXE 8.1.6.2 CLDs, and QARs reporting this problem: 8.1.6.3 CLD(s) CFS.99020,70-3-6915 8.1.6.4 QAR(s) None. 8.1.6.5 Problem Analysis: See Problem Description 8.1.6.6 Work-arounds: None. 8.1.7 "UNXSIGNAL, Unexpected signal name in ACP" bugcheck 8.1.7.1 Problem Description: The system can crash with an "UNXSIGNAL, Unexpected signal name in ACP" bugcheck. Crashdump Summary Information: ------------------------------ Bugcheck Type: UNXSIGNAL, Unexpected signal name in ACP Current Process: TC_ESG_0 Current Image: Failing PC: FFFFFFFF.802442C0 F11BXQP+222C0 Failing PS: 30000000.00000000 Module: F11BXQP (Link Date/Time: 18-JUL-2002 19:55:23.70) Offset: 000222C0 Stack Pointers: KSP = 00000000.7AEE4DF0 ESP = 00000000.7FFA6000 SSP = 00000000.7FFAC230 USP = 00000000.7ADA9AF0 Images Affected: - [SYS$LDR]F11BXQP.EXE Page 47 8.1.7.2 CLDs, and QARs reporting this problem: 8.1.7.3 CLD(s) None. 8.1.7.4 QAR(s) 75-83-1048 8.1.7.5 Problem Analysis: When a header is extended, the FCB may not yet be built on a particular node. The FCB chain is incomplete or may have been truncated and not rebuilt. As the location of the next extent is found, the header chain is completed, but the FCB chain is not. Thus an ACCVIO (UNXSIGNAL)occurs. 8.1.7.6 Work-arounds: None. 8.1.8 Revision date moves backwards 8.1.8.1 Problem Description: When reading the revision date, the use of the FCB field on an ODS-2 disk can result in the revision date moving backwards. That is, the ATR$C_REVDATE would read the FCB modification when in reality, it is not valid for an ODS-2 disk. This is also true in the case where access_dates are not enabled on an ODS-5 disk. Images Affected: - [SYS$LDR]F11BXQP.EXE 8.1.8.2 CLDs, and QARs reporting this problem: 8.1.8.3 CLD(s) None. Page 48 8.1.8.4 QAR(s) None. 8.1.8.5 Problem Analysis: See Problem Description 8.1.8.6 Work-arounds: None. 8.1.9 DIRECTORY/FULL command gives incorrect revision dates 8.1.9.1 Problem Description: When a program, such as BACKUP, accesses the secondary header, information from the header in the form of a date will be improperly moved into the FCB$Q_xxxDATE field. The result can be a fairly strange (far in the future) date in the revision section of a DIRECTORY/FULL command output. Images Affected: - [SYS$LDR]F11BXQP.EXE 8.1.9.2 CLDs, and QARs reporting this problem: 8.1.9.3 CLD(s) CFS.102062,70-3-7296 8.1.9.4 QAR(s) None. 8.1.9.5 Problem Analysis: The IMAGE_GET_DATE routines do not account for secondary headers. 8.1.9.6 Work-arounds: None. Page 49 8.1.10 "EXTCACHIV, Contents of extent cache is garbage" bugcheck 8.1.10.1 Problem Description: The system could crash with the bugcheck: EXTCACHIV, Contents of extent cache is garbage Images Affected: - [SYS$LDR]F11BXQP.EXE 8.1.10.2 CLDs, and QARs reporting this problem: 8.1.10.3 CLD(s) 70-3-6837,CFS.98502 8.1.10.4 QAR(s) 75-100-58 8.1.10.5 Problem Analysis: This occurs when a volume, encountering an extreme condition such as a volume invalid error, tries to flush the extent cache back to the disk. An entry does not properly fit the clusters size of the volume. 8.1.10.6 Work-arounds: None. 8.2 Problems addressed in the VMS73_FIBRE_SCSI-V0600 kit 8.2.1 The system can crash with an INCONSTATE bugcheck at SYS$FGEDRIVER+1100C. 8.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 Page 50 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 8.2.1.2 CLDs, and QARs reporting this problem: 8.2.1.3 CLD(s) None. 8.2.1.4 QAR(s) 75-83-999 8.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(). 8.2.1.6 Work-arounds: None. 8.2.2 Mis-leading errors when mounting tape drive 8.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. Page 51 Images Affected: - [SYS$LDR]SYS$MKDRIVER.EXE 8.2.2.2 CLDs, and QARs reporting this problem: 8.2.2.3 CLD(s) CFS.96327,CFS.97599,CFS.98783,CFS.99263 8.2.2.4 QAR(s) None. 8.2.2.5 Problem Analysis: See Problem Description 8.2.2.6 Work-arounds: None. 8.2.3 Provide Additional error logging 8.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 8.2.3.2 CLDs, and QARs reporting this problem: 8.2.3.3 CLD(s) None. 8.2.3.4 QAR(s) None. Page 52 8.2.3.5 Problem Analysis: See Problem Description 8.2.3.6 Work-arounds: None. 8.2.4 Display of some controller and device identifiers missing in some SHOW commands. 8.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 8.2.4.2 CLDs, and QARs reporting this problem: 8.2.4.3 CLD(s) None. 8.2.4.4 QAR(s) None. 8.2.4.5 Problem Analysis: See Problem Description. 8.2.4.6 Work-arounds: None. 8.2.5 The system can crash with an INCONSTATE bugcheck at SYS$FGEDRIVER+12968 Page 53 8.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 8.2.5.2 CLDs, and QARs reporting this problem: 8.2.5.3 CLD(s) None. 8.2.5.4 QAR(s) 75-13-1126 8.2.5.5 Problem Analysis: The fg$fcp_fp_ring_attention did not recognize the XRI_ABORTED_CX command. 8.2.5.6 Work-arounds: None. Page 54 8.3 Problems addressed in the VMS73_IPC-V0200 kit 8.3.1 The REGISTRY appeared to hang while running down 8.3.1.1 Problem Description: The REGISTRY appeared to hang while running down. Images Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE 8.3.1.2 CLDs, and QARs reporting this problem: 8.3.1.3 CLD(s) None. 8.3.1.4 QAR(s) 75-66-460 8.3.1.5 Problem Analysis: ICC was in an ICC AST routine that is queued by IPC$_UNLINK to signal that the association had been rundown. 8.3.1.6 Work-arounds: None. 8.3.2 Non-paged pool fills with ICCPSBs. 8.3.2.1 Problem Description: Non-paged pool fills with ICCPSBs, consuming the pool. Images Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE 8.3.2.2 CLDs, and QARs reporting this problem: Page 55 8.3.2.3 CLD(s) None. 8.3.2.4 QAR(s) None. 8.3.2.5 Problem Analysis: There is a function inside the module ICC$TRANSFER_ROUTINES.B32 called cleanup_pxb. This function takes two parameters, the second being a boolean to indicate whether the ICC structure should be deallocated. The cleanup_pxb function is called from a number of places in the code, in particular, in EXE$ICC_REPLY in the synch path. If a SS$_SYNCH status is received from IPC for the reply, and the caller has indicated it is prepared to accept SYNCH, cleanup_pxb will be called for the ICCPSB with one parameter, not two. The missing second parameter influences whether nonpaged pool is returned for the ICCPSB. The flag defaults to FALSE and pool is leaked. 8.3.2.6 Work-arounds: None. 8.3.3 Hang at IPL 2 and bytecount quota could be leaked 8.3.3.1 Problem Description: o A hang can occur at IPL 2 due to quota recovery. o Under some circumstances, if a SYS$ICC_TRANSMIT or SYS$ICC_TRANSCEIVE call returned a non-success status, bytecount quota could be leaked. Images Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE 8.3.3.2 CLDs, and QARs reporting this problem: Page 56 8.3.3.3 CLD(s) 70-3-6452,CFS.95931 8.3.3.4 QAR(s) None. 8.3.3.5 Problem Analysis: o Credit accounting could be called at IPL2. o Not all failure paths out of the common routine called by TRANSMIT and TRANSCEIVE correctly returned previously charged quota. 8.3.3.6 Work-arounds: None. 8.3.4 INVEXCEPTN bugcheck at SYS$IPC_SERVICES+137D4 or SYS$IPC_SERVICES+13734 8.3.4.1 Problem Description: The system can crash with an INVEXCEPTN bugcheck at SYS$IPC_SERVICES+137D4 or SYS$IPC_SERVICES+13734 Crashdump Summary Information ----------------------------- Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Failing PC: FFFFFFFF.8035D734 SYS$IPC_SERVICES+13734 Failing PS: 30000000.00000804 Module: SYS$IPC_SERVICES (Link Date/Time: 10-JAN-2003 18:41:27.05) Offset: 00013734 Stack Pointers: KSP = 00000000.7FF87698 ESP = 00000000.7FF8B7A0 SSP = 00000000.7FF9BD20 USP = 00000000.7AE49710 Failing Instruction: SYS$IPC_SERVICES+13734: LDL R3,#X0008(R5) Images Affected: Page 57 - [SYS$LDR]SYS$IPC_SERVICES.EXE 8.3.4.2 CLDs, and QARs reporting this problem: 8.3.4.3 CLD(s) None. 8.3.4.4 QAR(s) 75-83-676 8.3.4.5 Problem Analysis: ICC is calling IPC$UNLINK twice on the same logical link. When the first ICC unlink is interrupted, or waits, and a second ICC unlink (same link) begins but "fails" (IPC returns SS$_DISCONNECT to ICC), ICC deallocates the ICCPCB+IPLK. When IPC, for the first unlink, then signals the disconnect completion, the ICCPCB+IPLK given to IPC to do the job are gone, and the ACCVIO occurs. 8.3.4.6 Work-arounds: None. 8.3.5 Quota is leaked 8.3.5.1 Problem Description: o Calls to SYS$ICC_TRANSMIT[W] or SYS$ICC_TRANCEIVE[W] that failed would leak 256 bytes of quota. o If a call to SYS$ICC_TRANSMIT[W] or SYS$ICC_TRANCEIVE[W] specifies a buffer that is not a multiple of 64 bytes in length, 64 bytes of BYTCNT quota is lost if the call fails (e.g. if the link had been disconnected by the remote side.) Images Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE Page 58 8.3.5.2 CLDs, and QARs reporting this problem: 8.3.5.3 CLD(s) 70-3-6452,CFS.95931,70-3-6709,CFS.97674 8.3.5.4 QAR(s) None. 8.3.5.5 Problem Analysis: o Return code does not credit quota in all cases. o The quota debit calls round up to a multiple of 64. The code attempted to credit quota with a single call that had been debited in two separate calls. The sum of two numbers rounded, is not always equal to the the rounded sum of two numbers. 8.3.5.6 Work-arounds: None. 8.3.6 System can crash with a BADDALRQSZ bugcheck 8.3.6.1 Problem Description: The system can crash with a BADDALRQSZ bugcheck when IPC deallocates a zero size ACB (AST Control Block) on disconnect. Crashdump Summary Information: ------------------------------ Bugcheck Type: BADDALRQSZ, Bad memory deallocation request size or address Failing PC: FFFFFFFF.80045958 EXE$DEANONPGDSIZ_C+000A8 Failing PS: 10000000.00000804 Module: SYSTEM_PRIMITIVES (Link Date/Time: 17-JAN-2003 21:12:57.01) Offset: 00015958 Stack Pointers: KSP = 00000000.7FF876D0 ESP = 00000000.7FF8C000 SSP = 00000000.7FF9CD00 USP = 00000000.000DFB30 Failing Instruction: EXE$DEANONPGDSIZ_C+000A8: BUGCHK Page 59 Images Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE 8.3.6.2 CLDs, and QARs reporting this problem: 8.3.6.3 CLD(s) None. 8.3.6.4 QAR(s) 75-83-728 8.3.6.5 Problem Analysis: EXE$DEANONPGDSIZ will bugcheck with BADDALRQSZ if the size of the target packet is 0. The reason why IPC was trying to deallocate an ACB of zero size is due to a bug in disconnect processing. The crashing node, A, had initiated a connection to node B. Before node A had received an accept or reject response to the link request, node B delivered a disconnect message. There is a flaw in the test for a fully formed logical link in the logic that processes an incoming disconnect message. Although the link was not fully formed, the logic took the path as if it were. Part of disconnecting a fully formed link is deallocating the various structures associated with that link. One of these structures is an ACB whose address is stored in the IPLK describing the link. Since the ACB fields are provided by the incoming buffer only on receipt of an accept or reject (which had not arrived) the contents were garbage. 8.3.6.6 Work-arounds: None. 8.3.7 System can crash with an "INCONSTATE, Inconsistent I/O data base" bugcheck. Page 60 8.3.7.1 Problem Description: System can crash with an "INCONSTATE, Inconsistent I/O data base" bugcheck. Crashdump Summary Information: ------------------------------ Bugcheck Type: INCONSTATE, Inconsistent I/O data base Failing PC: FFFFFFFF.8039F7E8 SYS$IPC_SERVICES+3D7E8 Failing PS: 20000000.00000804 Module: SYS$IPC_SERVICES (Link Date/Time: 16-OCT-2001 01:57:51.25) Offset: 0003D7E8 Stack Pointers: KSP = FFFFFFFF.9DDF1CA0 ESP = FFFFFFFF.9DDF3000 SSP = FFFFFFFF.9DDED000 USP = FFFFFFFF.9DDED000 Failing Instruction: SYS$IPC_SERVICES+3D7E8: BUGCHK Images Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE 8.3.7.2 CLDs, and QARs reporting this problem: 8.3.7.3 CLD(s) 70-3-6983,CFS.99600 8.3.7.4 QAR(s) None. 8.3.7.5 Problem Analysis: TVCB$W_SENDSEQNM was incremented unconditionally, but decremented only when the CDRP send sequence number was zero. 8.3.7.6 Work-arounds: None. Page 61 8.3.8 System can crash with an "INVEXCEPTN, Exception while above ASTDEL" bugcheck 8.3.8.1 Problem Description: System can crash with an "INVEXCEPTN, Exception while above ASTDEL" bugcheck at SYS$IPC_SERVICES+368AC. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Failing PC: FFFFFFFF.8036E8AC SYS$IPC_SERVICES+368AC Failing PS: 30000000.00000804 Module: SYS$IPC_SERVICES (Link Date/Time: 18-JUL-2002 19:56:02.02) Offset: 000368AC Stack Pointers: KSP = FFFFFFFF.A2387B28 ESP = FFFFFFFF.A2389000 SSP = FFFFFFFF.A2385000 USP = FFFFFFFF.A2385000 Failing Instruction: SYS$IPC_SERVICES+368AC: INSQUEL/D Images Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE 8.3.8.2 CLDs, and QARs reporting this problem: 8.3.8.3 CLD(s) 70-3-7047,CFS.100124,CFS.78468 8.3.8.4 QAR(s) None. 8.3.8.5 Problem Analysis: When the error path is taken during TP$CONNECT_INITIATE due to a bad TVCB state, a deallocated TLCB is still on the TVCB queue, still in the TVCB connect cell, and still counted as a connection on the TVCB (TVCB$B_REF_CNT). If the deallocation of the TLCB and a TLCB reallocation occur closely enough in time, the effect is an attempt to queue the same TLCB off the TVCB, twice. Page 62 8.3.8.6 Work-arounds: None. 8.4 Problems addressed in the VMS73_LIBRTL-V0300 kit 8.4.1 csign returns erroneous results 8.4.1.1 Problem Description: When the total digits argument to STR$DIVIDE is less than or equal to 4, the csign returns 1 (negative) for quotient values that are zeros in the first four decimal places and non-zero beyond the 4th decimal place. For example, -0.0000036 will return as -0.0000. The return of the negative sign indicator causes some products, such as Basic RTL, to print out "-0" rather than "0". Images Affected: - [SYSLIB]LIBRTL.EXE 8.4.1.2 CLDs, and QARs reporting this problem: 8.4.1.3 CLD(s) 70-16-57,CFS.99137 8.4.1.4 QAR(s) None. 8.4.1.5 Problem Analysis: The assignment value to the sign was correct. The code logic has been enhanced to set the csign argument to positive if there is a zero result to be returned in the user-specified precision. 8.4.1.6 Work-arounds: None. 8.4.2 Overflow not detected. Page 63 8.4.2.1 Problem Description: Calls to LIB$CVT_DX_DX using string descriptor class, DSC$K_CLASS_SD, with longword type, DSC$K_DTYPE_L, and non-zero scales do not detect overflow. Images Affected: - [SYSLIB]LIBRTL.EXE 8.4.2.2 CLDs, and QARs reporting this problem: 8.4.2.3 CLD(s) None. 8.4.2.4 QAR(s) 75-13-1049 8.4.2.5 Problem Analysis: The macro used for longword to longword scaling had no overflow detection. 8.4.2.6 Work-arounds: None. 8.4.3 Potential application hangs 8.4.3.1 Problem Description: Some LIB$ RTL routines are not thread-safe because they use event flag zero (0) when they should be using EFN$C_EFN. Using these LIB$ RTL routines can cause a potential application hang since event flag zero can be set/cleared from two or more potential threads affecting other threads. Note that this fix is required to run new versions of the SAS software. Images Affected: - [SYSLIB]LIBRTL.EXE Page 64 8.4.3.2 CLDs, and QARs reporting this problem: 8.4.3.3 CLD(s) CFS.100354,70-16-59 8.4.3.4 QAR(s) None. 8.4.3.5 Problem Analysis: See problem Description 8.4.3.6 Work-arounds: None. 8.5 Problems addressed in the VMS73_LINKER-V0400 kit 8.5.1 Fortran generates %LINK-W-MULPSC warnings. 8.5.1.1 Problem Description: When using Fortran's ADDRESS64 attribute to allocate memory from P2 space, the linker generates %LINK-W-MULPSC warnings. Images Affected: - [SYSEXE]LINK.EXE 8.5.1.2 CLDs, and QARs reporting this problem: 8.5.1.3 CLD(s) CFS.97961 8.5.1.4 QAR(s) None. 8.5.1.5 Problem Analysis: There is a conflict within the PSECT attribute bitmask variable. Bitmask PSFLAGS has a bit set/clear for each PSECT attribute. The bit indicating the PSECT (PSC$M_SOLITARY) had the same value as the bit indicating 64bit allocation (EGPS$M_ALLOC_64BIT). The conflict Page 65 occurred since $PSCDEF is defined in the linker facility while EGPSDEF is part of the object language standard defined in the [VMSLIB] facility. 8.5.1.6 Work-arounds: None. 8.5.2 Images not installed resident 8.5.2.1 Problem Description: Alpha image section size is limited to 32MB, the same size as VAX image section. This limitation prevented large images, with image sections that spanned more than one image section, from being installed resident. With this change, the maximum size of the code image section is being increased to 1GB. Images Affected: - [SYSEXE]LINK.EXE 8.5.2.2 CLDs, and QARs reporting this problem: 8.5.2.3 CLD(s) None. 8.5.2.4 QAR(s) 75-83-598 8.5.2.5 Problem Analysis: See Problem Description 8.5.2.6 Work-arounds: None. 8.5.3 Code section binding is not being disabled, resulting in image corruption Page 66 8.5.3.1 Problem Description: When a code image section spans across more than one image section and the image is linked with /SECTION_BINDING, code section binding is not being disabled. The resultant image is corrupted and should not be installed resident. The following example shows an image linked with /SECTION_BINDING, the linker left the code section binding bit set. %LINK-W-BINDFAILS, binding failed, psect INSTRUCTIONS spanned image section located at %X00000000 %LINK-W-DBINDISABLE, section binding of DATA has been disabled %ANALYZE-I-ERRORS, $1$DKB300:[VERIFICATION.LINKER .LINKER_TESTS]Y.EXE;2 0 errors (8) EIHD$V_BIND_CODE_SEC 1 (9) EIHD$V_BIND_DATA_SEC 0 Images Affected: - [SYSEXE]LINK.EXE 8.5.3.2 CLDs, and QARs reporting this problem: 8.5.3.3 CLD(s) None. 8.5.3.4 QAR(s) 75-83-598 8.5.3.5 Problem Analysis: The eisd$m_exe bit in the EISD structure had not been set before it was tested. 8.5.3.6 Work-arounds: None. 8.6 New problems addressed in the VMS73_MEM_CHAN-V0200 kit Page 67 8.6.1 PMDRIVER FORK_THREAD TQE DOUBLE-INSERT FIX 8.6.1.1 Problem Description: After installation of the VMS73_MEM_CHAN-V0100 ECO kit, systems may hang when using the Memory Channel SCS-port. The system will hang and not crash, requiring manual intervention and a system-HALT (Console ^P) to recover. This hang only occurs if there is high SCS-data-transfer activity (MSCP/TMSCP disk/tape serving) with high IPL-8 fork latency on the Memory Channel target node. A forced operator crash-dump and analysis will reveal the OpenVMS EXEC looping within the following routines: + SYSTEM_PRIMITIVE*.EXE: EXE$SWTIMER_FORK Primary SMP CPU stuck scanning EXE$GL_TQFL TQE-queue; check PCs on CPU-0 stack. + SYS$PMDRIVER.EXE: PM$COMQ_RETRY V7.2-2: TQE$L_FPC: SYS$PMDRIVER+13CC0 SDA> FORMAT/TYPE=TQE @EXE$GL_TQFL SDA> FORMAT/TYPE=TQE @. SDA> REPEAT .......... The OpenVMS EXE$GL_TQFL TQE-timer-queue will be corrupted, typically with the first TQE linked back to itself: + SDA> VAL QUE EXE$GL_TQFL Occasionally, there will be an ACCVIO within TIMESCHDL_xxx (SYSTEM_PRIMITIVES) while servicing TQE-queue. Images Affected: - [SYS$LDR]SYS$PMDRIVER.EXE 8.6.1.2 CLDs, and QARs reporting this problem: 8.6.1.3 CLD(s) CFS.97083,CFS.97225,CFS.98090,CFS.98928 8.6.1.4 QAR(s) 75-83-734,75-83-993 Page 68 8.6.1.5 Problem Analysis: A PMDRIVER.C retry (and TQE-stall) mechanism reschedules servicing of stalled SCS-port commands on PMx0: PDT COMQ (cmd. queue). The TQE used for the TQE-stalled retry, in routine FORK_THREAD, was not synchronized, allowing multiple insertions into VMS system TQE-queue by successively stalled PM commands. 8.6.1.6 Work-arounds: None. 8.7 Problems addressed in the VMS73_MEM_CHAN-V0100 kit 8.7.1 Memory Channel virtual-hub (VHUB) can fail to come "ONLINE" 8.7.1.1 Problem Description: 1. A Memory Channel virtual-hub (VHUB) will fail to come "ONLINE" and form SCS-virtual-circuitlink-up if the Memory Channel VHUB VH0/Master node is not booted first, prior to booting the VHUB VH1/Slave MC-node 2. If a VH0/Master Memory Channel node crashes and/or reboots while the VH1/Slave Memory Channel node remains running, the Memory Channel link will fail and both VHUB Memory Channel nodes MCA0 (and MCB0 if applicable) will remain "OFFLINE" This MCx0 "OFFLINE" problem may also occur during MCA0/MCB0 adapter/link error-handling/recovery. The following symptoms are manifestations of this MC VHUB BOOT "OFFLINE" problem: OPA0: console errors: -------------------- %MCA0 CPU00: 19-SEP-2000 04:17:50 Slave but adapter_ok off, retrying. %MCA0 CPU00: 19-SEP-2000 04:17:50 MC re-init 5 second timer. %MCA0 CPU00: 19-SEP-2000 04:17:55 Slave but adapter_ok off, retrying. %MCA0 CPU00: 19-SEP-2000 04:17:55 MC re-init 5 second timer. . . . ON REMOTE NODE ATTEMPTING MC SW INIT ......... MCA0 CPU00: 19-SEP-2000 04:27:50 node state retries exceeded" DCL SHOW DEVICE command output: ------------------------------- Page 69 $ DCL SHOW DVICE MCA0: & PMA0: (& MCB0:/PMB0:) = OFFLINE: $ SHOW DEVICE MC Device Device Error Name Status Count MCA0: Offline 2 MCB0: Offline 16 $ SHOW DEVICE PM Device Device Error Name Status Count PMA0: Offline 0 PMB0: Offline 0 Images Affected: - [SYS$LDR]SYS$MCDRIVER.EXE 8.7.2 MC_INCONSTATE (SYS$MCDRIVER) bugcheck 8.7.2.1 Problem Description: An MC_INCONSTATE (SYS$MCDRIVER) bugcheck may occur during local/remote Memory Channel node reboot or Memory Channel adapter/Memory Channel link- error-recovery. This bugcheck can occur regardless of the Memory Channel hub configuration: VHUB or real-HUB. The MC_INCONSTATE bugcheck will typically occur when a "nested error (MCDRIVER-internal or MC-adapter HW-error)" is encountered while recovering from a memory channel link error or local/remote memory channel node crash/reboot. The "MC_INCONSTATE" bugcheck is obvious, and is nearly always caused by this "nested error-handling" bug. A typical MCx0: error-log event sequence, and SDA> crash summary are shown below: MCx0: ERROR-LOG SUMMARY: Unsuccessful events: --------------------------------------------- MCB0 - Hardware error, reinitializing. MCB0 - Node 0: State: Uninitialized Node 1: State: Uninitialized MCB0 - Memory channel link online failure 2 MCB0 - We shouldn't be here. CRASH - MC_INCONSTATE Crashdump Summary Information: ------------------------------ Bugcheck Type: MC_INCONSTATE, Fatal error detected by Memory Channel Failing PC: FFFFFFFF.E2983A44 SYS$MCDRIVER+0BA44 Failing PS: 30000000.00000804 Module: SYS$MCDRIVER (Link Date/Time: Page 70 29-DEC-1999 04:09:37.99) Offset: 0000BA44 Images Affected: - [SYS$LDR]SYS$MCDRIVER.EXE 8.7.3 Memory Channel Receive channel (RX_MESS_CHAN) message processing may hang 8.7.3.1 Problem Description: Memory Channel Receive channel (RX_MESS_CHAN) message processing may hang after processing 512 RX_MESS_CHAN messages during a single fork-thread ([MEM_CHAN]MC$HANDLE_MESS_CHAN_INT routine). This could occur with heavy Memory Channel SCS-traffic and high IPL-8 fork-thread scheduling latency. A Memory Channel RX_MESS_CHAN message-handling hang will lead to CNXMGR/LOCK_MGR stalls (and potential cluster hangs) as well as SCS "virtual-circuit timeouts". OPA0: CONSOLE PM/MC ERROR MESSAGES: ----------------------------------- %PMA0 CPU00: ... MC$_CHAN_QUE_EMPTY channel = 541C8 ppd = 83DD4CC0 %PMA0 CPU00: ... stall state CLEAR channel = 541C8 ppd = 83DD4CC0 %MCA0 CPU00: ... Timeslice exceeded while in workque for node RM763A %MCA0 CPU00: ... Timeslice exceeded while in workque for node RM763A %MCA0 CPU00: ... Timeslice exceeded while in workque for node RM763A %PMA0, Virtual Circuit Timeout - REMOTE PORT xxxx SCS VC-TIMEOUT ERRLOG ENTRY: ---------------------------- . . . Error Type/SubType x4009 Signaled via Packet, Virtual Circuit Timeout. The "... Timeslice exceeded" error may continue to occur after this fix is applied. However, MC RX_MESS_CHAN processing will no longer hang after this event. Images Affected: - [SYS$LDR]SYS$MCDRIVER.EXE Page 71 8.7.4 MCDRIVER enters an infinite Hardware/Software initialization error-retry loop 8.7.4.1 Problem Description: Following a boot-time Memory Channel C unit-init/self-test "LOOPBACK WRITE TEST" failure, which indicates a Memory Channel adapter PCI-DMA error, the MCDRIVER will enter an infinite HW/SW initialization error-retry loop. The following OPA0:/console errors will be issued at 5 second intervals, changing to 10 minute intervals after 20 retries: %MCA0 CPU00: ... MC loopback write interrupt test failed. %MCA0 CPU00: ... Couldn't get mgmt lock. %MCA0 CPU00: ... ERR - ucb offline and adapter not crashing . %MCA0 CPU00: ... Couldn't get mgmt lock. %MCA0 CPU00: ... ERR - ucb offline and adapter not crashing . %MCA0 CPU00: ... Couldn't get mgmt lock. %MCA0 CPU00: ... ERR - ucb offline and adapter not crashing . Note: The first error message occurs on the first pass only. Images Affected: - [SYS$LDR]SYS$MCDRIVER.EXE 8.7.5 System crashes with a CPUSPINWAIT, CPU spinwait timer expired bugcheck. 8.7.5.1 Problem Description: CPUSPINWAIT bugchecks may occur on any GSxxx Alphaserver platform (GS140,GS80/160/320) with a Memory Channel-adapter. The bugchecks occur due to an eror in the SYS$MCDRIVER "MC$ALLOCATE_MESSAGE" routine performing Memory Channel message free-queue-header "loopback WRITE", and an incorrect timer implementation. The CPUSPINWAIT bugcheck will always involve an SMP$TIMEOUT acquiring the SCS-spinlock while another SMP-CPU is holding the SCS-spinlock within the SYS$MCDRIVER / [MEM_CHAN]MCCHANNELS.CMC$ALLOCATE_MESSAGE routine. Crashdump Summary Information: ------------------------------ Bugcheck Type: CPUSPINWAIT, CPU spinwait timer expired Failing PC: FFFFFFFF.8007A384 SMP$TIMEOUT_C+00064 Failing PS: 28000000.00000804 Module: SYSTEM_SYNCHRONIZATION_MIN Offset: 00000384 Page 72 NOTE: The "MC loopback write interrupt test failed" error is typically due to a leftover/stale Memory Channel adapter PCI-logic error-state that will only clear with a CONSOLE >>> INIT operation (to perform PCI-bus RESET). Users who frequently reboot without using the CONSOLE >>> BOOT_RESET = ON switch (Environment Variable) or without performing a CONSOLE >>> INIT command are susceptible to this "MC loopback write test" error. Images Affected: - [SYS$LDR]SYS$MCDRIVER.EXE 8.7.6 System can crash with a INVPTEFMT, Invalid page table entry format 8.7.6.1 Problem Description: Any SCS-data-transfer of "0-length", using the Memory-Channel/MC SCS-port will result in an "INVPTEFMT, Invalid page table entry format" bugcheck The bugcheck is within IOC_STD$PTETOPFN, as a result of a call to IOC_STD$FILSPT from PMDRIVER.C/SETUP_COPY. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVPTEFMT, Invalid page table entry format Current Process: NULL Current Image: Failing PC: FFFFFFFF.800B88FC IOC_STD$PTETOPFN_C+0008C Failing PS: 38000000.00000804 Module: IO_ROUTINES (Link Date/Time: 13-DEC-2000 00:39:37.49) Offset: 000048FC Images Affected: - [SYS$LDR]SYS$PMDRIVER.EXE 8.7.7 SCS "SEND MESSAGE" and SCS data transfer commands can stall or hang Page 73 8.7.7.1 Problem Description: SCS "SEND MESSAGE" (typically LOCK_MGR and MSCP disk commands) and SCS data transfer commands, issued over a PM/MC SCS virtual circuit (VC), can stall or hang following exhaustion of Memory channel "channel-free-queue" entries. The duration of this stall or hang is entirely dependent on SCS-sysap traffic and flow-control (SCS "credit") patterns and will persist until one of the following occurs: o SCS VC timeout error closes the VC o SCS-sysap sends a message that breaks the stalemate o SCS VC timeout mechanism sends a message that breaks the stalemate o PMx0: SCS-port timeout occurs, crashing the MC port This SYS$PMDRIVER MC-SCS-command processing hang/stall can occur under the following two conditions: - HANG: Under heavy and primarily unidirectional loads; - STALL: Under more bi-directional loads, stalls will create low performance over the Memory Channel VC, drastically reducing Memory Channel performance under load. Because this hang/stall will block internode SCS-sysap cluster communications, symptoms can be obscure and numerous, or may manifest as: o Performance degradation over Memory Channel based SCS VCs o A SCS VC-timeout o A LOCK_MGR stall/hang or performance loss o MSCP served disk command timeouts or disk I/O slowdowns o Customer LOCK_MGR-dependent application stalls, hangs, or slowdowns Images Affected: [SYS$LDR]SYS$PMDRIVER.EXE Page 74 8.8 New problems addressed in the VMS73_NETACP-V0100 kit 8.8.1 Process hangs in RWAST 8.8.1.1 Problem Description: A process hangs in RWAAST wait state during process rundown. Images Affected: - [SYS$LDR]NETDRIVER.EXE - [SYSEXE]NETACP.EXE 8.8.1.2 CLDs, and QARs reporting this problem: 8.8.1.3 CLD(s) CFS.102284 8.8.1.4 QAR(s) None. 8.8.1.5 Problem Analysis: EXE$DEASSGN had called the NETDRIVER DEASSIGN routine and then called the same routine again for the same channel before the first deassign call had completed. 8.8.1.6 Work-arounds: None. 8.9 Problems addressed in VMS73_RMS-V0400 kit 8.9.1 RMS: Prevent possible process hangs and system crashes when files with global buffers are accessed. 8.9.1.1 Problem Description: RMS: Fix to prevent possible process hangs and system crashes when files with global buffers are accessed. An application accessing a file with global buffers enabled might experience any one of several symptoms ranging from an IVLOCKID being returned to RMS through a possible SSRVEXCEPTN due to corruption of an RMS internal control structure. Page 75 Prior to this change, it is possible for an internal table maintained by RMS (the Global Buffer Interlock Table) within its global buffer sections to overflow. This can potentially result in corruption to adjoining control structures. No user data are compromised; however, the process may hang or the system crash dependent on what is overwritten. This problem is most prevalent on systems where there is a high turnover of processes. Images Affected: - [SYS$LDR]RMS.EXE 8.9.1.2 CLDs, SPRs, and QARs reporting this problem: 8.9.1.3 CLD(s) CFS.92786; CFS.92655; CFS.93534. 8.9.1.3.1 SPR(s) None. 8.9.1.4 QAR(s) None. 8.9.1.5 Problem Analysis: This problem is fixed in the next release after OpenVMS Alpha V7.3. To determine if the GBIT table has overflowed, the System Dump Analyzer can be utilized. Examination of a process's Global Buffer Headers will exhibit a value for the "GBIT FREEPTR" that is greater than the "GBD_START" address as shown below. SDA> SHOW PROCESS/RMS=GBH GBH Address: 0011C000 ----------- GBD_FLNK: 00006280 GBD_BLNK: 00006300 BID: 33 51. BLN: 1A 26. GS_SIZE: 00022000 LOCK_ID: 010003C8 USECNT: 0000034F SAVED_GBD: 00000000 --->GBD_START: 00004000 GBD_END: 00007180 GBD_NEXT: 00004000 SCAN_NUM: 00000008 GBD_SYSVA: FFFFFFFEFABB2000 GBDBUFOBJ_HNDL: 00000003815C9200 HIT: 00007F21 MISS: 0000002F Page 76 OUTBUFQUO: 00000000 HASH MASK: FFFFFFC0 HASH SHIFT: FFFFFFFF GBIT BASE: 00000480 GBIT FREEPTR: 00006E40 <--- FREELIST FLINK: 00006D08 BLINK: 00006D08 COUNT OF GBIS ON FREE LIST: 00000001 If the FREEPTR (6E40 in this example) is greater then the GBD start value (4000 in this example), the table has overflowed. 8.9.1.6 Work-arounds: Workarounds: o Apply this remedial kit. o Disable global buffers on the affected file. 8.9.2 RMS: Fix for a lock hang on a global buffer resource. 8.9.2.1 Problem Description: The symptoms of the hang are as follows: - A global buffer resource has in its granted queue a process PW lock and a system CR lock. - The conversion queue for this resource has a long line of NL-to-PW or NL-to-EX requests blocked by the PW granted lock. This is not a lock manager problem. The PW global buffer lock holder is waiting for the system CR lock to be released. The release of the system CR lock is dependent on a flag (internally managed by RMS) indicating a writer wants access to the resource and a reference count maintained in an internal RMS structure. Until the system CR lock is released and the flag cleared by the last referencer, the process holding the PW lock will continue to block any other processes lining up in the conversion queue. This fix corrects a race condition where if a process was interrupted (stopped or aborted by a $delprc) while actively using the system CR lock, it was possible for the cleanup of the internal RMS structure to be bypassed. This would cause the reference count to get out of sync and result in the system CR lock not getting properly released after a writer requested access to the resource. Images Affected: Page 77 - [SYS$LDR]RMS.EXE 8.9.2.2 CLDs, SPRs, and QARs reporting this problem: 8.9.2.3 CLD(s) CFS.93578; CFS.92380. 8.9.2.4 QAR(s) None. 8.9.2.5 Problem Analysis: This problem is fixed in the next release after OpenVMS Alpha V7.3. 8.9.2.6 Work-arounds: Apply this remedial kit. 8.9.3 RMS: Avoid an exec-mode infinite loop if RMS ever attempts to add a duplicate key value to a compressed index bucket. 8.9.4 Problem Description: Avoid an exec-mode infinite loop if RMS ever attempts to add a duplicate key value to a compressed index bucket. An index bucket should never have a duplicate key value. There is the potential, however, some inconsistency (corruption) in a lower level could result in such an attempt in the case of a compressed key. A correction has been added to issue a nonfatal RMS bugcheck (ISAM) and avoid the loop. Images Affected: - [SYS$LDR]RMS.EXE 8.9.4.1 CLDs, SPRs, and QARs reporting this problem: Page 78 8.9.4.2 CLD(s) None. 8.9.4.3 SPR(s) PTR 75-86-128. 8.9.4.4 QAR(s) None. 8.9.4.5 Problem Analysis: This problem is fixed in the next release after OpenVMS Alpha V7.3. 8.9.4.6 Work-arounds: Apply this remedial kit. 8.9.5 RMS: Fix for some records being potentially skipped over in a reverse key search. 8.9.5.1 Problem Description: If the very last bucket in the data bucket chain for a particular key-of-reference is empty (no valid records), the potential exists for any valid records in the next-to-the-last bucket (and only this bucket) being skipped over in the backwards scan done by a reverse key search. This problem is restricted to a reverse key search. Images Affected: - [SYS$LDR]RMS.EXE 8.9.5.2 CLDs, SPRs, and QARs reporting this problem: 8.9.5.3 CLD(s) CFS.92922. Page 79 8.9.5.4 QAR(s) None 8.9.5.5 Problem Analysis: This problem is fixed in OpenVMS Alpha V7.3-1 8.9.5.6 Work-arounds: Apply this remedial kit. 8.9.6 RMS: Correction for circumflex returned in resultant string for search error cases. 8.9.6.1 Problem Description: When a one-character wildcard % is used in a search, if no file is found (an error is returned), the resultant string returned in the user NAM[L] structure has a circumflex (^) character inappropriately inserted just before the %. This affects a number of DCL utilities which display the resultant string with their error messages (e.g., DELETE, TYPE, RENAME and COPY). For example: $ delete %.jnk;* %DELETE-W-SEARCHFAIL, error searching for SYS$COMMON:[FOO]^%.JNK;* -RMS-E-FNF, file not found Images Affected: - [SYS$LDR]RMS.EXE 8.9.6.2 CLDs, SPRs, and QARs reporting this problem: 8.9.6.3 CLD(s) CFS.91124 8.9.6.4 QAR(s) None. Page 80 8.9.6.5 Problem Analysis: This problem is fixed in the next release after OpenVMS Alpha V7.3. 8.9.6.6 Work-arounds: Workarounds: Apply this remedial kit. 8.9.7 RMS: Set the return length of the auxiliary buffer for calls to SYS$FILESCAN. 8.9.7.1 Problem Description: The return length of the auxiliary buffer ("retlen" optional parameter) that was passed to SYS$FILESCAN was not being set when the Field Flags argument ("fldflags" parameter) was absent. This change sets the return length value unconditionally when one has been requested. Images Affected: - [SYS$LDR]RMS.EXE 8.9.7.2 CLDs, SPRs, and QARs reporting this problem: 8.9.7.3 CLD(s) None. 8.9.7.4 QAR(s) None. 8.9.7.5 Problem Analysis: This problem is fixed in the next release after OpenVMS Alpha V7.3. 8.9.8 Work-arounds: Workarounds: Apply this remedial kit. Page 81 8.9.9 CONVERT: Fix for remote file DAP protocol regression. 8.9.9.1 Problem Description: The convert utility fails with the following error when the input file is a sequential file on a remote foreign (non-VMS) system and the output file is a sequential file on a VMS system if and only if /SORT is explicitly specified or implied by /FDL: %CONV-F-READERR, Error reading (IBM_filename) -RMS-F-BUG_DAP, Data Access Protocol error detected; DAP code = 0001A008 The problem is not reproducable using a remote VMS system. Images Affected: - [SYSEXE]CONVERT.EXE - [SYSLIB]CONVSHR.EXE 8.9.9.2 CLDs, SPRs, and QARs reporting this problem: 8.9.9.3 CLD(s) CFS.92563 8.9.9.4 QAR(s) None 8.9.9.5 Problem Analysis: This problem is fixed in the next release after OpenVMS Alpha V7.3. 8.9.9.6 Work-arounds: Apply this remedial kit. 8.10 Problems addressed in VMS73_RMS-V0300 kit kit Page 82 8.10.1 RMS: Fix for global buffer hang due to abort ($delprc) rundowns. 8.10.1.1 Problem Description: An application may experience a hang under the following conditions: - RMS global buffers are enabled on some files. - Many processes are terminated with $delprc (e.g., STOP/ID) when files are still open. - The application is restarted after the process terminations without rebooting the system. The symptom for this problem is that during the restart of the application, a process enters a tight loop in executive mode. Once encountered, a system reboot is required to clear the problem. Images Affected: - [SYS$LDR]RMS.EXE - [SYSLIB]SDARMS$SHARE.EXE 8.10.1.2 CLDs, SPRs, and QARs reporting this problem: 8.10.1.3 CLD(s) CFS.89318; CFS.90488; CFS.90932. 8.10.1.4 QAR(s) None. 8.10.1.5 Problem Analysis: This problem is fixed in the next release after OpenVMS Alpha V7.3. 8.10.2 Work-arounds: Workarounds: o Apply this remedial kit. o Avoid terminating processes with $delprc (e.g. STOP/ID). Page 83 8.10.3 RMS: Fix for inconsistent secondary key index structure. 8.10.3.1 Problem Description: Any application that does a lot of deleting or does updates that change a no duplicate secondary key value to another value in an indexed file is a potential candidate for this problem. An ANALYZE/RMS_FILE of the indexed file reports the following error for a secondary key: "Index bucket references missing data bucket with VBN nnn" The problem may be that the secondary index structure has duplicate index value entries and there should never be duplicates in the index structure. If the secondary index allows a binary search (is uncompressed), records could be hidden using an exact secondary key lookup. This problem results from the entire space being inappropriately reclaimed for the physically last SIDR record in some secondary data bucket which contains only deleted entries. This problem is restricted to an indexed file with a secondary key that allows no duplicates. The primary key contents will be intact and correct, and a convert of the file will rebuild the secondary indexes and leave the file in a consistent state. Images Affected: - [SYS$LDR]RMS.EXE 8.10.3.2 CLDs, SPRs, and QARs reporting this problem: 8.10.3.3 CLD(s) CFS.88045 8.10.3.4 QAR(s) None. 8.10.3.5 Problem Analysis: This problem is fixed in the next release after OpenVMS Alpha V7.3. Page 84 8.10.3.6 Work-arounds: Apply this remedial kit. 8.10.4 CONVERT/RECLAIM: Fix to prevent inconsistent index structure in an indexed file during a reclamation. 8.10.4.1 Problem Description: An ANALYZE/RMS_FILE reports the following error: "Index bucket references missing data bucket with VBN nnn" A level 1 index record associated with a data (level 0) bucket that was reclaimed was not removed from the index bucket, as it should have been. It is extremely difficult to detect in advance of doing a convert/reclaim whether an indexed file is vulnerable if a reclaim were applied to it. For example, one condition is that one of the initial level 1 index buckets associated with data buckets eligible for reclamation has some condition (for example, only one index record) that will cause a rollback of a removed index record during a reclamation. Without the fix, doing a full convert (without the /RECLAIM qualifier) ensures avoiding this problem. Images Affected: - [SYSEXE]RECLAIM.EXE - [SYSEXE]CONVERT.EXE - [SYSLIB]CONVSHR.EXE 8.10.4.2 CLDs, SPRs, and QARs reporting this problem: 8.10.4.3 CLD(s) CFS.89033 8.10.4.4 QAR(s) None. Page 85 8.10.4.5 Problem Analysis: This problem is fixed in the next release after OpenVMS Alpha V7.3-1. 8.10.5 Work-arounds: Workarounds: o Apply this remedial kit. o Remove the /RECLAIM qualifier from the convert command and add an output file specification (in other words, do a full convert). 8.10.6 CONVERT: Prevent callable convert %CONV-F-READERR with success secondary status. 8.10.6.1 Problem Description: Fix to the CONVERT utility to prevent the signal of a fatal read error (CONV-F-READERR) with an RMS-S-NORMAL secondary status when callable convert is invoked within a threaded application. This correction prevents the erroneous error signal when the end of the input file is reached. Although callable convert is not a thread safe application, it is possible to invoke the callable interface from within a single instance within a single thread. Images Affected: - [SYSEXE]CONVERT.EXE - [SYSLIB]CONVSHR.EXE 8.10.6.2 CLDs, SPRs, and QARs reporting this problem: 8.10.6.3 CLD(s) CFS.89032 8.10.6.4 QAR(s) None Page 86 8.10.6.5 Problem Analysis: This problem is fixed in OpenVMS Alpha V7.3-1 8.10.6.6 Work-arounds: Apply this remedial kit. 8.10.7 CONVERT: Fix for network or tape convert resulting in empty output indexed file. 8.10.7.1 Problem Description: Fix to the CONVERT utility to prevent a convert, which uses either network or tape input, from creating an empty output indexed file. Images Affected: - [SYSEXE]CONVERT.EXE - [SYSLIB]CONVSHR.EXE 8.10.7.2 CLDs, SPRs, and QARs reporting this problem: 8.10.7.3 CLD(s) CFS.88339 8.10.7.4 QAR(s) None 8.10.7.5 Problem Analysis: This problem is fixed in OpenVMS Alpha V7.3-1. 8.10.8 Work-arounds: Apply this remedial kit. 8.11 Problems addressed in the VMS73_SHADOWING-V0300 kit Page 87 8.11.1 System hang during the mounting of a shadowset. 8.11.1.1 Problem Description: During the mounting of a shadowset, a series of protocols can collide such that a thread is left waiting to be resumed and there is no thread to resume it. This can result in a system hang. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 8.11.1.2 CLDs, and QARs reporting this problem: 8.11.1.3 CLD(s) 75-13-829,CFS.90085 8.11.1.4 QAR(s) None. 8.11.1.5 Problem Analysis: The START_MBR_CHANGE_VP macro used in the START_PROTOCOL_END macro will exit with an error when it detects PASSIVE_MV. This causes either a loop in the START_PROTOCOL_END macro or two NL enques in a row which causes the STALL mechanism in the GRANT_LOCK code to fail to resume a stalled thread. The check for PASSIVE was added to prevent incorrect member removal during volume processing. To fix this problem the original START_MBR_CHANGE_VP has been restored and called START_MBR_CHANGE_MNT to be used in the START_PROTOCOL_END macro. This allows MOUNTS to do the right thing. The error loop has been taken out of START_PROTOCOL_END. 8.11.1.6 Work-arounds: None. 8.11.2 Multi-site cluster shadowset member is returned to the shadowset incorrectly Page 88 8.11.2.1 Problem Description: In a multisite cluster with all timeouts set to the maximum, a shadowset member is returned to the shadwoset incorrectly. Manual removal of a member from one site, followed by manual aborting of the virtual unit at a second site, allowed a third site to return the member to the shadowset without either a copy or a merge. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 8.11.2.2 CLDs, and QARs reporting this problem: 8.11.2.3 CLD(s) 70-3-5465,CFS.88963 8.11.2.4 QAR(s) None. 8.11.2.5 Problem Analysis: When the virtual unit is aborted, if there is an outstanding write a merge is triggered. Although the member has been removed from the first site, the third site still thinks it can do a merge. As soon as it can access the removed member it starts the merge. The update of the merge being started causes the member to be added back into the set on the first site. The fix is to not allow NODE_FAILURE to proceed untill PASSIVE_MV has completed. 8.11.2.6 Work-arounds: None. 8.11.3 Ensure shadow copies handle bad blocks correctly 8.11.3.1 Problem Description: If a bad block is detected on the source disk during a full copy operation, the copy will abort with the following OPCOM message : %%%%%%%%%%% OPCOM 10-MAY-2002 09:41:23.94 %%%%%%%%%%% (from node UKVMS3 at 10-MAY-2002 09:41:22.46) Message from user SYSTEM on UKVMS3 %SHADOW_SERVER-E-SSRVTRMSTS, reason for termination Page 89 of operation on device _DSA1: IVADDR, invalid media address The virtual unit will look like this afterwards: Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DSA1: Mounted 0 ALPHAE731_CD 15330438 1 1 $7$DKA100:(UKVMS3) ShadowSetMember 2 (member of DSA1:) $7$DKA1000:(UKVMS3) ShadowCopying 0 (copy trgt DSA1:11% copied) Note that the virtual unit will still be accessible in this state. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 8.11.3.2 CLDs, and QARs reporting this problem: 8.11.3.3 CLD(s) 75-66-1156 8.11.3.4 QAR(s) None. 8.11.3.5 Problem Analysis: When the SHADOW_SERVER is asked to do a shadow copy, it "steps" through the disk processing one 127-block chunk after another (the SCB is handled differently). It does this by sending IO$_COPYSHAD $QIOs to the shadowing driver. There are three pieces of information that the driver sends back to SHADOW_SERVER in response to a IO$_COPYSHAD, which are: 1. Status code 2. Byte transfer count 3. LBN copy fence, ie the last LBN successfully copied. If the LBN copy fence does not agree with what SHADOW_SERVER thinks it should be, then it adjusts its value before moving onto the next LBN range. The problem occurs when a bad block is detected on the source volume. In this case, a zero is returned erroneously as the "LBN copy fence". The SHADOW_SERVER then attempts to start copying at LBN 1 again. It Page 90 encouners a consistency check in SHDRIVER which aborts the COPYSHAD with an SS$_IVADDR error status. 8.11.3.6 Work-arounds: None. 8.11.4 Shadowset Aborts after node is shutdown 8.11.4.1 Problem Description: Shadowsets on the remaining node of a multi-site cluster abort after the serving node of one member is shutdown. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 8.11.4.2 CLDs, and QARs reporting this problem: 8.11.4.3 CLD(s) CFS.90313,CFS.91498,CFS.93820 8.11.4.4 QAR(s) None. 8.11.4.5 Problem Analysis: An attempt was made to keep a shadowset together when a cluster interconnect is intermittent. This allowed the behaviour of hanging the set until MVTIMOUT then aborting it. 8.11.4.6 Work-arounds: None. 8.11.5 Host Based Volume Shadowing (HBVS) Mini Copy Problem Page 91 8.11.5.1 Problem Description: When using HBVS, if Mini Copy is used to return a former Shadow Set Member (SSM) to a virtual unit, and that SSM is removed from the shadow set before the copy can complete, the user must execute the following commands before adding that SSM is added back into the shadow set: $ SHOW DEVICE/BITMAP/FULL DSAnnnn: $ DELETE /BITMAP x "DSAnnnn:" is the virtual unit and "x" is the BitMap ID displayed by the SHOW DEVICE/BITMAP/FULL command. If multiple BitMap IDs are displayed, delete the one that has the SSM in the Bitmap Name portion of the display. If these steps are not taken, data integrity could be affected. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 8.11.5.2 CLDs, and QARs reporting this problem: 8.11.5.3 CLD(s) CFS.100146 8.11.5.4 QAR(s) None. 8.11.5.5 Problem Analysis: See problem description 8.11.5.6 Work-arounds: None. 8.11.6 Repair read bias calculation for multipath devices 8.11.6.1 Problem Description: The read performance for a multiple member shadow set, that has multipath enabled members, has been using only the primary UCB, not the current UCB. Images Affected: Page 92 - [SYS$LDR]SYS$SHDRIVER.EXE 8.11.6.2 CLDs, and QARs reporting this problem: 8.11.6.3 CLD(s) None. 8.11.6.4 QAR(s) None. 8.11.6.5 Problem Analysis: Use the correct primary UCB number 8.11.6.6 Work-arounds: None. 8.11.7 Default read cost for locally remote device set to high 8.11.7.1 Problem Description: Default read cost for locally remote device is set to high Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 8.11.7.2 CLDs, and QARs reporting this problem: 8.11.7.3 CLD(s) None. 8.11.7.4 QAR(s) None. Page 93 8.11.7.5 Problem Analysis: Change to a more reasonable value. The user is able to modify the value. 8.11.7.6 Work-arounds: None. 8.11.8 INVEXCPTN Crash during shadow copy 8.11.8.1 Problem Description: When doing a controller assisted copy, available with HSC and HSJ controllers, if the source member gets an error an incorrect index is set up that results in a crash. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: NULL Current Image: Failing PC: FFFFFFFF 80268D60 Failing PS: 30000000 00000804 Module: SYS$SHDRIVER Offset: 0004AD60 : Exception Frame: R2 = FFFFFFFF 837A6380 R3 = 00000000 00000000 R4 = FFFFFFFF 839CB3C0 R5 = FFFFFFFF 83689D80 R6 = FFFFFFFF 839CB680 R7 = 00000000 00000000 PC = FFFFFFFF 80268D60 PS = 30000000 00000804 Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 8.11.8.2 CLDs, and QARs reporting this problem: 8.11.8.3 CLD(s) CFS.99512 8.11.8.4 QAR(s) None. Page 94 8.11.8.5 Problem Analysis: Ensure all users of shad$ca_target_index use a longword to move in and out of this field. 8.11.8.6 Work-arounds: None. 8.12 Problems addressed in VMS73_SYS-V0600 kit 8.12.1 A system can hang or crash with an INVEXCEPTN bugcheck 8.12.1.1 Problem Description: A system can hang or crash with an INVEXCEPTN bugcheck. The symptoms of this problem can take several different forms, including exception bugchecks and forced crashes of hung systems. Crashes have occurred at PC = PROCESS_MANAGEMENT+0AAF8 = SCH$ONE_SEC_C+00258 in module [SYS]RSE and at PC = LOCKING+0ADE0 = LCK$QUEUEWAIT_C+00050 in module [SYS]SYSENQDEQ. Crashdump Summary Information: ------------------------------ Bugcheck Type: OPERCRASH, Operator forced system crash Current Process: NULL Current Image: Failing PC: FFFFFFFF.8013813C SCH$CLASS_IDLE_C+000BC Failing PS: 00000000.00000003 Module: PROCESS_MANAGEMENT (Link Date/Time: 28-MAR-2002 14:21:36.47) Offset: 0003213C Failing Instruction: SCH$CLASS_IDLE_C+000BC: CMPLE R2,#X3F,R7 Crashdump Summary Information: ------------------------------ Bugcheck Type: OPERCRASH, Operator forced system crash Current Process: NULL Current Image: Failing PC: FFFFFFFF.92637FC8 Failing PS: 00000000.00001504 Module: Offset: 00000000 Failing Instruction: FFFFFFFF.92637FC8: BR R31,#XFFFF9F Page 95 Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 8.12.1.2 CLDs, SPRs, and QARs reporting this problem: 8.12.1.3 CLD(s) CFS.92144,CFS.93253 8.12.1.4 QAR(s) None. 8.12.1.5 Problem Analysis: After deallocating the JIB, due to an error during creation of a detached class scheduled process, register R4 was not reset to the current PCB in routine ABORT in module SYSCREPRC. 8.12.1.6 Work-arounds: None. 8.12.2 SS$_RSDMNOTFOU - Resource domain not found errors 8.12.2.1 Problem Description: When creating many resource domain IDs via $SET_RESOURCE_DOMAIN with RSDM$_JOIN_DOMAIN, subsequent calls to end that association with RSDM$_LEAVE could result in the error SS$_RSDMNOTFOU (resource domain not found) on some IDs. Images Affected: - [SYS$LDR]LOCKING.EXE Page 96 8.12.2.2 CLDs, SPRs, and QARs reporting this problem: 8.12.2.3 CLD(s) CFS.96833 8.12.2.4 QAR(s) None. 8.12.2.5 Problem Analysis: Routine RSDM_FIND_RSDM_ID was not checking the boundary conditions correctly when moving from one RDPB structure to the next. If the index being looked up is the first one in the NEXT RDPB, it is incorrectly assumed that it belonged to this current RDPB structure and picked up as the RDAB address. However, this address is beyond the end of the structure. When the contents are validated, they do not match and a SS$_RSDMNOTFOU error code is returned. The real RDAB is in the next RDPB. 8.12.2.6 Work-arounds: None. 8.12.3 INVSECURESTATE system crash 8.12.3.1 Problem Description: Several multi-threaded servers have experienced a condition where the reference counts of various persona structures have fallen out of sync. The security subsystem triggers an INVSECURESTATE system crash when this condition is detected by the sanity checks. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVSECURESTATE, Invalid state detected by SECURITY subsystem Current Process: TNT_SERVER Current Image: $1$DUA0:[SYS3.SYSCOMMON.][SYSEXE] TNT$SERVER.EXE Failing PC: FFFFFFFF.801A8E94 NSA$ASSUME_PERSONA_C+00064 Failing PS: 10000000.00000000 Module: SECURITY (Link Date/Time: 13-SEP-2000 06:39:51.16) Offset: 00006E94 Page 97 Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY_MON.EXE 8.12.3.2 CLDs, SPRs, and QARs reporting this problem: 8.12.3.3 CLD(s) CFS.84630, CFS.92481 8.12.3.4 QAR(s) None. 8.12.3.5 Problem Analysis: The change includes raising IPL at an earlier point in the persona switching logic. Previous to this change, it was possible to have been interrupted between the point where data had been captured from the KTB, and before the KTB was updated. If such an interrupt occurred, and a change was made to the content of the KTB before returning. The interrupted thread could end up acting on stale data it collected before the interrupt. 8.12.3.6 Work-arounds: None. 8.12.4 SMTP mail delivery process hang 8.12.4.1 Problem Description: After installing the DEC-AXPVMS-VMS73_SYS-V0500--4.PSCI ECO kit, process hangs could occur when using SMTP mail. When sending a mail message via SMTP, the mail is delivered but the process handling SMTP mail delivery hangs on creating the mail notification. The mail delivery notification is never sent and any subsequent SMTP mail accumulates, unsent, in the queue. The process hangs occur because BRKTHR tries to allocate memory from P1 space. If it is unsuccessful, it tries to allocate from P0 space. This is when the hangs occur. This kit removes the code fix for V7.3 that caused this problem to occur. This fix was originally done to solve the following problem. Since this fix is being removed, this problem could re-occur: Page 98 - The system can crash with a SSRVEXCEPT bugcheck when an image exits before the $BRKTHRU has been delivered to some of its targets. Note that occurrence of this problem is rare and can only occur if: 1. A user program must use the asynchronous version of the system call $BRKTHRU -- using the synchronous form, $BRKTHRUW, prevents this) 2. The P1 allocation area sized by the SYSGEN parameter CTLPAGES must be exhausted 3. The program must then exit before the $BRKTHRU call has finished sending messages to all the appropriate terminals. Note that the third issue cannot happen if the synchronous form of the $BRKTHRU call, $BRKTHRUW, is used. Crash Dump Summary: ------------------- Bugcheck Type: SSRVEXCEPT, Unexpected system service exception Current Process: SDNCC_MBX_MAIN Current Image: Failing PC: FFFFFFFF.98B56AAC IO_ROUTINES+46AAC Failing PS: 00000000.00000000 Module: IO_ROUTINES (Link Date/Time: 17-MAR-2001 03:30:01.24) Offset: 00046AAC Signal Array: 64-bit Signal Array: Arg Count = 00000005 Arg Count = 00000005 Condition = 0000000C Condition = 00000000.0000000C Argument #2 = 00000000 Argument #2 = 00000000.00000000 Argument #3 = 006C41D0 Argument #3 = 00000000.006C41D0 Argument #4 = 98B56AAC Argument #4 = FFFFFFFF.98B56AAC Argument #5 = 00000000 Argument #5 = 00000000.00000000 Failing Instruction: IO_ROUTINES+46AAC: LDL R6,(R7) Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB Page 99 8.12.4.2 CLDs, SPRs, and QARs reporting this problem: 8.12.4.3 CLD(s) CFS.95559,CFS.96560,CFS.96677,CFS.96974,CFS.96821 8.12.4.4 QAR(s) None. 8.12.4.5 Problem Analysis: See Problem Description. 8.12.4.6 Work-arounds: This workaround applies to the SMTP mail problem. Increasing the size of CTLPAGES will provide more P1 space and help alleviate the process hangs. If you have experienced these hangs and have undelivered SMTP mail messages in the queue, executing the following command procedure, in batch, on each node with a problem, will clear the mail messages. To use this command file substitute "node" with the name of the system. Note that the lines enclosed by "[ ]" are optional. They are used if you wish to list multiple nodes. $SET NOON $TCPIP STOP MAIL $stop/que/reset TCPIP$SMTP_node_01 [$stop/que/reset TCPIP$SMTP_node_02] $tcpip anal mail/repair $start/que TCPIP$SMTP_node_01 [$start/que TCPIP$SMTP_node_02 $TCPIP START MAIL $ sho que TCPIP$SMTP_node_01/full/all [$ sho que TCPIP$SMTP_node_02/full/all] $exit Note that increasing the size of CTLPAGES to provide more P1 space may also help alleviate the $BRKTHRU crash issue. 8.12.5 .hl 3 System crash caused by NPP corruption 8.12.5.1 Problem Description: Recent changes to handle segmented data capturing from remote processes failed to detect possible data overrun conditions. If a buffer of insufficient size is passed to the service, the resulting overrun could result in NPP corruption. Customer's experiencing a crash due to the data overrun would see corruption in NNP as the cause. Programs that pass data buffers too small to contain the data items request, JPI$_RIGHTLIST items in particular, can trigger this crash. Page 100 Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 8.12.5.2 CLDs, SPRs, and QARs reporting this problem: 8.12.5.3 CLD(s) CFS.97350 8.12.5.4 QAR(s) None. 8.12.5.5 Problem Analysis: See problem description. 8.12.5.6 Work-arounds: None. 8.12.6 INVEXCEPTN, Exception while above ASTDEL system crash 8.12.6.1 Problem Description: The system can crash with an INVEXCEPTN, Exception while above ASTDEL bugcheck at FIND_CVCB_C+0001C. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: NULL Current Image: Failing PC: FFFFFFFF.8022939C FIND_CVCB_C+0001C Failing PS: 20000000.00000804 Module: SYS$VCC (Link Date/Time: 5-AUG-2001 01:16:26.26) Offset: 0000539C Stack Pointers: KSP = FFFFFFFF.C5FE9BE8 ESP = FFFFFFFF.C5FEB000 SSP = FFFFFFFF.C5FD5000 USP = FFFFFFFF.C5FD5000 Page 101 Images Affected: - [SYS$LDR]SYS$VCC.EXE - [SSY$LDR]SYS$VCC_MON.EXE 8.12.6.2 CLDs, SPRs, and QARs reporting this problem: 8.12.6.3 CLD(s) 70-3-6762,CFS.97750,CFS.96647,CFS.84900 8.12.6.4 QAR(s) None. 8.12.6.5 Problem Analysis: The insertion and walking of the CVCB queue is covered by the CACHE (MMG) spinlock. However, there were cases where the removal of a CVCB entry in the queue was covered only by the SCS spinlock. In faster and larger SMP configurations a DISMOUNT operation might cause another CPU to misread the CVCB queue and access an incorrect element. 8.12.6.6 Work-arounds: None. 8.12.7 PFNREFNZRO, PFN reference count nonzero bugcheck 8.12.7.1 Problem Description: Under rare circumstances the nonpaged pool expansion code could try to allocate additional physical memory for pool expansion without proper synchronization (ie, without the MMG spinlock). This results in lost synchronization to the PFN data base that in turn could lead to a PFNREFNZRO bugcheck. Crashdump Summary Information: ------------------------------ Bugcheck Type: PFNREFNZRO, PFN reference count nonzero Current Process: BATCH_515 Current Image: $1$DGA20:[SQR4_3_4.ORA.BIN]SQR.EXE;6 Failing PC: FFFFFFFF.8006A82C MMG$INS_PFNH_C+0014C Failing PS: 18000000.00000203 Module: SYSTEM_PRIMITIVES_MIN (Link Date/Time: 4-NOV-2002 16:37:10.53) Page 102 Offset: 0004282C Stack Pointers: KSP = 00000000.7FFA1AD8 ESP = 00000000.7FFA6000 SSP = 00000000.7FFAC100 USP = 00000000.7A8FDE50 Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 8.12.7.2 CLDs, SPRs, and QARs reporting this problem: 8.12.7.3 CLD(s) CFS.97324 8.12.7.4 QAR(s) None. 8.12.7.5 Problem Analysis: The code path for expansion checked to see if the current CPU owned the MMG spinlock or not. But it did this check at IPL 2, and could be rescheduled from one CPU to another in the middle of the check. This could result in the code thinking it owns the MMG spinlock, when in fact it is now owned by another CPU. It could then call the low level routines to allocate a PFN without taking out the MMG spinlock, resulting in PFN database corruption. 8.12.7.6 Work-arounds: None. 8.12.8 "%JBC-E-NOPRIV, insufficient privilege or queue protection violation" error Page 103 8.12.8.1 Problem Description: An image without UIC based protection access to a QUEUE object, but which is installed with the OPER privilege, will not be able to manipulate the QUEUE object as allowed when holding the OPER privilege. This can result in a "%JBC-E-NOPRIV, insufficient privilege or queue protection violation" error message. Images Affected: - [SYS$LDR]MESSAGE_ROUTINES.EXE 8.12.8.2 CLDs, SPRs, and QARs reporting this problem: 8.12.8.3 CLD(s) 70-3-6406,CFS.95632 8.12.8.4 QAR(s) 75-13-818 8.12.8.5 Problem Analysis: Previous to VMS V7.2, WORKING and IMAGE privileges were combined in a single privilege mask. Per-Thread security maintains separate masks. Modifications to the QUEUE_OBJECT module to support Per-Thread neglected to bring these two masks together before calling the SYS$CHECK_PRIVILEGE service. 8.12.8.6 Work-arounds: None. 8.12.9 Extra SIO entry in IOPERFORM buffers 8.12.9.1 Problem Description: On IO to a fibre channel disk, there are two SIO entries made in the IOPERFORM buffers for each IO request. Normally we would expect to see SRQ (start request), SIO (start IO), EIO (end IO, and ERQ (end request). What we are seeing SRQ, SIO, SIO, EIO, and ERQ. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE Page 104 - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 8.12.9.2 CLDs, SPRs, and QARs reporting this problem: 8.12.9.3 CLD(s) 70-3-6509,CFS.96317 8.12.9.4 QAR(s) None. 8.12.9.5 Problem Analysis: Routine PMS_STD$START_IO (used by performance tools such as DECps) is called to log the start of an I/O operation. The call to this routine is hidden in the INITIATE_SETUP macro, which is traditionally called at the start of an IO in routine IOC$INITIATE_NEW_IO. With the introduction of fastpath, more code was added and now the INITIATE_SETUP macro appears in more places. For fastpath I/Os which do not originate on the fastpath CPU the start IO is logged twice. THe fix is to remove the INITIATE_SETUP macro in IOC$INITIATE_PORT_CPU, and add the code from INITIATE_SETUP excluding the call to PMS$START_IO 8.12.9.6 Work-arounds: None. 8.12.10 Values cannot be represented exactly in the available mantissa bits 8.12.10.1 Problem Description: Converting an integer to IEEE S floating with software completion produces a denormal (i.e. very small) result value for very large integer values. These denormal values cannot be represented exactly in the available mantissa bits. The following C program demonstrates the problem : $ type test.c #include Page 105 main() { const float f1 = (float) 0x7fffffff; const float f2 = (float) 2147483647; const float f3 = (float) 2147483647.0; printf("f1 = %f\n", f1); printf("f2 = %f\n", f2); printf("f3 = %f\n", f3); return 0; } $ cc /float=ieee /ieee=denorm test $ link test $ run test f1 = 0.000000 f2 = 0.000000 f3 = 2147483648.000000 $ Note that any code using floating point constants to hold the float numbers, that is suffering from this bug, needs to be recompiled and relinked after the applying the new image. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION_MON.EXE 8.12.10.2 CLDs, SPRs, and QARs reporting this problem: 8.12.10.3 CLD(s) None. 8.12.10.4 QAR(s) 75-13-1032 8.12.10.5 Problem Analysis: See Problem Description 8.12.10.6 Work-arounds: None. Page 106 8.12.11 "ASSERTFAIL, System ASSERT failure detected" bugcheck 8.12.11.1 Problem Description: Callers to IO_PERFORM that have not provided an astprm when they completed IO_SETUP can cause the system to crash. The timing of this problem is such that it has only happened when XFC is being used. The crash typically occurs in CACHE$RESUME, in XFC, when a FASTIO IRP is one which XFC has already dismissed. Crashdump Summary Information ----------------------------- Bugcheck Type: ASSERTFAIL, System ASSERT failure detected Current Process: ORA_PRSPC3267 Current Image: $1$DGA2:[ORACLE.V734.RDBMS]SRV.EXE Failing PC: FFFFFFFF.802DE6B0 CACHE$RESUME_C+00AC0 Failing PS: 10000000.00000804 Module: SYS$XFCACHE (Link Date/Time: 15-JUL-2002 16:07:47.11) Offset: 000246B0 Stack Pointers: KSP = 00000000.7FFA1E90 ESP = 00000000.7FFA6000 SSP = 00000000.7FFAC100 USP = 00000000.7AF19DC0 Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE 8.12.11.2 CLDs, SPRs, and QARs reporting this problem: 8.12.11.3 CLD(s) 70-3-6247,70-3-6326,70-4-6487,70-3-6584,70-3-6849 8.12.11.4 QAR(s) None. 8.12.11.5 Problem Analysis: If an AST routine is not supplied to $IO_SETUP, it cannot be known exactly when that I/O is complete. Since IRPs used for FASTIOs are reusable, this can be a problem. Page 107 8.12.11.6 Work-arounds: None. 8.12.12 Fibre channel disks may not all failover, and may hang. 8.12.12.1 Problem Description: In the case where a fibre channel switch is disabled and the votes from a fibre channel quorum disk are required to maintain quorum, fibre channel disks may not all failover, and may hang. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE 8.12.12.2 CLDs, SPRs, and QARs reporting this problem: 8.12.12.3 CLD(s) 70-3-6902 8.12.12.4 QAR(s) None. 8.12.12.5 Problem Analysis: When quorum is lost, EXE$CLUTRANIO attempts to start mount verification to freeze the initiation of any pending I/O. If a device is busy, i.e. UCB$V_BSY is set, EXE$CLUTRANIO cannot assume that the driver can handle an immediate call to EXE$MOUNT_VER. So, instead, it sets UCB$V_MNTVERPND and UCB$V_MNTVERIP and relies on IOC$REQCOM to initiate mount verification on the completion of the next I/O. Unfortunately, there is a circumstance when the UCB$V_MNTVERPND condition does not work as expected. If the active I/O on the device fails and the I/O not otherwise eligible for mount verification, UCB$V_MNTVERPND will not trigger mount verification and it will be "lost. Since mount verification is what triggers multipath failover, the affected devices can get hung on a failed path. Page 108 8.12.12.6 Work-arounds: None. 8.12.13 System crash when HSM is running in the system. 8.12.13.1 Problem Description: The system can crash when HSM is running in the system. The crash indicates that DIOCNT is larger than DIOLMT. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE 8.12.13.2 CLDs, SPRs, and QARs reporting this problem: 8.12.13.3 CLD(s) None. 8.12.13.4 QAR(s) None. 8.12.13.5 Problem Analysis: If the cache_resume bit is set in IRP, iociopst increases the DIOCNT. Cache$resumes also increases the DIOCNT, which causes DIOCNT to be more than DIOLMT. 8.12.13.6 Work-arounds: None. 8.13 Problems addressed in VMS73_SYS-V0500 kit 8.13.1 A process hang in RWSCS state. 8.13.1.1 Problem Description: On a multi-processor machine, in a small cluster, when creating or updating a clusterwide logical name, a process may hang in RWSCS state. Images Affected: Page 109 - [SYS$LDR]SYS$CLUSTER.EXE 8.13.1.2 CLDs, SPRs, and QARs reporting this problem: 8.13.1.3 CLD(s) 70-3-5763,cfs.90906 8.13.1.4 QAR(s) None. 8.13.1.5 Problem Analysis: An incorrect assumption was made that message completion could not happen prior to return from a called routine which schedules the RWSCS wait state. This fix removes the SCHED spinlock before releasing SCS spinlock on code paths which could exhibit the problem. 8.13.1.6 Work-arounds: None. 8.13.2 System can crash with a BADDALRQSZ bugcheck in EXE$DEANONPGDSIZ_C 8.13.2.1 Problem Description: The system can crash with a BADDALRQSZ bugcheck in EXE$DEANONPGDSIZ_C. In some, but not all cases, the current process is CLUSTER_SERVER. In cases where the current process is not CLUSTER_SERVER, the stack will have addresses in EXE$CSP_BRDCST and EXE$ALLOC_CSD. Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE 8.13.2.2 CLDs, SPRs, and QARs reporting this problem: Page 110 8.13.2.3 CLD(s) None. 8.13.2.4 QAR(s) 75-13-861, 75-22-197 8.13.2.5 Problem Analysis: The crash occurs following an attempt to deallocate a structure whose W_SIZE offset contains 0. 8.13.2.6 Work-arounds: None. 8.13.3 F$GETSYI('RAD_MAX_RADS',node)fails to get the information from the specified node. 8.13.3.1 Problem Description: F$GETSYI('RAD_MAX_RADS',node) fails to get the information from the specified node. Instead, the command returns information from the current node the command is executing on. Note that with OpenVMS versions before V7.3-1, RAD_MAX_RADS will return 1 if there is no RAD support, and will return 8 no matter how many QBBs are physically present. This limitation was documented in the V7.2-1H1R New Features and Release Notes, June 2000, section 3.5.6.1. Images Affected: - [SYS$LDR]SYSGETSYI.EXE 8.13.3.2 CLDs, SPRs, and QARs reporting this problem: 8.13.3.3 CLD(s) CFS.89598 Page 111 8.13.3.4 QAR(s) None. 8.13.3.5 Problem Analysis: The problem is due to a simple coding error. To correct the error the code will now check to see if the command specifies a remote node, and if so, then get the information from that node rather than returning information from the current node. 8.13.3.6 Work-arounds: None. 8.13.4 System can crash with a FILCNTNONZ bugcheck 8.13.4.1 Problem Description: The system can crash with a FILCNTNONZ bugcheck. CrashDump Summary ----------------- Bugcheck Type: FILCNTNONZ, Open file count nonzero after process rundown Current Image: Failing PC: FFFFFFFF.D269A360 PROCESS_MANAGEMENT+3C360 Failing PS: 18000000.00000000 Module: PROCESS_MANAGEMENT (Link Date/Time: 18-OCT-2000 07:01:30.44) Offset: 0003C360 Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]SYS$CLUSTER.EXE 8.13.4.2 CLDs, SPRs, and QARs reporting this problem: Page 112 8.13.4.3 CLD(s) CFS.84385 8.13.4.4 QAR(s) None. 8.13.4.5 Problem Analysis: There is a lingering bug which causes occasional FILCNTNONZ bugchecks, which cause perhaps 3 or 4 problem escalations each year. Most of these cases have a channel open which cannot be closed because the channel number, stored at CCB$L_CHAN in the channel control block, has been overwritten by a zero. The mechanism which causes this has not been identified. Over the past two years diagnostic images have been run at several customer sites to try to track down when and how this happens. So far we have come up empty. Since virtually all of the crashes showed the corrupted channel was used for I/O on a section file, and most appeared to be shareable images (when the FID was tracked down to get the filespec),the diagnostic code was included in the image activator, as well as in SYSRUNDWN. All of the corruption detected was caught by the image rundown code. With increasing customer pressure to solve the problem, efforts to identify this mechanism have stopped. This fix will simply detect the problem, and using the same code in a neighboring routine it will recompute the channel number and repair the CCB, thus allowing the channel to be closed. 8.13.4.6 Work-arounds: None. 8.13.5 System can crash with a CWLNMERR bugcheck 8.13.5.1 Problem Description: The system can crash with a CWLNMERR bugcheck. The failing PC is in the LOGICAL_NAMES executive image. Images Affected: - [SYS$LDR]LOGICAL_NAMES.EXE - [SYS$LDR]LOGICAL_NAMES.STB Page 113 8.13.5.2 CLDs, SPRs, and QARs reporting this problem: 8.13.5.3 CLD(s) None. 8.13.5.4 QAR(s) 75-13-871 8.13.5.5 Problem Analysis: To do a clusterwide logical name operation, $ENQW is requested to lock the cwlogical name resource. Any error is totally unexpected and inexplicable, so the service crashes in response. A process in a job with no ENQCNT quota can cause an $ENQW failure, causing the crash. 8.13.5.6 Work-arounds: None. 8.13.6 Program using C signals can be aborted with the condition code set to the C signal value. 8.13.6.1 Problem Description: A program using C signals can be aborted with the condition code set to the C signal value. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION_MON.EXE 8.13.6.2 CLDs, SPRs, and QARs reporting this problem: 8.13.6.3 CLD(s) 70-3-5990,70-17-64,CFS.92523 8.13.6.4 QAR(s) None. Page 114 8.13.6.5 Problem Analysis: The code in OpenVMS condition handling that searches for a handler, srchandler,checks for exceptions within the dispatcher, sys$call_handl. It filters out signals, such as SS$_DEBUG, SS$_IMGDMP, and SS$_BREAK. It was not filtering C signals. When it encounters a C signal, srchandler branches to the badhandler code, which is fatal to the program. 8.13.6.6 Work-arounds: None. 8.13.7 System can crash with an SSRVEXCEPT, Unexpected system bugcheck at EXE$IO_PERFORM_C+00650 8.13.7.1 Problem Description: The system can crash with an SSRVEXCEPT, Unexpected system bugcheck at EXE$IO_PERFORM_C+00650 Crashdump Summary Information: ------------------------------ Bugcheck Type: SSRVEXCEPT, Unexpected system service exception Current Process: ORA_P10111B1238 Current Image: $1$DGA92:[A_ORACLE.ORACLEV7336.RDBMS]SRV.EXE Failing PC: FFFFFFFF.800CBEB0 EXE$IO_PERFORM_C+00650 Failing PS: 30000000.00000203 Module: IO_ROUTINES (Link Date/Time: 5-NOV-2001 11:49:25.01) Offset: 00017EB0 Failing Instruction: EXE$IO_PERFORM_C+00650: LDQ R18,#X0108(R18)\ Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE 8.13.7.2 CLDs, SPRs, and QARs reporting this problem: Page 115 8.13.7.3 CLD(s) 70-3-5965,CFS.92424 8.13.7.4 QAR(s) None. 8.13.7.5 Problem Analysis: A local variable was not initialized resulting in the crash. The correction for this problem is to fix the code path to store the correct information in this local variable. 8.13.7.6 Work-arounds: None. 8.13.8 User-written device driver can result in an SSREXCEPT bugcheck in MMG_STD$IOLOCK_BUF 8.13.8.1 Problem Description: An SSREXCEPT bugcheck in MMG_STD$IOLOCK_BUF if it must fault in the affected page. Section 2.2.1 of the OpenVMS Alpha Guide to Upgrading Privileged Code Applications describes how device drivers can lock down multiple I/O buffers using IRPEs with the EXE_STD$READLOCK, WRITELOCK, or MODIFYLOCK routines. Unfortunately, when an IRPE was passed in and the buffer required a page fault this code used the IRP$PS_FDT_CONTEXT offset on the IRPE, which is only valid on an IRP. The correction for this problem is to delay the use of the IRP$PS_FDT_CONTEXT cell until after the original IRP pointer has been restored by a call to the error call back routine. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.STB Page 116 8.13.8.2 CLDs, SPRs, and QARs reporting this problem: 8.13.8.3 CLD(s) CFS.92197 8.13.8.4 QAR(s) None. 8.13.8.5 Problem Analysis: See Problem Description 8.13.8.6 Work-arounds: None. 8.13.9 Process may hang waiting for the completion of an RMS $FLUSH operation. 8.13.9.1 Problem Description: If there is a lot of cluster-wide $GETJPI activity, a process may hang waiting for the completion of an RMS $FLUSH operation. The I/O request resulting from this may wait forever because the IOSB is not filled in. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE 8.13.9.2 CLDs, SPRs, and QARs reporting this problem: 8.13.9.3 CLD(s) CFS.83753,CFS.92041,CFS.92830 8.13.9.4 QAR(s) None. Page 117 8.13.9.5 Problem Analysis: The problem is highly dependent on timing. In the final stages of clusterwide $GETJPI processing an AST may become active, delivering the result of remote $GETJPI operations. At that time, it may also be needed to do some more local $GETJPI processing. For this to function properly, the previous mode in the PSL must be set to the mode of the thread invoking the original system service. This is to allow buffer probing to work correctly. What may happen however is that before we exit, another kernel AST is queued to our process. This AST is the result of RMS modifying a file, asking the XQP to do the work, and the XQP completing the I/O. Before the AST delivery code dismisses the AST it will notice that another kernel mode AST is pending, and allow that AST to run. That AST is then executing code in I/O post-processing filling in the final IOSB. Now, because RMS has an IOSB in its private space, protected as EW and because the previous mode is user due to the GETJPI processing, the probe checking the accessibility of the IOSB fails leaving the IOSB untouched and RMS waiting forever. 8.13.9.6 Work-arounds: None. 8.13.10 System that supports NUMA and has RAD_SUPPORT enabled, can crash with an INVEXCEPTN bugcheck 8.13.10.1 Problem Description: A system that supports NUMA and has RAD_SUPPORT enabled, can crash with an INVEXCEPTN bugcheck when the swapper is the current process. The failing PC is at or around MMG$WRTMFYPAG_C+006E4. Images Affected: - [SYS$LDR]SYS$VM.EXE 8.13.10.2 CLDs, SPRs, and QARs reporting this problem: Page 118 8.13.10.3 CLD(s) None. 8.13.10.4 QAR(s) 75-66-1366 8.13.10.5 Problem Analysis: The size of the GBLSEC_RADS array failed to take into account that more global sections can be created than indicated by the GBLSECTIONS SYSGEN parameter. The size of the GBLSEC_RADS array is now calculated based on the different between the end of the global section table and the last WSL entry for the system PHD. This calculation is larger than the value found in the GBLSECTIONS SYSGEN parameter and allows enough array entries for all possible global sections. 8.13.10.6 Work-arounds: None. 8.13.11 If a "space" pattern string is combined with an NEQ match qualifier, the expected results of all processes will not be returned. 8.13.11.1 Problem Description: If a "space" pattern string is combined with an NEQ match qualifier, the expected results of all processes will not be returned. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB Page 119 8.13.11.2 CLDs, SPRs, and QARs reporting this problem: 8.13.11.3 CLD(s) CFS.92971 8.13.11.4 QAR(s) None. 8.13.11.5 Problem Analysis: The problem occurred when a change to strip trailing blanks from the compare strings failed to take into account that a single space could also be used. The fix checks the length of the string after stripping the trailing spaces and if zero, a string length of 1 is used. 8.13.11.6 Work-arounds: None. 8.13.12 Lookup of a device may fail 8.13.12.1 Problem Description: Under some circumstances lookup of a device may fail. If the system doing the lookup has a zero allocation class specified, and attempts to access an MSCP-served disk by using the NODE$DUA form, the access may fail because the device will not be found. This can be seen in the following SET VOLUME/REBUILD DCL example (SHOW DEVICE fields have been edited for space reasons). $ SHOW DEVICE $8$DUA10 Device Device Error Volume Name Status Count Label $8$DUA10: (UTRAMP) Mounted alloc 0 TEST1 $ WRITE SYS$OUTPUT F$GETDVI("$8$DUA10:","EXISTS") TRUE $ $ WRITE SYS$OUTPUT F$GETDVI("$8$DUA10:","ROOTDEVNAM") _UTRAMP$DUA10: $ $ WRITE SYS$OUTPUT F$GETDVI("$8$DUA10:","DEVNAM") _UTRAMP$DUA10: $ $ WRITE SYS$OUTPUT F$GETDVI("_utramp$dua10:","EXISTS") Page 120 FALSE $ $ SET VOLUME/REBUILD $8$DUA10: %SET-E-NOTSET, error modifying _UTRAMP$DUA10: -RMS-F-DEV, error in device name or inappropriate device type for operation %SET-E-NOTSET, error modifying _UTRAMP$DUA10: -SYSTEM-W-NOSUCHDEV, no such device available A lookup via the runtime library function LIB$FIND_IMAGE_SYMBOL will also show the problem. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE 8.13.12.2 CLDs, SPRs, and QARs reporting this problem: 8.13.12.3 CLD(s) CFS.90852 8.13.12.4 QAR(s) None. 8.13.12.5 Problem Analysis: The root of the problem (DDB's without any units attached) will be covered in SYS$DUDRIVER at a later time, but it was determined that there are two places where we could improve things now. One is in IOC_STD$SEARCHINT which does not look any further if it encounters a DDB without any units attached to it. The other thing is that SYS$GETDVI's item codes DVI$_ROOTDEVNAM and DVI$_NEXTDEVNAM return DVI$_DEVNAMDEVNAM which in reality should be DVI$_FULLEVNAM. 8.13.12.6 Work-arounds: None. Page 121 8.13.13 Starting up Pathworks Advanced server may fail with a SS$_BADPARAM error 8.13.13.1 Problem Description: PWRK$STREAMSOS_V7.EXE is a big file, about 1760 blocks in size. If this file has become very fragmented after installation then Advanced server startup may fail with a SS$_BADPARAM error. This can occur if PWRK$STREAMSOS_V7.EXE is heavily fragmented and has multiple file headers (the following example has been modified for space reasons): $ @sys$startup:pwrk$startup The file server will use DECnet, TCP/IP. Advanced Server mail notification will use DECnet. %SYSTEM-F-BADPARAM, bad parameter value %TRACE-F-TRACEBACK, symbolic stack dump follows image module routine line PWRK$LOADSTREAMS_V7 LOAD main 7822 rel PC abs PC 000000000000213C 000000000003213C image module routine line PWRK$LOADSTREAMS_V7 LOAD __main 0 rel PC abs PC 0000000000000070 0000000000030070 image module routine line 0 rel PC abs PC FFFFFFFF802653B4 FFFFFFFF802653B4 Images Affected: - [SYS$LDR]SYSLDR_DYN.EXE 8.13.13.2 CLDs, SPRs, and QARs reporting this problem: 8.13.13.3 CLD(s) None. Page 122 8.13.13.4 QAR(s) 75-13-893 8.13.13.5 Problem Analysis: The system module is loaded via a call to LDR$LOAD_IMAGE, which opens the file in question with cathedral windows so that all mapping pointers are available. If the file is loaded after the system startup has completed, then the XQP is used so that a multi-header file should not be an issue. There is, however, one problem in that the loader calculates the size of a file in routine GET_FILE_LENGTH in [SYS]SYSLDR_COMMON.MAR, which is only looking at the first WCB created for the file. For a multi-header file, multiple WCB's may be created which are not taken into account. The result is that routine PROCESS_GST needs the file length which is used to calculate the number of PTE's to allocate for the GST, If the file length is short because not all the WCB's have been looked at, the allocation turns out to be negative which causes LDR_STD$ALLOC_S0S1_VA to return SS$_BADPARAM. 8.13.13.6 Work-arounds: None. 8.13.14 System can crash with a SSRVEXCEPT bugcheck 8.13.14.1 Problem Description: The system can crash with a SSRVEXCEPT bugcheck when an image exits before the $BRKTHRU has been delivered to some of its targets. Crash Dump Summary: ------------------- Bugcheck Type: SSRVEXCEPT, Unexpected system service exception Current Process: SDNCC_MBX_MAIN Current Image: Failing PC: FFFFFFFF.98B56AAC IO_ROUTINES+46AAC Failing PS: 00000000.00000000 Module: IO_ROUTINES (Link Date/Time: 17-MAR-2001 03:30:01.24) Offset: 00046AAC Signal Array: 64-bit Signal Array: Arg Count = 00000005 Arg Count = 00000005 Condition = 0000000C Condition = 00000000.0000000C Argument #2 = 00000000 Argument #2 = 00000000.00000000 Argument #3 = 006C41D0 Argument #3 = 00000000.006C41D0 Argument #4 = 98B56AAC Argument #4 = FFFFFFFF.98B56AAC Page 123 Argument #5 = 00000000 Argument #5 = 00000000.00000000 Failing Instruction: IO_ROUTINES+46AAC: LDL R6,(R7) Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 8.13.14.2 CLDs, SPRs, and QARs reporting this problem: 8.13.14.3 CLD(s) CFS.70569, CFS.86451 8.13.14.4 QAR(s) None. 8.13.14.5 Problem Analysis: $BRKTHRU is asynchronous and, since terminal/display devices are much slower than contemporary CPUs, may take a long time to finish its work, To avoid errors caused by insufficient P1 pool space (insufficient CTLPAGES for the demands on a given system), $BRKTHRU uses EXE$ALOP1IMAG to allocate from P1 pool if available. If it is not, it then allocates from P0 space. Image rundown does nothing to the P1 pool but will deallocate all of P0 space, including any allocations made by EXE$ALOP1IMAG. With some attention to loading down the terminal or display devices, one can manage to get through image rundown (at least past P0 teardown) before one of the $BRKTHRU requests has finished. With the BRK$ packet stored in a suddenly-deallocated page, the $BRKTHRU code gets an access violation, which translates to a SSRVEXCEPT crash. 8.13.14.6 Work-arounds: None. Page 124 8.13.15 Entering an empty path into a SET DEVICE/SWITCH/PATH command can crash the system 8.13.15.1 Problem Description: Entering an empty path into a SET DEVICE/SWITCH/PATH command, such as: SET DEVICE/SWITCH/PATH ="" will cause the system to bugcheck. The SET_DEVICE system service used with a zero path length will also cause the system to crash. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: SYSTEM Current Image: $1$DGA100:[SYS7.SYSCOMMON.] [SYSEXE]SET.EXE Failing PC: FFFFFFFF.803A7050 MPDEV$MANUAL_SWITCH_C+00290 Failing PS: 10000000.00000803 Module: MULTIPATH (Link Date/Time: 18-JUN-2002 08:04:33.18) Offset: 00001050 Stack Pointers: KSP = 00000000.7FFA1BA8 ESP = 00000000.7FFA6000 SSP = 00000000.7FFAC100 USP = 00000000.7AE9B5B0 Failing Instruction: MPDEV$MANUAL_SWITCH_C+00290: LDL R17,#X0010(R6) Images Affected: - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB - [SYS$LDR]MULTIPATH_MON.EXE - [SYS$LDR]MULTIPATH_MON.STB 8.13.15.2 CLDs, SPRs, and QARs reporting this problem: 8.13.15.3 CLD(s) None. Page 125 8.13.15.4 QAR(s) 75-66-1401 8.13.15.5 Problem Analysis: The fix is to check if the path length is valid. If it is not, return an error status. 8.13.15.6 Work-arounds: None. 8.13.16 When using $GETJPI to request rightslist information about a process, incorrect information is returned. 8.13.16.1 Problem Description: If a process uses $GETJPI to request rightslist information about itself then the information appears to be correct. However, if another process uses $GETJPI to get rightslist information about that same process then the information returned is incorrect. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 8.13.16.2 CLDs, SPRs, and QARs reporting this problem: 8.13.16.3 CLD(s) CFS.92887 8.13.16.4 QAR(s) None. Page 126 8.13.16.5 Problem Analysis: $GETJPI does not properly handle PSB segmented data for remote processes. The result is incomplete data being returned to the caller. This change employs a loop which continues to copy segmented data until all of it has been transferred to the users buffer. 8.13.16.6 Work-arounds: None. 8.13.17 Lock manager and nonpaged pool usage may increase over time. 8.13.17.1 Problem Description: Lock manager and nonpaged pool usage may increase over time due to a memory leak of lock blocks (LKB) and AST control blocks (ACB64). This lock manager leak only occurs under very specific circumstances which are not that common. The specific circumstances are the $DEQ of a process based lock with a pending completion AST that has not yet been delivered. Images Affected: - [SYS$LDR]LOCKING.EXE - [SYS$LDR]LOCKING.STB 8.13.17.2 CLDs, SPRs, and QARs reporting this problem: 8.13.17.3 CLD(s) 70-3-5967,CFS.92447 8.13.17.4 QAR(s) None. 8.13.17.5 Problem Analysis: Under certain conditions, LKBs were not placed on the cache by the LOCK_KAST routine when the Pending Cache bit was set. Within LOCK_KAST, the NODELETE bit of the ACB is tested instead of the LKB. When dequeueing a lock without an outstanding completion AST, the PCACHE bit is set in the LKB and the NODELETE bit is cleared. The NODELETE bit in the ACB is not cleared at this point. Page 127 To correct this problem, change code in LOCK_KAST to test the LKB bit as opposed to the ACB bit. Also, if NODELETE is cleared, copy the RMOD byte from the LKB to the ACB so ASTDEL will delete the ACB. 8.13.17.6 Work-arounds: None. 8.13.18 A call to SYS$GETSYI to return system rights will only return the first right in the rightslist. 8.13.18.1 Problem Description: A call to SYS$GETSYI to return system rights will only return the first right in the rightslist, regardless of how many rights are in the list. Images Affected: - [SYS$LDR]SYSGETSYI.EXE 8.13.18.2 CLDs, SPRs, and QARs reporting this problem: 8.13.18.3 CLD(s) CFS.92887 8.13.18.4 QAR(s) None. 8.13.18.5 Problem Analysis: The routine, SPC_SYSTEM_RIGHTS, only returned a single right because the register to hold the data length, R3, was preserved across the call. The value of R3 coming into the routine was always 8. R3 would be updated with the right length in the routine, but would then be restored with its original value upon returning to the caller. The fix is to adjust the register masks for input/output/reserve such that R3 is no longer preserved across the call. Page 128 8.13.18.6 Work-arounds: None. 8.13.19 Use of SPAWN or DCL PIPE commands result in the increase of the process 'PAGFILCNT (JIB$L_PGFLCNT). 8.13.19.1 Problem Description: Use of SPAWN or DCL PIPE commands result in the increase of the process' PAGFILCNT (JIB$L_PGFLCNT). The more SPAWN or PIPE activity, the higher the PAGFILCNT grows. Images Affected: - [SYS$LDR]SHELL8K.EXE 8.13.19.2 CLDs, SPRs, and QARs reporting this problem: 8.13.19.3 CLD(s) CFS.93928 8.13.19.4 QAR(s) None. 8.13.19.5 Problem Analysis: See Problem Analysis 8.13.19.6 Work-arounds: None. 8.13.20 System can crash with a WSLXVANMAT bugcheck during image rundown. 8.13.20.1 Problem Description: If a global section follows a process section in process P0 space with the same section index value, the system can crash with a WSLXVANMAT bugcheck during image rundown. Crash Information: ------------------ Bugcheck Type: WSLXVANMAT, Working set list entry does not match VA Failing PC: FFFFFFFF.8016FEF0 SYS$VM+25EF0 Page 129 R1 = 00000000.00000000 Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 8.13.20.2 CLDs, SPRs, and QARs reporting this problem: 8.13.20.3 CLD(s) CFS.92670,70-3-5998,CFS.91933,70-3-5893 8.13.20.4 QAR(s) None. 8.13.20.5 Problem Analysis: The "same section" check in DELETE_CLUSTER did not take into account that a global section could be following a process section with both having the same section index value. This could cause DELPAG_NOWRTREQ to be called with a global page. As PFN$L_WSLX_QW for a global page is not a Working Set List Index, but a counter for the number of times the page has been locked into memory (see IDSM Chapter 16.2.7), this will cause a WSLXVANMAT bugcheck. The reason is that the VA part of the WSLE indexed by R1 = PFN$L_WSLX_QW = 0 is not equal to the VA of the page to be deleted. The fix is to explicitly check for the page type in DELETE_CLUSTER and exit the rdonly_loop if the current page is not a process page. 8.13.20.6 Work-arounds: None. 8.13.21 Multiprocessors making heavy use of RMS global buffers could encounter a variety of system crashes Page 130 8.13.21.1 Problem Description: Multiprocessors making heavy use of RMS global buffers could encounter a variety of system crashes related to a corrupted system buffer object list, PCB$Q_BUFOBJ_LIST off of the system PCB (process control block). These could include things such as: o SSRVEXCEPTN at MMG_STD$INSERT_BOD_C+2C o INVEXCEPTN at EXE$DELETE_BUFOBJ_C+1C0 o Nonpaged pool corruption involving BOD sized packets and lists o CPUSPINWAIT due to pool corruption with TQE list o Global Buffered File access getting SYS-F-IVLOCKID errors Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 8.13.21.2 CLDs, SPRs, and QARs reporting this problem: 8.13.21.3 CLD(s) CFS.93787,CFS.93119,CFS.93436 8.13.21.4 QAR(s) None. 8.13.21.5 Problem Analysis: There could be conflicts accessing the list when it is for the system PCB (as RMS uses the system wide buffer objects for its global buffers. The fix is to protect the PCB, that is being added or removed, with the MMG spinlock. The removal code (DELETE_BUFOBJ_INT) already uses this spinlock. Page 131 8.13.21.6 Work-arounds: None. 8.13.22 System crash with an INVEXCEPTN, Exception while above ASTDEL bugcheck 8.13.22.1 Problem Description: When the lock manager is unable to obtain physical memory to allocate an RSB, the error path to return an insufficient memory error may result in a system crash. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Failing PC: FFFFFFFF.80184888 RSDM_OSR_PREPROCESS_C+00658 Failing PS: 18000000.00000804 Module: LOCKING (Link Date/Time: 28-MAR-2002 09:11:25.76) Offset: 00004888 Failing Instruction: RSDM_OSR_PREPROCESS_C+00658: LDL R23,#X00C0(R5) Images Affected: - [SYS$LDR]LOCKING.EXE - [SYS$LDR]LOCKING.STB 8.13.22.2 CLDs, SPRs, and QARs reporting this problem: 8.13.22.3 CLD(s) 70-3-6180,CFS.93936 8.13.22.4 QAR(s) None. 8.13.22.5 Problem Analysis: After allocating an LKB, the address of the LCKCTX block is placed into the LKB. If the LKB was not initially allocated but succeeded via the fill_cache routine, the routine continues without putting the address of the LCKCTX block in the LKB until later. If however, an RSB was not allocated, the error path assumed the LKB already Page 132 had the address of the LCKCTX block and thus crashed. 8.13.22.6 Work-arounds: None. 8.13.23 Process can exit with the status SYS$_UNWIND (920) 8.13.23.1 Problem Description: A process can exit with the status SYS$_UNWIND (920). If this is a detached process, this error status can be seen in the accounting report by executing the command: $ account /since=time/before=time where time is the time the detached process exited. This problem can affect Oracle 9i RAC LMS processes such that the Oracle instance crashes with the error ORA-00484. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB 8.13.23.2 CLDs, SPRs, and QARs reporting this problem: 8.13.23.3 CLD(s) None. 8.13.23.4 QAR(s) None. 8.13.23.5 Problem Analysis: The exception handler goto_unwind_handler in module [SYS]SYSUNWIND.MAR did not expect exceptions that are actually signals coming from another process. It treated such a signal as an error condition and called SYS$EXIT. To fix the problem, in the exception handler, goto_unwind_handler, test for signals from other processes. These are SS$_DEBUG, SS$_IMGDMP, and C signals. If the condition is one of these, resignal the condition instead of calling SYS$EXIT. Page 133 8.13.23.6 Work-arounds: None. 8.13.24 A system can hang or crash with an INVEXCEPTN bugcheck 8.13.24.1 Problem Description: The symptoms of this problem can take several different forms, including exception bugchecks and forced crashes of hung systems. Crashes have occurred at PC = PROCESS_MANAGEMENT+0AAF8 = SCH$ONE_SEC_C+00258 in module [SYS]RSE and at PC = LOCKING+0ADE0 = LCK$QUEUEWAIT_C+00050 in module [SYS]SYSENQDEQ. Crashdump Summary Information: ------------------------------ Bugcheck Type: OPERCRASH, Operator forced system crash Current Process: NULL Current Image: Failing PC: FFFFFFFF.8013813C SCH$CLASS_IDLE_C+000BC Failing PS: 00000000.00000003 Module: PROCESS_MANAGEMENT (Link Date/Time: 28-MAR-2002 14:21:36.47) Offset: 0003213C Failing Instruction: SCH$CLASS_IDLE_C+000BC: CMPLE R2,#X3F,R7 Crashdump Summary Information: ------------------------------ Bugcheck Type: OPERCRASH, Operator forced system crash Current Process: NULL Current Image: Failing PC: FFFFFFFF.92637FC8 Failing PS: 00000000.00001504 Module: Offset: 00000000 Failing Instruction: FFFFFFFF.92637FC8: BR R31,#XFFFF9F Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE Page 134 8.13.24.2 CLDs, SPRs, and QARs reporting this problem: 8.13.24.3 CLD(s) CFS.92144,CFS.93253 8.13.24.4 QAR(s) None. 8.13.24.5 Problem Analysis: After deallocating the JIB, due to an error during creation of a detached class scheduled process, register R4 was not reset to the current PCB in routine ABORT in module SYSCREPRC. 8.13.24.6 Work-arounds: None. 8.14 Problems addressed in VMS73_SYS-V0400 kit 8.14.1 V7.3 nodes do not correctly handle Quorum Disks 8.14.1.1 Problem Description: V7.3 nodes do not correctly handle Quorum Disks. The issues can result in either CLUEXIT bugchecks or numerous connection manager console messages: %CNXMAN, Proposing modification of quorum or quorum disk membership Any cluster with a quorum disk and V7.3 nodes requires this fix. Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE 8.14.1.2 CLDs, SPRs, and QARs reporting this problem: Page 135 8.14.1.3 CLD(s) 70-3-5396,CFS.88544,70-3-5457,CFS.88899 8.14.1.4 QAR(s) None. 8.14.1.5 Problem Analysis: When building the cluster status message, the CSB$L_STATUS bit should be tested to determine if the QF_NOACCESS bit should be set or cleared in the message. The code was testing the incorrect bit. When a status message is received, whether the quorum disks are the same should be validated unless QF_SAME is already set. A change in V7.3 did not validate if QF_SAME or QF_NOACCESS was set. This resulted in the QF_SAME bit not getting set when it should have. 8.14.1.6 Work-arounds: None. 8.14.2 SDA can ACCVIO when the SHOW LOCK/POOL command is issued. 8.14.2.1 Problem Description: SDA can ACCVIO when the SHOW LOCK/POOL command is issued. SDA> SHOW LOCK/POOL/SUMMARY %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000678472, PC=0000000000144070, PS=0000001B Images Affected: - [SYSLIB]SDA$SHARE.EXE 8.14.2.2 CLDs, SPRs, and QARs reporting this problem: Page 136 8.14.2.3 CLD(s) 70-3-5515 8.14.2.4 QAR(s) None. 8.14.2.5 Problem Analysis: When analyzing the running system and there is lots of lock activity, the poolzone can be changing while it's being looked at. SDA was blindly grabbing data and using it. 8.14.2.6 Work-arounds: None. 8.14.3 UCB$L_OPCNT in the primary path UCB incorrectly incremented 8.14.3.1 Problem Description: Doing I/O on a multipath device, when the current path is a secondary, results in an increase in the UCB$L_OPCNT in the primary as well as the current path UCB. Although the UCB$L_OPCNT in the secondary grows faster than in the primary, the UCB$L_OPCNT in the primary should not be changing (except, at most by once per second for polling.) This is easily observed when doing a DIR/SIZE on the system disk. A number of customers and third-parties rely on these counters to be accurate in their performance and capacity planning tools. Images Affected: - SYS$LDR]IO_ROUTINES.EXE - SYS$LDR]IO_ROUTINES_MON.EXE - SYS$LDR]IO_ROUTINES.STB - SYS$LDR]IO_ROUTINES_MON.STB Page 137 8.14.3.2 CLDs, SPRs, and QARs reporting this problem: 8.14.3.3 CLD(s) None. 8.14.3.4 QAR(s) 75-66-826 8.14.3.5 Problem Analysis: See problem Description. 8.14.3.6 Work-arounds: None. 8.14.4 SSRVEXCEPT, Unexpected system service bugcheck 8.14.4.1 Problem Description: The Lock Manager can deliver a blocking AST to the system owned locks incorrectly. The window of opportunity for this to occur is very small, but if it happens, the system will often crash with an Invalid exception error. Crashdump Summary Information: ------------------------------ Bugcheck Type: SSRVEXCEPT, Unexpected system service exception Failing PC: FFFFFFFF.802059E8 XQP$FCBSTALE_C Failing PS: 00000000.00000000 Module: F11BXQP (Link Date/Time: 17-MAR-2001 03:16:47.08) Offset: 0000D9E8 Images Affected: - [SYS$LDR]LOCKING.EXE 8.14.4.2 CLDs, SPRs, and QARs reporting this problem: Page 138 8.14.4.3 CLD(s) CFS.90620,CFS.90999 8.14.4.4 QAR(s) None. 8.14.4.5 Problem Analysis: See problem Description. 8.14.4.6 Work-arounds: None. 8.14.5 SYS$COMMON:[SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT not updated correctly 8.14.5.1 Problem Description: During installation of an OpenVMS ECO kit, the names of the installed images are written to SYS$COMMON:[SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT. These file names should be written with _OLD appended to the end of the filename along with the name of the kit. The VMS73_SYS-V0300 ECO kit did not do this editing correctly. When upgrading from V7.3 to a later version of OpenVMS, operating system files from the previous version of OpenVMS are deleted. The above file name errors will cause old operating system files to be left on the system after the upgrade. In addition, users will see multiple instances of the following installation warning message during the upgrade: [SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT %UPGRADE-W-NOTOLD2, does not have "_OLD" at end %UPGRADE-W-NOTOLD2, file not deleted This change corrects the filenames in [SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT. Images Affected: - [SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT Page 139 8.14.5.2 CLDs, SPRs, and QARs reporting this problem: 8.14.5.3 CLD(s) None. 8.14.5.4 QAR(s) None. 8.14.5.5 Problem Analysis: See Problem Description 8.14.5.6 Work-arounds: None. 8.15 Problems addressed in VMS73_SYS-V0300 kit 8.15.1 Commands do not change the path to the disk 8.15.1.1 Problem Description: The following command should change the path to the disk: $SET DEVICE/SWITCH/PATH= Sometimes it does not. Images Affected: - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB 8.15.1.2 CLDs, SPRs, and QARs reporting this problem: 8.15.1.3 CLD(s) 70-3-4607 8.15.1.4 QAR(s) None. Page 140 8.15.1.5 Problem Analysis: The routine that sets up the trigger for the switch to happen (trigger pulled by mount verification) loops through all UCBs for that device and sets the "path verification already tried" bit. In the command to force it to be tried first, the routine did not assure that the bit was clear for the path specified. Thus, if two set path commands for different paths are issued without an intervening mount verify (to switch paths), all paths look like they have been tried. This causes MULTIPATH to start trying paths beginning with the one that is currently open. 8.15.1.6 Work-arounds: None. 8.15.2 System hang with many processes in MUTEX wait state 8.15.2.1 Problem Description: A system can hang with many processes in MUTEX wait state. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.STB 8.15.2.2 CLDs, SPRs, and QARs reporting this problem: 8.15.2.3 CLD(s) CFS.84188 8.15.2.4 QAR(s) None. Page 141 8.15.2.5 Problem Analysis: The number of free blocks associated with normal volumes is kept in a resource value block of the volume lock ID. The routine EXE$DVI_FREEBLOCKS calls the $GETLKI system service to obtain the value block for the volume lock. Certain types of devices such as DNFS devices do not utilize a volume lock and have a zero in this field. The EXE$DVI_FREEBLOCKS still calls the $GETLKI system service with the lock ID as 0. This translates to a wildcard system service and $GETLKI returns data on the very first lock ID it finds. If this lock happens to be a process based lock and the process has not yet joined the default resource domain, the $GETLKI routine will try and do so. This action requires the IO Mutex. However, since the SHOW DEVICE code already acquired the mutex, the process is placed in a MUTEX wait state and the IO MUTEX will never be released. 8.15.2.6 Work-arounds: None. 8.15.3 Improve Pool Expansion Failure handing on AlphaSerever GS-series 8.15.3.1 Problem Description: On Alphaserver GS-series machines running OpenVMS V7.3, after several console messages indicating pool expansion failure, the system may hang, or crash with CPUSPINWAIT or CPUSANITY bugchecks. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MON.STB - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MON.STB 8.15.3.2 CLDs, SPRs, and QARs reporting this problem: Page 142 8.15.3.3 CLD(s) None. 8.15.3.4 QAR(s) None. 8.15.3.5 Problem Analysis: A change in the design of non-paged pool to cause multiple pools changed the way a console output routine can be called. Before it could only be called once. Now it may be called simultaneously multiple times. It is not designed for that. 8.15.3.6 Work-arounds: None. 8.15.4 F$PID lexical function returns the wrong PID 8.15.4.1 Problem Description: The F$PID lexical function in DCL does not work as expected when the user running the procedure does not have sufficient privilege to examine other processes. The result may be that process selection in combination with F$CONTEXT returns the wrong PID. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 8.15.4.2 CLDs, SPRs, and QARs reporting this problem: 8.15.4.3 CLD(s) CFS.83670. Page 143 8.15.4.4 QAR(s) None. 8.15.4.5 Problem Analysis: See Problem Description 8.15.4.6 Work-arounds: None. 8.15.5 System crash with INVEXCEPTN, Exception while above ASTDEL bugcheck 8.15.5.1 Problem Description: The system can crash with an INVEXCEPTN, Exception while above ASTDEL bugcheck: Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: SWAPPER Current Image: Failing PC: FFFFFFFF.80115E0C SCH$REPORT_EVENT_C+0082C Failing PS: 10000000.00000800 Module: PROCESS_MANAGEMENT (Link Date/Time: 6-JUN-2001 17:31:27.58) Offset: 00009E0C Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 8.15.5.2 CLDs, SPRs, and QARs reporting this problem: Page 144 8.15.5.3 CLD(s) None. 8.15.5.4 QAR(s) 75-45-2616,75-45-2619,75-45-2621,75-76-111 8.15.5.5 Problem Analysis: This is a day 1 bug in kernel thread support. It shows up only under extreme conditions when new process header pages cannot be locked into the working set because the working set itself is extremely confined. This condition can be caused when the system is artificially forced into very heavy swapping with a small value of SWPOUTPGCNT. When this locking into the working set fails, we return the already allocated thread pages and the vector pointing to them. However, the PCB had already been updated to point at the vector. This corruption can later on lead to a variety of symptoms. 8.15.5.6 Work-arounds: None. 8.15.6 Relax MOUNT and Mount Verification sanity checks 8.15.6.1 Problem Description: MOUNT and Mount Verification sanity checks have been relaxed to correct the following issues: o A MOUNT/NOWRITE command on a disk on one cluster will now work correctly even if the disk is mounted with a /WRITE qualifier on another cluster in the SAN (Storage Area Network). Previously, depending on the order in which the mounts were executed, the mount would fail with the error message: DIFVOLMNT - different volume already mounted on this device. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE Page 145 - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.STB 8.15.6.2 CLDs, SPRs, and QARs reporting this problem: 8.15.6.3 CLD(s) 70-3-4593, CFS.83449 8.15.6.4 QAR(s) None. 8.15.6.5 Problem Analysis: Customers have requested that MOUNT and Mount Verification relax their sanity checks on volumes that are mounted /NOWRITE. The primary use of this seems to be that within a SAN, the customers want the ability to MOUNT/NOWRITE a disk from one (or more) clusters while it is MOUNT/WRITEable on another cluster. Depending on the order of the MOUNTs. MOUNT and MountVerification would fail on the /NOWRITE cluster because the SCB is updated by the /WRITE cluster. 8.15.6.6 Work-arounds: None. 8.15.7 Queue and other clusterwide operations fail. with SS$_BADPARAM 8.15.7.1 Problem Description: Queue and other clusterwide operations fail with a SS$_BADPARAM bugcheck when a COE-baselevel node is in the cluster. Images Affected: - [SYSLIB]SECURESHR.EXE - [SYSLIB]SECURESHRP.EXE Page 146 8.15.7.2 CLDs, SPRs, and QARs reporting this problem: 8.15.7.3 CLD(s) None. 8.15.7.4 QAR(s) 75-61-923 8.15.7.5 Problem Analysis: The TLV mechanism is not extensible. 8.15.7.6 Work-arounds: None. 8.15.8 ACCVIOs are returned from SYS$PERSONA_CREATE. 8.15.8.1 Problem Description: When called from exec mode, ACCVIOs are returned from SYS$PERSONA_CREATE. Images Affected: - [SYSLIB]SECURESHR.EXE - [SYSLIB]SECURESHRP.EXE 8.15.8.2 CLDs, SPRs, and QARs reporting this problem: 8.15.8.3 CLD(s) None. 8.15.8.4 QAR(s) 75-13-771 8.15.8.5 Problem Analysis: The $PROBE macro always maximizes with PRVMOD. Page 147 8.15.8.6 Work-arounds: None. 8.15.9 SSRVEXCEPT system crash 8.15.9.1 Problem Description: A SSRVEXCEPT system crash can occur when a call to $PERSONA_CREATE is made for an account with a [0,0] UIC. (Though it is possible to create such an account, the account is invalid on VMS systems). Crashdump Summary Information: ------------------------------ Bugcheck Type: SSRVEXCEPT, Unexpected system service exception Current Process: BUILDER Failing PC: FFFFFFFF.801CB968 NSA$REFERENCE_RIGHTS_CHAIN_C+00008 Failing PS: 10000000.00000201 Module: SECURITY (Link Date/Time: 5-AUG-2001 01:12:10.86) Offset: 0000B968 Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY_MON.EXE 8.15.9.2 CLDs, SPRs, and QARs reporting this problem: 8.15.9.3 CLD(s) None. 8.15.9.4 QAR(s) 75-76-145 8.15.9.5 Problem Analysis: A call to a routine which initializes a control variable is bypassed. Decisions are then made based on the uninitialized content (stack) of that variable resulting in bad data being put in the resulting persona structure (PSB) created by the service. The system chokes on this bad data during security operations or process rundown, and crashes the system. Page 148 The source change simply moves the variable initialization before the decision to make or bypass the routine call. 8.15.9.6 Work-arounds: None. 8.15.10 Threads can erroneously run on CPU31 instead of primary CPU 8.15.10.1 Problem Description: On a system that contains a CPU numbered 31, CPU #31 can run a thread even if that thread has specified, either by setting required capabilities or hard affinity, that it must run on another CPU. Thus, some functions which must run on the primary CPU may occasionally be run on CPU #31. There need not actually be 31 CPUs. This bug can cause problems with CPU power down/up of any CPU, with CPU assignment between soft partitions, or garbled or missing console output. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 8.15.10.2 CLDs, SPRs, and QARs reporting this problem: 8.15.10.3 CLD(s) None. 8.15.10.4 QAR(s) None. 8.15.10.5 Problem Analysis: An AMACRO subtlety: BITL actually does a 64-bit AND, so that if one of the registers being tested was loaded with EVAX_LDQ, the most significant longword is taking part in the test. Page 149 8.15.10.6 Work-arounds: None. 8.15.11 Nonpaged pool expands unnecessarily to NPAGEVIR. 8.15.11.1 Problem Description: If a packet is requested from nonpaged pool that is larger than nonpaged pool's maximum allowed size (NPAGVIR), the request fails. However, nonpaged pool expands to its maximum size, even though the request can not be satisfied. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 8.15.11.2 CLDs, SPRs, and QARs reporting this problem: 8.15.11.3 CLD(s) CFS.86612 8.15.11.4 QAR(s) None. 8.15.11.5 Problem Analysis: The current code continually tries to extend nonpaged pool and retry the allocation request, giving up only when nonpaged pool extends to NPAGEVIR. 8.15.11.6 Work-arounds: None. Page 150 8.15.12 Problems due to possible corruption of the process scheduling queues and/or the SCH$GQ_PFWQ queue 8.15.12.1 Problem Description: A system may have one of the following problems caused by possible corruption of the process scheduling queues and/or the SCH$GQ_PFWQ queue: o Processes stuck in CUR but on the PFW queue and not executing o Processes stuck in PFW on the PFW queue and not executing o The PFW queue merged in with a COM queue, usually resulting in an INCON_SCHED or a CPUSPINWAIT bugcheck. o An INVEXCEPTN at SCH$QEND_C+38 trying to access the cell CTL$GL_REPORT_USER_FAULTS. Images Affected: - [SYS$LDR]SYS$VM.EXE 8.15.12.2 CLDs, SPRs, and QARs reporting this problem: 8.15.12.3 CLD(s) CFS.84479 8.15.12.4 QAR(s) None. 8.15.12.5 Problem Analysis: When we went from V62R's MMG$LOCKPGTB to V71R's MMG_STD$LOCKPGTB_64 we no longer returned from LOCKGPTB with the MMG spinlock held. But, the PAGEFAULT code (which calls EXE$BUILDPTKR which calls IOC_STD$FILL_DIOBM which calls MMG_STD$LOCKPGTB_64) is written such that it "assumes" this continues to be the case. The DIOBM code, IOC_STD$FILL_DIOBM, was occasionaly using "Method 3" calls MMG_STD$LOCKPGTB_64, when the pagefault I/O is greater than ioc$gl_diobm_ptecnt_max. When this occurs we are breaking synchronization when trying to place the process on the SCH$GQ_PFWQ queue. Page 151 8.15.12.6 Work-arounds: None. 8.15.13 Fatal invalid identifier format (%SYSTEM-F-IVIDENT) error 8.15.13.1 Problem Description: In an OpenVMS mixed version clustered environment, a fatal invalid identifier format (%SYSTEM-F-IVIDENT) error can result in versions of OpenVMS that are not OpenVMS COE (Common Operating Environment) compliant. This can occur on non-COE compliant OpenVMS systems when attempting to display the rights identifiers of a process that is granted a valid GID COE identifier. The following commands, lexicals, (and respective system services), cause the %SYSTEM-F-IVIDENT system message to be displayed instead of the text translation of this COE GID IDENTIFIER: 1. F$GETJPI("PID_xxx","PROCESS_RIGHTS") 2. F$GETJPI("PID_xxx","RIGHTSLIST") 3. $ SHOW PROCESS/ALL 4. $ SHOW PROCESS/RIGHTS Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.STB 8.15.13.2 CLDs, SPRs, and QARs reporting this problem: 8.15.13.3 CLD(s) None. Page 152 8.15.13.4 QAR(s) 75-61-105 8.15.13.5 Problem Analysis: Requirements have changed. 8.15.13.6 Work-arounds: None. 8.15.14 System fails to boot with %INIT_IO_DB-F-LOAD_SH_ERROR 8.15.14.1 Problem Description: A system can fail to boot with the following error: %INIT_IO_DB-F-LOAD_SH_ERROR, Error Loading shadowing driver SYS$SHDRIVER.EXE, error = 0x00000870 Images Affected: - [SYS$LDR]EXEC_INIT.EXE - [SYS$LDR]EXEC_INIT.STB 8.15.14.2 CLDs, SPRs, and QARs reporting this problem: 8.15.14.3 CLD(s) CFS.86282. 8.15.14.4 QAR(s) None. 8.15.14.5 Problem Analysis: The problem is caused by a buffer for retrieval pointers that is too small. If a system file has more than about 63 retrieval pointers (depending on the retrieval pointer format) this buffer would overflow. Reading the file later on would abort when pointers were exhausted. Note that very fragmented files with one or more extension headers can still not be loaded. Page 153 8.15.14.6 Work-arounds: None. 8.15.15 Memory wrongly indicated as reserved. 8.15.15.1 Problem Description: The sys$crmpsc_gdzro_64() returns a numeric value indicating that memory is reserved when it is not. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB - [SYS$LDR]SYS$VM.EXE 8.15.15.2 CLDs, SPRs, and QARs reporting this problem: 8.15.15.3 CLD(s) 70-3-5063,CFS.86494 8.15.15.4 QAR(s) None. 8.15.15.5 Problem Analysis: Fix the reserved_length return value from sys$crmpsc_gdzro_64. 8.15.15.6 Work-arounds: None. 8.15.16 System crash due to invalid exception bugcheck Page 154 8.15.16.1 Problem Description: If a RADCHECK is done on a system running the DECwindows Display Server (or possibly other images that memory map I/O space or other pages that do not appear in the PFN database) the system will crash with an invalid exception bugcheck. Analysis will show the exception is an ACCVIO in image SYS$VM, image MMG$RADCHECK_PROCESS. Images Affected: - [SYS$LDR]SYS$VM.EXE 8.15.16.2 CLDs, SPRs, and QARs reporting this problem: 8.15.16.3 CLD(s) None. 8.15.16.4 QAR(s) None. 8.15.16.5 Problem Analysis: The code did not test correctly for an I/O space PFN. 8.15.16.6 Work-arounds: None. 8.15.17 REFCNTNEG bugcheck 8.15.17.1 Problem Description: A system can crash with a REFCNTNEG, PFN reference count is negative bugcheck. The PFN database element being mapped is pointed to by R15, so, the SDA command: FORMAT @^QR15/TYPE=PFN can be used to examine the value in the PFN$W_BO_REFC field. If it is greater than or equal to 8000, 32768 decimal, this is the cause of the bugcheck. Crashdump Summary Information: ------------------------------ Bugcheck Type: REFCNTNEG, PFN reference count is negative Current Process: ORA_CLUS_DBWR Current Image: DSA2:[ORACLE.CODE_V7344.RDBMS]SRV.EXE Failing PC: FFFFFFFF.801131C8 Page 155 MMG_STD$DELBUFOBJPAGES_C+00678 Failing PS: 04000000.00000800 Module: SYS$VM (Link Date/Time: 29-DEC-1999 04:29:36.63) Offset: 000251C8 Images Affected: - [SYS$LDR]SYS$VM.EXE 8.15.17.2 CLDs, SPRs, and QARs reporting this problem: 8.15.17.3 CLD(s) CFS.82056 8.15.17.4 QAR(s) None. 8.15.17.5 Problem Analysis: The REFCNTNEG bugchecks occur in routines DELBUFOBJPAGES and DECPT_BUFOBJ in module [SYS]SYSLKWSET.MAR when the PFN$W_BO_REFC field is being decremented during buffer object deletion. Although values up to 64 k are allowed in the field during buffer object creation, during deletion the field is tested and a bugcheck occurs if it is negative. This restricts the value to less than 32 k. 8.15.17.6 Work-arounds: None. 8.15.18 Stop release of PFNs to exec data huge page region 8.15.18.1 Problem Description: On NUMA systems, at the end of the system startup, unused PFNs are released for the exec data huge page region, and then the exec code and resident code region will be replicated. Customers having their own drivers, which can be reloaded on the fly, need to clear the RELEASE_PFNS bit in the LOAD_SYS_IMAGES SYSGEN parameter to avoid releasing PFNs for the exec data region. Otherwise the driver reload fails with an error. This change stops release of PFNs for the exec data region. This allows customers to reload drivers on the fly and still get the benefit of system code replication. Page 156 Images Affected: - [SYS$LDR]SYSLDR_DYN.EXE 8.15.18.2 CLDs, SPRs, and QARs reporting this problem: 8.15.18.3 CLD(s) None. 8.15.18.4 QAR(s) None. 8.15.18.5 Problem Analysis: See problem description 8.15.18.6 Work-arounds: None. 8.15.19 Connection to an Oracle server can fail 8.15.19.1 Problem Description: Connection to an Oracle server can fail: ORACLE error--- ORA-01034: ORACLE not available ORA-27123: unable to attach to shared memory segment %SYSTEM-E-SECREFOVF, too many section refer %SYSTEM-W-UNWIND, unwind currently in progress %TRACE-W-TRACEBACK, symbolic stack dump follows %SYSTEM-W-UNWIND, unwind currently in progress Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]IMAGE_MANAGEMENT.EXE - [SYS$LDR]IMAGE_MANAGEMENT.STB - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE Page 157 - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB - [SYSEXE]INSTALL.EXE - [SYSLIB]IMGDMP.EXE - [SYSLIB]SDA$SHARE.EXE 8.15.19.2 CLDs, SPRs, and QARs reporting this problem: 8.15.19.3 CLD(s) CFS.87174 8.15.19.4 QAR(s) None. 8.15.19.5 Problem Analysis: The 32-bit sec$l_refcnt field has the potential to overflow if huge global sections are mapped by many processes. The risk is particularly high for memory resident sections mapped through shared page tables. 8.15.19.6 Work-arounds: None. 8.15.20 Call to $GETJPI returns SS$_NOPRIV status 8.15.20.1 Problem Description: A call to $GETJPI to return information about the calling process could return a SS$_NOPRIV status if that call is made while a persona representing a security profile that differs from the natural persona (Persona_ID 1) is active. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB Page 158 - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 8.15.20.2 CLDs, SPRs, and QARs reporting this problem: 8.15.20.3 CLD(s) 70-3-5262/CFS.87744 8.15.20.4 QAR(s) None. 8.15.20.5 Problem Analysis: Changes in the security module for Perthread did not take into consideration that the existing UIC check in $CHECKS_PROCESS_ACCESS would no longer be sufficient in determining if the current and target process were equivalent. 8.15.20.6 Work-arounds: None. 8.15.21 INVEXCEPTN bugcheck at LDR_STD$DEALLOC_S2_VA_C+006C4. 8.15.21.1 Problem Description: Under the following circumstances: o The system is a GS80, GS160, or GS320. o The SYSGEN parameter RAD_SUPPORT has bit 2 set, enabling system space replication. o The SYSGEN parameter GH_RSRVPGCNT is set to a non-zero value. The system can crash with an INVEXCEPTN bugcheck at LDR_STD$DEALLOC_S2_VA_C+006C4. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB Page 159 - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 8.15.21.2 CLDs, SPRs, and QARs reporting this problem: 8.15.21.3 CLD(s) None. 8.15.21.4 QAR(s) 75-66-455 8.15.21.5 Problem Analysis: During S2 space expansion, a test is made to determine if replication is on or off. This test included a check for a non-zero GH_RSRVPGCNT. This check is no longer valid since replication is now done with GH_RSRVPGCNT set to a non-zero value. 8.15.21.6 Work-arounds: None. 8.15.22 -SYSTEM-W-MBFULL, mailbox is full errors 8.15.22.1 Problem Description: Applications that make a call to the $SNDOPR system service can get a SS$_MBFULL return status. For example, Oracle/Rdb applications can fail with the following error: %COSI-F-UNEXPERR, unexpected system error -SYSTEM-W-MBFULL, mailbox is full Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB Page 160 8.15.22.2 CLDs, SPRs, and QARs reporting this problem: 8.15.22.3 CLD(s) 70-3-4930 8.15.22.4 QAR(s) None. 8.15.22.5 Problem Analysis: With the faster systems, OPCOM messages are being generated faster and piling up in the OPCOM mailbox. While increasing the mailbox size will only put off the problem if the rate of incoming messages is greater than the rate at which OPCOM can process them, it is believed that this will solve the problem of sudden, short bursts of messages arriving in the mailbox at roughly the same time. The extra space will allow the messages to sit in the mailbox until OPCOM can catch up with its processing. 8.15.22.6 Work-arounds: None. 8.15.23 INVEXCEPTN bugcheck at SCH$QEND_C+001E0 8.15.23.1 Problem Description: It is possible to sometimes get an INVEXCEPTN bugcheck at SCH$QEND_C+001E0 during quantum end processing. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: Current Image: Failing PC: FFFFFFFF.800CFB50 SCH$QEND_C+001E0 Failing PS: 10000000.00000804 Module: PROCESS_MANAGEMENT (Link Date/Time: 23-JAN-2001 08:37:04.46) Offset: 00007B50 Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE Page 161 - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 8.15.23.2 CLDs, SPRs, and QARs reporting this problem: 8.15.23.3 CLD(s) CFS.87597,CFS.83708 8.15.23.4 QAR(s) None. 8.15.23.5 Problem Analysis: The failure occurs because the process is being deleted and the KTB$L_PER_KT_AREA it is trying to access is already gone. The quantum end processing code checks PCB$B_PKTA_LOCK before accessing KTB$L_PER_KT_AREA, but does not check to see if the process is in the middle of being deleted. Occassionally, PCB$B_PKTA_LOCK is 1 but we have already deleted the PER_KT_AREA's virtual address space. 8.15.23.6 Work-arounds: None. 8.15.24 Make sure PERFMON interrupts are turned off 8.15.24.1 Problem Description: If PERFMON interrupts are not turned off for PCTR0, PCTR1 and PCTR2 during BUGCHECK, and on any STOP/CPU, severe hangs in the console can occur. It could take a power cycle to clear the situation. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB - [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE Page 162 - [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.EXE - [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE - [SYS$LDR]SYSTEM_SYNCHRONIZATION.STB - [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.STB - [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.STB 8.15.24.2 CLDs, SPRs, and QARs reporting this problem: 8.15.24.3 CLD(s) None. 8.15.24.4 QAR(s) None. 8.15.24.5 Problem Analysis: See Problem Description 8.15.24.6 Work-arounds: None. 8.15.25 SS$_IVLOGNAM error 8.15.25.1 Problem Description: When using the SYS$WAKE system service, if a PID or username for a process on a remote node is specified, a SS$_IVLOGNAM error will be returned. Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB Page 163 8.15.25.2 CLDs, SPRs, and QARs reporting this problem: 8.15.25.3 CLD(s) CFS.88476 8.15.25.4 SPR(s) None. 8.15.25.5 QAR(s) None. 8.15.25.6 Problem Analysis: The problem was introduced in V7.3 by making the SYS$WAKE system service 64-bit capable. A side effect of this was that the arguments passed to a lower level routine used for remote processes (CWPS$P_CNTRL) were incorrectly specified. That routine needed a homed argument list but that is not possible when 64-bit parameters are used. So, the wrong address of arguments was passed which caused another lower routine (CWPS$ALLOCATE_SRV) to return the error. 8.15.25.7 Work-arounds: None. 8.15.26 INVSECURESTATE bugcheck at NSA$DEREFERENCE_RIGHTS_CHAIN_C+0008C 8.15.26.1 Problem Description: The system can crash with a INVSECURESTATE bugcheck at NSA$DEREFERENCE_RIGHTS_CHAIN_C+0008C Crashdump Summary Information ----------------------------- Bugcheck Type: INVSECURESTATE, Invalid state detected by SECURITY subsystem Current Process: YERTLE$SRV73 Current Image: DSA20:[SYS0.SYSCOMMON.] [SYSEXE]OAFC$SERVER.EXE Failing PC: FFFFFFFF.8019798C NSA$DEREFERENCE_RIGHTS_CHAIN_C+0008C Failing PS: 30000000.00000203 Module: SECURITY_MON (Link Date/Time: 17-OCT-2001 01:01:12.57) Offset: 0000B98C Page 164 Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.STB 8.15.26.2 CLDs, SPRs, and QARs reporting this problem: 8.15.26.3 CLD(s) CFS.89089 8.15.26.4 QAR(s) None. 8.15.26.5 Problem Analysis: None. 8.15.26.6 Work-arounds: None. 8.15.27 KRNLSTAKNV, Kernel stack not valid, bugcheck 8.15.27.1 Problem Description: The system can crash with a KRNLSTAKNV, Kernel stack not valid, bugcheck" Crashdump Summary Information: ------------------------------ Bugcheck Type: KRNLSTAKNV, Kernel stack not valid Current Process: Current Image: Failing PC: FFFFFFFF.800243A8 SMP$BUGCHK_HALT_CPU_C+001F8 Failing PS: 00000000.00001F00 Module: SYS$CPU_ROUTINES_2208 (Link Date/Time: 17-MAR-2001 03:15:26.81) Offset: 000163A8 Page 165 Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 8.15.27.2 CLDs, SPRs, and QARs reporting this problem: 8.15.27.3 CLD(s) CFS.88619 8.15.27.4 QAR(s) None. 8.15.27.5 Problem Analysis: Something (as yet unknown) corrupted CTL$GQ_REMOTE_FULLNAME with an invalid size field. ACCOUNTing tried allocating some stack space to copy this field as part of its accounting message and ran off the top of the stack, resulting in the KRNLSTAKNV bugcheck. 8.15.27.6 Work-arounds: None. 9 INSTALLATION INSTRUCTIONS: 9.1 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_UPDATE /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt Page 166 9.2 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 definitions and commands: - $ DEFINE/SYS NO_ASK$BACKUP TRUE - $ DEFINE/SYS NO_ASK$REBOOT TRUE - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure: PROD INSTALL/PRODUCER=DEC/BASE=AXPVMS/VERSION=kit_version/- SAVE_RECOVERY_DATA kit_name Note that in order to automate installation of the kit you must use the /SAVE_RECOVERY_DATA qualifier. If you were to use /NOSAVE_RECOVERY_DATA, PCSI would ask you to confirm this choice. At the current time there is no way to avoid this question. A future release of PCSI will provide that capability. - De-assign the logicals assigned For example, a sample command file to install the VMS73_UPDATE-V0300 kit, saving recovery data, would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $! $PROD INSTALL/PRODUCER=DEC/BASE=AXPVMS/VERSION=3.0/- SAVE_RECOVERY_DATA VMS73_UPDATE $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 10 COPYRIGHT AND DISCLAIMER: (C) Copyright 2003 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. Page 167 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 COMPAQ 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.