ECO NUMBER: VMS722_UPDATE-V0100 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 COVER LETTER 1 KIT NAME: VMS722_UPDATE-V0100 2 KITS SUPERSEDED BY THIS KIT: o VMS722_ACRTL-V0100 o VMS722_AMACRO-V0100 o VMS722_AUDSRV-V0100 o VMS722_BACKUP-V0100 o VMS722_CLIUTL-V0100 o VMS722_DCL-V0100 o VMS722_DDTM-V0100 o VMS722_DECW_XTERM-V0100 o VMS722_DELETE-V0100 o VMS722_DRIVER-V0100 o VMS722_DW_MOT_MUP-V0100 o VMS722_F11X-V0100 o VMS722_FIBRE_SCSI-V0200 o VMS722_GRAPHICS-V0100 o VMS722_INSTALL-V0100 o VMS722_IPC-V0100 o VMS722_LAN-V0200 o VMS722_MAIL-V0100 o VMS722_MANAGE-V0100 o VMS722_MONTOR-V0100 o VMS722_MOUNT96-V0100 o VMS722_PPPD-V0100 -- COVER LETTER -- Page 2 8 July 2002 o VMS722_REM-V0100 o VMS722_RMS-V0200 o VMS722_RTPAD-V0100 o VMS722_SHADOWING-V0100 o VMS722_SYS-V0100 o VMS722_SYSLOA-V0200 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: None. 3.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.2-2 4.2 Files patched or replaced: o [SYSEXE]ALPHA_MACRO.EXE (new image) o [SYSEXE]APB.EXE (new image) o [SYSEXE]AUDIT_SERVER.EXE (new image) o [SYSEXE]BACKUP.EXE (new image) o [SYSLIB]BACKUPSHR.EXE (new image) o [SYSMSG]CLIUTLMSG.EXE (new image) o [SYSLIB]CLUE$SDA.EXE (new image) o [SYSEXE]CONVERT.EXE (new image) -- COVER LETTER -- Page 3 8 July 2002 o [SYSLIB]CONVSHR.EXE (new image) o [SYSEXE]CREATE.EXE (new image) o [SYSEXE]DCL.EXE (new image) o [SYS$LDR]DDIF$RMS_EXTENSION.EXE (new image) o [SYSEXE]DEBUG_APB.EXE (new image) o [SYSLIB]DECC$SHR.EXE (new image) o [SYSEXE]DECW$DWT_FONT_DAEMON.EXE (new image) o [SYSLIB]DECW$OPENGLPEERRI.EXE (new image) o [SYSLIB]DECW$OPENGLSHR_V11.EXE (new image) o [SYSLIB]DECW$OPENGLUSHR_V11.EXE (new image) o [SYSLIB]DECW$OPENGLUTSHR.EXE (new image) o [SYSLIB]DECW$OPENGLWIDGETSHR_V11.EXE (new image) o [SYSLIB]DECW$OPENGL_PROTOCOL_V11.EXE (new image) o [SYSLIB]DECW$SERVER_DDX_GB.EXE (new image) o [SYSLIB]DECW$SERVER_DDX_GZ.EXE (new image) o [SYSLIB]DECW$SERVER_DDX_P2.EXE (new image) o [SYSLIB]DECW$SERVER_DDX_P3.EXE (new image) o [SYSLIB]DECW$SERVER_DIX.EXE (new image) o [SYSLIB]DECW$SERVER_RIDDGL.EXE (new image) o [SYSLIB]DECW$SERVER_SISWDDGL.EXE (new image) o [SYSEXE]DECW$SETSHODIS.EXE (new image) o [SYSLIB]DECW$SVEXT_DEC_PEER_GLX.EXE (new image) o [SYSLIB]DECW$SVEXT_GLX_P350.EXE (new image) o [SYSLIB]DECW$TRANSPORT_COMMON.EXE (new image) o [SYSLIB]DECW$TRANSPORT_DECNET.EXE (new image) o [SYSLIB]DECW$TRANSPORT_LAT.EXE (new image) o [SYSLIB]DECW$TRANSPORT_LOCAL.EXE (new image) -- COVER LETTER -- Page 4 8 July 2002 o [SYSLIB]DECW$TRANSPORT_TCPIP.EXE (new image) o [SYSEXE]DECW$XFS.EXE (new image) o [SYSEXE]DELETE.EXE (new image) o [SYS$LDR]EXCEPTION.EXE (new image) o [SYS$LDR]EXCEPTION_MON.EXE (new image) o [SYS$LDR]EXEC_INIT.EXE (new image) o [SYS$LDR]F11BXQP.EXE (new image) o [SYSHLP.UNSUPPORTED]FC$CP.EXE (new image) o [SYSLIB]FC$SDA.EXE (new image) o [SYSEXE]FSINFO.EXE (new image) o [SYSEXE]FSLSFONTS.EXE (new image) o [SYS$LDR]IMAGE_MANAGEMENT.EXE (new image) o [SYSEXE]INSTALL.EXE (new image) o [SYS$LDR]IO_ROUTINES.EXE (new image) o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) o [SYS$LDR]LOCKING.EXE (new image) o [SYSEXE]MAIL.EXE (new image) o [SYSLIB]MAILSHR.EXE (new image) o [SYSLIB]MAILSHRP.EXE (new image) o [SYSEXE]MAIL_SERVER.EXE (new image) o [SYSLIB]MONTORSHR.EXE (new image) o [SYSLIB]MOUNTSHR.EXE (new image) o [SYS$LDR]MULTIPATH.EXE (new image) o [SYS$LDR]MULTIPATH_MON.EXE (new image) o [SYS$LDR]NET$CSMACD.EXE (new image) o [SYS$LDR]NET$FDDI.EXE (new image) o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) -- COVER LETTER -- Page 5 8 July 2002 o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) o [SYSEXE]QUEMAN.EXE (new image) o [SYSEXE]RECLAIM.EXE (new image) le;[SYSEXE]REMACP.EXE (new image) o [SYS$LDR]RMS.EXE (new image) o [SYSEXE]RTPAD.EXE (new image) o [SYSLIB]SDA$SHARE.EXE (new image) o [SYSLIB]SDARMS$SHARE.EXE (new image) o [SYS$LDR]SECURITY.EXE (new image) o [SYS$LDR]SECURITY_MON.EXE (new image) o [SYSLIB]SECURESHR.EXE (new image) o [SYSLIB]SECURESHRP.EXE (new image) o [SYSEXE]SET.EXE (new image) o [SYSEXE]SHADOW_SERVER.EXE (new image) o [SYSEXE]SHOW.EXE (new image) o [SYSLIB]SMI$OBJSHR.EXE (new image) o [SYSEXE]SMISERVER.EXE (new image) o [SYSLIB]SPISHR.EXE (new image) o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) o [SYS$LDR]SYS$CLUSTER.EXE (new image) o [SYS$LDR]SYS$DKDRIVER.EXE (new image) o [SYS$LDR]SYS$DQDRIVER.EXE (new image) o [SYS$LDR]SYS$ECDRIVER.EXE (new image) o [SYS$LDR]SYS$EIDRIVER.EXE (new image) o [SYS$LDR]SYS$ERBTDRIVER.EXE (new image) o [SYS$LDR]SYS$ESDRIVER.EXE (new image) o [SYS$LDR]SYS$EW1000A.EXE (new image) -- COVER LETTER -- Page 6 8 July 2002 o [SYS$LDR]SYS$EWBTDRIVER.EXE (new image) o [SYS$LDR]SYS$EWDRIVER.EXE (new image) o [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image) o [SYS$LDR]SYS$IPC_SERVICES.EXE (new image) o [SYS$LDR]SYS$FGEDRIVER.EXE (new image) o [SYS$LDR]SYS$GBDRIVER.EXE (new image) o [SYS$LDR]SYS$GFDRIVER.EXE (new image) o [SYS$LDR]SYS$GYCDRIVER.EXE (new image) o [SYS$LDR]SYS$GZDRIVER.EXE (new image) o [SYS$LDR]SYS$GZVDRIVER.EXE (new image) o [SYS$LDR]SYS$INDRIVER.EXE (new image) o [SYS$LDR]SYS$MKDRIVER.EXE (new image) o [SYS$LDR]SYS$PGADRIVER.EXE (new image) o [SYS$LDR]SYS$PKADRIVER.EXE (new image) o [SYS$LDR]SYS$PKQDRIVER.EXE (new image) o [SYS$LDR]SYS$PKWDRIVER.EXE (new image) o [SYS$LDR]SYS$PPPDRIVER.EXE (new image) o [SYS$LDR]SYS$SHDRIVER.EXE (new image) o [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE (new image) o [SYS$LDR]SYS$VM.EXE (new image) o [SYS$LDR]SYS$WSDRIVER.EXE (new image) o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) o [SYSEXE]TPSERV.EXE (new image) o [SYSEXE]VMOUNT.EXE (new image) o [SYSEXE]VPM.EXE (new image) o [SYSEXE]VPM_SERVER.EXE (new image) -- COVER LETTER -- Page 7 8 July 2002 o [SYSLIB]CRTL.OBJ (new file - used to update STARLET.OBJ) o [SYSLIB]CRTLMSGDEF.OBJ (new file - used to update STARLET.OBJ) o [SYSMGR]DECW$DEVICE_CONFIG_GB.COM (new file) o [SYSMGR]DECW$DEVICE_CONFIG_GF.COM (new file) o [SYSMGR]DECW$DEVICE_CONFIG_GZ.COM (new file) o [SYSMGR]DECW$DEVICE_CONFIG_P2.COM (new file) o [SYSMGR]DECW$STARTSERVER.COM (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 [SYS$LDR]F11BXQP.STB (new file) o [DECW$INCLUDE.GL_1_1]GL.H (new file) o [DECW$INCLUDE.GL_1_1]GLU.H (new file) o [DECW$INCLUDE.GL_1_1]GLUT.H (new file) o [DECW$INCLUDE.GL_1_1]GLWDRAWA.H (new file) o [DECW$INCLUDE.GL_1_1]GLWMDRAWA.H (new file) o [DECW$INCLUDE.GL_1_1]GLX.H (new file) o [DECW$INCLUDE.GL_1_1]GLXDECPROTO.H (new file) o [DECW$INCLUDE.GL_1_1]GLXINT.H (new file) o [DECW$INCLUDE.GL_1_1]GLXMD.H (new file) o [DECW$INCLUDE.GL_1_1]GLXPROTO.H (new file) o [DECW$INCLUDE.GL_1_1]GLXTOKENS.H (new file) o [DECW$INCLUDE.GL_1_1]GL_1_1_SETUP.COM (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 [SYSEXE]IPCDEF.STB (new file) -- COVER LETTER -- Page 8 8 July 2002 o [SYS$LDR]LOCKING.STB (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) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) o [SYS$LDR]SECURITY.STB (new file) o [SYS$LDR]SECURITY_MON.STB (new file) o [SYSEXE]SYS$CONFIG.DAT (new file) o [SYS$LDR]SYS$VM.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) o [SYSLIB]STARLET.MLB (new file) o [SYSHLP]P300_350_V2_README.HTML (new file) o [SYSHLP]P300_350_V2_README.PDF (new file) o [SYSHLP]P300_350_V2_README.TXT (new file) o [SYSHLP]P300_350_V2_README_CONTENTS.HTML (new file) o [SYS$LDR]RMSDEF.STB (new file) 5 PROBLEMS ADDRESSED IN VMS722_UPDATE-V0100 KIT o The VMS722_UPDATE-V0100 kit is a consolidation of previously released OpenVMS V7.2-2 ECO kits. The following ECO kits are included: VMS722_ACRTL-V0100 VMS722_AMACRO-V0100 VMS722_AUDSRV-V0100 VMS722_BACKUP-V0100 VMS722_CLIUTL-V0100 VMS722_DCL-V0100 VMS722_DDTM-V0100 VMS722_DECW_XTERM-V0100 VMS722_DELETE-V0100 VMS722_DRIVER-V0100 VMS722_DW_MOT_MUP-V0100 VMS722_F11X-V0100 VMS722_FIBRE_SCSI-V0200 VMS722_GRAPHICS-V0100 VMS722_INSTALL-V0100 VMS722_IPC-V0100 VMS722_LAN-V0200 VMS722_MAIL-V0100 VMS722_MANAGE-V0100 VMS722_MONTOR-V0100 VMS722_MOUNT96-V0100 VMS722_PPPD-V0100 VMS722_REM-V0100 VMS722_RMS-V0200 VMS722_RTPAD-V0100 VMS722_SHADOWING-V0100 -- COVER LETTER -- Page 9 8 July 2002 VMS722_SYS-V0100 VMS722_SYSLOA-V0200 Following are the problems addressed by the above kits. Note that the problems addressed in the VMS722_ACRTL-V0100 kit can be found in a separate file, [SYSHLP]VMS722_ACRTL-V0100_CVRLET.TXT. 6 PROBLEMS ADDRESSED IN VMS722_AMACRO-V0100 o CMPW of values that are more than 32767 apart will give the wrong result. Images Affected: - [SYSEXE]ALPHA_MACRO.EXE o AMACRO's floating point support macros do not correctly handle double-precision floating point immediate operands require more than 7 digits of precision. Images Affected: - [SYSLIB]STARLET.MLB 7 PROBLEMS ADDRESSED IN VMS722_AUDSRV-V0100 KIT o Digital command language (DCL) does not regain control when the SET SECURITY command is issued. When this occurs, the profile for the object in question may not be updated on all nodes in a cluster environment. Images Affected: - [SYSEXE]AUDIT_SERVER.EXE 8 PROBLEMS ADDRESSED IN VMS722_BACKUP-V0100 KIT o When BACKUP operations are done on a system with many resources and where either the authorized privileges or SYSGEN PQL values are very large, an ACCVIO could occur. -- COVER LETTER -- Page 10 8 July 2002 Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP fails when the input saveset is referenced via a searchlist. For example: $ DIR VDE$SYSTEM:*.BCK Directory SYS$COMMON:[VDE] VDE$UPLOAD.BCK;1 Total of 1 file. $ BACKUP VDE$SYSTEM:VDE$UPLOAD.BCK/SAVE/LIST Listing of save set(s) %BACKUP-F-OPENIN, error opening CLU$COMMON:[VDE.ALP_IMAGES]VDE$UPLOAD.BCK; as input -RMS-E-FNF, file not found Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o When a backup fails part way through, if the set is remounted using the backup target disk, the backup target disk is wrongly chosen as the master member. The valid disk is added as a copy member and the data is lost. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP will create a tape volume label from the saveset name if no name is provided in the BACKUP command. When PARSE_STYLE = EXTENDED and the saveset name is lowercase, BACKUP does not explicitly change the case to uppercase. When the tape is initialized the tape volume label is lowercase. Images Affected: -- COVER LETTER -- Page 11 8 July 2002 - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o If a BACKUP/LIST of a save-set is on a disk that was mounted /FOREIGN, the disk is inaccessible until it is dismounted or until BACKUP is used to create another save-set on the disk. Trying to access the disk fails with a %SYSTEM-F-VOLINV error. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o When using BACKUP to copy a directory tree, a directory version limit can be improperly placed on the destination's parent directory. This can occur if the first file copied into the parent directory is a directory file which does have a directory limit. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o If ODS-2 disks are converted to ODS-5 and then converted back to ODS-2, the following problems can occur: - A BACKUP/IMAGE of the disk with the /NOALIAS switch would not pick up the directory structure of any files and directories which were created during the time the disk was an ODS-5 structure. - Trying to add ACL's to previously created ODS-5 files, results in the following error: %SET-I-NOALIAS, $11$DUA431:[FMCDBS]SDBXD1.JIM;1 is an alias entry; file not modified - Previously created ODS-5 directories can be deleted when they have files in them, with no error. - An ANALYZE/DISK reports the following error on previously created ODS-5 files which have been deleted after the disk was converted: %ANALDISK-W-LOSTHEADER, file (18,1,1) JP.TXT not found in a directory -- COVER LETTER -- Page 12 8 July 2002 Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP fails with a %BACKUP-E-POSITERR, -SYSTEM-F-ILLIOFUNC error combination with RMT or INFOSERVER remotely accessed tape devices. Particularly when only a /LIST and no /DENSITY/MEDIA qualifiers are supplied in the BACKUP command line. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o A "%backup-f-insbufspace, insufficient buffer space" error can occur when an application makes excessive calls to backup$start. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE 9 PROBLEMS ADDRESSED IN VMS722_CLIUTL-V0100 KIT o When a SHO QUEUE command is entered, a queue entry number that is over 10,000,000 shows as asterisks rather than the queue entry number. Images Affected: - [SYSEXE]QUEMAN.EXE - [SYSMSG]CLIUTLMSG.EXE o Error openning file message could be incorrectly signaled. Images Affected: - [SYSEXE]SET.EXE o The output of a CREATE/DIRECTORY/LOG command prints the resulting directory name in uppercase, regardless of the actual on-disk case. The actual directory is created correctly, but -- COVER LETTER -- Page 13 8 July 2002 the informational message does not reflect the actual case of the directory. For example: $ SET DEFAULT DISK$ODS5:[test] $ SET PROCESS/PARSE=EXTENDED $ CREATE/DIRECTORY/LOG [test.MixedCaseDir] %CREATE-I-CREATED,DISK$ODS5:[TEST.MIXEDCASEDIR] created $ DIR Mixed*.dir Directory DISK$ODS5:[test] MixedCaseDir.DIR;1 Images Affected: - [SYSEXE]CREATE.EXE o A MTXCNTNONZ bugcheck could occur during logical name translation via the DCL SHOW LOGICAL command. Crashdump Summary Information: ------------------------------ Bugcheck Type: SSRVEXCEPT, Unexpected system service exception Current Process: APACHE$WWW_5 Current Image: DSA30:[SYS0.SYSCOMMON.][SYSEXE]SHOW.EXE Failing PC: 00000000.00052050 SHOW+62050 (VMS721_UPDATE-V0300) Failing PS: 00000000.00000003 Module: SHOW Offset: 0006205 Images Affected: - [SYSEXE]SHOW.EXE 10 PROBLEMS ADDRESSED IN VMS722_DCL-V0100 KIT o When the DCL PIPE command is issued in batch mode, it skips over the DCL statement immediately following the PIPE command. This occurs when the ";" separator is followed by a command sequence containing an "@filespec" command. Images Affected: -- COVER LETTER -- Page 14 8 July 2002 - [SYSEXE]DCL.EXE o Running the pipe command in a loop might result in one of the following errors: o DOUBLDEALO user mode bugchecks o ACCVIO in various symbol manipulation routines o SYMOVF error message Images Affected: - [SYSEXE]DCL.EXE o A process that has spawned several jobs, using a combination of SPAWN/WAIT and SPAWN/NOWAIT commands, stays in state HIB after all the spawned subprocesses have completed. Images Affected: - [SYSEXE]DCL.EXE 11 PROBLEMS ADDRESSED IN VMS722_DDTM-V0100 KIT o The system can crash with a SSRVEXCEPT bugcheck in TPSERV. Crashdump Summary Information: ------------------------------ Crash Time: 9-NOV-1999 16:14:48.85 Bugcheck Type: SSRVEXCEPT, Unexpected system service exception Current Process: TP_SERVER Current Image: DSA0:[SYS1.SYSCOMMON.] [SYSEXE]TPSERV.EXE;1 Failing PC: 00000000.00022B10 TPSERV+22B10 Failing PS: 10000000.00000000 Module: TPSERV Offset: 00022B10 This problem can also manifest itself as the TP_SERVER process looping and consuming CPU cycles. Images Affected: - [SYSEXE]TPSERV.EXE -- COVER LETTER -- Page 15 8 July 2002 o o INSF_NONPAGED, Insufficient nonpaged pool system crashes in a variety of (victim) images because most of non-paged pool is consumed by IPC buffers allocated by DECdtm. These IPBs consistently have the following characteristics: o IPB$W_SIZE contains 140 o IPB$B_EVENT contains 03,(DATA) o IPB$L_SEND_LEN contains 4C (value of lm$k_max_write_size) o IPB$L_REPLY_LEN contains A00 (value of lmsvmsg$k_bln) o IPB$L_FLAGS contains 421, o IPB$L_STATUS contains 01, o IPB$L_ALIAS contains the address of an LM_LCB structure which is also on the free list o The IPC trace log shows a repeat pattern: START: o IPC$_LINK o EV_LINK o IPC$_ACCEPT o EV_ACCEPT o IPC$_GETBUF The IPB specified in the following two entries is one of the leaked buffers and does not appear in any of the other trace entries. o IPC$_SEND o EV_DATA o EV_DATA o IPC$_UNLINK o EV_DISC o EV_DISC_COMP -- COVER LETTER -- Page 16 8 July 2002 END: o IPC$_RELBUF o Accessing the DECdtm log file via LMCP shows this error: $ MCR LMCP LMCP> SHOW LOG SYSTEM$foobar.LM$JOURNAL %LMCP-E-VERS_MISMATCH, version mismatch for transaction log format - operation aborted Images Affected: - [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE o The system can crash due to a forced DDTMBUG bugcheck in SYS$TRANSACTION_SERVICES. Crashdump Summary Information: ------------------------------ Bugcheck Type: DDTMBUG, DDTM has detected an invalid condition Failing PC: FFFFFFFF.801D3AA0 SYS$TRANSACTION_SERVICES+0BAA0 Failing PS: 20000000.00000203 Module: SYS$TRANSACTION_SERVICES (Link Date/Time: = 4-MAY-2001 18:05:37.03) Offset: 0000BAA0 Images Affected: - [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE o Some DECdtm initialization does not occur. Images Affected: - [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE 12 PROBLEMS ADDRESSED IN VMS722_DECW_XTERM-V0100 KIT o Several FONTS (such as Hebrew) cause a process crash trying to start the FONT_DAEMON (process DECW$FD). Users will see the following error message: -- COVER LETTER -- Page 17 8 July 2002 %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000B9CA8`, PC=000000000003A328, PS=0000001B Images Affected: - [SYSEXE]DECW$DWT_FONT_DAEMON.EXE 13 PROBLEMS ADDRESSED IN VMS722_DELETE-V0100 KIT o A PURGE/LOG ::[...]*.* command results in a SYSTEM-F-ACCVIO. SYSTEM-F-ACCVIO, Access violation, Reason mask=00, virtual address=00000000304c4154, PC=FFFFFFFF804C1CDC, PS=0000001B Images Affected: - [SYSEXE]DELETE.EXE 14 PROBLEMS ADDRESSED IN VMS722_DRIVER-V0100 KIT o When the CD-ROM is booted on an ES40, the following error message is returned after the initial boot messages: %SYSBOOT-I-GCTMINOR, GCT used with minor revision mismatch expected 00000005.00000001 - seen: 00000005.00000002 %SYSBOOT-F-LDFAIL,unable to load SYS$BASE_IMAGE.EXE, status=00000054 halted CPU = 0 halt code = 5 HALT instruction executed PC = 1d5e8 boot failure Images Affected: - [SYS$LDR]SYS$DQDRIVER.EXE o When mounting an ATAPI device an ATA init_device_param command attempts to set the disk geometry. This command is illegal for ATAPI devices but it takes 15 seconds before the drive reports -- COVER LETTER -- Page 18 8 July 2002 the error. Images Affected: - [SYS$LDR]SYS$DQDRIVER.EXE 15 PROBLEMS ADDRESSED IN VMS722_DW_MOT_MUP-V0100 KIT o Compaq has determined that systems running OpenVMS Alpha, OpenVMS VAX, SEVMS VAX or SEVMS Alpha with the DECwindows MotifServer installed have a potential security vulnerability that could be exploited to allow existing users unauthorized access to data and system resources. To protect against this potential security risk, Compaq is making available a mandatory update patch for OpenVMS customers. Installation of the DECwindows Motif Server is optional during the installation of the OpenVMS Operating System. You can verify whether or not the DECwindows Motif Server has been installed on your system using the following command: $ DIRECTORY SYS$LIBRARY:DECW$*.EXE If no DECW$*.EXE files are present on your system, the DECwindows Motif Server is not installed on your system and you do not need to apply this mandatory update. NOTE ---- If the DECwindows Motif Server is not installed on your system you do NOT need to install this mandatory update. Apply this mandatory update if the DECwindow Motif Server is installed on your system and you are running one of the following versions of OpenVMS or SEVMS: o OpenVMS Alpha Version 6.2 and all associated hardware releases (for example, Version 6.2-1H1) o SEVMS Alpha Version 6.2 o OpenVMS Alpha Version 7.1-2 o OpenVMS Alpha Version 7.2-1 o OpenVMS Alpha Version 7.2-2 o OpenVMS Alpha Version 7.2-1H1 -- COVER LETTER -- Page 19 8 July 2002 o OpenVMS Alpha Version 7.3 o OpenVMS VAX Version 6.2 o OpenVMS VAX Version 7.1 o OpenVMS VAX Version 7.2 o OpenVMS VAX Version 7.3 o SEVMS VAX Version 6.2 NOTE ---- OpenVMS VAX V5.5-2 is not subject to this potential security vulnerability. After completing the update, Compaq strongly recommends that you perform an immediate backup of your system disk so that any subsequent restore operations begin with updated software. Otherwise, you must reapply the update after a future restore operation. Also, if at some future time you upgrade your system to one of the versions of OpenVMS or SEVMS listed you must reapply the update. Images Affected: - [SYSLIB]DECW$TRANSPORT_COMMON.EXE - [SYSLIB]DECW$TRANSPORT_DECNET.EXE - [SYSLIB]DECW$TRANSPORT_LAT.EXE - [SYSLIB]DECW$TRANSPORT_LOCAL.EXE - [SYSLIB]DECW$TRANSPORT_TCPIP.EXE 16 PROBLEMS ADDRESSED IN VMS722_F11X-V0100 KIT o A synchronization issue between RMS's read of directory files for wildcard operations and concurrent XQP activity has been identified and corrected. Prior to this change, it was possible that RMS could obtain an inconsistent view of a directory file when reading it into its internal cache. This could result in spurious RMS-E-FNF (file not found) errors. A synchronization mechanism has been implemented between the XQP and RMS in order to ensure that a consistent view of a directory is achieved. -- COVER LETTER -- Page 20 8 July 2002 In order to get this complete fix, you also need to install the VMS722_RMS-V0200 ECO kit. Images Affected: - [SYS$LDR]F11BXQP.EXE o The system can crash with a "MAPCNTZER, Attempted to generate zero length map pointer" bugcheck. Crashdump Summary: ------------------ Bugcheck Type: MAPCNTZER, Attempted to generate zero length map pointer Current Process: _TNA69: Current Image: DSA0:[SYS0.SYSCOMMON.][SYSEXE]SYSGEN.EXE Failing PC: FFFFFFFF.A89F6B98 MAKE_POINTER_C+00044 Failing PS: 30000000.00000000 Module: F11BXQP (Link Date/Time: 24-AUG-2000 07:20:45.47) Offset: 00026B98 R3 = 00000000.00000000 <<< value of COUNT - ARG1: block count SDA> CLUE STACK Stack Frame: PV 00000000.7B009230 FFFFFFFF.A8A28390 MAKE_POINTER Entry Point FFFFFFFF.A89F6B54 MAKE_POINTER_C 00000000.7B009238 00000000.0090AE6C return PC 00000000.7B009240 FFFFFFFF.A89F1DBC EXTEND_C+00978 ^^^^^^^ caller saved R2 00000000.7B009248 FFFFFFFF.A8A275D0 EXTEND saved R3 00000000.7B009250 00000000.00000000 saved R8 00000000.7B009258 00000000.00000000 saved FP 00000000.7B009260 00000000.7B009270 Images Affected: - [SYS$LDR]F11BXQP.EXE o On Multi-Path devices, a MONITOR DISK/ITEM=QUEUE_LENGTH command will show a high queue length. It will stay high until reboot. The queue length on a switched path device, as seen from SDA, will show as negative. Images Affected: - [SYS$LDR]F11BXQP.EXE -- COVER LETTER -- Page 21 8 July 2002 17 PROBLEMS ADDRESSED IN VMS722_FIBRE_SCSI-V0200 KIT o The system can crash with a SSRVEXCEPT, Unexpected system service exception" bugcheck. Crashdump Summary Information: ------------------------------ Bugcheck Type: SSRVEXCEPT, Unexpected system service exception CPU Type: AlphaServer 2100 4/233 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]SYS$FGEDRIVER.EXE o When a Fibre Channel disk is being brought back online, after a controller failover, the user may see a variety of problems, ranging from process hangs, system hangs, and system crashes with a variety of bugchecks. All systems using disks served from the affected HSG controllers will be affected. The nature of this problem is two fold. o It completely shuts down the HSG controller. Anything accessing that HSG will hang until their I/O times out. This will cause any number of failures from all the disks becoming unavailable. o It consumes a number of resources on the systems. A crash will result from what ever critical resource runs out first. If the wrong equilibrium is reached, the systems can appear to hang forever. It is possible, but not likely, that they will also recover with no intervention. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE o The system can crash with an "INCONSTATE, Inconsistent I/O data base" bugcheck at SYS$FGEDRIVER+8C3C. Crashdump Summary Information: ------------------------------ -- COVER LETTER -- Page 22 8 July 2002 Bugcheck Type: INCONSTATE, Inconsistent I/O data base Current Process: NULL Current Image: Failing PC: FFFFFFFF.802DAC3C SYS$FGEDRIVER+08C3C Failing PS: 18000000.00000804 Module: SYS$FGEDRIVER (Link Date/Time: 5-DEC-2001 14:41:56.69) Offset: 00008C3C Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE - [SYSLIB]FC$SDA.EXE o When a TLZ10 tape with an incorrect label is installed on a 789X SCSI adapter (KZPEA 7899 card or built-in 7895 card in a DS20E), the user should receive a MEDOFL (Medium offline) error. Instead, the user receives an incorrect DRVERR (Drive Error) error. Images Affected: - [SYS$LDR]SYS$PKADRIVER.EXE o The system can crash with a INVEXCP bugcheck. Crashdump Summary Information ----------------------------- Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Failing PC: FFFFFFFF.80363B80 SYS$PKADRIVER+0BB80 Failing PS: 00000000.00001504 Offset: 0000BB80 Images Affected: - [SYS$LDR]SYS$PKADRIVER.EXE o An INIT command, when used on SCSI tapes, can take 1/2 hour or more to quit if no tape is in the unit. With this change, the INIT command fails immediately with no media in the drive. Images Affected: - [SYS$LDR]SYS$MKDRIVER.EXE -- COVER LETTER -- Page 23 8 July 2002 18 NEW FUNCTIONALITY INTRODUCED IN VMS722_FIBRE_SCSI-V0100 KIT 1. KZPEA-DB Ultra 160 SCSI Storage Adapter support The Compaq KZPEA-DB SCSI Storage Adapter is a high-performance dual channel Ultra 160 SCSI adapter that connects external or internal SCSI storage devices to a PCI-based host Alpha system. The module provides multimode SCSI support for both Single-Ended (SE) and Low Voltage Differential (LVD)SCSI peripherals in a 33/66 MHz PCI slot. The KZPEA adapter has the following features: 1. Provides full-featured dual-channel Ultra 160 SCSI host adapter with a 66/33 MHz 64-bit PCI interface. 2. Supports Ultra160 data transfer rates up to 160 MB/sec on the 16-bit SCSI bus using LVD SCSI peripherals. 3. Supports mixed SCSI-2, Ultra2, and Ultra160 SCSI peripherals on Compaq Storageworks enclosures. 4. Supports hot-swapping/hot-adding of SCSI peripherals. Images Affected: - [SYS$LDR]SYS$PKADRIVER.EXE o Restrictions and Workarounds The KZPEA-DB Ultra 160 SCSI Storage Adapter currently supports only split bus racks, not single bus Starbrite storage racks. 2. Interrupt and Response Coalescing Interrupt and Response Coalescing is a functional option implemented in KGPSA firmware which allows LP8000 and LP9002 adapters to reduce the number of interrupts seen by a host. Given a response count and a delay time (in ms), the adapter can defer interrupting the host until that number of responses is available or until that amount of time has passed, whichever occurs first. This also makes each interrupt seen by the host more cost-effective because it will generally process more responses per interrupt than without Interrupt Coalescing. Images Affected: - [SYSHLP.UNSUPPORTED]FC$CP.EXE - [SYS$LDR]SYS$FGEDRIVER.EXE - [SYS$LDR]SYS$PGADRIVER.EXE -- COVER LETTER -- Page 24 8 July 2002 o Enabling Interrupt and Response Coalescing You can turn on Interrupt and Response Coalescing with the following command: $ MCR SYS$ETC:FC$CP FGx [] - $_ [] - FGx : the type of FG device (FGA, FGB etc.). To determine which FG devices are present, refer to the section titled "Determining FGx Devices" - : Enables bit 1 = Response Coalescing and bit 0 = Interrupt Coalescing. - : Delay is in milliseconds and can range from 0 to 255 decimal. - Response count can range from 0 to 63 decimal. - Any negative value leaves a parameter unchanged. - Values returned are those which are current after any changes. The recommended command is: MCR SYS$ETC:FC$CP FGA 3 1 8 You should substitute FGA with whatever FG device you wish to configure. The command must be run once per boot for every Emulex FibreChannel adapter on which Interrupt Coalescing is to be enabled. Once enabled it will persist across adapter initializations, path switches, CPU affinity changes, etc., in other words, until the next boot. Interrupt Coalescing can be turned off by passing an "enables" value of 0. 3. Determining FGx Devices In order to tell which FGx device(s) you have on your system, execute the following commands: $ ANALYZE/SYSTEM SDA>CLUE CONFIG/A Following is an excerpt of an example of the output of the above commands. Note that all fields are not included, only those needed to determine adapter type. Adapter Configuration: ---------------------- Port BusArrayEntry Device Name / HW-Id -- COVER LETTER -- Page 25 8 July 2002 ---- ---------------- -------------------- FGA: FFFFFFFF.810FBC40 KGPSA-CA (Emulex LP8000) FGB: FFFFFFFF.810FBC78 KGPSA-** (Emulex LP9000) Interrupt and Response Coalesing will only operate on LP8000 and LP9002 adapters. If the device name is not listed you will you will need to EXAMINE the BusArrayEntry entry to tell whether the Adapter is an LP8000, LP9002 or an earlier type of adapter. Following is an example of the EXAMINE command: SDA> EXAMINE FFFFFFFF.810FBC40 FFFFFFFF.810FBC40: F80010DF.F80010DF "ß..øß..ø" SDA> EXAMINE FFFFFFFF.810FBC78 FFFFFFFF.810FBC78: F90010DF.F90010DF "ß..ùß..ù" The field F80010DF.F80010DF shows that the adapter is an LP8000 adapter. The field F90010DF.F90010DF shows that the adapter is an LP9002 adapter. 19 PROBLEMS ADDRESSED IN VMS722_FIBRE_SCSI-V0100 KIT o When an HSZ/HSG device reports mirror copy status events, the ERRCNT of the device is incremented. This gives the false impression that there is a problem with the device(s). Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE o In a multiprocessor environment, exception conditions (such as AUTOGEN, disk errors, power glitches, etc.) cause the PKWDRIVER, the hardware interface, and the script code to become unsynchronized relative to each other. This un-synchronization can cause excessive bus resets, mount verify timeouts, command timeouts, I/O system hangs, system crashes and/or file corruption. The most obvious problem is the occurrence of SCSI bus resets. These can be seen with a "SHOW ERROR" command and will be in the error log. Images Affected: - [SYS$LDR]SYS$PKWDRIVER.EXE o A system can crash with an INVEXCEPTN @SYS$K_VERSION_01+00D20 error. Crashdump Summary Information: ------------------------------ -- COVER LETTER -- Page 26 8 July 2002 Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: O-2-BAD Current Image: $1$DGA1000:[SYS3.SYSCOMMON.] [SYSEXE]OPCCRASH.EXE;4 Failing PC: 00000000.00030D20 SYS$K_VERSION_01+00D20 Failing PS: 10000000.00000803 Module: OPCCRASH Offset: 00030D20 Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE o Odd byte records, read from tape to a memory buffer larger than the tape record, results in one extra byte of data. Images Affected: - [SYS$LDR]SYS$PKWDRIVER.EXE o If a disk is mounted software write protected, when the disk enters and completes mount verification, the disk is changed to software write enabled. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE o I/O to or from a Qlogic bus can hang when the bus is heavily loaded and undergoing stress, such as in a cluster transition. Images Affected: - [SYS$LDR]SYS$PKQDRIVER.EXE o For 8MM tapes only (eg. Exabyte, TZK15), a COPY command to a freshly initialized tape results in a fatal drive error whenever the COPY command is issued on a TMSCP client node. The error log shows that an Illegal Request has been sent to the drive. Images Affected: - [SYS$LDR]SYS$MKDRIVER.EXE -- COVER LETTER -- Page 27 8 July 2002 o FGEDRIVER can experience the following problems: o INVEXCEPTN, Exception while above ASTDEL o INCONSTATE, Inconsistent I/O data base Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE o A system can crash during system startup if a SCSI Exabyte tape drive is present on a parallel SCSI bus. Images Affected: - [SYS$LDR]SYS$MKDRIVER.EXE o Mounting CDs in the Yamaha CD-Writer CRW8424S results in a '%MOUNT-F-FORMAT, invalid media format' error message. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE o When booting, a shadowed system disk can hang the cluster. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE o The system can crash with a SHADDETINCON bugchek in SYS$SHDRIVER. Crashdump Summary Information: ------------------------------ Bugcheck Type: SHADDETINCON, SHADOWING detects inconsistent state Current Process: NULL Current Image: Failing PC: FFFFFFFF.A9C2EB98 SYS$SHDRIVER+82B98 Failing PS: 34000000.00000804 Module: SYS$SHDRIVER (Link Date/Time: 5-AUG-2001 01:03:45.34) Offset: 00082B98 Images Affected: le;[SYS$LDR]SYS$FGEDRIVER.EXE -- COVER LETTER -- Page 28 8 July 2002 20 NEW FUNCTIONALITY ADDED IN THE VMS722_GRAPHICS-V0100 KIT 20.1 PowerStorm 300/350 OpenVMS Graphics Support This document contains the release notes for PowerStorm 300/350 Graphics Support Version 2.0 for OpenVMS. Specific information about this support can be found in the P300_350_V2_README file. This file is available in the following formats: File Format ------------------- ------------------ P300_350_V2_README.TXT Text P300_350_V2_README.PDF Acrobat Reader P300_350_V2_README.HTML HTML P300_350_V2_README_CONTENTS.HTML HTML These files can be found at SYS$COMMON:[SYSHLP] 20.2 New ELSA GLoria Synergy DDX image A new device dependent X server image is provided to improve performance on EV6 (21264) based platforms containing ELSA GLoria Synergy graphics modules. A new procedure, SYS$MANAGER:DECW$DEVICE_CONFIG_P2.COM, is executed automatically during DECwindows startup. The new procedure will, on appropriate platforms, define a logical name that will redirect the server to use the new P2 device dependent X code, DECW$SERVER_DDX_P2.EXE. DECW$SERVER_DDX_GZ.EXE will continue to be used on older platforms containing ELSA GLoria Synergy graphics modules. Image(s) Affected: - [SYSLIB]DECW$SERVER_DDX_P2.EXE 21 GENERAL GRAPHICS PROBLEMS ADDRESSED IN THE VMS722_GRAPHICS-V0100 KIT o Attempts to use the MIT-SHM Shared Memory Extension fail with the following error: X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 131 (MIT-SHM) Minor opcode of failed request: 1 (X_ShmAttach) Serial number of failed request: 11 Current serial number in output stream: 12 -- COVER LETTER -- Page 29 8 July 2002 Images Affected: - [SYSLIB]DECW$SERVER_DIX.EXE o In OpenVMS V7.3, the default decwindows transport can be specified via the logical name DECW$SETDISPLAY_DEFAULT_TRANSPORT. However, any SET DISPLAY commands will now change the transport to the default transport, not the transport previously specified. For example, $ show display Device: WSA24: [super] Node: NODE1 Transport: DECNET Server: 0 Screen: 0 $ show log DECW$SETDISPLAY_DEFAULT_TRANSPORT "DECW$SETDISPLAY_DEFAULT_TRANSPORT" = "tcpip" (LNM$SYSTEM_TABLE) $ set displ/node=NODE2 $ show display Device: WSA24: [super] Node: NODE2 Transport: tcpip Server: 0 Screen: 0 $ set display/screen=1 $ show display Device: WSA24: [super] Node: NODE1 Transport: tcpip Server: 0 Screen: 1 The DECW$SETDISPLAY_DEFAULT_TRANSPORT default transport setting should only be used with the "$set display/create" qualifier. Images Affected: - [SYSEXE]DECW$SETSHODIS.EXE o Under some circumstances the DECwindows server can abort during startup. The SYS$MANAGER:DECW$SERVER_0_ERROR.LOG file contains the error message "failed to initialize core devices". -- COVER LETTER -- Page 30 8 July 2002 Images Affected: - [SYSLIB]DECW$SERVER_DIX.EXE o When drawing connected line segments with the line width set to 1, the pixel at the join point between two line segments is not drawn in some cases. Images Affected: - [SYSLIB]DECW$SERVER_DIX.EXE o The system may crash with an SSRVEXCEPT or PGFIPLHI bugcheck on SMP systems when terminating client processes which are connected using the local transport. Images Affected: - [SYSLIB]DECW$TRANSPORT_LOCAL.EXE 22 ELSA PROBLEMS ADDRESSED IN THE VMS722_GRAPHICS-V0100 KIT o When an X/Motif application issues an XDrawRectangle or XDrawRectangles request with a negative x coordinate, the coordinate is incorrectly treated as a large positive number, resulting in spurious lines being drawn on the screen. Images Affected: - [SYSLIB]DECW$SERVER_DDX_GZ.EXE o If the DECwindows server is started with the pixel depth (DECW$SERVER_PIXEL_DEPTH logical name) set to 16, the server will crash. This problem is seen with the ELSA Gloria Synergy graphics controller (SN-PBXGK-BB), only when using the older DECW$SERVER_DDX_GZ.EXE server image. Images Affected: - [SYSLIB]DECW$SERVER_DDX_GZ.EXE o When using the ELSA Gloria Synergy graphics controller (SN-PBXGK-BB) in 8 bit mode, the DECwindows server can crash when copying data from the screen to a pixmap. This is most often seen when performing a drag-and-drop operation. The server can crash in several different locations depending on the timing of the operation. -- COVER LETTER -- Page 31 8 July 2002 Another symptom of the same problem is that the server can return spurious BadAlloc errors (server resources exhausted). Images Affected: - [SYSLIB]DECW$SERVER_DDX_GZ.EXE o There are screen corruption problems when using the ELSA Gloria Synergy graphics controller (SN-PBXGK-BB): o Spurious horizontal lines are displayed when drawing diagonal lines in 8 bit mode. o When dragging a window on the screen with "display window contents during move" enabled and the screen backdrop set to Background, remnants of the window are left behind on the backdrop. Images Affected: - [SYSLIB]DECW$SERVER_DDX_P2.EXE o When using the ELSA Gloria Synergy graphics controller (SN-PBXGK-BB) and running applications which write a lot of data to the screen (such as rapidly scrolling text in a DECterm window), the system clock loses time. Images Affected: - [SYS$LDR]SYS$GZDRIVER.EXE - [SYS$LDR]SYS$GZVDRIVER.EXE o User messages enabled in the console variable BOOT_OSFLAGS (bit<17> = 1) or on the console BOOT command line (e.g., >>> B -FL 0,20000) may cause a system crash or hang while booting with an ELSA GLoria Synergy graphics controller (SN-PBXGK-BB), a JIB graphics controller (3X-DEPVD-AA), or a Trifecta graphics controller (3X-DEPVZ-AA), especially on an SMP system with the console variable CONSOLE set to SERIAL. Images Affected: - [SYS$LDR]SYS$GZDRIVER.EXE - [SYS$LDR]SYS$GZVDRIVER.EXE -- COVER LETTER -- Page 32 8 July 2002 o Some monitors like the Compaq P75 & P700, fail to synchronize when the Trifecta graphics controller (3X-DEPVZ-AA) or the JIB graphics controller (3X-DEPVD-AA) attempts to put the screen into standby mode. The problem manifests itself with the screen going partly black; you may see a partial display and the screen may blink and/or click. Images Affected: - [SYS$LDR]SYS$GZDRIVER.EXE - [SYS$LDR]SYS$GZVDRIVER.EXE 23 TGA2 (POWERSTORM 4D20/3D30) PROBLEMS IN THE VMS722_GRAPHICS-V0100 KIT o When booting with a PowerStorm 3D30 (SN-PBXGB-AA) or a PowerStorm 4D20 (SN-PBXGB-CA) graphics controller and the SYSGEN parameter POOLCHECK enabled, the system may crash with an ACCVIO bugcheck. Images Affected: - [SYS$LDR]SYS$GYCDRIVER.EXE 24 VX1 PROBLEMS ADDRESSED IN THE VMS722_GRAPHICS-V0100 KIT o The following screen corruption problems occur when using the 3Dlabs Oxygen VX1 graphics controller (SN-PBXGF-AB): o Video corruption is produced when dragging certain icons around the CDE desktop. For example, after moving an icon from the Application Manager window to the desktop, each subsequent move of the icon on the desktop (backdrop required), leaves behind unintended pixels. o With selected backdrops, video corruption is produced when dragging objects around the CDE desktop. For example, when dragging a window around the desktop with the "GRAY" backdrop selected, remnants of the left and right window borders are left behind on the desktop in the form of spurious vertical lines. -- COVER LETTER -- Page 33 8 July 2002 Images Affected: - [SYSLIB]DECW$SERVER_DDX_P3.EXE o With the 3Dlabs Oxygen VX1 graphics controller (SN-PBXGF-AB) and either 8 or 16 bits per pixel selected, extra pixels may be drawn around the edges of objects. Images Affected: - [SYSLIB]DECW$SERVER_DDX_P3.EXE o With the 3Dlabs Oxygen VX1 graphics controller (SN-PBXGF-AB), the Monitor utility may show excessive time in "Interrupt State" when the screen saver is active. Images Affected: o [SYS$LDR]SYS$GFDRIVER.EXE 25 P350 PROBLEMS ADDRESSED IN THE VMS722_GRAPHICS-V0100 KIT o Occasionally the DECwindows server would crash when an application did extensive creation and deletion of 3D contexts interspersed with extensive 2D drawing, including window creation and destruction. Images Affected: o [SYSLIB]DECW$SERVER_DIX.EXE o [SYSLIB]DECW$OPENGLPEERRI.EXE o Running the Viewperf 6.1.2 MedMCAD test causes an application crash when using LOCAL transport or a server crash when using network transport. Images Affected: o [SYSLIB]DECW$SERVER_RIDDGL.EXE o [SYSLIB]DECW$OPENGLPEERRI.EXE o When 3D contexts using a network connection are destroyed, their buffers are not being properly deallocated. The result is that, as applications create and delete 3D contexts, over time the server's virtual memory undergoes unconstrained growth. -- COVER LETTER -- Page 34 8 July 2002 Images Affected: o [SYSLIB]DECW$SERVER_DDX_GB.EXE o Certain OpenGL viewing transformations result in incorrect placement of primitives drawn. Images Affected: o [SYSLIB]DECW$OPENGLPEERRI.EXE o [SYSLIB]DECW$SERVER_RIDDGL.EXE o The following problems are corrected: - Repeated calls to glXMakeCurrent with a network connection caused a slow but steady increase in the server's virtual memory space. - Drawing polygons or triangles in GL_LINE mode along the bottom or right edge of the OpenGL viewport resulted in extra lines being drawn along the edge of the viewport. - When a single OpenGL context was used to render to two different windows, sometimes the display in one window was corrupted. - Stippled line strips with sub-pixel segments were not rendered by OpenGL. - In some instances, the DECwindows server would hang when rendering certain horizontal lines as filled rectangles. - In some instances, the DECwindows server would hang when rendering certain polygons. - Drop-down menu items became blank when the mouse was moved over a menu tear-off line. - In some instances, pixel corruption would occur when a window was moved over a highlighted item. Images Affected: o [SYSLIB]DECW$OPENGLSHR_V11.EXE o [SYSLIB]DECW$OPENGL_PROTOCOL_V11.EXE o [SYSLIB]DECW$OPENGLPEERRI.EXE -- COVER LETTER -- Page 35 8 July 2002 o [SYSLIB]DECW$SERVER_DDX_GB.EXE o [SYSLIB]DECW$SERVER_RIDDGL.EXE o [SYSLIB]DECW$SVEXT_GLX_P350.EXE o Some programs using GLUT (OpenGL Utility Toolkit) - specifically the glutIdleFunc function - would loop infinitely and/or ignore keyboard/mouse input. Images Affected: o [SYSLIB]DECW$OPENGLUTSHR.EXE o XFillRectangle calls with extremely out-of-range coordinates sometimes resulted in erroneous drawing artifacts outside the window. Images Affected: o [SYSLIB]DECW$SERVER_DDX_GB.EXE o [SYSLIB]DECW$SERVER_RIDDGL.EXE 26 PROBLEMS ADDRESSED IN VMS722_INSTALL-V0100 KIT o For performance reasons, it is beneficial to install large and heavily accessed images RESIDENT. On NUMA platforms, RESIDENT installed images also get replicated into each RAD to reduce memory latency. Until now, it was not possible to install an image RESIDENT that was linked TRACEBACK. Customers are not always willing to re-link their images /NOTRACEBACK because they would like the stack tracedump for trouble shooting, in case of any errors. On the other hand they would like the performance benefit that installing an image RESIDENT gives. This change allows /TRACEBACK linked images to be installed RESIDENT if they do not specify any privileges. Privileged installed images with the debug/traceback handler are vulnerable. For these images the INSTALL ADD or REPLACE command will still be prohibited. Images Affected: - [SYSEXE]INSTALL.EXE -- COVER LETTER -- Page 36 8 July 2002 27 PROBLEMS ADDRESSED IN VMS722_IPC-V0100 KIT o A system can crash with an "INCONSTATE, Inconsistent I/O data base" bugcheck when another node is rejoining the cluster after rebooting, and the ACCEPT fails. Crashdump Summary Information: ------------------------------ Bugcheck Type: INCONSTATE, Inconsistent I/O data base Current Process: NULL Current Image: Failing PC: FFFFFFFF.83350640 SYS$IPC_SERVICES+48640 Failing PS: 1C000000.00000804 Module: SYS$IPC_SERVICES (Link Date/Time: 19-MAY-2001 01:30:51.36) Offset: 00048640 Images Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE o When processes are communicating via ICC, if process resource wait is enabledand the transmitter gets too far ahead of the receiver, then the transmitting process goes into MUTEX wait. This is expected as the BYTLIM quota is exhausted. However, the transmitter processes hangs in MUTEX wait waiting for BYTCNT/BYTLM to be returned. Images Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE o A system crash due to a KRNLSTAKNV bugcheck can occur. The crash is caused by fork queue corruption. In order for the corruption to occur, all of the following must be true: - Multinet is running - IPC is using the CI - The CI is not running on the primary CPU - There is heavy Multinet and IPC activity, pushing the timing of fork queue access for both Images Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE -- COVER LETTER -- Page 37 8 July 2002 - [SYSEXE]IPCDEF.STB 28 PROBLEMS ADDRESSED IN VMS722_LAN-V0200 KIT o A DE602 installed in an ES40, and configured via the console as half-duplex mode, will put an Ethernet switch in full duplex mode when the switch is configured in auto-negotiate mode. Images Affected: - [SYSEXE]APB.EXE - [SYS$LDR]NET$CSMACD.EXE - [SYS$LDR]NET$FDDI.EXE - [SYS$LDR]SYS$ECDRIVER.EXE - [SYS$LDR]SYS$EIDRIVER.EXE - [SYSEXE]SYS$ERBTDRIVER.EXE - [SYS$LDR]SYS$ESDRIVER.EXE - [SYS$LDR]SYS$EWDRIVER.EXE - [SYSEXE]SYS$EWBTDRIVER.EXE - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE - [SYS$LDR]SYS$EW1000A.EXE 29 PROBLEMS ADDRESSED IN VMS722_LAN-V0100 KIT o A scatter/gather mapping error can occur. This is seen as a machine check bythe system followed by a system crash. Crash Dump Summary ------------------ Bugcheck Type: MACHINECHK, Machine check while in kernel mode Current Process: Current Image: $82$DUA51:[CTM$TMROOT.][CTM_BYTEM] CTM_BYTEM_ALPHA_32.EXE;2 Failing PC: FFFFFFFF.80014688 EXE$SYSTEM_CORRECTED_ERROR_C+004F8 Failing PS: 00000000.00001F04 -- COVER LETTER -- Page 38 8 July 2002 Module: SYS$CPU_ROUTINES_2608 (Link Date/Time: 17-MAR-2001 03:15:10.47) Offset: 00006688 Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o A DE602 installed in an ES40, and configured via the console as half-duplex mode, will put an Ethernet switch in full duplex mode when the switch is configured in auto-negotiate mode. Images Affected: - [SYSEXE]APB.EXE - [SYS$LDR]NET$CSMACD.EXE - [SYS$LDR]NET$FDDI.EXE - [SYS$LDR]SYS$ECDRIVER.EXE - [SYS$LDR]SYS$EIDRIVER.EXE - [SYSEXE]SYS$ERBTDRIVER.EXE - [SYS$LDR]SYS$ESDRIVER.EXE - [SYS$LDR]SYS$EWDRIVER.EXE - [SYSEXE]SYS$EWBTDRIVER.EXE - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE - [SYS$LDR]SYS$EW1000A.EXE o A system can crash with an INVEXCEPTN, Exception while above ASTDEL bugcheck after the user issues an NCL SHOW FDDI STATION * ALL command. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: SCHED#_563 Current Image: DSA2000:[SYS3.SYSCOMMON.][SYSEXE]NCL.EXE;1 Failing PC: FFFFFFFF.F793B758 NET$FDDI+0D758 Failing PS: 20000000.00000804 Module: NET$FDDI (Link Date/Time: 18-MAY-2000 00:48:44.06) Offset: 0000D758 -- COVER LETTER -- Page 39 8 July 2002 Images Affected: - [SYS$LDR]NET$FDDI.EXE 30 PROBLEMS ADDRESSED IN VMS722_MAIL-V0100 KIT o If a username logical is defined using /TRANSLATION=TERMINAL, sending a mail message to that person will fail with a "%MAIL-E-NOSUCHUSR, no such user logical_name" error. See example below: $ DEFINE/TRANSLATION=TERMINAL js john_smith $ MAIL MAIL> SEND To: js %MAIL-E-NOSUCHUSR, no such user JS Images Affected: - [SYSEXE]MAIL.EXE o After a COMPRESS command fails, subsequent mail commands cannot be processed. See example below: MAIL> COMPRESS %MAIL-E-NOFILEOPEN, no mail file open MAIL> DIR %MAIL-E-NOFILEOPEN, no mail file open MAIL> READ %MAIL-E-NOFILEOPEN, no mail file open %MAIL-E-NOMSGS, no messages MAIL> SELECT A %MAIL-E-NOFILEOPEN, no mail file open MAIL> EXIT %MAIL-E-NOFILEOPEN, no mail file open %MAIL-E-NOFILEOPEN, no mail file open Images Affected: - [SYSEXE]MAIL.EXE o If a message line containing an embedded NULL character was extracted to a file, the message line was truncated at the NULL character. -- COVER LETTER -- Page 40 8 July 2002 Example message: 111111111111111111111111111111 111111111111^@1111111111111111 111111111111111111111111111111 Extracting the message results in output file: 111111111111111111111111111111 111111111111111111111111111111 111111111111111111111111111111 Images Affected: - [SYSEXE]MAIL.EXE o Using callable mail routines over a period of time may fail with '%LIB-F-INSVIRMEM, insufficient virtual memory'. Callable Mail allocates free memory space, but does not return all of it. Images Affected: - [SYSLIB]MAILSHR.EXE o Attempting to DEFINE/KEY function keys F6 thru F14 fails without an error message; the newly defined key will not function. Images Affected: - [SYSEXE]MAIL.EXE o The statistics returned in a call to MAIL$MAILFILE_PURGE_WASTE are incorrect. The MAIL$_MAILFILE_TOTAL_RECLAIM and MAIL$_MAILFILE_DATA_RECLAIM item codes to the MAIL$MAILFILE_PURGE_WASTE callable mail routine always return identical values. Further, the value returned when using the item code MAIL$MAILFILE_DELETED_BYTES is always 0. The OpenVMS documentation states that this field returns the number of bytes deleted from a mail file. See example below: %MAIL-I-RECLPLSWAIT, reclaiming deleted file space. Please wait... Data buckets reclaimed: [6] Number of data buckets scanned: [7] Number of index buckets reclaimed [0] Number of deleted bytes: [0] -- COVER LETTER -- Page 41 8 July 2002 Number of messages deleted: [68] Number of bytes reclaimed: [6] Images Affected: - [SYSLIB]MAILSHR.EXE o If a user is in Mail and issues a SET FILE command for a different Mail subdirectory. Mail ignores the command. See the example below: PROMPT> mail MAIL> sho ver Mail V1.0 MAIL> SHOW FILE Your current mail file is SYS$SYSROOT:[SYSMGR]MAIL.MAI. MAIL> SET FILE SYS$SYSDEVICE:[BAT.MAIL] MAIL> DIR/FOLDER Listing of folders in SYS$SYSROOT:[SYSMGR]MAIL.MAI Press CTRL/C to cancel listing MAIL MAIL> SHOW FILE Your current mail file is SYS$SYSROOT:[SYSMGR]MAIL.MAI. MAIL> EXIT Images Affected: - [SYSEXE]MAIL.EXE o Errors can occur when copying a Mail folder from one file to another. Not all of the files may be copied and no error message is displayed. See the example below: MAIL> SELECT "MAIL-nov-1998" %MAIL-I-SELECTED, 3121 messages selected MAIL> SEL/SINCE=01-jan-80 %MAIL-I-SELECTED, 3121 messages selected MAIL> COPY/ALL "MAIL-nov-1998" dua3:[mpiati] MAIL> SET FILE dua3:[mpiati] MAIL> SELECT "MAIL-nov-1998" %MAIL-I-SELECTED, 169 messages selected -- COVER LETTER -- Page 42 8 July 2002 Images Affected: - [SYSLIB]MAILSHR.EXE o The DATE in the header of a message is omitted from extracted messages. Images Affected: - [SYSEXE]MAIL.EXE o When a new message arrives and the mail file in use is not the default, the READ/NEW command does not close the current mail file and open the default mail file. An explicit SET FILE command to the default mail file must be executed before the READ/NEW command is issued. Further, the new messages remain in the NEWMAIL folder. Images Affected: - [SYSEXE]MAIL.EXE o UCX$SMTP_MAILSHR.EXE fails with an 'ACCVIO, access violation' when sending a mail message with a record greater than 1,000 bytes. Images Affected: - - [SYSLIB]MAILSHR.EXE o The SEND/LAST command fails to include the text from the previous mail message when MAIL is invoked with MAIL/EDIT. This only occurs when the /EDIT qualifier is used without the MAIL DCL command. Images Affected: - [SYSEXE]MAIL.EXE o OpenVMS Mail does not filter out the character on the header fields, i.e., From:, To:, CC: and Subj: strings. In some instances, a mail message could be received with a type of VT Escape Sequence that could modify the behavior of a user's terminal; the potential would be to render the terminal unusable. Images Affected: -- COVER LETTER -- Page 43 8 July 2002 - [SYSEXE]MAIL.EXE o An %MAIL-E-ALTPRIJOB error message displays without cause. See example below: $ MAIL MAIL> 22 (Message #22 is displayed) MAIL> PRINT MAIL> 5 (Message #5 is displayed) MAIL> PRINT/QUEUE=32$LB2A %MAIL-E-ALTPRIJOB, error altering parameters of job 505 queue 32$LB2A Job MAIL (queue 34$LB4L, entry 505) started on 34$LB4L MAIL> EXIT $ In this example, print queue 34$LB4L is the default print queue in the user's MAIL profile. This error is benign because the print job eventually is released to the printer (32$LB2A in the example above), even though the user is not notified. Images Affected: - [SYSEXE]MAIL.EXE o A spawned MAIL command MAIL/SUBJ="......." fails with the following error: %MAIL-E-UAFGETERR, error reading user authorization file Images Affected: - [SYSEXE]MAILSHRP.EXE o Mail gives ill-formed audit error messages: $ SET AUDIT/ALARM/AUDIT/ENABLE=PRIVILEGE=SUCCESS $ REPLY/ENABLE $ MAIL MAIL> SHOW FORW/ALL/USER=* Username Forwarding address USERA NODE1 -- COVER LETTER -- Page 44 8 July 2002 %%%%%%%%%%% OPCOM 99-MAY-9999 99:99:99.99 %%%%%%%%%%% Message from user AUDIT$SERVER on MYNODE Auditable event: Ill-formed internal (TCB) audit . . Status: %SYSTEM-F-BADBUFLEN, specified buffer length is invalid or out-of-range Images Affected: - [SYSLIB]MAILSHRP.EXE 31 PROBLEMS ADDRESSED IN VMS722_MANAGE-V0100 KIT o Customers have questioned why SYSMAN DO commands, issued from a local node, generate an ALTPRI audit alarm and set a priority of 7. For example: Message from user AUDIT$SERVER on NODE1 Security alarm (SECURITY) on NODE1, system id: 00000 Auditable event: Privilege failure Event information: ALTPRI not used to create process with elevated priority (RUN/PRIORITY, $CREPRC) Event time: 9-JUL-2001 14:49:12.18 PID: 21A00427 Process name: pname Username: uname Process owner: [gname,uname] Terminal name: TNA4: Image name: $40$DKA0:[SYS0.SYSCOMMON.] [SYSEXE]SYSMAN.EXE New priority: 7 Privileges missing: ALTPRI Customers do not understand why there is a request to create the process at priority 7. The subprocess is created at the lower priority and functions properly for a client who does not have the ALTPRI privilege. This change provides the following priority settings: o If the requester has ALTPRI, use current behavior, i.e. create the subprocess at priority 7. o If the requester does not have ALTPRI, create the subprocess at the requester default priority. -- COVER LETTER -- Page 45 8 July 2002 o If default priority is greater than 7, create the subprocess at priority 7. This maintains the current priority settings on the subprocess creation and eliminates the unnecessary audit alarm. Images Affected: - [SYSLIB]SMI$OBJSHR.EXE o The USERNAME of the SMISERVER process is not set back to the username of the starting process after a user exits SYSMAN. For example: Starting username: SYSTEM1>sho proc/id=20200218 9-MAR-2001 13:21:12.00 User: SYSTEM Process ID: 20200218 Node: SYSTEM1 Process name:"SMISERVER" SYSTEM1> >>> From another system: SYSTEM2> mc sysman set env/node=SYSTEM1/user=testusr Remote Password: %SYSMAN-I-ENV, current command environment: Individual nodes: SYSTEM1 At least one node is not in local cluster Username TESTUSR will be used on nonlocal nodes SYSMAN> do sho proc %SYSMAN-I-OUTPUT, command execution on node SYSTEM1 9-MAR-2001 13:22:46.81 User: TESTUSR Process ID: 202002E7 Node: SYSTEM1 Process name:"SMI$TESTUSR_1" SYSMAN> >>> SMISERVER process on SYSTEM1 before exiting SYSMAN on SYSTEM2 SYSTEM1>sho proc/id=20200218 9-MAR-2001 13:24:02.82 User: TESTUSR Process ID: 20200218 Node: SYSTEM1 Process name:"SMISERVER" SYSTEM1> >>> SMISERVER process on SYSTEM1 after exiting SYSMAN on SYSTEM2: SYSTEM1>sho proc/id=20200218 -- COVER LETTER -- Page 46 8 July 2002 9-MAR-2001 13:26:06.02 User: TESTUSR Process ID: 20200218 Node: SYSTEM1 Process name:"SMISERVER" The username should be "SYSTEM". Images Affected: - [SYSEXE]SMISERVER.EXE o This kit affects some tape devices (tape drives and robots) which are connected to Fibre Channel via an MDR (Modular Data Router). The affected tape devices have binary WWIDs that contain embedded byte values between 61h and 7Ah. For example, a WWID of 02000008:500E-09E0-0005-3072 (note the last byte value is 72h). These devices are detected during a SYSMAN IO FIND_WWID command, as verified by the WWID value recorded in SYS$SYSTEM:SYS$DEVICES.DAT. However, the devices do not configure if SYSMAN IO AUTOCONFIGURE is invoked immediately after the the SYSMAN IO FIND_WWID command. Only a reboot will result in configuring these devices. The purpose of this kit is to avoid this need for a reboot. Note: Similar issues can arise when using the SYSMAN IO REPLACE_WWID command. Images Affected: - [SYSLIB]SMI$OBJSHR.EXE 32 PROBLEMS ADDRESSED IN VMS722_MONTOR-V0100 KIT o The command MONITOR RMS/FILE=LOGIN.COM will access violate. For example: $ monitor rms/file=login.com %MONITOR-E-COLLERR, error during data collection -SYSTEM-F-ACCVIO, access violation, reason mask=5B, virtual address=000000000000001B, PC=000000007ACAF7EC, PS=7ACAF82D Images Affected: - [SYSLIB]MONTORSHR.EXE - [SYSLIB]SPISHR.EXE - [SYSEXE]VPM.EXE -- COVER LETTER -- Page 47 8 July 2002 - [SYSEXE]VPM_SERVER.EXE 33 PROBLEMS ADDRESSED IN VMS722_MOUNT96-V0100 KIT o Roxio CD Creator V5.0 for PCs creates a disk that is not compliant to the ISO standard. Attempting to mount these disks on an OpenVMS system will crash the system with an SSRVEXCEPT, Unexpected system service exception bugcheck. Crash Dump Summary ------------------ Bugcheck Type: SSRVEXCEPT, Unexpected system service exception Current Process: DKA400CACP Current Image: $82$DKA0:[SYS0.SYSCOMMON.] [SYSEXE]F11CACP.EXE Failing PC: FFFFFFFF.800ACD10 EXE$QIO_C+00170 Failing PS: 30000000.00000001 Module: IO_ROUTINES (Link Date/Time: 29-MAR-2000 00:52:23.33) Offset: 0001AD10 Images Affected: - [SYSLIB]MOUNTSHR.EXE - [SYSEXE]VMOUNT.EXE o A SET VOLUME/REBUILD command on a volume set may not reset the volume write count to the correct number of writers in the cluster. This can occur when a node that had the volume set mounted did not update the volume write count on dismount or on a crash. A SHOW DEVICE/REBUILD command always shows this volume as needing a rebuild. Even a SET VOLUME/REBUILD=FORCE command will not clear this rebuild status. Images Affected: - [SYSLIB]MOUNTSHR.EXE 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 mount commands were executed, the mount would fail with the message: -- COVER LETTER -- Page 48 8 July 2002 DIFVOLMNT - different volume already mounted on this device. - If a disk is mounted with a /WRITE qualifier on one cluster and a /NOWRITE qualifier on another cluster in the SAN, mount verification will fail with a WrongVolume status error on the system which had the disk mounted /NOWRITE. This change allows mount verification to complete successfully in this configuration. Note: To receive this complete correction you must also install the VMS722_SYS-V0100 and VMS722_FIBRE_SCSI-V0200 ECO kits. Images Affected: - [SYSLIB]MOUNTSHR.EXE - [SYSEXE]VMOUNT.EXE o Read failures during a disk mount that were due to an inability to read the home block and failures that were due to transient errors, such as from a path switch or SCSI bus reset, were following the same failure path. That is, reading the alternate home block and if successful, mounting the disk as read only. However, failures due to transient errors should not read the alternate home block and should mount the disk as READ/WRITE. For transient error failures, this change will now cause the READ to be re-tried for 30 seconds (30 re-tries at one per second). If the READ succeeds, the disk will be mounted as READ/WRITE. Images Affected: - [SYSEXE]VMOUNT.EXE - [SYSLIB]MOUNTSHR.EXE 34 PROBLEMS ADDRESSED IN VMS722_PPPD-V0100 KIT o Line table lookup fails when line number is greater than 9. -- COVER LETTER -- Page 49 8 July 2002 Images Affected: - [SYS$LDR]SYS$PPPDRIVER.EXE 35 PROBLEMS ADDRESSED IN VMS722_REM-V0100 KIT o The following problems have ben corrected: 1. Stopping and restarting the REMACP process without the provided management utilities (STOPREM and RTTLOAD.COM results in a system crash. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: REMACP Current Image: $1$DGA300:[SYS61.SYSCOMMON.] [SYSEXE]REMACP.EXE;1 Failing PC: 00000000.0000C278 Failing PS: 0C000000.00000800 Module: REMACP Offset: 0000C278 2. SET HOST connections are rejected even though RJOBLIM has not been reached. Stopping and restarting the REMACP process temporarily clears the condition. Images Affected: - [SYSEXE]REMACP.EXE 36 PROBLEMS ADDRESSED IN VMS722_RMS-V0200 KIT o Fix for RMS global buffer hang due to abort ($delprc) rundowns. 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. -- COVER LETTER -- Page 50 8 July 2002 - 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 o RMS fix for inconsistent secondary key index structure. 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 o Fix to prevent the CONVERT/RECLAIM utility from producing an inconsistent index structure in an indexed file during a reclamation. -- COVER LETTER -- Page 51 8 July 2002 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 o 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 o 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: -- COVER LETTER -- Page 52 8 July 2002 - [SYSEXE]CONVERT.EXE - [SYSLIB]CONVSHR.EXE 37 PROBLEMS ADDRESSED IN VMS722_RMS-V0100 KIT o Fix to increase the directory path cache size to accommodate larger directories. A threaded process may deplete the RMS directory path cache when multiple process threads are performing simultaneous directory lookups. This can result in a race condition in which the threads end up in an infinite loop attempting to traverse their respective paths while the cache is being frequently flushed. This problem is aggravated when the directory paths contain long names and/or deep structures. The directory path cache size has been increased to prevent this behavior. Images Affected: - [SYS$LDR]RMS.EXE o Fix to increase the size of RMS's internal ASB stack. RMS's internal ASB stack boundaries may be exceeded due to unanticipated third party EXEC mode activity such as an AST delivery while RMS is operating on its internal stack. Because the stack was initially sized for exclusive RMS use, the stack limits can overflow causing adjacent RMS data structures to become corrupted. This can result in various aberrant RMS conditions including non-fatal EXEC mode System Service Exceptions. Images Affected: - [SYS$LDR]RMS.EXE o Fix to prevent EXEC mode hangs with EXEC ASTs disabled. Under rare circumstances, non-atomic access to an RMS process global data cell could result in status bits being lost during concurrent cell access. A status bit to indicate whether RMS currently has ASTs disabled could inadvertently be cleared through this access resulting in an infinite hang within RMS waiting for an AST delivery, but with EXEC mode ASTs disabled. Atomic access to this cell prevents this from occurring. -- COVER LETTER -- Page 53 8 July 2002 Images Affected: - [SYS$LDR]RMS.EXE o RMS RU journaling fix for an update window when a SIDR (secondary index data record) marked as RU-DELETE may be inappropriately re-marked as deleted while the SIDR is still part of an active recovery unit. If this transaction were aborted, this could result in the new secondary key value being retained in the primary data record. Images Affected: - [SYS$LDR]RMS.EXE o Fixes for problems associated with deleting an accessor of a file with global buffers enabled. The probability of these problems occurring increases not only with processes deleted with a $delprc or stop/id but also if they are also accessing a file that is opened and closed constantly for only one operation, with brief windows when the file has only one accessor (for example, SYSUAF.DAT). - Process hang waiting for exclusive global section process lock if same file is opened more than once and process is deleted during a $connect to the same file before the section is completely initialized. This could leave one stream still holding the exclusive lock when the process is terminated. - Fatal accvio. The last accessor of the file is deleted, and during the abort rundown a new process is waiting to connect to the global section when the global section lock is released by the last accessor. Because the global section is a temporary section and doesn't get marked for delete, there is the possibility of a lag before the section is deleted by the system. There was a potential race condition when the new connect might map to the old global section before it was deleted. This could result in the new mapper using some stale (no longer valid) pointers in the old section. Images Affected: - [SYS$LDR]RMS.EXE - [SYS$LDR]DDIF$RMS_EXTENSION.EXE -- COVER LETTER -- Page 54 8 July 2002 - [SYSLIB]SDARMS$SHARE.EXE - [SYS$LDR]RMSDEF.STB o Enhance minimum process quotas that the RMSREC_SERVER detached process is created with. This server is dedicated to RMS RU journaling detached recovery. ENQLM and PGFLQUOTA are the process quotas that some applications have found it necessary to override the minimum on their system or cluster by increasing the associated PQL_Mxxxx sysgen parameter (e.g. PQL_MENQLM). The defaults for these quotas are now 1 million for ENQLM and 100 thousand for PGFLQUOTA. The enhancement also sets WSEXTENT at runtime to the WSMAX sysgen parameter. Images Affected: - [SYS$LDR]RMS.EXE o Rollback of a remote file transfer change made in V7.2 to its day 1 behavior in order to restore prior performance metrics for remote file transfers that request file transfer mode by setting the SQO (FAB$L_FOP) option. The change was made to ignore the file transfer mode (FTM) request if the remote file was write shared. This has led to a number of reports of applications that previously had SQO specified for remote files that are experiencing significant performance degradations in their remote applications with the V7.2 family and V7.3. We have reviewed the previous behavior for file transfer mode and found that while there is the appearance of locking inconsistencies for readers when FTM is used, there is no potential for data corruption. We have concluded that when users set the FTM (SQO) option, they are in effect giving permission for the same kind of inconsistencies that a user allows when the read-regardless (RRL) option is set. This change restores the pre-V7.2 behavior for the file transfer mode for remote files. If SQO is set, file transfer mode will be used regardless of the sharing specified for the remote file. Users should expect to see the same kind of inconsistencies in reading data as they see when the read-regardless (RRL) option is set. The SQO option should be disabled if this is not acceptable for some application. In addition, to avoid the possibility of a hang that may be induced by retrying remote accesses after a record lock error, users should consider setting both the no-lock (NLK) and read-regardless (RRL) options in the RAB$L_ROP in applications that use the file transfer mode (SQO) option for remote file accesses. (Note: The new NQL (no query locking) option introduced -- COVER LETTER -- Page 55 8 July 2002 in V7.2-1H1 is not supported by the DAP protocol for remote files.) An application should continue to work with the restored behavior without a new change even if a change has been made to an existing application to restore the file transfer mode behavior since the SQO fix was made in V7.2 (e.g., adding the UPI sharing option). There is just one potential problem that we need to point out. For new applications designed and implemented in V7.2 or later that may allow remote accesses to write shared files, they should check whether SQO (FAB$L_FOP) is enabled. Currently the SQO option is being ignored (unless the UPI sharing option is specified), and the file transfer mode is not being used for any remote accesses. With the restore of pre-V7.2 SQO behavior, it will start being used and so the behavior of the application could change. Anyone with a new application that has SQO set and the possibility of write shared files being remotely accessed by the application should consider whether the SQO option needs to be disabled. Images Affected: - [SYS$LDR]RMS.EXE o Fix to prevent an infinite loop in SDA's SHOW PROCESS/RMS. Under rare circumstances, a high priority process utilizing the online System Dump Analyzer (ANALYZE/SYSTEM) to examine a low priority process's RMS attributes (SHOW PROCESS/RMS) may enter an infinite loop. Since the process is at high priority, it may have an adverse impact on other processes on the system. Images Affected: - [SYSLIB]SDARMS$SHARE.EXE o Fix for a user-mode accvio when converting a sequential file when the maximum record size (MRS) in its file header is inappropriately set to zero. Images Affected: - [SYSLIB]CONVSHR.EXE - [SYSEXE]CONVERT.EXE -- COVER LETTER -- Page 56 8 July 2002 38 PROBLEMS ADDRESSED IN VMS722_RTPAD-V0100 KIT o When running RTPAD, a process can hang in LEF state Images Affected: - [SYSEXE]RTPAD.EXE 39 PROBLEMS ADDRESSED IN VMS722_SHADOWING-V0100 KIT o A system can experience many MountVerifcation messages occur with no apparent cause and no errors reported. There is no way to identify what is causing these messages Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE o In a multi-node cluster, some cluster members may hang when accessing a shadowset if: o The shadowset being accessed has multiple members. o All the shadowset members are local to one of the cluster nodes. o All the shadowset members are being MSCP-served by the local node to the other cluster members. o The local node goes down and remains down for at least MVTIMEOUT seconds. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE o On multiple member shadow sets greater than 18 Gigabyte in size, if the port driver returns an SS$_DATACHECK for a IO$_WRITEPBLK, the wrong LBNs will be written by the shadowing driver. This could lead to data corruption. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE -- COVER LETTER -- Page 57 8 July 2002 o On a stand alone system, when a virtual unit aborts, the system could crash with an INVEXCEPTN bugcheck. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE o OPCOM will frequently display a virtual unit device, or the member device string, without any other message. This can be seen during startup if you are using a shadowed system disk, or even during the dismount of the virtual unit or the dismount of members. This has been corrected so that you now will receive a complete VMS message, such as: %SHADOW-I-VOLPROC, DSA719: shadow master has changed. Dump file WILL be written if system crashes. rather than just displaying: DSA719: Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 40 PROBLEMS ADDRESSED IN VMS722_SYS-V0100 KIT o The kill() sys$sigprc CRTL functions return the error SS$_SUSPENDED when the process is neither suspended nor waiting on a resource. The processes is simply waiting on a mutex or is in the transient RWSCS state. This leads to ORA-482 crashes on Oracle 8.1.6 or 8.1.7 OPS could also occur. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB -- COVER LETTER -- Page 58 8 July 2002 o An application that uses signals, may contain processes that hang with an AST (Asynchronous System Trap) queued to it. It hangs until another AST is delivered to the process. Since ASTs are commonly sent to processes, this hang may not be noticed but it will cause some performance degradation. This change will prevent this hang and result in performance improvement. The amount of improvement is dependent on the application causing the hang. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o The following command string should change the path to the disk: $SET DEVICE/SWITCH/PATH=PGB0: $1$DGA11 $DIR $1$DGA11:[000000] $SHOW DEVICE/MULTI Sometimes it does not. Images Affected: - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB o Two new variants of the DE600 have been added to the configuration file. Images Affected: - [SYSEXE]SYS$CONFIG.DAT o 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: -- COVER LETTER -- Page 59 8 July 2002 - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o 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. .le;If a disk is mounted with a /WRITE qualifier on one cluster and a /NOWRITE qualifier on another cluster in the SAN, MountVerification will fail with a WrongVolume status error on the system which had the disk mounted /NOWRITE. This change allows MountVerification to complete successfully in this configuration. .end list .literal Note: To receive this complete correction you must also install the VMS722_MOUNT96-V0100 and VMS722_FIBRE_SCSI-V0200 ECO kits. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.STB o o The system can crash with an INCONMMGST bugcheck. o The system can crash with an PGFIPLHI bugcheck. The dump will be unintelligable where the level 1 page table became invalid. -- COVER LETTER -- Page 60 8 July 2002 Both problems have only been seen after lengthy stress tests where processes had very small working sets. This condition can occur when the system is forced into heavy swapping. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o SYS$GETJPI incorrectly returned BADPARAM, when called with JPI$M_NO_TARGET_INSWAP flag and at least one CTL and PSB item code (like JPI$_IMAGNAME and JPI$_RIGHTS_SIZE). Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o If a packet is requested from non-paged pool that is larger than nonpaged pool's maximum allowed size (NPAGVIR), the request fails but 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 o In an OpenVMS, mixed version, clustered environment, a fatal invalid identifier format (%SYSTEM-F-IVIDENT) error can result on versions of OpenVMS that are not OpenVMS COE (Common Operating Environment) compliant. -- COVER LETTER -- Page 61 8 July 2002 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 - [SYSLIB]SECURESHR.EXE - [SYSLIB]SECURESHRP.EXE o 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 o A call to $GETJPI to return information about the calling process could return a SS$_NOPRIV status. This occurs if the 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 -- COVER LETTER -- Page 62 8 July 2002 - SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - SYS$LDR]PROCESS_MANAGEMENT_MON.STB o Calls to the $SNDOPR system service can result in a SS$_MBFULL return status: status = sys$sndopr(&req_desc, 0); This change increases the size of the OPCOM mailbox. With faster systems, OPCOM messages are being generated faster and accumulating 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, this change 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. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB o The system can experience an INVEXCEPTN bugcheck at SCH$QEND_C+001E0 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 -- COVER LETTER -- Page 63 8 July 2002 - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o The system can crash with a "REFCNTNEG, PFN reference count is negative" bugcheck at MMG$DELETE_BUFOBJ_C+00B7C, SYS$VM+251CC, in routine DELBUFOBJPAGES. Another REFCNTNEG bugcheck, caused by the same problem, could also occur at MMG$DELETE_BUFOBJ_C+00E24, SYS$VM+25474, in routine DECPT_BUFOBJ. The bugcheck is caused by PFN database corruption. 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. Images Affected: - [SYS$LDR]SYS$VM.EXE o The system can crash with an RNLSTAKNV, Kernel stack not valid, bugcheck during process or image rundown. 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 Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o 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 -- COVER LETTER -- Page 64 8 July 2002 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 o The system can crash with an "SSRVEXCEPT, Unexpected system service" bugcheck. Crashdump Summary Information: ------------------------------ Bugcheck Type: SSRVEXCEPT, Unexpected system service exception Current Process: ACMS00ESP001000 Current Image: DSA4:[DTV.EXE]DTVSV750.EXE;5 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 41 PROBLEMS ADDRESSED IN VMS722_SYSLOA-V0200 KIT o Two systems in a cluster can crash with a LOCKMGRERR bugcheck. Crashdump Summary Information: ------------------------------ Bugcheck Type: LOCKMGRERR, Error detected by Lock Manager Current Process: _OVRNITE3921 Current Image: Failing PC: FFFFFFFF.8022DB48 LCK$SND_CVTREQ_C+00EE8 -- COVER LETTER -- Page 65 8 July 2002 Failing PS: 38000000.00000804 Module: SYS$CLUSTER (Link Date/Time: 29-DEC-1999 04:13:30.44) Offset: 0001FB48 Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE o All FTP client process and many others (including SECURITY_SERVER) can end up waiting for a cluster lock which is being held by another system.When this happens, all new logins (telnet, FTP, Network, Console) on ANY node of the cluster hang. Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE o Following an attempt to deallocate a structure whose W_SIZE offset contains 0, 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. Crashdump Summary Information: ------------------------------ Bugcheck Type: BADDALRQSZ, Bad memory deallocation request size or address Current Process: Current Image: [SYS0.SYSCOMMON.] [SYSEXE]TCPIP$IMAP_SERVER.EXE Failing PC: FFFFFFFF.800432B4 EXE$DEANONPGDSIZ_C+000C4 Failing PS: 20000000.00000801 Module: SYSTEM_PRIMITIVES (Link Date/Time: 5-AUG-2001 01:12:07.09) Offset: 000152B4 Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE -- COVER LETTER -- Page 66 8 July 2002 42 PROBLEMS ADDRESSED IN VMS722_SYSLOA-V0100 KIT o Audit data is not captured for non-trusted processes. Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE 43 KIT INSTALLATION RATING: The following kit 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) INSTALLATION RATING: INSTALL_1 : To be installed by all customers. 44 INSTALLATION INSTRUCTIONS: 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 VMS722_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 This kit requires a system reboot. Compaq 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. -- COVER LETTER -- Page 67 8 July 2002 44.1 Special Installation Instructions: 44.1.1 SYSGEN Parameter Changes As part of the post installation processing of this kit, two SYSGEN parameters (PIOPAGES and IMGIOCNT) will be modified in order to accommodate changes being made within the RMS image. The post installation process will make an effort to add appropriate lines to the MODPARAMS.DAT files for all system roots found on the installation disk and will perform a SYSGEN write current with the modifications on the system from which this kit is being installed. The installation process will provide the status of these changes and any further instructions as necessary. 44.1.2 %INSTALL-E-NODELSHRADR Error Message During installation you may see the following message: %INSTALL-E-NODELSHRADR, unable to delete image with shareable address data -INSTALL-I-PLSREBOOT, please reboot to install a new version of this image This is not a cause for concern. It simply means that DECC$SHR.EXE was installed as a resident image, which is the standard configuration for OpenVMS Alpha systems. The new image will not take effect until the system is rebooted. 44.1.3 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following definitions and commands: - Define logical NO_ASK$BACKUP as TRUE - Define logical NO_ASK$REBOOT as TRUE - Define logical ARCHIVE_DW_MOT_MUP as TRUE if you wish to delete the replaced files. If you do not want the replaced files deleted (NOT recommended by Compaq), define this logical as FALSE. -- COVER LETTER -- Page 68 8 July 2002 - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V1.0 - De-assign the logicals assigned For example, a sample command file to install the VMS722_UPDATE-V0100 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/SYS ARCHIVE_DW_MOT_MUP "TRUE" $! $ PROD INSTALL VMS722_UPDATE/PROD=DEC/BASE=AXPVMS/VER=V1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $ DEASSIGN/SYS ARCHIVE_DW_MOT_MUP $! $ exit Copyright (c) Compaq Computer Company, 2002 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. COMPAQ, the COMPAQ logo, VAX, Alpha, VMS, and OpenVMS are registered in the U.S. Patent and Trademark Office. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from COMPAQ are 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. COMPAQ shall not 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 COMPAQ 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 -- COVER LETTER -- Page 69 8 July 2002 OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.