ECO NUMBER:     VMS721H1_UPDATE-V0500
             PRODUCT:        OpenVMS Alpha OPERATING SYSTEM V7.2-1H1
             UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1H1




                                COVER LETTER


1  KIT NAME:

     VMS721H1_UPDATE-V0500


2  KITS SUPERSEDED BY THIS KIT:


      o  VMS721H1_ACRTL-V0200

      o  VMS721H1_AUDSRV-V0200

      o  VMS721H1_CLIUTL-V0300

      o  VMS721H1_CPU2308-V0200

      o  VMS721H1_DDTM-V0100

      o  VMS721H1_DRIVER-V0200

      o  VMS721H1_DW_MOT_MUP-V0100

      o  VMS721H1_F11X-V0100

      o  VMS721H1_FIBRE_SCSI-V0400

      o  VMS721H1_IPC-V0200

      o  VMS721H1_LAN-V0200

      o  VMS721H1_LAT-V0100

      o  VMS721H1_LIBRTL-V0400

      o  VMS721H1_MAIL-V0300

      o  VMS721H1_MANAGE-V0200

      o  VMS721H1_MOUNT96-V0200

      o  VMS721H1_PPPD-V0100

      o  VMS721H1_PTHREAD-V0100

      o  VMS721H1_RENAME_OLD-V0100

      o  VMS721H1_RMS-V0600

      o  VMS721H1_RPC-V0100

      o  VMS721H1_SHADOWING-V0500

-- COVER LETTER --                                              Page 2
                                                         18 March 2002


      o  VMS721H1_SYS-V0400

      o  VMS721H1_SYSLOA-V0300

      o  VMS721H1_UPDATE-V0400

      o  VMS721H1_VX1-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-1H1


     4.2  Files patched or replaced:


      o  [SYSEXE]AGEN$FEEDBACK.EXE (new image)

      o  [SYSEXE]APB.EXE (new image)

      o  [SYSEXE]AUDIT_SERVER.EXE (new image)

      o  [SYSMSG]CLIUTLMSG.EXE (new image)

      o  [SYSEXE]CONVERT.EXE (new image)

      o  [SYSLIB]CONVSHR.EXE (new image)

      o  [SYSEXE]CREATE.EXE (new image)

      o  [SYSEXE]DBGHK$HOST_KERNEL.EXE (new image)

      o  [SYSEXE]DBGHK$SYSDUMP_KERNEL.EXE (new image)

      o  [SYSLIB]DCE$LIB_SHR.EXE (new image)

-- COVER LETTER --                                              Page 3
                                                         18 March 2002


      o  [SYSLIB]DCE$SOCKSHR_DNET_IV.EXE (new image)

      o  [SYSLIB]DCE$SOCKSHR_DNET_OSI.EXE (new image)

      o  [SYS$LDR]DDIF$RMS_EXTENSION.EXE (new image)

      o  [SYSLIB]DEBUG.EXE (new image)

      o  [SYSEXE]DEBUG_APB.EXE (new image)

      o  [SYSLIB]DECC$SHR.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  [SYSLIB]DECW$SVEXT_DEC_PEER_GLX.EXE (new image)

      o  [SYSLIB]DECW$SVEXT_GLX_P350.EXE (new image)

      o  [SYSLIB]DECW$PORT_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)

      o  [SYSLIB]DECW$TRANSPORT_TCPIP.EXE (new image)

      o  [SYSEXE]DECW$XFS.EXE (new image)

-- COVER LETTER --                                              Page 4
                                                         18 March 2002


      o  [SYSLIB]DISMNTSHR.EXE (new image)

      o  [SYSEXE]DISMOUNT.EXE (new image)

      o  [SYSLIB]DTSS$SHR.EXE (new image)

      o  [SYSEXE]EDF.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  [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  [SYSLIB]IOGEN$SHARE.EXE (new image)

      o  [SYS$LDR]IO_ROUTINES.EXE (new image)

      o  [SYS$LDR]IO_ROUTINES_MON.EXE (new image)

      o  [SYSEXE]JBC$JOB_CONTROL.EXE (new image)

      o  [SYSLIB]LAN$SDA.EXE (new image)

      o  [SYSEXE]LANACP.EXE (new image)

      o  [SYSEXE]LANCP.EXE (new image)

      o  [SYS$LDR]LAT$RATING.EXE (new image)

      o  [SYSLIB]LAT$SHR.EXE (new image)

      o  [SYSEXE]LATACP.EXE (new image)

      o  [SYSEXE]LATCP.EXE (new image)

      o  [SYSEXE]LATSYM.EXE (new image)

      o  [SYSLIB]LIBRTL.EXE (new image)

      o  [SYSLIB]LIBRTL_INSTRUMENTED.EXE (new image)

-- COVER LETTER --                                              Page 5
                                                         18 March 2002


      o  [SYS$LDR]LOCKING.EXE (new image)

      o  [SYS$LDR]LOGICAL_NAMES.EXE (new image)

      o  [SYSEXE]LTPAD.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  [SYS$LDR]MESSAGE_ROUTINES.EXE (new image)

      o  [SYSEXE]MIME.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)

      o  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image)

      o  [SYSLIB]PTHREAD$DBGSHR.EXE (new image)

      o  [SYSLIB]PTHREAD$RTL.EXE (new image)

      o  [SYSEXE]QUEMAN.EXE (new image)

      o  [SYS$LDR]RMS.EXE (new image)

      o  [SYSLIB]SDA$SHARE.EXE (new image)

      o  [SYSLIB]SDARMS$SHARE.EXE (new image)

      o  [SYSLIB]SECURESHR.EXE (new image)

      o  [SYSLIB]SECURESHRP.EXE (new image)

      o  [SYS$LDR]SECURITY.EXE (new image)

      o  [SYS$LDR]SECURITY_MON.EXE (new image)

      o  [SYSEXE]SET.EXE (new image)

-- COVER LETTER --                                              Page 6
                                                         18 March 2002


      o  [SYSEXE]SETAUDIT.EXE (new image)

      o  [SYSEXE]SHADOW_SERVER.EXE (new image)

      o  [SYSEXE]SHOW.EXE (new image)

      o  [SYSEXE]SHWCLSTR.EXE (new image)

      o  [SYSLIB]SMI$OBJSHR.EXE (new image)

      o  [SYSLIB]SMI$SHR.EXE (new image)

      o  [SYSEXE]SMISERVER.EXE (new image)

      o  [SYS$LDR]SYS$ASNDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$BASE_IMAGE.EXE (new image)

      o  [SYS$LDR]SYS$CLUSTER.EXE (new image)

      o  [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE (new image)

      o  [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE (new image)

      o  [SYS$LDR]SYS$CPU_ROUTINES_2508.EXE (new image)

      o  [SYS$LDR]SYS$DKDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$DQDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$DRDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$DUDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$ECDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$EIBTDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$EIDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$ELDRIVER4.EXE (new image)

      o  [SYS$LDR]SYS$ERBTDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$ERDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$ESDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$EW1000A.EXE (new image)

      o  [SYS$LDR]SYS$EWBTDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$EWDRIVER.EXE (new image)

-- COVER LETTER --                                              Page 7
                                                         18 March 2002


      o  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image)

      o  [SYS$LDR]SYS$EZDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$FADRIVER.EXE (new image)

      o  [SYS$LDR]SYS$FCBTDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$FCDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$gkFGEDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$FRBTDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$FRDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$FWBTDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$FWDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$GALAXY.EXE (new image)

      o  [SYS$LDR]SYS$GBDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$GFDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$GKDRIVER.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$HWDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$HWDRIVER4.EXE (new image)

      o  [SYS$LDR]SYS$ICDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$INDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$IPC_SERVICES.EXE (new image)

      o  [SYS$LDR]SYS$IRDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$IWDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$LAN.EXE (new image)

      o  [SYS$LDR]SYS$LAN_ATM.EXE (new image)

      o  [SYS$LDR]SYS$LAN_ATM4.EXE (new image)

-- COVER LETTER --                                              Page 8
                                                         18 March 2002


      o  [SYS$LDR]SYS$LAN_CSMACD.EXE (new image)

      o  [SYS$LDR]SYS$LAN_FDDI.EXE (new image)

      o  [SYS$LDR]SYS$LAN_TR.EXE (new image)

      o  [SYS$LDR]SYS$LTDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$MCDRIVER.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$PKCDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$PKEDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$PKJDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$PKQDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$PKSDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$PKTDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$PKWDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$PKZDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$PLUS_SHDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$PPPDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$SHDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$SMHANDLER_SLAVE_2308.EXE (new image)

      o  [SYSLIB]SYS$SSISHR.EXE (new image)

      o  [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE (new image)

      o  [SYS$LDR]SYS$TUDRIVER.EXE (new image)

      o  [SYS$LDR]SYS$VCC.EXE (new image)

      o  [SYS$LDR]SYS$VCC_MON.EXE (new image)

      o  [SYS$LDR]SYS$VM.EXE (new image)

      o  [SYS$LDR]SYS$WSDRIVER.EXE (new image)

-- COVER LETTER --                                              Page 9
                                                         18 March 2002


      o  [SYSEXE]SYSBOOT.EXE (new image)

      o  [SYS$LDR]SYSGETSYI.EXE (new image)

      o  [SYS$LDR]SYSLDR_DYN.EXE (new image)

      o  [SYSEXE]SYSMAN.EXE (new image)

      o  [SYSMSG]SYSMSG.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  [SYSUPD]AUTOGEN.COM (new file)

      o  [SYSUPD]CRTL.OBJ (new file)

      o  [SYSUPD]CRTLMSGDEF.OBJ (new file)

      o  [SYSMGR]DCE$RPC_STARTUP.COM (new file)

      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$P350_SINGLE_CPU.COM (new file)

      o  [SYSMGR]DECW$STARTSERVER.COM (new file)

      o  [SYSUPD]DISMOUNT.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  [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)

-- COVER LETTER --                                             Page 10
                                                         18 March 2002


      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]IODEF.STB (new file)

      o  [SYS$LDR]IO_ROUTINES.STB (new file)

      o  [SYS$LDR]IO_ROUTINES_MON.STB (new file)

      o  [SYSEXE]IPCDEF.STB     

      o  [SYS$STARTUP]LAN$STARTUP.COM (new file)

      o  [SYSLIB]LIBRTL.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  [SYSHLP]MIME$HELP.HLB (new file)

      o  [SYS$LDR]MULTIPATH.STB (new file)

      o  [SYS$LDR]MULTIPATH_MON.STB (new file)

      o  [SYSHLP]P300_350_README.HTML (new file)

      o  [SYSHLP]P300_350_README.PDF (new file)

      o  [SYSHLP]P300_350_README.TXT (new file)

      o  [SYS$LDR]PROCESS_MANAGEMENT.STB (new file)

      o  [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file)

-- COVER LETTER --                                             Page 11
                                                         18 March 2002


      o  [SYS$LDR]RMSDEF.STB (new file)

      o  [SYS$LDR]SECURITY.STB (new file)

      o  [SYS$LDR]SECURITY_MON.STB (new file)

      o  [SYSUPD]SET.CLD (new file)

      o  [SYSEXE]SYS$CONFIG.DAT (new file)

      o  [SYSLIB]SYS$LIB_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]SYSGETSYI.STB (new file)

      o  [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file)

      o  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file)

      o  [SYS$STARTUP]VMS$CONFIG-050_JOBCTL.COM (new file)

      o  [SYS$STARTUP]VMS$CONFIG-050_LMF.COM (new file)

      o  [SYS$STARTUP]VMS$LPBEGIN-050_STARTUP.COM (new file)

      o  [SYSHLP]VMS721H1_UPDATE-V0500.RELEASE_NOTES (new file)

      o  [SYSHLP]VMS721H1_VX1-V0200_CVRLET.TXT (new file)



5  PROBLEMS ADDRESSED IN VMS721H1_UPDATE-V0500 KIT


      o  The VMS721H1_UPDATE-V0500 ECO kit is  a  consolidation  of  ECO
         kits that have shipped since the release of, and including, the
         VMS721H1_UPDATE-V0400 ECO kit.  There are  no  new  changes  in
         this kit.

         If you have installed all the kits  listed  under  the  heading
         "KITS  SUPERSEDED  BY THIS KIT:" you do not need to install the
         VMS721H1_UPDATE-V0500 remedial kit.

         With   the   exception   of   the   VMS721H1_UPDATE-V0400   and
         VMS721H1_VX1-V0200  ECO  kits,  the following sections describe
         the  problems  addressed  by  the  superseded  kits.   Problems
         addressed  by  the VMS721H1_UPDATE-V0400 and VMS721H1_VX1-V0200
         can be found in the following separate files:

-- COVER LETTER --                                             Page 12
                                                         18 March 2002


          o  [SYSHLP]VMS721H1_UPDATE-V0400.README

          o  [SYSHLP]VMS721H1_VX1-V0200_CVRLET.TXT




6  PROBLEMS ADDRESSED IN KIT VMS721H1_ACRTL-V0200


      o  Linker informational "%LINK-I-DATMISMCH"

         After installation of previous CRTL ECO kits, user sees:

             %LINK-I-DATMISMCH, creation date of <date> <time> in
             shareable image SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1
             differs from date of <date> <time> in shareable image 
             library SYS$COMMON:[SYSLIB]IMAGELIB.OLB

         Previous ECO kits did not correctly replace DECC$SHR.EXE in the
         system IMAGELIB.OLB, which resulted in this message.

         This change is Alpha only.

      o  C$ERRNO symbols not defined in STARLET

         The linker reported multiple definitions when linking  programs
         referencing the following symbols.

         This was because C$ERRNO was not inserted  in  STARLET.OLB  for
         Selective search.

          o  C$_SIG0
          o  C$_SIGN
          o  C$_SIGPIPE
          o  C$_SIGCHLD
          o  C$_HOST_NOT_FOUND
          o  C$_TRY_AGAIN
          o  C$_NO_RECOVERY
          o  C$_NO_DATA
          o  C$_NO_ADDRESS
          o  C$_NO_TCP
          o  C$_NOSYSSHR
          o  C$_EXIT1
          o  C$_EXIT255
          o  C$_ILLSYSTDF
          o  C$_QSORT2BIG

         This was a problem with previous CRTL ECO kits.

         This change is Alpha only.

      o  mktime() performance

         Function mktime()'s  algorithm  locked  thread  specific  data,
         which didn't need to be done.  This change uses stack allocated

-- COVER LETTER --                                             Page 13
                                                         18 March 2002


         data, and improves performance.

      o  Performance in open()

         Function open() had unnecessary  calls  to  SYS$GETJPI.   These
         were removed.

      o  Functions mmap() and munmap() changes

         Several  problems  in  function  mmap()   and   munmap()   were
         addressed.

          -  Calling function mmap() could result in memory  corruption,
             when specifying specific addresses in parameter addr.

             Under  complex  conditions  the  CRTL  sometimes  allocated
             internal  memory  needed  by  the  CRTL  for mmap() related
             routines in the address space mapped, which could result in
             memory corruption.

             This change is Alpha only.

          -  Function mmap(), with parameter addr set to 0, now  returns
             the  first  available chunk of memory from the freelist (if
             any).  It previously returned a "best fit" chunk  from  the
             freelist.

             This change is Alpha only.

          -  Function  munmap()  would  sometimes  fail  when  releasing
             memory allocated with MAP_ANON.  This is because it wrongly
             tried to deassign a file channel that  was  not  associated
             with the memory range.

          -  Function mmap() was incorrectly  specifying  global  memory
             when MAP_ANON is specified.

             Change will only do this with flag MAP_SHARED specified.


      o  Function gettimeofday() fails without setting errno

         Function  gettimeofday()  now   sets   errno   and   vaxc$errno
         appropriately  if  UTC  time functions fail because of a system
         service failure.

      o  Function getcwd() returns wrong case string for device

         In UNIX mode, getcwd() returns uppercase for the device.

         This problem was introduced in CRTL kits VMS721_ACRTL-V0200 and
         VMS721H1_ACRTL-V0100.

         Case  preservation   in   files   names   was   introduced   in
         VMS721_ACRTL-V0200.   This  only  applies  to  files  saved  or
         reported from ODS-5 devices.  The case of the logical  name  or

-- COVER LETTER --                                             Page 14
                                                         18 March 2002


         device name was preserved using this same rule.



7  PROBLEMS ADDRESSED IN KIT VMS721H1_ACRTL-V0100


      o  File creation incorrectly inherits directory attributes

         The file creation functions  (fopen,  open,  creat)  have  been
         corrected  to not inherit file attributes if a directory by the
         same name exists for the  file  being  created.   For  example,
         creating  a  file named "foo." in a directory which contained a
         "foo.dir" would incorrectly inherit file attributes  from  this
         directory file.

      o  Incorrect timestamp returned from stat and fstate functions

         The stat function no longer puts the wrong values into st_?time
         members of the stat structure.  More precisely, during daylight
         savings time the values of st_?time  are  no  longer  one  hour
         ahead  from  file  creation/modification  time  reported by the
         $DIRECTORY command.

      o  Support for timezones requiring a TDF of -13

         The time functions time, ftime, gettimeofday and getclock would
         fail  for  a  TDF  (time differential factor) of -13 hours, the
         value required in New Zealand.  According to  the  U.S.   Naval
         Observatory  information  the valid range for the TDF is -13.75
         to +13, inclusive.  The C RTL now allows this full range.

      o  Calling _malloc64 in threaded application may access violate

         The _malloc64 function was corrected to allow initialization of
         this function in a threadsafe manner.  Prior to this change, if
         the first call occurs after the program  has  created  multiple
         threads  and  more than one thread calls the _malloc64 routine,
         an access violation may occur.

      o  Correct interpretation of years in strptime function

         In the previous  ECO  kit,  a  change  was  introduced  to  the
         function    strptime()   for   XPG5-compatibility   to   handle
         expressions for the 2-digit year format %y when the century was
         not  specified.   The  requirement  is for 2-digit years in the
         range 0-68 to be treated as 21st century and years in the range
         69-99  as  20th  century.  The 2-digit years in the range 69-99
         were incorrectly being treated as 21st century.

      o  Prefixing of image names in execlp and execvp functions

         The execlp and execvp functions were unconditionally  prefixing
         the  file  specification  of  the  image to be run in the child
         process  with  "VAXC$PATH:"  string.   When  passed   a   fully
         qualified  file  specification, this would result in an invalid

-- COVER LETTER --                                             Page 15
                                                         18 March 2002


         file specification.

      o  Seeking past end of file no longer extends the physical file

         The behavior of lseek() and fseek() at positions beyond the end
         of  data  in  a  file  were  not  conforming  to the POSIX/ANSI
         standard.  The file was being physically null  padded  on  disk
         even  though  the  standard  only requires this null padding if
         data is actually written at this point.  In the  case  reported
         by  the  user,  seeking  to  the end of a file by using a large
         offset would take a long time and may  exhaust  available  disk
         space.    To   get   the   POSIX   behavior,  you  must  define
         DECC$POSIX_SEEK_STREAM_FILE as "ENABLE".  The default  behavior
         is unchanged.

      o  Implicitly open files for shared access

         The Compaq C RTL was enhanced to  open  all  files  for  shared
         access  as if the "shr=del,get,put,upd" option was specified in
         the open* or creat call.  To enable this  feature,  define  the
         logical  name  DECC$FILE_SHARING  to  the  value "ENABLE".  The
         value is case-insensitive and is checked only  once  per  image
         activation, not on a file-by-file basis.

      o  Writing large amounts of data to a pipe

         The Compaq C RTL was failing when the amount of data written to
         a  pipe  exceeded  the  buffer  size of that pipe.  The RTL now
         breaks the large write into a sequence of writes whose size  is
         the size of the underlying mailbox used to implement pipes.

      o  Image  exit  handler  processing  changed  to  avoid  hangs  in
         multithreaded programs

         A problem was reported that the RTL could  hang  if  exit  were
         called  while  threads  were  continuing  to  do I/O.  Analysis
         showed that the hang was caused by a thread  holding  the  lock
         necessary  to  close  the file and the exit handler blocking on
         this lock.  The change implemented was to not attempt to  close
         files whose locks were currently in use.

      o  Extending a file using ftruncate does not extend  the  physical
         file

         When  a  stream  file  is  extended  using  ftruncate()  it  is
         documented  that  the extended area will be filled with zeroes.
         This is now done correctly.  Prior to this change, the file was
         not extended.

      o  Select function is not terminated by exceptions as documented

         The documentation of the select function states that it returns
         either  when  a socket is ready to be read or written, when the
         timeout period expires, or when exceptions occur.  It  was  not
         properly  terminating when an exception occurred.  This problem
         was corrected by dynamically linking to and  calling  an  abort

-- COVER LETTER --                                             Page 16
                                                         18 March 2002


         function  in  the  socket  library.   A  complete correction to
         interrupting the select function will also require an  ECO  kit
         from  the  Compaq  TCP/IP product which includes this new abort
         function.

      o  Calls to fstat function may result in an Access Violation

         The fstat function was corrected to  not  access  violate  when
         called   with   stdin,   stdout,   stderr,   or   a   directory
         specification.

      o  Supporting search lists in calls to chdir

         The chdir function  was  not  well  behaved  when  the  calling
         program  passed  an  argument  which was a search list logical.
         The chdir function was  unconditionally  changing  the  logical
         sys$disk to the first member of the search list was effectively
         dropping the remaining members.  The change in behavior is seen
         as  a step in the right direction, but there are plans for more
         work in this area.

      o  Support of hyphens in file specifications

         The RTL functions which process file  specifications  were  not
         correctly  processing files which contained a hyphen character.
         The RTL was incorrectly assuming that hyphens were only allowed
         to specify a relative directory path.

      o  Enhancements made in ODS-5 support

         The Compaq C RTL functions which make calls to  RMS  have  been
         modified  to  better support ODS-5 disks.  This is an extensive
         set of changes throughout the RTL to support case preservation,
         long  file  names,  and non-standard file name characters.  The
         default behavior of the RTL has not changed.

         The Compaq C RTL supports case preservation in  file  names  on
         ODS  level  5  disks.   This applies when creating or reporting
         file names.  By default, this feature is disabled.   To  enable
         this  feature define the logical name DECC$EFS_CASE_PRESERVE to
         "ENABLE".   If  file  names  are  all  in  upper  case,  define
         DECC$EFS_CASE_SPECIAL  to  "ENABLE"  to  convert the names into
         lower case when reporting the name  in  UNIX  style.   If  file
         names are not all in upper case, then the case is preserved.

         Most C RTL functions now accept long OpenVMS-style  file  names
         as arguments.  For OpenVMS Alpha Version 7.2, some basic Compaq
         C RTL I/O functions (creat, stat, and the  functions  from  the
         open   family  of  functions)  were  enhanced  to  accept  long
         OpenVMS-style file names for an ODS-5 device.

         In this ECO kit, all other Compaq C RTL functions, except chdir
         and  the functions from the exec family of functions, were also
         enhanced to accept long OpenVMS-style file names for  an  ODS-5
         device.

-- COVER LETTER --                                             Page 17
                                                         18 March 2002


         All  C  RTL  functions  that  accept  or   report   full   file
         specifications  will  process  file  specifications  up to 4095
         bytes long, subject to the rules defined for the media  format.
         For file specifications in OpenVMS format, there are no special
         restrictions.  In situations where a  full  file  specification
         cannot  be  reported  because  the  buffer  is  too  short, the
         function attempts to report the abbreviated name.

         There are restrictions with UNIX file names.  Names  containing
         special   characters,  such  as  multiple  periods,  caret,  or
         multinational characters, may be rejected.  A function call may
         report  failure  if  the  output  buffer is not large enough to
         receive the full name.  For OpenVMS-style names,  the  reported
         name  would  contain  a  FID-abbreviated  name.   There  is  no
         representation of FID-abbreviated names defined for UNIX.

      o  Disabling logical name translation in decc$to_vms function

         The Compaq C RTL was enhanced to allow interpreting the leading
         part   of   a   UNIX-style   file  specification  as  either  a
         subdirectory name or a device name.

         The translation of the UNIX-style file name  "foo/bar"  to  the
         OpenVMS-style  file  name "foo:bar" was the only translation in
         previous versions OpenVMS.  It remains the default.

         To request translation of the UNIX-style name "foo/bar" to  the
         OpenVMS-style  name  "[.foo]bar",  DEFINE the following logical
         name:

         $ DEFINE DECC$DISABLE_TO_VMS_LOGNAME_TRANSLATION ENABLE

         To return to the default file-name translation, either DEASSIGN
         the logical name or set the value to DISABLE.  The logical name
         is  checked  only  once  per  image  activation,   not   on   a
         file-by-file basis.

      o  Case-sensitive support in argv/argc program arguments

         Non-quoted command line arguments passed to C and C++  programs
         (argv  arguments) can now optionally have their case preserved,
         rather than being  lowercased  as  in  previous  versions.   By
         default, this feature is disabled.

         To enable this case preservation feature,  define  the  logical
         name    DECC$ARGV_PARSE_STYLE   to   "ENABLE"   and   set   the
         process-level DCL parse style flag to "EXTENDED" in the process
         running  the  program.  Enabling this feature also ensures that
         the image name returned in argv[0] is also case-preserved.

         $ SET PROCESS/PARSE_STYLE=EXTENDED

      o  Accepting opendir("..") as a valid directory specification

         The opendir function now accepts ".." to be equivalent to  both
         "../" and "[-]".

-- COVER LETTER --                                             Page 18
                                                         18 March 2002


      o  Correction made to stat("file.dir") which was not a directory

         The stat functions were not correctly handling files which were
         not directories but did use a .dir extension.  This problem was
         discovered when porting an application which used a  .dir  file
         type for a UNIX file that was not a directory.



8  PROBLEMS ADDRESSED IN VMS721H1_AUDSRV-V0200 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




9  PROBLEMS ADDRESSED IN VMS721H1_AUDSRV-V0100 KIT


      o  The command reply  mailbox  timeout  has  been  raised  to  120
         seconds  for  the SET AUDIT/SERVER=INITIATE command.  The retry
         timer for Object Initiation has been  dropped  to  15  seconds.
         This allows multiple INIT retries before the command times out.
         Before this change, any object INIT retry would be meaningless,
         since  it  would not be attempted until after the command timed
         out, which could result in a failure status  for  a  successful
         operation.

         Images Affected:

          -  [SYSEXE]SETAUDIT.EXE

          -  [SYSEXE]AUDIT_SERVER.EXE


      o  A cluster-wide AUDIT_SERVER hang prevents boot from completing.
         A  deadlock  exists  within  the  object  server portion of the
         AUDIT_SERVER.  The deadlock  is  triggered  by  some  boot-time
         commands that were added to the startup procedures.

         Images Affected:

          -  [SYSEXE]AUDIT_SERVER.EXE           


      o  The order in which certain  locks  are  taken  was  changed  to
         prevent  deadlocks  between blocking locks and RMS record locks
         on the Objects database.

-- COVER LETTER --                                             Page 19
                                                         18 March 2002


         Images Affected:

          -  [SYSEXE]AUDIT_SERVER.EXE


      o  Delete an unused reply mailbox before returning to the caller.

         Images Affected:

          -  [SYSEXE]SETAUDIT.EXE


      o  The command SET AUDIT/NOLISTENER fails under all circumstances.
         See error message below:

         $ set audit/nolistener
         %SET-E-VERIFYFAIL, specified operation was not performed
         due to the following error:
         -AUDSRV-W-REQPKTINV, required packet missing or invalid;
         requester PID:00000000
         $


         Images Affected:

          -  [SYSEXE]AUDIT_SERVER.EXE


      o  Modify the handling of AUDIT_SERVER INITIATION to better handle
         and report server startup failures.

         Images Affected:

          -  [SYS$STARTUP]VMS$LPBEGIN-050_STARTUP.COM




10  PROBLEMS ADDRESSED IN VMS721H1_CLIUTL-V0300 KIT


      o  After installation of VMS721H1_CLIUTL-V0200  ECO  kit,  a  SHOW
         QUEUE  command  gives  incorrect  output.   Some fields are not
         displayed in the correct columns and some  data  items  in  the
         show queue and show entry displays are missing completely.

         For example a SHOW QUEUE/ALL command  leads  to  the  following
         output:

         Entry  Jobname   Username       Status
         -----  -------   --------       ------
           119  TEST      no privilege           File:  SLS  Pending


-- COVER LETTER --                                             Page 20
                                                         18 March 2002


         Images Affected:

          -  [SYSMSG]CLIUTLMSG.EXE




11  PROBLEMS ADDRESSED IN VMS721H1_CLIUTL-V0200 KIT


      o  When a process exists on the system that is in the MUTEX or CEF
         state,  a  SHOW  SYSTEM  command  will  ACCVIO  when the /STATE
         qualifier is used.  For example:

         QUEBIT>  SHOW SYS/STATE=MUTEX
         %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
         address=FFFFFFFFC0022A58, PC=0000000000042BE0, PS=0000001B


         Images Affected:

          -  [SYSEXE]SHOW.EXE


      o  The system can crash with an SSRVEXCEPT bugcheck in  SHOW+61DA0
         or  SHOW+62050.   with  an  ACCVIO  executing  instruction  LDL
         R18,#X0014(R0) and R0=007812f2 %SHOW-E-INSVIRMEM

         This problem has been seen when running the Apache WEB server.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     SSRVEXCEPT, Unexpected system service 
                            exception
         Current Process:   APACHE$WWW_19
         Current Image:     DSA100:[SYS1.SYSCOMMON.][SYSEXE]SHOW.EXE
         Failing PC:        00000000.00051DA0    SHOW+61DA0
         Failing PS:        00000000.00000003
         Module:            SHOW
         Offset:            00061DA0



         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     SSRVEXCEPT, Unexpected system service
                            exception
         Current Process:   APACHE$WWW_20
         Current Image:     DSA1:[SYS2.SYSCOMMON.][SYSEXE]SHOW.EXE
         Failing PC:        00000000.00052050    SHOW+62050
         Failing PS:        00000000.00000003
         Module:            SHOW
         Offset:            00062050


-- COVER LETTER --                                             Page 21
                                                         18 March 2002


         Images Affected:

          -  [SYSEXE]SHOW.EXE


      o  On volumes where the INDEXF.SYS file size exceeds the  MAXFILES
         value  for  the volume, a volume rebuild operation will ACCVIO.
         VERIFY shows no problems but the commands to rebuild the volume
         will consistently fail.

         Note: To receive this complete change you must also install
               the VMS721H1_MOUNT-V0200 ECO kit.

         Images Affected:

          -  [SYSEXE]SET.EXE


      o  When a SHOW QUEUE command is entered, a queue entry number that
         is  over  10  million  shows as asterisks rather than the queue
         entry number.

         Images Affected:

          -  [SYSEXE]QUEMAN.EXE

          -  [SYSMSG]CLIUTLMSG.EXE


      o  A SET VOLUME/REBUILD command on a volume set, where a node that
         had  it  mounted  did  not  update  the  volume  write count on
         dismount (or a crash), does not reset the volume write count to
         the   correct  number  of  writers  in  the  cluster.   A  SHOW
         DEVICE/REBUILD command always shows this volume  as  needing  a
         rebuild.   Even  a SET VOLUME/REBUILD=FORCE will not clear this
         rebuild status.

         Note: To receive this complete change you must also install
               the VMS721H1_MOUNT96-V0200 ECO kit.


         Images Affected:

          -  [SYSLIB]MOUNTSHR.EXE


      o  In a  SET  FILE/LOG/VERSION  command,  the  /LOG  qualifier  is
         ignored.  For example:

            SYSTEM1>SET FILE/LOG/VER LOGIN.COM;
            SYSTEM1>


         The correct behavior is:

            SYSTEM1>SET FILE/LOG/VER LOGIN.COM;

-- COVER LETTER --                                             Page 22
                                                         18 March 2002


            %SET-I-MODIFIED, WORK:[USER1]LOGIN.COM;2 modified
            SYSTEM1>


         Images Affected:

          -  [SYSEXE]SET.EXE


      o  An invalid "error opening file" message could be displayed.

         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
         the  informational  message does not reflect the actual case of
         the directory.

         For example:

            $ SET DEFAULT DISK:[TEST]
            $ SET PROCESS/PARSE=EXTENDED
            $ CREATE/DIRECTORY/LOG [TEST.MixedCaseDir]
            %CREATE-I-CREATED, DISK:[TEST.MIXEDCASEDIR] created
            $ dir Mixed*.dir

            Directory DISK:[test]

            MixedCaseDir.DIR;1


         Images Affected:

          -  [SYSEXE]CREATE.EXE


      o  When DCL SHOW LOGICAL command is issued, a MTXCNTNONZ  bugcheck
         could occur during logical name translation.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     MTXCNTNONZ, Mutex count nonzero
                            at system service exit
         Current Process:   APACHE$WWW_7
         Current Image:     DSA30:[SYS0.SYSCOMMON.][SYSEXE]SHOW.EXE
         Failing PC:        FFFFFFFF.80080FD4
                            __RELEASE_SERVICE_ERROR_EXCEPT+00094
         Failing PS:        38000000.00000000
         Module:            EXCEPTION
                            (Link Date/Time: 26-APR-2001 12:37:41.13)
         Offset:            00018FD4


-- COVER LETTER --                                             Page 23
                                                         18 March 2002


         Images Affected:

          -  [SYSEXE]SHOW.EXE


      o  When doing SHOW PROCESS/ID=xxxx, if the process  resides  on  a
         VAX cluster member, the following error is displayed:

            %SYSTEM-F-INCOMPAT, feature incompatible
            with previous system version


         Images Affected:

          -  [SYSEXE]SHOW.EXE


      o  When using SHOW  CLUSTER/OUTPUT  and  SHOW  CLUSTER/CONTINUOUS'
         commands  with  a  WRITE command, the output is truncated after
         the  first  page,  even  though  additional  nodes  should   be
         displayed on a second page.  This problem occurs if there are a
         large number of  nodes  (OpenVMS  and/or  HSx  nodes)  and  the
         display is less than 132 characters wide.

         Images Affected:

          -  [SYSEXE]SHWCLSTR.EXE




12  PROBLEMS ADDRESSED IN VMS721H1_CPU2308-V0200 KIT


      o  This change allows EV67 and EV68 CPUs to co-exist on  the  same
         Wildfire  system.   Without  this  change,  you  will  see  the
         following message during boot:

           %SMP-F-CPUBAD, CPU # cpu type does not match that of primary


         Images Affected:

          -  [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE


      o  PCI  snapshot  subpackets   are   not   logged   correctly   in
         GS80/160/320  machine  check  errorlog  entries.  Consequently,
         some machine check errorlogs were missing this subpacket.

         Images Affected:

          -  [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE



-- COVER LETTER --                                             Page 24
                                                         18 March 2002


13  PROBLEMS ADDRESSED IN VMS721H1_DDTM-V0100 KIT


      o  A  SSRVEXCEPT  system  crash  ,  'Unexpected   system   service
         exception'  occurs  in  TPSERV.EXE  as  a  result  of a failing
         instruction is INSQUEL.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:    SSRVEXCEPT, Unexpected system service 
                           exception
         Node:             PERU02  (Clustered)
         VMS Version:      V7.1
         Current Process:  TP_SERVER
         Current Image:    $1$DUA107:[SYS1.SYSCOMMON.][SYSEXE]TPSERV.EXE
         Failing PC:       00000000.000233D4
         Failing PS:       10000000.00000000
         Module:           TPSERV
         Offset:           000233D4


         Images Affected:

          -  [SYSEXE]TPSERV.EXE


      o  The TP_SERVER process becomes compute bound in a tight loop and
         consumes CPU.

         Images Affected:

          -  [SYSEXE]TPSERV.EXE


      o  A DDTMBUG bugcheck, 'DDTMBUG,  DDTM  has  detected  an  invalid
         condition', at offset SYS$TRANSACTION_SERVICES_NPRO+00D10.

         Crashdump Summary Information:
         -------------------------------
         Bugcheck Type:     DDTMBUG, DDTM has detected an invalid condition
                            condition
         Current Process:   BATCH_1007867
         Current Image:     $1$DUA12:[EXPLOITER.][EXPEDIENTE.EXE_ALPHA]
                            OEEX95B.EXE;15
         Failing PC:        FFFFFFFF.80180D10 
                            SYS$TRANSACTION_SERVICES_NPRO+00D10
         Failing PS:        34000000.00000202
         Module:            SYS$TRANSACTION_SERVICES
         Offset:            00000D10


         Images Affected:

          -  [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE


-- COVER LETTER --                                             Page 25
                                                         18 March 2002


14  PROBLEMS ADDRESSED IN VMS721H1_DRIVER-V0200 KIT


      o  An        INVEXCEPTN         bugcheck         occurs         at
         SCS$FAST_SENDMSG_REQUEST_C+0002C.

         Images Affected:

          -  [SYS$LDR]SYS$DUDRIVER.EXE

          -  [SYS$LDR]SYS$TUDRIVER.EXE


      o  If DUTU$POLL_FOR_UNITS encounters an error, it does not  return
         an  ILLCDTST error.  Rather, it returns to the caller's caller,
         which hangs the thread and stalls I/O.  See partial crash  dump
         summary below:

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         CPU Type:          AlphaServer 2100A 4/275
         VMS Version:       X90F-SSB
         Current Process:   CTM$_0038004B
         Current Image:     DSA4:[CTM$TMROOT.]
                               [CTM_HIGH_IO]CTM_HIGH_IO_ALPHA_32.EXE;8
         Failing PC:        FFFFFFFF.800DBA7C
                               IOC_STD$INITIATE_NEW_IO_C+002FC
         Failing PS:        00000000.00000803
         Module:            IO_ROUTINES
                             (Link Date/Time: 17-FEB-2001 04:09:41.59)
         Offset:            0000FA7C

         Images Affected:

          -  [SYS$LDR]SYS$DUDRIVER.EXE

          -  [SYS$LDR]SYS$TUDRIVER.EXE




15  PROBLEMS ADDRESSED IN VMS721H1_DRIVER-V0100 KIT


      o  When a user attempts to create  a  directory  on  an  IDE  disk
         device  larger  than 30 GB, the system crashes with a UNXSIGNAL
         bugcheck at OTS$REM_UL_C+000B4 (a divide-by-0 crash).

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     UNXSIGNAL, Unexpected signal name in ACP
         Current Process:   face - 407
         Current Image:     $14$DKB0:[SYS4.SYSCOMMON.][SYSEXE]CREATE.EXE
         Failing PC:        FFFFFFFF.80007268    OTS$REM_UL_C+000B8
         Failing PS:        10000000.00000000

-- COVER LETTER --                                             Page 26
                                                         18 March 2002


         Module:            SYS$BASE_IMAGE    (Link Date/Time:
                            29-DEC-1999 03:52:51.75)
         Offset:            00005268


         Images Affected:

          -  [SYS$LDR]SYS$DQDRIVER.EXE


      o  The system cannot play audio CDs.

         Images Affected:

          -  [SYS$LDR]SYS$DQDRIVER.EXE


      o  A second instance of a GALAXY can not be booted.  Also observed
         are  repeated Bus Addressable Pool (BAP) errors with subsequent
         AUTOGEN runs.

         Images Affected:

          -  [SYS$LDR]SYS$DQDRIVER.EXE


      o  Not all DRcu::  disks are seen by all cluster members.

         Images Affected:

          -  [SYS$LDR]SYS$DRDRIVER.EXE


      o  DRDRIVER deletes the UCB for unit  0  if  there  are  no  disks
         configured  on  the  adapter.  This unit is being served to the
         cluster before the keep/delete decision is made.  When  another
         cluster  node  inquired about DR?0 via MSCP, the invalid UCB is
         referenced resulting in a crash.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   NULL
         Current Image:     <not available>
         Failing PC:        FFFFFFFF.8022C8AC    
                            SCS$MSCP_CHECK_SERVICE_C+0085C
         Failing PS:        10000000.00000804
         Module:            MSCP
         Offset:            000028AC


         Images Affected:

          -  [SYS$LDR]SYS$DRDRIVER.EXE


-- COVER LETTER --                                             Page 27
                                                         18 March 2002


      o  BACKUP between a V7.2-1 client and a  V7.1  TMSCP  served  tape
         fails with POSITERR and IVDENS errors.

         Images Affected:

          -  [SYS$LDR]SYS$DUDRIVER.EXE

          -  [SYS$LDR]SYS$TUDRIVER.EXE


      o  A MOUNT/FOR/NOASSIST/DENSITY=6250 command can be is issued  for
         devices  such  as  TA90 and TZ88.  These commands make no sense
         for these devices but customers have command files, that  issue
         this command, without regard to the type of drive.  When such a
         command file runs, the process or tape device will hang.

         Images Affected:

          -  [SYS$LDR]SYS$TUDRIVER.EXE




16  PROBLEMS ADDRESSED IN VMS721H1_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:

-- COVER LETTER --                                             Page 28
                                                         18 March 2002


          o  OpenVMS Alpha  Version  6.2  and  all  associated  hardware
             releases (for example, Version 6.2-1H1)

          o  OpenVMS Alpha Version 7.1-2

          o  OpenVMS Alpha Version 7.2-1

          o  OpenVMS Alpha Version 7.2-1H1

          o  OpenVMS Alpha Version 7.2-2

          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 Alpha Version 6.2

          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



-- COVER LETTER --                                             Page 29
                                                         18 March 2002


17  PROBLEMS ADDRESSED IN VMS721H1_F11X-V0100 KIT


      o  An application that calls IO$_ACCESS  with  an  ATR$C_CACHE_SEQ
         attribute,  fast  read of cache sequence numbers, will cause an
         exception in routine READ_ATTRIB and the XQP will bugcheck with
         a UNXSIGNAL.

         Images Affected:

          -  [SYS$LDR]F11BXQP.EXE


      o  The XQP bugchecks with an XQPERR  in  routine  MAKE_DIRINDX  in
         module  RDBLOK,  'All  the index buffers are active'.  There is
         DFO (Disk File Optimizer) (IO$M_MOVEFILE) activity on the  node
         at the time of the crash.

         In  XQP  routine  OPEN_INPUT_FILE  in  module  MOVEFILE,  if  a
         directory  FCB  is  returned from SEARCH_FCB, then FCB$V_DIR is
         not set before returning SS$_ACCONFLICT.  This causes directory
         FCBs  to linger forever without the option of being deleted, so
         that the associated BFRD can be reused.

         Images Affected:

          -  [SYS$LDR]F11BXQP.EXE


      o  During the DISMOUNT of a bound volume set, the XQP  signals  an
         XQPERR   bugcheck   in  CHECK_DISMOUNT  after  a  $DEQ  against
         RVT$L_STRUCLKID  fails  with  'Cannot  dequeue  a   lock   with
         sublocks'.

         Images Affected:

          -  [SYS$LDR]F11BXQP.EXE


      o  The XQP for trusted processes/threads is supposed  to  suppress
         the  audit  messages that may emanate from their actions.  This
         is  based  on  the  PSB$L_NOAUDIT/PCB$W_NOAUDIT   field   being
         non-zero  and  the  setting of an internal thread flag based on
         this field.  During the Raven per-thread security  update,  the
         internal  flag  was  no  longer being set and the process would
         then continue to generate audit messages.              

         Images Affected:

          -  [SYS$LDR]F11BXQP.EXE



-- COVER LETTER --                                             Page 30
                                                         18 March 2002


18  NEW FUNCTIONALITY INTRODUCED IN VMS721H1_FIBRE_SCSI-V0400 KIT


      o  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


          o  Enabling Interrupt and Response Coalescing

             You can turn on Interrupt and Response Coalescing with  the
             following command:

             $ MCR SYS$ETC:FC$CP FGx <enables> [<delay ms>] -
             $_ [<response count>]


              -  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> :  Enables bit 1 =  Response  Coalescing  and
                 bit 0 = Interrupt Coalescing.

              -  <delay ms> :  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

-- COVER LETTER --                                             Page 31
                                                         18 March 2002


             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.

          o  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
             ----    ----------------        --------------------
             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 VMS721H1_FIBRE_SCSI-V0400 KIT


      o  Tape Density values are  not  stored  correctly.   This  causes
         third  party  tape  applications,  such  as Oracle's RMU backup
         utility, to fail when performing multi-volume tape  backup  and
         other  operations  which  require the tape density to be stored

-- COVER LETTER --                                             Page 32
                                                         18 March 2002


         correctly.

         Images Affected:

          -  [SYS$LDR]SYS$MKDRIVER.EXE


      o  On OpenVMS Alpha clusters sharing a SCSI bus  and  attached  to
         the  bus with KZPBA SCSI controllers, disks may not come out of
         Mount Verify.

         Images Affected:

          -  [SYS$LDR]SYS$PKQDRIVER.EXE


      o  When performing multi-volume Backup (and various  other  Backup
         operations involving label processing) with generic SCSI tapes,
         compaction status gets turned off.

         Images Affected:

          -  [SYS$LDR]SYS$MKDRIVER.EXE


      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  un-synchronized  relative  to each other.  This lack of
         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  Tape drive performance  degrades  significantly  after  a  tape
         error.

         Images Affected:

-- COVER LETTER --                                             Page 33
                                                         18 March 2002


          -  [SYS$LDR]SYS$MKDRIVER.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 software
         write enabled.

         Images Affected:

          -  [SYS$LDR]SYS$DKDRIVER.EXE


      o  A system can crash with an INVEXCEPTN,  Exception  while  above
         ASTDEL bugcheck.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   NULL
         Current Image:     <not available>
         Failing PC:        FFFFFFFF.802FB820 SCS$POLL_MODE_C+00460
         Failing PS:        1C000000.00000804
         Module:            SYS$SCS    (Link Date/Time:
                            9-DEC-2000 00:44:16.18)
         Offset:            00005820


         Images Affected:

          -  [SYS$LDR]SYS$PGADRIVER.EXE


      o  A system can experience CPUSPINWAIT Crashes.   See  Crash  dump
         summary below.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     CPUSPINWAIT, CPU spinwait timer
                            expired
         Current Process:   NULL
         Current Image:     <not available>
         Failing PC:        FFFFFFFF.80088384
                            SMP$TIMEOUT_C+00064
         Failing PS:        18000000.00000804
         Module:            SYSTEM_SYNCHRONIZATION_MIN
                            (Link Date/Time: 26-MAY-2001 22:21:11.81)
         Offset:            00000384


-- COVER LETTER --                                             Page 34
                                                         18 March 2002


         Images Affected:

          -  [SYS$LDR]SYS$PKQDRIVER.EXE


      o  For 8MM tapes (for example 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 will show that an Illegal Request has been sent
         to the drive.

         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




20  PROBLEMS ADDRESSED IN VMS721H1_IPC-V0200 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:     <not available>
         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:

-- COVER LETTER --                                             Page 35
                                                         18 March 2002


          -  [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

          -  [SYSEXE]IPCDEF.STB 




21  PROBLEMS ADDRESSED IN VMS721H1_LAN-V0200 KIT


      o  The following problems are being corrected:

          o  The length on a packet which has a false error summary  bit
             may  not  be  set correctly.  This could cause lost packets
             when the hardware does not set  the  error  bits  correctly
             (which is rare).

          o  If the receive or transmit  process  enters  the  'stopped'
             state (an extremely rare event), the system appears to hang
             because of continuous interrupts.

          o  Support has been added  for  the  XP1000  media  attachment
             options.

-- COVER LETTER --                                             Page 36
                                                         18 March 2002


          o  On startup or shutdown,  a  false  hardware  error  may  be
             declared  causing  unnecessary  reset  of  the NIC (Network
             Interface Card)

          o  Possible machine checks on certain Galaxy configurations.

          o  Potential  problems  on  EV6  systems,  such  as   transmit
             timeouts or apparent receive lockups.

          o  A receive hang caused  by  not  supplying  receive  buffers
             before  starting  the  NIC,  which  could  cause  a receive
             overflow.  This could then induce a receive hang because of
             a  bug  in  the  NIC.   This  could  cause the NIC to never
             receive packets until it was reset.

          o  Applications may not start correctly

          o  Transmit data corruption may occur with  late  versions  of
             the DE435 and DE450 cards.

          o  The DE425 may not work on AlphaServer 2100 systems  because
             of insufficient map registers available to EISA devices.


         Images Affected:

          -  [SYS$LDR]SYS$EWDRIVER.EXE

          -  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE


      o  This  kit  adds  boot  support  for  the  Titan  chip  set  for
         AlphaServer  ES45,  for  Intel  chips 82558/82559, the DE435 to
         DE500 systems and for the DEFPA.

         Images Affected:

          -  [SYS$LDR]SYS$EWDRIVER_DE5000BA.EXE

          -  [SYS$LDR]SYS$ERDRIVER.EXE

          -  [SYS$LDR]SYS$EWDRIVER.EXE

          -  [SYS$LDR]SYS$ERBTDRIVER.EXE

          -  [SYS$LDR]SYS$EWBTDRIVER.EXE

          -  [SYSEXE]APB.EXE


      o  OpenVMS support was incomplete for the XP1000 embedded Ethernet
         option  when  the XP1000 first shipped.  This kit provides that
         support.

-- COVER LETTER --                                             Page 37
                                                         18 March 2002


         Images Affected:

          -  [SYS$LDR]SYS$ERDRIVER.EXE

          -  [SYS$LDR]SYS$EWDRIVER.EXE

          -  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE

          -  [SYS$LDR]SYS$ERBTDRIVER.EXE

          -  [SYS$LDR]SYS$EWBTDRIVER.EXE

          -  [SYSEXE]SYS$APB.EXE


      o  When using the Auto-Negotiate  console  setting  on  an  XP1000
         system,  Auto-Negotiation is not done.  Instead, after boot the
         device is in 10mb/half-duplex mode.

         Images Affected:

          -  [SYS$LDR]SYS$EWDRIVER_DE5000BA.EXE


      o  A scatter/gather mapping error can occur.  This is  seen  as  a
         machine check by the 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
         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  When one link partner is not doing auto-negotiation and another
         link partner is, if a link bounce is not done, the link partner
         that is not doing auto-negotiation may not see a change in  the
         link status during system boot or a LANCP command to change the
         speed or duplex mode.  If the link partner  does  not  see  the
         change,  it  does  not  restart  auto-negotiation  but  may  do
         parallel detection which may or  may  not  set  the  speed  and
         duplex mode correctly.

-- COVER LETTER --                                             Page 38
                                                         18 March 2002


         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  When the SYSGEN parameter NISCS_LAN_OVRHD is set to 0-5  bytes,
         the  packet size exceeds the size of the receive buffers in the
         FDDI boot driver.  This typically results  in  bytes  of  zeros
         scattered  about the images loaded by the boot driver.  When an
         affected image attempts to execute the corrupted portion of the
         image, a SSRVEXCEPT system crash results.

         The  problem  is  significant  only  when  the  NISCA_LAN_OVRHD
         parameter  is set to 0-5 bytes on system which is the FDDI boot
         server.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     SSRVEXCEPT, Unexpected system service 
                            exception
         Current Process:   STARTUP
         Current Image:     $1$DGA9994:[SYS1.SYSCOMMON.]
                            [SYSEXE]VMOUNT.EXE
         Failing PC:        FFFFFFFF.991B1120    SYS$SHDRIVER+81120
         Failing PS:        00000000.00000201
         Module:            SYS$SHDRIVER
                            (Link Date/Time: 10-MAY-2001 21:41:14.47)
         Offset:            00081120


         Images Affected:

          -  [SYSEXE]APB.EXE

          -  [SYS$LDR]SYS$FCBTDRIVER.EXE

          -  [SYS$LDR]SYS$FRBTDRIVER.EXE

          -  [SYS$LDR]SYS$FWBTDRIVER.EXE


      o  Under the following conditions, the Etherworks port will be set
         to 100mbs/half-duplex mode when it should be set to full-duplex
         mode.

         1.  An XP1000 system is connected to a Etherworks 10/100 switch
             with a console setting of EIA0_MODE FASTFD

         2.  The Etherworks port is set to Auto-Negotiate.

         3.  OpenVMS is booted and the Etherworks switch is then powered
             OFF and then ON.


-- COVER LETTER --                                             Page 39
                                                         18 March 2002


         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  When a DE500 on a  satellite  server  node,  which  is  set  to
         auto-negotiate,   is   connected   point-to-point   to  another
         satellite node which is also set  to  auto-negotiate,  the  two
         nodes  will  not  synchronize  speed/duplex correctly such that
         they cannot complete the loading of OpenVMS off a served system
         disk.

         Images Affected:

          -  [SYS$LDR]SYS$EWDRIVER.EXE

          -  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE


      o  XP1000 systems will fail  to  boot  as  satellite  nodes  in  a
         cluster  using  the  integrated  DE500  chip  and  external PHY
         (Physical Layer):  BNC, AUI or Twisted-Pair.

         Images Affected:

          -  [SYS$LDR]SYS$EWBTDRIVER.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

-- COVER LETTER --                                             Page 40
                                                         18 March 2002


          -  [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

         Images Affected:

          -  [SYS$LDR]NET$FDDI.EXE




22  NEW FUNCTIONALITY ADDRESSED IN VMS721H1_LAN-V0100 KIT

     22.1  Compaq 3X-DAPBA-FA and Compaq 3X-DAPCA-FA ATM Adapters

     The 3X-DAPBA-FA and the 3X-DAPCA-FA are PCI based ATM adapters  for
     Alpha  based  systems  that  provide  high  performance  PCI-to-ATM
     capability.  The  3X-DAPBA-FA  adapter  offers  a  155  Mbps  fiber
     connection;  the  3X-DAPCA-FA  adapter  offers  a  622  Mbps  fiber
     connection.

     The datalink drivers for these adapters function in a  new  OpenVMS
     ATM   environment.   The  new  OpenVMS  ATM  environment  is  fully
     compatible with the existing legacy ATM support and allows both ATM
     environments  to  be  configured on a single system.  Additionally,
     the  LANCP  management  interface  is  the  same   for   both   ATM
     environments.   The  following images/files support the new OpenVMS
     ATM environment:

      o  [SYS$LDR]SYS$LAN.EXE

      o  [SYS$LDR]SYS$LAN_CSMACD.EXE

      o  [SYS$LDR]SYS$LAN_ATM.EXE

      o  [SYS$LDR]SYS$LAN_ATM4.EXE (new)

      o  [SYS$LDR]SYS$$ELDRIVER4.EXE (new)

      o  [SYS$LDR]SYS$$HWDRIVER4.EXE (new)

-- COVER LETTER --                                             Page 41
                                                         18 March 2002


      o  [SYSEXE]SYS$CONFIG.DAT

      o  [SYSEXE]LANCP.EXE

      o  [SYSEXE]LANACP.EXE



     22.1.1  Requirements

     These  adapters  require  a  great  deal  of  non-paged  pool,  and
     therefore,  care  should  be  taken  when  configuring  them.   The
     following restrictions apply to these adapters:

      o  For each 3X-DAPBA-FA adapter, Compaq recommends increasing  the
         SYSGEN parameter NPAGEVIR by 3000000.

      o  For each  3X-DAPCA-FA  adapter,  Compaq  recommends  increasing
         NPAGEVIR by 6000000.

     To perform the above changes, add  the  ADD_NPAG_VIR  parameter  to
     MODPARAMS.DAT  and then run AUTOGEN.  For example, on a system with
     two 3X-DAPBA-FAs and one 3X-DAPCA-FA, you would add  the  following
     line to MODPARAMS.DAT:

             ADD_NPAG_VIR = 12000000



     22.1.2  Restrictions

     The following restrictions apply to these adapters:

      o  The adapter cannot be located on a  PCI  bus  that  is  located
         behind   a   PCI-to-PCI   bridge.    Systems   that  have  this
         configuration are the following:

          -  Digital Personal AlphaWorkstation 600

          -  AlphaStation 1000A

          -  COMPAQ Professional Workstation XP1000

          -  AlphaServer 2000 and 2100


      o  Classical IP is not supported with these new adapters.

      o  SDA does not correctly identify these  new  ATM/FORE  adapters.
         They  are  identified as "unknown adapters." This will be fixed
         in a subsequent support release.


-- COVER LETTER --                                             Page 42
                                                         18 March 2002


     22.1.3  Additional Information

     For additional information about the 3X-DAPBA-FA PCI HE155 ATM  and
     3X-DAPCA-FA PCI HE622 ATM adapters, refer to the following URL:

        http://www.digital.com/alphaserver/products.html



     22.2  Add support for unlimited chained transmit segments to  ALPHA
           LAN drivers.

     Support has been added for unlimited chained transmit  segments  to
     LAN  drivers.   Support  for  this  functionality  is a performance
     enhancement for both IPv4 and IPv6.

     Images Affected:

      -  [SYS$LDR]SYS$ERDRIVER.EXE

      -  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE

      -  [SYS$LDR]SYS$FXDRIVER.EXE

      -  [SYS$LDR]SYS$ESDRIVER.EXE

      -  [SYS$LDR]SYS$HCDRIVER.EXE

      -  [SYS$LDR]SYS$HWDRIVER.EXE

      -  [SYS$LDR]SYS$FADRIVER.EXE

      -  [SYS$LDR]SYS$FCDRIVER.EXE

      -  [SYS$LDR]SYS$FRDRIVER.EXE

      -  [SYS$LDR]SYS$EXDRIVER.EXE

      -  [SYS$LDR]SYS$FWDRIVER.EXE

      -  [SYS$LDR]SYS$EWDRIVER.EXE



     22.3  Add new functionality to support a gigabit Ethernet driver.

     Support for gigabit Ethernet drivers has been added.

     Images Affected:

     - [SYS$LDR]SYS$EW1000A.EXE

     - [SYS$LDR]SYS$LAN.EXE

-- COVER LETTER --                                             Page 43
                                                         18 March 2002


23  PROBLEMS ADDRESSED IN VMS721H1_LAN-V0100 KIT


      o  On some systems, the PCI FDDI adapter (the DEFPA) halts with  a
         fatal  hardware error.  When the driver attempts to restart the
         DEFPA, the driver detects either a parity error being  reported
         by  the  DEFPA, or it detects a command failure, which prevents
         the driver from getting the DEFPA restarted successfully.

         Images Affected:

          -  [SYS$LDR]SYS$FWDRIVER.EXE

          -  [SYS$LDR]SYS$FRDRIVER.EXE

          -  [SYS$LDR]SYS$FADRIVER.EXE


      o  The LAN Device Characteristics block (LDC) contains the  device
         line  speed,  which  applications may use to determine how fast
         the device is running.  The Token Ring  driver  sets  the  line
         speed  at  16, even if driver is set to 4 megabits.  The change
         enables the driver to set the speed in  the  LDC  to  4  or  16
         megabits, whenever a new speed is determined.

         Images Affected:

          -  [SYS$LDR]SYS$IWDRIVER.EXE

          -  [SYS$LDR]SYS$IRDRIVER.EXE

          -  [SYS$LDR]SYS$ICDRIVER.EXE


      o  A  multitude  of  data  overruns  causes  very   poor   network
         performance when running from DE504 in ES40 to DE602 in GS160.

         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  The system can crash with an INVEXCEPTN bugcheck.

         Images Affected:

          -  [SYS$LDR]SYS$EWDRIVER.EXE

          -  [SYS$LDR]SYS$ERDRIVER.EXE


      o  The  system  can  crash  when   an   interrupt   occurs   after
         de-allocating  the  buffer.   The  crash occurs when the system
         attempts to make an interrupt trace entry.

-- COVER LETTER --                                             Page 44
                                                         18 March 2002


         Images Affected:

          -  [SYS$LDR]SYS$LAN.EXE

          -  [SYS$LDR]SYS$LAN_CSMACD.EXE

          -  [SYS$LDR]SYS$LAN_FDDI.EXE

          -  [SYS$LDR]SYS$LAN_TR.EXE

          -  [SYS$LDR]SYS$LAN_ATM.EXE

          -  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE

          -  [SYSEXE]LANCP.EXE


      o  An INVEXCEPTN crash can  occur  when  CSMACD  executes  an  NCL
         script.

         Images Affected:

          -  [SYS$LDR]SYS$EWDRIVER.EXE

          -  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE

          -  [SYS$LDR]SYS$EIDRIVER.EXE

          -  [SYS$LDR]SYS$FWDRIVER.EXE

          -  [SYS$LDR]SYS$FCDRIVER.EXE

          -  [SYS$LDR]SYS$FRDRIVER.EXE

          -  [SYS$LDR]SYS$FADRIVER.EXE

          -  [SYS$LDR]SYS$EW1000A.EXE

          -  [SYS$LDR]SYS$ELDRIVER.EXE

          -  [SYSEXE]SYS$CONFIG.DAT

          -  [SYSEXE]LANCP.EXE


      o  The LAN device  line  speeds  are  displayed  incorrectly  with
         NISCACP.

         Images Affected:

          -  [SYS$LDR]SYS$EWDRIVER.EXE

          -  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE

-- COVER LETTER --                                             Page 45
                                                         18 March 2002


          -  [SYS$LDR]SYS$EIDRIVER.EXE

          -  [SYS$LDR]SYS$FWDRIVER.EXE

          -  [SYS$LDR]SYS$FCDRIVER.EXE

          -  [SYS$LDR]SYS$FRDRIVER.EXE

          -  [SYS$LDR]SYS$FADRIVER.EXE

          -  [SYS$LDR]SYS$EW1000A.EXE

          -  [SYS$LDR]SYS$ELDRIVER.EXE

          -  [SYSEXE]SYS$CONFIG.DAT

          -  [SYSEXE]LANCP.EXE


      o  An INVEXCEPTN crash occurs in the SYS$EW1000A driver  following
         a SET HOST/LAT.

         Images Affected:

          -  [SYS$LDR]SYS$EWDRIVER.EXE

          -  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE

          -  [SYS$LDR]SYS$EIDRIVER.EXE

          -  [SYS$LDR]SYS$FWDRIVER.EXE

          -  [SYS$LDR]SYS$FCDRIVER.EXE

          -  [SYS$LDR]SYS$FRDRIVER.EXE

          -  [SYS$LDR]SYS$FADRIVER.EXE

          -  [SYS$LDR]SYS$EW1000A.EXE

          -  [SYS$LDR]SYS$ELDRIVER.EXE

          -  [SYSEXE]SYS$CONFIG.DAT

          -  [SYSEXE]LANCP.EXE


      o  If the CLUSTER_CONFIG LANACP  configuration  process  quota  is
         exceeded,  LAN  devices  cannot  be enabled and the LAN process
         will abort.

         Images Affected:

          -  [SYS$STARTUP]LAN$STARTUP.COM


-- COVER LETTER --                                             Page 46
                                                         18 March 2002


      o  DE425 does not function on systems that  do  not  have  mapping
         registers.

         Images Affected:

          -  [SYS$LDR]SYS$ERDRIVER.EXE


      o  Fix driver extension codes to facilitate accurate printing.  In
         some  instances,  the extension codes were in conflict with the
         drivers' if-then-else implementations.

         Images Affected:

          -  [SYSEXE]LANCP.EXE


      o  Prevent SHOW_NODE from displaying error messages even after the
         specified node is found.

         Images Affected:

          -  [SYSEXE]LANCP.EXE


      o  A system can  crash  following  the  entry  of  a  STOP/IP/ISA1
         command from within the TCPWare management interface.

         Images Affected:

          -  [SYS$LDR]SYS$EZDRIVER.EXE


      o  On some systems, the DE600 may discard receive packets  because
         it  cannot  get  sufficient memory bandwidth to unload incoming
         receive packets.   This  results  in  poor  system  performance
         levels, e.g., network copies that take longer than expected and
         set host and TELNET sessions that see  pauses,  which  are  all
         caused   by   lost   packets  that  force  error  recovery  and
         re-transmission by individual applications.

         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  The transmit routine in the Gigabit Ethernet  driver  does  not
         properly  deal  with  buffers  that  cross  more  than two page
         boundaries.  Data corruption may occur in the last 822 or  less
         bytes of a large buffer and zeros may be transmitted instead of
         the correct data.

         Images Affected:

-- COVER LETTER --                                             Page 47
                                                         18 March 2002


          -  [SYS$LDR]SYS$EW1000A.EXE


      o  A receive packet could occasionally be received into  a  buffer
         that  the  device  had  previously  used, which results in pool
         corruption.

         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  A multi-segment transmit could transmit incorrect data  to  the
         destination or could result in a system machine check crash.

         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  Packets are left in the DE500BA receive ring and  they  do  not
         get processed until another packet is received, which decreases
         performance.

         Images Affected:

          -  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE


      o  The LAN driver is called by a bugcheck to  shutdown  before  it
         has  run a unit init, so the LSD is zero.  As a result, the LAN
         driver ACCVIOs.

         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE




24  PROBLEMS ADDRESSED IN VMS721H1_LAT-V0100 KIT


      o  Due to a protocol error, an  INCONSTATE  bugcheck  occurred  in
         routine  LT$PROT_VIO  while  tearing  down  a  virtual circuit.
         Images Affected:

          -  [SYS$LDR]SYS$LTDRIVER.EXE


      o  Some applications may hang after receiving  an  XOFF  character
         when TTSYNC was set.

         Images Affected:

-- COVER LETTER --                                             Page 48
                                                         18 March 2002


          -  [SYSEXE]LTPAD.EXE


      o  An  INCONSTATE  crash  occurs  in   SYS$LTDRIVER   in   routine
         LT$XMT_RUN.  See partial crash dump summary below:

         Bugcheck Type:     INCONSTATE, Inconsistent I/O data base
         Current Process:   LAB_PO>124
         Current Image:     DSA538:[SYS1.SYSCOMMON.][SYSEXE]DSM.EXE
         Failing PC:        FFFFFFFF.8BD02E08    SYS$LTDRIVER+0AE08
         Failing PS:        20000000.00000804
         Module:            SYS$LTDRIVER
         Offset:            0000AE08


         Images Affected:

          -  [SYS$LDR]SYS$LTDRIVER.EXE


      o  An INVEXCEPTN crash occurs  in  the  LT$CRASH  routine  (module
         LTDRIVER_SOLICIT)  if a periodic timeout event is declared when
         SSB$B_SOL_STATE = 0.

         Images Affected:

          -  [SYS$LDR]SYS$LTDRIVER.EXE


      o  A system can crash with an INVEXCEPTN, 'Exception  while  above
         ASTDEL' error.  See partial crash dump summary below:

         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   IMPARATIB
         Current Image:     DSA4:[COMPTA.][CPTTIERS.EXE]CTLM.EXE;40
         Failing PC:        FFFFFFFF.9199F9F0    SYS$LTDRIVER+159F0
         Failing PS:        30000000.00000804
         Module:            SYS$LTDRIVER    (Link Date/Time: 28-MAY-1999 
                            23:24:58.19)
         Offset:            000159F0


         Images Affected:

          -  [SYS$LDR]SYS$LTDRIVER.EXE

          -  [SYSEXE]LATACP.EXE


      o  The system crashed when SYS$LTDRIVER tried to access an invalid
         virtual address while in kernel mode and while falling over.

         Images Affected:

-- COVER LETTER --                                             Page 49
                                                         18 March 2002


          -  [SYS$LDR]SYS$LTDRIVER.EXE


      o  An INCONSTATE crash occurs at  SYS$LTDRIVER+13384  on  a  stale
         SSB.  See partial crash dump summary below:

         Bugcheck Type:     INCONSTATE, Inconsistent I/O data base
         Current Process:   NULL
         Current Image:     <not available>
         Failing PC:        FFFFFFFF.BE5FF384    SYS$LTDRIVER+13384
         Failing PS:        10000000.00000804
         Module:            SYS$LTDRIVER    (Link Date/Time: 28-MAY-1999 
         23:24:58.19)
         Offset:            00013384


         Images Affected:

          -  [SYS$LDR]SYS$LTDRIVER.EXE




25  PROBLEMS ADDRESSED IN VMS721H1_LIBRTL-V0400 KIT


      o  Exception/signal rich applications, like Oracle, can experience
         significant performance degradation.

         Images Affected:

          -  [SYSEXE]DBGHK$HOST_KERNEL.EXE

          -  [SYSEXE]DBGHK$SYSDUMP_KERNEL.EXE

          -  [SYSLIB]DEBUG.EXE

          -  [SYSLIB]LIBRTL.EXE

          -  [SYSLIB]LIBRTL_INSTRUMENTED.EXE




26  PROBLEMS ADDRESSED IN VMS721H1_MAIL-V0300 KIT


      o  MAILSHR.EXE needs to be installed before MAIL.EXE is installed.
         This was not being done.

         Images Affected:

          -  [SYSLIB]MAILSHR.EXE



-- COVER LETTER --                                             Page 50
                                                         18 March 2002


27  PROBLEMS ADDRESSED IN VMS721H1_MAIL-V0200 KIT


      o  After installation of  the  VMS721H1_MAIL-V0100  ECO  kit,  the
         MAILSHR.EXE   image   has   the  wrong  file  protection.   The
         protection is (RWED,RWED,RE,), it should be  (RWED,RWED,RE,RE).
         This could cause some TCP/IP services to fail.

         Images Affected:

          -  [SYSLIB]MAILSHR.EXE




28  PROBLEMS ADDRESSED IN VMS721H1_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

            On a Alpha V6.1 platform:
            $ mail
            MAIL> send
            To: js
            Subject:

            On a Alpha V7.1-2 platform:
            $ 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> sel A

-- COVER LETTER --                                             Page 51
                                                         18 March 2002


         %MAIL-E-NOFILEOPEN, no mail file open

         MAIL> exit
         %MAIL-E-NOFILEOPEN, no mail file open
         %MAIL-E-NOFILEOPEN, no mail file open
         ETOSHA>


         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.

         example message:
         111111111111111111111111111111
         111111111111^@1111111111111111
         111111111111111111111111111111

         Extract 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

-- COVER LETTER --                                             Page 52
                                                         18 March 2002


         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]
         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> sho file
         Your current mail file is SYS$SYSROOT:[SYSMGR]MAIL.MAI.

         MAIL> set file SYS$SYSDEVICE:[BAT.MAIL]

         MAIL> dir/fol
         Listing of folders in SYS$SYSROOT:[SYSMGR]MAIL.MAI       
              Press CTRL/C to cancel listing
         MAIL

         MAIL> sho 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> sel "MAIL-nov-1998"
         %MAIL-I-SELECTED, 3121 messages selected

-- COVER LETTER --                                             Page 53
                                                         18 March 2002



         MAIL> sel/sinc=01-jan-80
         %MAIL-I-SELECTED, 3121 messages selected

         MAIL> copy/all "MAIL-nov-1998" dua3:[mpiati]

         MAIL> set file dua3:[mpiati]

         MAIL> sel "MAIL-nov-1998"
         %MAIL-I-SELECTED, 169 messages selected


         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:

-- COVER LETTER --                                             Page 54
                                                         18 March 2002


          -  [SYSEXE]MAIL.EXE


      o  Sending mail from VMSMAIL  to  Microsoft  Exchange  mail  using
         TCP/IP  merges  the To:  and CC:  lines to one To:  line in the
         received message.  See example below:

         MAIL> Send/CC
         To: SMTP%"A.B@C.COM"
         CC: SMTP%"D.E@F.COM"

         The To: line in Exchange:

         To: A.B@C.COM,D.E@F.COM


         Images Affected:

          -  [SYSEXE]MAIL.EXE

          -  [SYSLIB]MAILSHR.EXE


      o  OVMS Mail does not filter out the <ESC> 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:

          -  [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
         $


-- COVER LETTER --                                             Page 55
                                                         18 March 2002


         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




29  PROBLEMS ADDRESSED IN VMS721H1_MANAGE-V0200 KIT


      o  The SYSMAN security profile is supposed to be identical on  all
         nodes  in  a  cluster  that uses the same security environment.
         However, SYSMAN may use the authorization privileges  from  the
         UAF  (user  authorization  file)  instead  of  the  locally set
         privileges on SOME nodes.  See the  following  cluster  example
         below  in  which  NODE1  should have same privilege settings as
         NODE2:
         SYSMAN> set env/clus

         %SYSMAN-I-ENV, current command environment:
             Clusterwide on local cluster
             Username SYSTEM       will be used on nonlocal nodes


         SYSMAN> show profile

         %SYSMAN-I-DEFDIR, default directory on node NODE2 -- 
         SYS$SYSROOT:[SYSMGR]

         %SYSMAN-I-DEFPRIV, process privileges on node NODE2 --
             TMPMBX
             OPER
             NETMBX

         %SYSMAN-I-DEFDIR, default directory on node NODE1 -- 
         SYS$SYSROOT:[SYSMGR]

         %SYSMAN-I-DEFPRIV, process privileges on node NODE1 --
             CMKRNL
             CMEXEC
             SYSNAM
             GRPNAM
             ALLSPOOL
             TMPMBX
             OPER
             NETMBX


-- COVER LETTER --                                             Page 56
                                                         18 March 2002


         Images Affected:

          -  [SYSLIB]SMI$SHR.EXE


      o  OpenVMS-ALPHA and OpenVMS-ALPHA-USER  licenses  do  not  always
         load  at  boot  on Galaxy.  When the OpenVMS-ALPHA license does
         not meet the required number of units to load, as per the  LURT
         table,  for a Galaxy processor with multiple CPU's, the license
         loads successfully and allows full access to the system as long
         as an OpenVMS-ALPHA-User license is also loaded.

         Images Affected:

          -  [SYS$STARTUP]VMS$CONFIG-050_LMF.COM


      o  The QUEUE_MANAGER process crashes and  produces  the  following
         error messages:

             Message from user QUEUE_MANAGE on MAUAX1
             %QMAN-F-WRITEERR, error writing
             $20$DKA204:[SYSCLUSTER.]
             [SYSEXE]SYS$QUEUE_MANAGER.QMAN$JOURNAL;1

             Message from user QUEUE_MANAGE on MAUAX1
             -RMS-F-SYS, QIO system service request failed

             Message from user QUEUE_MANAGE on MAUAX1
             -RMS-F-SYS, QIO system service request failed

             Message from user QUEUE_MANAGE on MAUAX1
             -NONAME-W-NOMSG, Message number 00000000

             Message from user QUEUE_MANAGE on MAUAX1
             -SYSTEM-F-EXQUOTA, process quota exceeded


         Crash Summary Information:
         --------------------------
         Current Process:   QUEUE_MANAGER
         Current Image:     <not available>
         Failing PC:        FFFFFFFF.D24FAAE4    IO_ROUTINES_PRO+02AE4
         Failing PS:        00000000.00000000
         Module:            IO_ROUTINES
         Offset:            0002EAE4


         Images Affected:

          -  [SYS$STARTUP]VMS$CONFIG-050_JOBCTL.COM


      o  Issuing SYSMAN Class Scheduler commands to a node that does not
         support Class Scheduling, causes the SMI server on that node to
         aborted.  See example output below:

-- COVER LETTER --                                             Page 57
                                                         18 March 2002



         SYSMAN> do show time
         %SYSMAN-I-OUTPUT, command execution on node NODE1
           16-NOV-2000 14:34:29
         %SYSMAN-I-OUTPUT, command execution on node NODE2
           16-NOV-2000 14:34:29
         SYSMAN> class add XX1
         /pri=(mon,tue,wed,thur,fri,nosat,nosun)/cpu=(prim,0-23=25
         ,sec,0-23=100)
         %SYSMAN-I-NODERR, error returned from node NODE1
         -SMI-E-NAMCONFLICT, class name already exists in class 
         scheduler database file
         %SMI-I-CLASSEXISTS, scheduling class already exists on 
         node NODE2
         %SYSMAN-I-NODERR, error returned from node NODE3
         -SMI-E-ABORT, SMI Server has aborted
         SYSMAN> do show time
         %SYSMAN-I-OUTPUT, command execution on node NODE1
           16-NOV-2000 14:35:20
         %SYSMAN-I-OUTPUT, command execution on node NODE2
           16-NOV-2000 14:35:20
         %SYSMAN-I-OUTPUT, command execution on node NODE3
         %SYSMAN-I-NODERR, error returned from node NODE3
         -SMI-E-NOSERVER, SMI Server not running in target node

         Images Affected:

          -  [SYSLIB]SMI$SHR.EXE


      o  The system crashes with "Kernel stack invalid" after an AUTOGEN
         reboot.   Large  values  of  NPAGEDYN  could  result  in values
         computed for NPAGEVIR that  are  too  large  to  fit  into  the
         available system space.

         Images Affected:

          -  [SYSUPD]AUTOGEN.COM

          -  [SYSEXE]AGEN$FEEDBACK.EXE


      o  The system crashes with a negative BALSETCNT while  an  AUTOGEN
         reboot  is  in  progress  following an increase in VCC_MAXSIZE.
         VCC_MAXSIZE may be sized too big to fit into the system.

         Images Affected:

          -  [SYSUPD]AUTOGEN.COM

          -  [SYSEXE]AGEN$FEEDBACK.EXE


      o  The BALSETCNT error message does not  display  the  VCC_MAXSIZE
         limit,  which  would  help  determine  how  to  set VCC_MAXSIZE
         properly.

-- COVER LETTER --                                             Page 58
                                                         18 March 2002


         Images Affected:

          -  [SYSUPD]AUTOGEN.COM

          -  [SYSEXE]AGEN$FEEDBACK.EXE


      o  AUTOGEN's DIGITAL command language (DCL)  arithmetic  overflows
         and generates incorrect data.  See the example below:

           $ SEARCH SYS$SYSTEM:AGEN$FEEDBACK.DAT;373 HDR,DIR
           DIRHITS = 559996826
           DIRATTEMPTS = 694808213
           HDRHITS = 289151114
           HDRATTEMPTS = 394307611
           ACP_DIRCACHE_CUR = 2000

         AUTOGEN will then perform operations similar to the  following,
         which overflows and turns negative.

           $WRITE report "    Attempt rate:
           ",(HDRattempts*10)/feedback_uptime,"attempts

           Csc64 $ write sys$output 394307611*10
           -351891186

         In this case,  no  warnings  were  generated  to  the  feedback
         report.

         Images Affected:

          -  [SYSUPD]AUTOGEN.COM

          -  [SYSEXE]AGEN$FEEDBACK.EXE


      o  Previously authorized SYSMAN commands fail  on  remote  systems
         with insufficient privilege errors.

         Images Affected:

          -  [SYSEXE]SMISERVER.EXE      




30  PROBLEMS ADDRESSED IN VMS721H1_MOUNT96-V0200 KIT


      o  Some reads to disk devices will occasionally fail as  a  result
         of  a path failover.  If this happens during a read of the home
         block, then MOUNT  will  read  the  alternate  home  block  and
         continue  to MOUNT the device.  Depending on which read failed,
         the MOUNT may mount the  disk  write-locked  or  display  other
         warning messages.

-- COVER LETTER --                                             Page 59
                                                         18 March 2002


         Images Affected:

          -  [SYSLIB]MOUNTSHR.EXE

          -  [SYSEXE]VMOUNT.EXE


      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  On volumes where the INDEXF.SYS file size exceeds the  MAXFILES
         value  for  the volume, a volume rebuild operation will ACCVIO.
         VERIFY shows no problems but the commands to rebuild the volume
         will consistently fail.

         Note: To receive this complete change you must also install
               the VMS721_CLIUTL-V0200 ECO kit.


         Images Affected:

          -  [SYSLIB]MOUNTSHR.EXE


      o  A SET VOLUME/REBUILD command on a volume set, where a node that
         had  it  mounted  did  not  update  the  volume  write count on
         dismount (or a crash), does not reset the volume write count to
         the   correct  number  of  writers  in  the  cluster.   A  SHOW
         DEVICE/REBUILD command always shows this volume  as  needing  a
         rebuild.   Even  a SET VOLUME/REBUILD=FORCE will not clear this
         rebuild status.

         Note: To receive this complete change you must also install

-- COVER LETTER --                                             Page 60
                                                         18 March 2002


               the VMS721_CLIUTL-V0200 ECO kit.


         Images Affected:

          -  [SYSLIB]MOUNTSHR.EXE


      o  The following problems are being corrected:

          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.


          o  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 VMS721_SYS-V1100 and VMS721_FIBRE_SCSI-V0500 ECO
               kits.


         Images Affected:

          -  [SYSLIB]MOUNTSHR.EXE

          -  [SYSEXE]VMOUNT.EXE


      o  Read failures during 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.   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 for 30 seconds (30 re-tries at one per
         second).  If the READ succeeds, the disk  will  be  mounted  as
         READ/WRITE.

-- COVER LETTER --                                             Page 61
                                                         18 March 2002


         Images Affected:

          -  [SYSEXE]VMOUNT.EXE

          -  [SYSLIB]MOUNTSHR.EXE




31  PROBLEMS ADDRESSED IN VMS721H1_PPPD-V0100 KIT


      o  The ASNDRIVER looses an IRP (I/O request packet) for read and a
         TWP (terminal write packet) for writes.  The cleanup code would
         fail while looking for the missing IRP and TWP  and  cause  the
         following ACCVIO:

           INVEXCEPTN, Exception while above ASTDEL

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   OROT-IGSI
         Current Image:     DKA0:[WRT.][OROT.EXE]IGSI_A-0195_00.EXE
         Failing PC:        FFFFFFFF.80318CEC SYS$ASNDRIVER_NPRO+00CEC
         Failing PS:        10000000.00000803
         Module:            SYS$ASNDRIVER
         Offset:            00000CEC


         Images Affected:

          -  [SYS$LDR]SYS$ASNDRIVER.EXE


      o  An INVEXCEPTN crash occurs when attempting to establish  a  PPP
         connection after a TCP/IP restart.

         Images Affected:

          -  [SYS$LDR]SYS$PPPDRIVER.EXE


      o  A port hangs when a timing  error  causes  the  port  state  to
         change before all pending I/Os have completed.

         Images Affected:

          -  [SYS$LDR]SYS$PPPDRIVER.EXE


      o  A PPP disconnection of a remote client,  such  as  MS  Outlook,
         could cause an INVEXCEPTN crash.

         Crashdump Summary Information:
         ------------------------------

-- COVER LETTER --                                             Page 62
                                                         18 March 2002


         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   NULL
         Current Image:     <not available>
         Failing PC:        FFFFFFFF.835076B8    SYS$PPPDRIVER+0F6B8
         Failing PS:        00000000.00000804
         Module:            SYS$PPPDRIVER
         Offset:            0000F6B8


         Images Affected:

          -  [SYS$LDR]SYS$PPPDRIVER.EXE




32  PROBLEMS ADDRESSED IN VMS721H1_PTHREAD-V0100 KIT


      o  Applications that disable ASTs may hang.

         Images Affected:

          -  [SYSLIB]PTHREAD$DBGSHR.EXE

          -  [SYSLIB]PTHREAD$RTL.EXE




33  PROBLEMS ADDRESSED IN VMS721H1_RENAME_OLD-V0100 KIT


      o  During an OpenVMS ECO kit installation, names of the  installed
         images               are               written               to
         SYS$COMMON:[SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT.    Several    of
         these  file  names  were  written  incorrectly by the following
         remedial kits.

          o  DEC-AXPVMS-VMS721_DRIVER-V0200-4.PCSI

          o  DEC-AXPVMS-VMS721_MANAGE-V0100-4.PCSI

          o  DEC-AXPVMS-VMS721_VX1-V0200-4.PCSI

          o  DEC-AXPVMS-VMS721H1_CPU2308-V0100-4.PCSI

          o  DEC-AXPVMS-VMS721H1_ACRTL-V0200-4.PCSI

         During an OpenVMS Version 7.3 upgrade, operating  system  files
         from  the  previous version of OpenVMS are deleted.  Because of
         these file errors, files from the newly installed system may be
         deleted.  This may cause the system to become un-bootable.

-- COVER LETTER --                                             Page 63
                                                         18 March 2002


         This    kit    will    verify    the    integrity    of     the
         SYS$COMMON:[SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT file and make the
         necessary file name corrections.  The files  corrected  are  as
         follows:

         Incorrect lines
         ----------------

         [SYSLIB]SYS$ICBM.EXE                   VMS721_DRIVER-V0200
         [SYSLIB]SMI$SHR.EXE                    VMS721_MANAGE-V0100 
         [SYS$LDR]SYS$GFDRIVER.EXE _OLD         VMS721_VX1-V0200
         [SYSEXE]SYS$CONFIG.DAT_0LD             VMS721_VX1-V0200
         [SYSLIB]DECC$SHR_OLD                   VMS721H1_ACRTL-V0200
         [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE     VMS721H1_CPU2308-V0100
         [SYSEXE]SYS$SMHANDLER_SLAVE_2308.EXE   VMS721H1_CPU2308-V0100


         Corrected Lines
         ----------------
         [SYSLIB]SYS$ICBM.EXE_0LD                 VMS721_DRIVER-V0200
         [SYSLIB]SMI$SHR.EXE_0LD                  VMS721_MANAGE-V0100
         [SYS$LDR]SYS$GFDRIVER.EXE_OLD            VMS721_VX1-V0200
         [SYSEXE]SYS$CONFIG.DAT_OLD               VMS721_VX1-V0200
         [SYSLIB]DECC$SHR.EXE_OLD                 VMS721H1_ACRTL-V0200
         [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE_OLD   VMS721H1_CPU2308-V0100
         [SYSEXE]SYS$SMHANDLER_SLAVE_2308.EXE_OLD VMS721H1_CPU2308-V0100


         Corrections Explained
         ---------------------

         [SYSLIB]SYS$ICBM.EXE_OLD              Add _OLD to name
         [SYSLIB]SMI$SHR.EXE_OLD               Add _OLD to name
         [SYS$LDR]SYS$GFDRIVER.EXE_OLD         Delete a space
         [SYSEXE]SYS$CONFIG.DAT_OLD            Change 0 (zero) to O
         [SYSLIB]DECC$SHR.EXE_OLD                  Add .EXE in name
         [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE_OLD    Add _OLD to name
         [SYSEXE]SYS$SMHANDLER_SLAVE_2308.EXE_OLD  Add _OLD to name


         In the event this kit fails to execute,  the  renaming  of  the
         problem  files can be done manually by performing the following
         steps:

         1.  Edit                        the                        file
             SYS$COMMON:[SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT.

             Change the incorrect lines with  the  corrected  lines  (as
             shown  in  the  previous  tables).  Note that the lines may
             appear within the file in any order, not necessarily in the
             order of these tables.

         2.  Close SYS$COMMON:[SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT file.

-- COVER LETTER --                                             Page 64
                                                         18 March 2002


         3.  Purge the previous version of the file.


         You will be able to install the OpenVMS Version  7.3  Operating
         System kit using the documented installation instructions.

         Images Affected:

          -  [SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT




34  PROBLEMS ADDRESSED IN VMS721H1_RMS-V0600 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

-- COVER LETTER --                                             Page 65
                                                         18 March 2002


         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.

         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

-- COVER LETTER --                                             Page 66
                                                         18 March 2002


          -  [SYS$LDR]DDIF$RMS_EXTENSION.EXE

          -  [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

-- COVER LETTER --                                             Page 67
                                                         18 March 2002


         introduced 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 68
                                                         18 March 2002


35  PROBLEMS ADDRESSED IN VMS721H1_RMS-V0500 KIT


      o  The VMS721H1_RMS-V0400 kit  had  typographical  errors  in  the
         installation  that  prevented  the DDIF$RMS_EXTENSION.EXE image
         from being installed properly and also caused a warning  during
         post-installation processing.  The related error messages are:

         %PCSI-I-RETAIN, file [SYS$LDR]DDIF$RMS_EXTENSION.EXE was not 
         replaced because file from kit has lower generation number
                                        .
                                        .
                                        .
                                        .
         ...100%NOCOMD, no command on line - reenter with alphabetic first
         character


         Images Affected:

          -  [SYS$LDR]DDIF$RMS_EXTENSION.EXE




36  PROBLEMS ADDRESSED IN VMS721H1_RMS-V0400 KIT


      o  Fix for potential RMS lock hang with global buffers  caused  by
         process deletion (e.g.  STOP/ID).

         This problem involves a race condition  that  may  occur  if  a
         process  is  interrupted by an abort rundown when it is stalled
         waiting for the convert of a system NL lock to a system CR lock
         to  be granted for a global buffer.  This can result in EX lock
         requests being blocked by an unreleased CR lock.

         Images Affected:

          -  [SYS$LDR]RMS.EXE


      o  Fix for sequential  file  corruption  with  global  buffers  in
         cluster.

         The corruption footprint is  a  gap  left  by  a  missing  data
         record.  The gap contains a record's worth of either null bytes
         or residual data in the global buffer from some prior use.

         The following conditions are  necessary  for  this  problem  to
         occur:

          o  The file must be a sequential file.

-- COVER LETTER --                                             Page 69
                                                         18 March 2002


          o  The sequential file must have global buffers enabled.

          o  The sequential file must be written to  (records  appended)
             simultaneously  from  2 or more nodes in a cluster.  If all
             accesses are from one node, the corruption will not occur.

         Images Affected:

          -  [SYS$LDR]RMS.EXE


      o  Fix to prevent a non-fatal SSRVEXCEPT bugcheck when a  wildcard
         network copy completes.

         Attempts to perform wild card file copy operations  across  the
         network  may  fail  with  a  non-fatal SSRVEXCEPT bugcheck upon
         completion when  a  third  party  event  notification  software
         package  is  installed.   Stale  information contained within a
         recycled DAP message buffer could cause an invalid path  to  be
         executed  during  the  implicit  $DISPLAY  of a file during RMS
         rundown.

         Images Affected:

          -  [SYS$LDR]RMS.EXE


      o  Fix to prevent a hang  on  EFN  29  with  missing  upcall  from
         threaded application.

         A user application that is threaded  may  have  a  thread  hang
         waiting  on  event  flag  29.   The IOSB of the thread has been
         filled in, but the thread continues to be  stalled.   This  fix
         ensures  that  an  upcall  is  always  made  when  RMS activity
         completes.

         This problem is fixed in OpenVMS Alpha V7.3.

         Images Affected:

          -  [SYS$LDR]RMS.EXE


      o  Warning added that the limit of 16383 for the number of  either
         file opens or stream connects by one process has been exceeded.

         The Internal File (IFI) and Stream Identifier (ISI) values  for
         file  opens  or  stream  connects  are limited to 14 bits (or a
         maximum value of 16383).  Exceeding the  limit  can  result  in
         unpredictable error conditions depending on what operations are
         attempted after the open or connect.  Prior to this change, RMS
         failed to issue a warning when this limit was exceeded.

         RMS has been modified to return a RMS$_DME error status  so  an
         application  won't  continue when this limit is exceeded for an
         $OPEN or $CONNECT.  This serves as a warning to an  application

-- COVER LETTER --                                             Page 70
                                                         18 March 2002


         that  it must be redesigned to limit either the number of files
         opened or streams connected to less than 16383.

         The check for this limit was introduced in OpenVMS Alpha V7.3.

         Images Affected:

          -  [SYS$LDR]RMS.EXE


      o  Fix to prevent accvio when repeated calls are made  to  CONVERT
         utility callable interface.

         When making repeated calls  to  the  CONVERT  utility  callable
         interface  from  within a user application, an access violation
         or  various  sort  errors  may  be  returned.   The   following
         conditions must exist for this error to occur:

          o  An  application  must  be  making  repeated  calls  to  the
             callable CONVERT interface.

          o  The current file being converted  must  have  more  than  3
             keys.

          o  At least one of the previously converted  files  must  have
             had all compressions disabled.

          o  The current file being converted must have some compression
             enabled.

         Images Affected:

          -  [SYSEXE]CONVERT.EXE

          -  [SYSLIB]CONVSHR.EXE


      o  Fix to correct the bucket size calculation for values that  are
         evenly divisible by the cluster size.

         The Edit/fdl Design Facility (EDF) may calculate a larger  than
         necessary  bucket size when the bucket size is evenly divisible
         by the cluster size of the disk.

         This problem is fixed in OpenVMS Alpha V7.3.

         Images Affected:

          -  [SYSEXE]EDF.EXE


      o  Fix for a GEM compiler related build problem.   There  are  two
         ways a user may see the effects of this problem:

-- COVER LETTER --                                             Page 71
                                                         18 March 2002


          o  ORA-482 crashes on Oracle 8.1.6 OPS.

          o  A process can exit with an unhandled exception with the  PC
             in SYS$PUT.

         A fix to the GEM compiler is included in OpenVMS Alpha V7.3.

         Images Affected:

          -  [SYS$LDR]RMS.EXE




37  PROBLEMS ADDRESSED IN VMS721_RPC-V0100 KIT


      o  The user is granted the option of setting the  dump  logical  -
         DCE$DUMP_DAEMONS.   Based  on  the  user's  preference, code in
         DCE$RPC_STARTUP.COM has been suitably modified to  include  the
         dump facility.

         Images Affected:

          -  [SYSMGR]DCE$RPC_STARTUP.COM


      o  Add a check for the logical DCE$MAX_USERS and modify  the  RPCD
         daemon quotas accordingly.

         Images Affected:

          -  [SYSMGR]DCE$RPC_STARTUP.COM


      o  

         DCE server processes such as DCE$SECD and DCE$CDSD, as well  as
         user  written  DCE  servers  sporadically abort with SS$_ACCVIO
         when hit with a fast burst of client request activity.

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  The DCE$RPCD daemon generated thousands of error  messages  and
         logged them into the DCE$RPCD.OUT file as:

          (rpc) *** FATAL ERROR (receive_dispatch) Unexpected exception

          raised at CNRCVR.C;2\587 ***

          (rpc) *** FATAL ERROR (rpc__cn_network_receiver) Unexpected

          exception is raised at CNRCVR.C;2\398 ***

-- COVER LETTER --                                             Page 72
                                                         18 March 2002




         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  A process using DCE RPC services aborts with a bugcheck similar
         to the one below:

          DECthreads bugcheck (version V3.15-262), terminating execution.
          % Reason:  mutex 0x00000000005DD868 :0 ref. overflow on lock


         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  A new logical has been defined to allow customers to  have  the
         DCE  daemon  files  produce  process  dumps.   The logical name
         DCE$DUMP_DAEMONS can be defined prior to DCE startup to add the
         /DUMP  qualifier to the daemon process.  Process dumps can only
         be reliably produced and read on  Alpha  V7.2-1  systems.   You
         must install special debugger kit ADB073 on your V7.2-1 for the
         DCE dumps to be usable.  Please  contact  your  Compaq  support
         representative to a copy of the ADB073 kit.

         Images Affected:

          -  [SYSMGR]DCE$RPC_STARTUP.COM

          -  [SYSMGR]DCE$SETUP.COM


      o  A  directory  of  SYS$MANAGER   or   SYS$SCRATCH   lists   many
         DCE_OUT*.tmp files.

         Images Affected:
             .le;[SYSMGR]DCE$RPC_STARTUP.COM


      o  Eliminate zero  block  files  left  in  the  credentials  cache
         directory.   When  a  dce_login  is  performed,  six  files are
         created     in     the     credentials     cache     directory,
         DCE$SPECIFIC:[VAR.SECURITY.CREDS].  An example is the following
         files:

                16   029D9101.;2           1-OCT-1998 15:28:18.37
                17   029D9101.;1           1-OCT-1998 15:28:17.76
                18   029D9102.;1           1-OCT-1998 15:28:19.27
                19   029D9200.;1           1-OCT-1998 15:28:19.02
                20   029D9200.DATA;1       1-OCT-1998 15:28:19.38
                21   029D9200.NC;1         1-OCT-1998 15:28:19.18

-- COVER LETTER --                                             Page 73
                                                         18 March 2002


         After a kdestroy, two files remain from the original login.  In
         the login example above, the following files are left:

                16   029D9101.;1           1-OCT-1998 15:28:17.76
                17   029D9102.;1           1-OCT-1998 15:28:19.27

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  DCE login fails when the input for the password is not obtained
         from a terminal.  The login fails with the error below:

         $ rgy_edit
         Current site is: registry server at /.../the_cell/subsys/DCE/
         sec/master l princ_name
         -DCE-
         login: Credentials cache I/O operation failed XXX Error in input 
         password. Login failed.

         exit
         bye


         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  DECnet RPC routines did not correctly update RPC  memory  usage
         statistics used for troubleshooting.

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE

          -  [SYSLIB]DCE$SOCSHR_DNET_OSI.EXE


      o  The is_local call did not work on DECnet OSI interface.

         Images Affected:

          -  [SYSLIB]DCE$SOCKSHR_DNET_OSI.EXE


      o  Attempting to start a DCE server with a  well  known  endpoint,
         such  as  RPCD (port 135) or PERF server (port 2001) fails with
         "unable to bind socket" error,  when  TCP  shows  there  is  no
         process using the port.

         Images Affected:

-- COVER LETTER --                                             Page 74
                                                         18 March 2002


          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  When many clients attempt to connect to one server, the  server
         may  not  be  able  to  accept  the  connections as fast as the
         clients are requesting.

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  The PC Name Service Interface daemon, process  DCE$NSID,  fails
         to  start  on  systems  that support DECnet as an RPC protocol.
         Typing  the  DCE$LOCAL:[000000.VAR.DIRECTORY]DCE$NSID.OUT  file
         shows the process failed with the error message below:
         INFO - manage_server_key thread created
         INFO - tcp_protseq_ok true
         Error - rpc_server_use_protseq (ncacn_dnet_nsp): cannot listen on socket
         (DCE /

         Images Affected:

          -  [SYSLIB]DCE$SOCKSHR_DNET_IV.EXE




38  PROBLEMS ADDRESSED IN VMS721H1_SHADOWING-V0500 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.


-- COVER LETTER --                                             Page 75
                                                         18 March 2002


         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


      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




39  PROBLEMS ADDRESSED IN VMS721H1_SHADOWING-V0400 KIT


      o  A system crash with an  INVEXCEPTN  @SYS$SHDRIVER+7889  running
         CTM_HIGH_IO can occur.

         Crashdump Summary Information:
         ------------------------------

-- COVER LETTER --                                             Page 76
                                                         18 March 2002


         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   NULL
         Current Image:     <not available>
         Failing PC:        FFFFFFFF.804AE890    SYS$SHDRIVER+78890
         Failing PS:        1C000000.00000804
         Module:            SYS$SHDRIVER
                            (Link Date/Time: 21-OCT-2000 03:11:44.71)
         Offset:            00078890


         Images Affected:

          -  [SYS$LDR]SYS$PLUS_SHDRIVER.EXE


      o  If a  second  shadowset  member  is  added,  with  a  /POL=MINI
         command,   while  another  member  is  doing  a  mini  copy,  a
         SS$_IVADDR crash can occur.

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE

          -  [SYS$LDR]SYS$PLUS_SHDRIVER.EXE


      o  An 'Operation incomplete" error can cause a host-based  raidset
         to hang.

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


      o  A SHADDETINCON bugcheck occurs in routine SHLK$MERGE_SIGNAL.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     SHADDETINCON, SHADOWING detects inconsistent
                            state
         Current Process:   CTM$_00060006
         Current Image:     [CTM_HAMMER]CTM_HAMMER_ALPHA_32.EXE
         Failing PC:        FFFFFFFF.804A1CD4
                            SYS$SHDRIVER+93CD4
         Failing PS:        14000000.00000804
         Module:            SYS$SHDRIVER
                            (Link Date/Time: 15-DEC-2000 15:08:57.95)
         Offset:            00093CD4


         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


-- COVER LETTER --                                             Page 77
                                                         18 March 2002


      o  Mini copy operation abort with a %SYSTEM-F-IVADDR bugcheck.

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


      o  Fibrechannel devices cannot execute write logging Phase  I.   A
         benchmark  on  GS  series systems was consuming needless cycles
         issuing TQEs that serve no purpose.

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


      o  A crash occurs with SHADDETINCON in SYS$SHDRIVER + 000762A0.

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE

          -  [SYS$LDR]SYS$PLUS_SHDRIVER.EXE


      o  If  the  device  is  unable  to  perform  a   read   SCB,   the
         /POLICY=MINICOPY command will fail.

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


      o  During a mini copy operation, the path to a shadow  set  member
         may  be  switched  before the SCB can be read.  This causes the
         operation to fail.

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE

          -  [SYS$LDR]SYS$PLUS_SHDRIVER.EXE


      o  Multiple  systems  may  hang  on  cluster  shutdown  because  a
         deadlock occurs when the WATCHER node closes.

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


      o  Multiple  systems  may  hang  on  cluster  shutdown  because  a
         deadlock occurs when the WATCHER node closes.

-- COVER LETTER --                                             Page 78
                                                         18 March 2002


         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


      o  A SHADDETINCON crash occurs in EXPEL_DEVICE.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     SHADDETINCON, SHADOWING detects inconsistent 
                            state
         Current Process:   NULL
         Current Image:     <not available>
         Failing PC:        FFFFFFFF.8047BC38    SYS$SHDRIVER+83C38
         Failing PS:        34000000.00000804
         Module:            SYS$SHDRIVER
                            (Link Date/Time: 30-MAR-2001 09:09:47.85)
         Offset:            00083C38


         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


      o  If system check is enabled, the first MOUNT of the system  disk
         or a shadow set will crash the system.

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


      o  The first  MOUNT  of  a  system  disk  will  crash,  if  SYSGEN
         system_check is enabled.

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


      o  A SHADDETINCON system crash  occurs  in  Watcher  code  when  a
         master  member  is  identified in an IN_SET lock value block is
         not a member of the set on the Watcher node.

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE



-- COVER LETTER --                                             Page 79
                                                         18 March 2002


40  PROBLEMS ADDRESSED IN VMS721H1_SYS-V0400 KIT


      o  A system can crash  with  an  INCONMMGST,  Inconsistent  memory
         management state bugcheck.

         Crash Dump Summary Information:
         ------------------------------
         Bugcheck Type:     INCONMMGST, Inconsistent memory management
                            state
         Current Process:   SWAPPER
         Current Image:     <not available>
         Failing PC:        FFFFFFFF.8016E5F4
                            MMG_STD$ALLOC_PAGSWP_PAGES_C+00954
         Failing PS:        00000000.00000800
         Module:            SYS$VM    (Link Date/Time:
                            9-FEB-2001 23:42:14.16)
         Offset:            0001C5F4


         Images Affected:

          -  [SYS$LDR]SYS$VM.EXE


      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


-- COVER LETTER --                                             Page 80
                                                         18 March 2002


         Sometimes it does not.

         Images Affected:

          -  [SYS$LDR]MULTIPATH.EXE

          -  [SYS$LDR]MULTIPATH.STB


      o  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


      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:

          -  [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 DSA device is in a copy or minimerge state, a SHOW  DEVICE
         DSA command can hang.

         Images Affected:

          -  [SYSLIB]SDA$SHARE.EXE


      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:

-- COVER LETTER --                                             Page 81
                                                         18 March 2002



             DIFVOLMNT - different volume already mounted on this
                         device.


             Note: To receive this complete correction you must also 
                   install the VMS721H2_MOUNT96-V0200 and 
                   VMS721_FIBRE_SCSI-V0400 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  System Service  SYS$GETJPIW,  with  the  JPI$M_NO_TARGET_INSWAP
         flag  set  and  at  least  one  CTL  and  PSB  item  code, e.g.
         JPI$_IMAGNAME or JPI$_RIGHTS_SIZE, returns a %SYSTEM-F-BADPARAM
         error.

         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 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


-- COVER LETTER --                                             Page 82
                                                         18 March 2002


      o  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  nonCOE  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


      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  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:

-- COVER LETTER --                                             Page 83
                                                         18 March 2002


          -  [SYS$LDR]SYSTEM_PRIMITIVES.EXE

          -  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE

          -  [SYS$LDR]SYSTEM_PRIMITIVES.STB

          -  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB




41  PROBLEMS ADDRESSED IN VMS721H1_SYS-V0300 KIT


      o  The use of HSM on a Multipath device results in a system  crash
         at  HSDRIVER+02AF8.   This  kit enables the use of Hierarchical
         Storage Manager (HSM) on Multipath devices.

         Images Affected:

          -  [SYS$LDR]IODEF.STB

          -  [SYS$LDR]MULTIPATH.EXE

          -  [SYS$LDR]MULTIPATH.STB

          -  [SYS$LDR]MULTIPATH_MON.EXE

          -  [SYS$LDR]MULTIPATH_MON.STB


      o  A   system   crashes   with   a   DOUBLEDEALO    bugcheck    at
         EXE$DEALLOCATE_C+00108  in  $BRKTHRU when trying to de-allocate
         P1 pool that has already been  de-allocated.   See  crash  dump
         summary information below:

         Crash Dump Summary
         ------------------

         Bugcheck Type:     DOUBLDEALO, Double deallocation of memory
                            block
         Current Process:   CANDOUGF_1
         Current Image:     $1$DUA0:[SYS1.SYSCOMMON.][SYSEXE]MAIL.EXE
         Failing PC:        FFFFFFFF.80048A28    EXE$DEALLOCATE_C+00108
         Failing PS:        20000000.00000200
         Module:            SYSTEM_PRIMITIVES_MIN
                            (Link Date/Time: 13-SEP-2000 06:34:17.45)
         Offset:            00012A28


         Images Affected:

          -  [SYS$LDR]IO_ROUTINES.EXE

-- COVER LETTER --                                             Page 84
                                                         18 March 2002


          -  [SYS$LDR]IO_ROUTINES.STB

          -  [SYS$LDR]IO_ROUTINES_MON.EXE

          -  [SYS$LDR]IO_ROUTINES_MON.STB

          -  [SYS$LDR]SYS$CLUSTER.EXE


      o  If host-based volume shadowing is running when I/O transfers to
         SCSI disks stop, and the disk is a member of a shadow set, then
         a SHADDETINCON crash occurs.

         Images Affected:

          -  [SYS$LDR]IO_ROUTINES.EXE

          -  [SYS$LDR]IO_ROUTINES.STB


      o  Under a heavy I/O load, where the processes DIOCNT is at  zero,
         certain circumstances exist that allow DIOCNT to go from 0 to a
         negative value.  Once this has occurred, it may be possible for
         an  application to hang a process or system with an unmanagable
         RWAST condition.  Or, it may be possible for an application  to
         absorb  all  of  non-paged  pool  with  IRPs.  This can cause a
         system to crash with an INSF_NONPAGED, 'Insufficient non- paged
         pool'  bugcheck  in  SYS$SHDRIVER.   See the crash dump summary
         below:

         Crash Dump Summary Information:
         ------------------------------
         Bugcheck Type:     INSF_NONPAGED, Insufficient nonpaged pool
         Current Process:   NMD_CQS4
         Current Image:     $2$DUA100:[MARS.V32.][EXE]CI_CQS.EXE;3
         Failing PC:        FFFFFFFF.92F8A204    SYS$SHDRIVER+70204
         Failing PS:        30000000.00000804
         Module:            SYS$SHDRIVER
                           (Link Date/Time: 24-JAN-2000 9:28:00.85)
         Offset:            00070204


         Images Affected:

          -  [SYS$LDR]IO_ROUTINES.EXE

          -  [SYS$LDR]IO_ROUTINES.STB

          -  [SYS$LDR]IO_ROUTINES_MON.EXE

          -  [SYS$LDR]IO_ROUTINES_MON.STB


      o  A system can crash during boot with a SHADDETINCON bugcheck  at
         SYS$SHDRIVER+7580C     in     module    SHD_THREADS,    routine
         SHTD$ENQ_LOCK_BLOCK.  See crash dump summary below:

-- COVER LETTER --                                             Page 85
                                                         18 March 2002



         Crash Dump Summary Information:
         ------------------------------
         Bugcheck Type:     SHADDETINCON, SHADOWING detects inconsistent
                            state
         Current Process:   NULL
         Current Image:     <not available>
         Failing PC:        FFFFFFFF.8047F80C    SYS$SHDRIVER+7580C
         Failing PS:        04000000.00000804
         Module:            SYS$SHDRIVER    
                           (Link Date/Time: 24-OCT-2000 15:06:45.56)
         Offset:            0007580C


         Images Affected:

          -  [SYS$LDR]MULTIPATH.EXE

          -  [SYS$LDR]MULTIPATH.STB

          -  [SYS$LDR]MULTIPATH_MON.EXE

          -  [SYS$LDR]MULTIPATH_MON.STB

          -  [SYS$LDR]IODEF.STB


      o  Pool corruption, caused by double deallocation of an  IRP,  can
         occur  when the current path to a $1$GGAn:  or $a$GKAn:  device
         is a secondary path and a polling I/O arrives while there is an
         active IRP on that path.

         Images Affected:

          -  [SYS$LDR]MULTIPATH.EXE

          -  [SYS$LDR]MULTIPATH.STB

          -  [SYS$LDR]MULTIPATH_MON.EXE

          -  [SYS$LDR]MULTIPATH_MON.STB

          -  [SYS$LDR]IODEF.STB


      o  When mounting FibreChannel shadowsets, a system can crash  with
         an  INVEXCEPTN,  'Exception  while  above  ASTDEL'  bugcheck at
         MULTIPATH_MON+3B2C, routine MPDEV$MAP_STATUS_SHDSET.   See  the
         crash dump summary below:

         Crash Dump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   NULL
         Current Image:     <not available>
         Failing PC:        FFFFFFFF.8038FB2C 

-- COVER LETTER --                                             Page 86
                                                         18 March 2002


                           MPDEV$MAP_STATUS_SHDSET_C+0005C
         Failing PS:        10000000.00000804
         Module:            MULTIPATH_MON
                            (Link Date/Time:  9-FEB-2001 23:41:29.09)
         Offset:            00003B2C


         Images Affected:

          -  [SYS$LDR]MULTIPATH.EXE

          -  [SYS$LDR]MULTIPATH.STB


      o  The  system  can  crash  with   an   SSRVEXCEPT   bugcheck   at
         LOCKING+019CC   on   an   LDQ_U   R11,(R26)  instruction  while
         processing a resource domain.  See crash dump summary below:

         Crash Dump Summary Information:
         ------------------------------
         Bugcheck Type:     SSRVEXCEPT, Unexpected system service 
                           exception
         Current Process:   BATCH_3084
         Current Image:     DSA509:[SSEXE.DP]SPCUSERMAINT.EXE;44
         Failing PC:        FFFFFFFF.801619CC    LOCKING+019CC
         Failing PS:        38000000.00000203
         Module:            LOCKING
                            Link Date/Time: 29-MAR-2000 00:58:34.67
         Offset:            000019CC


         Images Affected:

          -  [SYS$LDR]LOCKING.EXE

          -  [SYS$LDR]LOCKING.STB


      o  Processes hang in Record Management Services (RMS) during  $GET
         and  no  apparent  locking conflict can be detected.  There are
         cases where the status does not get updated  after  granting  a
         byte range lock.

         Images Affected:

          -  [SYS$LDR]LOCKING.EXE

          -  [SYS$LDR]LOCKING.STB


      o  With multithreaded processes, systems have been seen  to  hang.
         Specifically,  an  AST  critical to the file system causes file
         system I/O operations to hang for all processes.  It  would  be
         appropriate  to  suspect  this problem is occurring on a system
         with otherwise unexplained system or application hangs, if  the
         system   has   multiple   CPUs  and  any  multi-kernel-threaded

-- COVER LETTER --                                             Page 87
                                                         18 March 2002


         applications.  This includes essentially any Java applications.

         Images Affected:

          -  [SYS$LDR]PROCESS_MANAGEMENT.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT.STB

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


      o  An ACCVIO occurs in MESSAGE_ROUTINES  near  "ALTNUMTIM."  There
         are several ways in which this problem may occur:

          -  A process ACCVIOs near the symbol EXE$ALTNUMTIM.

          -  ORA-482 crashes on Oracle 8.1.6 OPS.

          -  An Oracle process exits with the status code 0C,  which  is
             an   ACCVIO.    Since  Oracle  processes  run  as  detached
             processes, this status code would appear in the  accounting
             log.


         Images Affected:

          -  [SYS$LDR]MESSAGE_ROUTINES.EXE

          -  [SYS$LDR]MESSAGE_ROUTINES.STB


      o  The GETTIMEOFDAY() CRTL function returns  an  error  in  ORACLE
         Parallel Server Version 8.1.6.  This can occur in several ways:

          -  The GETTIMEOFDAY() function returns status code 103DFE0.

          -  The VMS user mode system services returns unexpected status
             codes,   including   C   signal   status  code,  SS$_BREAK,
             SS$_IMGDMP or SS$_DEBUG.

          -  An ORA-7211 Oracle 8.1.6 OPS crash could occur.

          -  A severe performance slowdown on Oracle 8.1.6 or 8.1.7  OPS
             could occur.

          -  Oracle 8.1.6 or 8.1.7 OPS might hang.


         Images Affected:

          -  [SYS$LDR]EXCEPTION.EXE

-- COVER LETTER --                                             Page 88
                                                         18 March 2002


          -  [SYS$LDR]EXCEPTION.STB

          -  [SYS$LDR]EXCEPTION_MON.EXE

          -  [SYS$LDR]EXCEPTION_MON.STB


      o  A process exits with an error status,  but  without  a  process
         dump.   The  image dump flag is set for the process.  There are
         several ways this can be seen:

         1.  Processes do not dump when they  exit  while  executing  an
             exception  handler.   The  process must have the image dump
             flag set.

         2.  Oracle8 OPS background processes do not dump when they  hit
             an error.  The processes must have the image dump flag set.


         Images Affected:

          -  [SYS$LDR]EXCEPTION.EXE

          -  [SYS$LDR]EXCEPTION.STB

          -  [SYS$LDR]EXCEPTION_MON.EXE

          -  [SYS$LDR]EXCEPTION_MON.STB


      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


      o  The user stack can become corrupt through repeated issuances of
         the   DEBUG   command.   The  following  sequence  of  commands
         illustrates the problem:

           $LINK/DEBUG FOO (where FOO simply executes an
                           infinite loop)
           $RUN FOO
           DBG> go
           DBG> CTRL/Y

-- COVER LETTER --                                             Page 89
                                                         18 March 2002


           $DEBUG
           DBG> go
           DBG> CTRL/Y
           $DEBUG

         %DEBUG-I-TRUNC64, address 0000000200000000 being truncated in
         DBGKREGISTERS\DBG$
         GET_PD_FROM_FP
         %DEBUG-I-TRUNC64, address 0000000200000000 being truncated in
         DBGKREGISTERS\DBG$
         GET_PD_FROM_FP
         DBG> g
         %DEBUG-I-BADSTACKPATCH1, Corrupt stack detected...attempting 
         patch STQ
         R27,(SP)
         %DEBUG-W-NORESUME, unable to resume execution, stack or PC 
         corrupted in %PROCESS_NUMBER 1
         DBG>

         The user stack is now corrupt.

         Images Affected:

          -  [SYS$LDR]EXCEPTION.EXE

          -  [SYS$LDR]EXCEPTION.STB

          -  [SYS$LDR]EXCEPTION_MON.EXE

          -  [SYS$LDR]EXCEPTION_MON.STB


      o  An Oracle Parallel Server can crash with an ORA-482 error.  The
         PC  is  near a routine's prologue code and the FP has been set.
         R27 is stored on the stack after the FP is set and the  process
         exits with an unhandled exception.

         Images Affected:

          -  [SYS$LDR]EXCEPTION.EXE

          -  [SYS$LDR]EXCEPTION.STB

          -  [SYS$LDR]EXCEPTION_MON.EXE

          -  [SYS$LDR]EXCEPTION_MON.STB


      o  A  system  can   crash   with   An   INCONSTATE   bugcheck   at
         SYS$VCC+0822C.

         Crash Dump Summary Information:
         ------------------------------
         Bugcheck Type:     INCONSTATE, Inconsistent I/O data base
         Current Process:   NULL
         Current Image:     <not available>

-- COVER LETTER --                                             Page 90
                                                         18 March 2002


         Failing PC:        FFFFFFFF.801E822C    SYS$VCC+0822C
         Failing PS:        08000000.00000804
         Module:            SYS$VCC    
                           (Link Date/Time: 18-MAY-2000 00:48:08.10)
         Offset:            0000822C


         This is not one of the conditions  that  the  CVCB_CHKLK  macro
         recognizes  as  temporary,  so it bugchecks rather than retries
         the lock conversion.  The restriction that fails in  this  case
         is the CVCB lock, which is already in PR mode.         

         Images Affected:

          -  [SYS$LDR]SYS$VCC.EXE

          -  [SYS$LDR]SYS$VCC.STB

          -  [SYS$LDR]SYS$VCC_MON.EXE

          -  [SYS$LDR]SYS$VCC_MON.STB


      o  The system hangs with the AUDIT_SERVER process  in  RWMBX  when
         Object_Server tries to write to its own mailbox.

         Images Affected:

          -  [SYS$LDR]SECURITY.EXE

          -  [SYS$LDR]SECURITY.STB

          -  [SYS$LDR]SECURITY_MON.EXE

          -  [SYS$LDR]SECURITY_MON.STB

          -  [SYS$LDR]IO_ROUTINES.EXE

          -  [SYS$LDR]IO_ROUTINES.STB

          -  [SYS$LDR]IO_ROUTINES_MON.EXE

          -  [SYS$LDR]IO_ROUTINES_MON.STB


      o  Shadow sets  with  FibreChannel  members  fail  to  mount  with
         MULTIPATH,  resulting  in MOUNTVERIFY error messages and member
         removals.

         Images Affected:

          -  [SYS$LDR]MULTIPATH.EXE


-- COVER LETTER --                                             Page 91
                                                         18 March 2002


      o  The following fields have been added for the virtual  unit  and
         shadow  set  members  in  the  output  of an SDA SHO DEVICE DSA
         command:

          o  Site Value

          o  Timeout Value

         Each member will now display Read Cost, Site, SM Timeout.   For
         example:

         OLD OUTPUT:
         -----------

         $ analyze/SYS
         SDA> SHO dev dsa64
         DSA64                         Generic_DK          UCB: 817CD500
                                                .
                                                .
                                                .
         I/O data structures
         -------------------

         ----- Shadow Descriptor Block (SHAD) 817DA080 -----

         Virtual Unit status:              0001 normal

         Members         3 Act user IRPs          0 VU UCB     817CD500
         Devices         3 SCB LBN         010F4627 Master FL  817DA3E4
         Fcpy Targets    0 Generation Num  2C34A8FF Restart FL 817DA3EC
         Mcpy Targets    0                 009FCC39
         Last Read Index 0 Virtual Unit Id 00000000
         Master Index    1                 12610040

         ----- SHAD Device summary for DSA64  -----

         Device $1$DGA110
           Index 0 Status    000000A0 src,valid
           UCB 816156C0   VCB 817DABC0   Unit Id. 10E1006E 00000001
         Device $1$DGA210
           Index 1 Status    000000A0 src,valid
           UCB 81615BC0   VCB 817DB540   Unit Id. 10E100D2 00000001
         Device $64$DKA301
           Index 2 Status    000000A0 src,valid
           UCB 81624540   VCB 8166E880   Unit Id. 1161012D 00000040



         NEW OUTPUT
         -----------

         $ analyze/SYS
         SDA> SHO dev dsa64
         DSA64                     Generic_DK          UCB: 81540000
         .
         .

-- COVER LETTER --                                             Page 92
                                                         18 March 2002


         .
         I/O data structures
         -------------------

         --- Shadowing Descriptor Block (SHAD) 816EC440 ---

         Virtual Unit SCB Status:        0001 normal

         Total Devices    3 VU_UCB           81540000
         Source Members   3 SCB LBN          010F4627
         Act Copy Target  0 Generation       009FCC39
         Act Merge Target 0 Number           2C34A8FF
         Last Read Index  1 VU Site Value    00000000
         Master Mbr Index 1 VU Timeout Value 3600

         Device $1$DGA110 
           Index 0 Status    000000A0 src,valid
           Read Cost 0000002A    Site 00000000   SM Timeout 120
                                 UCB  8153D440   VCB 8161F880
         Device $1$DGA210        ...  Master Member
           Index 1 Status    000000A0 src,valid
           Read Cost 0000002A    Site 00000000   SM Timeout 120
                                 UCB  81543800   VCB 8187CA40
         Device $64$DKA301
           Index 2 Status    000000A0 src,valid
           Read Cost 0000002A    Site 00000000   SM Timeout 120
                                 UCB  81503700   VCB 8179D800


         Images Affected:

          -  [SYSLIB]SDA$SHARE.EXE


      o  The console callback FIND_NODE takes too long  to  perform  its
         task and the console loses clock ticks.

         Images Affected:

          -  [SYS$LDR}SYSTEM_PRIMITIVES.EXE

          -  [SYS$LDR}SYSTEM_PRIMITIVES_MIN.EXE


      o  Using the  emulated  FIND_NODE  routine  requires  setting  the
         SYSGEN parameter VMS8 to %x1029000.

         Images Affected:

          -  [SYS$LDR}SYSTEM_PRIMITIVES.EXE

          -  [SYS$LDR}SYSTEM_PRIMITIVES_MIN.EXE


-- COVER LETTER --                                             Page 93
                                                         18 March 2002


      o  The system can crash with INVEXCEPTN bugcheck at  LOCKING+0B540
         after reaching the end of the lock i table.

         Images Affected:

          -  [SYS$LDR]EXEC_INIT.EXE


      o  On a pre-EV56 system, STB R31,xxx(Ry) sometimes stored a  value
         other  than  0.   The  manifestation  is  that  a program could
         operate correctly on an EV56 processor, but fail on an  EV5  or
         earlier  processor.  The failure depends on the exact nature of
         the program.  It will  happen  only  if  some  modules  in  the
         program  were  compiled with the /ARCHITECTURE= switch, and the
         processor specified by this switch  was  EV56  or  later.   See
         error message below:

         %SYSTEM-I-EMULATED, an instruction not implemented on this
                             processor was emulated at PC=xxxxx, PS=yyyy

         This message does not mean the problem has  happened;  it  just
         means that some of the conditions are right for it to happen.

         Images Affected:

          -  [SYS$LDR}EXCEPTION.EXE

          -  [SYS$LDR}EXCEPTION_MON.EXE


      o  Make two minor changes to the executive to support DCPI.

         1.  Shut off Perfmon interrupts when the system shuts  down  or
             crashes.

         2.  Send a message to DCPI through a dedicated mailbox whenever
             an  image  is activated.  (DCPI creates the mailbox, and no
             message is sent if there is no mailbox).


         DCPI  perform  well  without  these   changes,   however,   the
         usefulness  and  robustness  of  DCPI  is improved, if they are
         available.

         Images Affected:

          -  [SYS$LDR]EXCEPTION.EXE

          -  [SYS$LDR]EXCEPTION.STB

          -  [SYS$LDR]EXCEPTION_MON.EXE

          -  [SYS$LDR]EXCEPTION_MON.STB

-- COVER LETTER --                                             Page 94
                                                         18 March 2002


          -  [SYS$LDR]IMAGE_MANAGEMENT.EXE

          -  [SYS$LDR]IMAGE_MANAGEMENT.STB

          -  [SYS$LDR]IMAGE_MANAGEMENT_MON.EXE

          -  [SYS$LDR]IMAGE_MANAGEMENT_MON.STB


      o  There is no display of the bugcheck information during a system
         crash.

         Images Affected:

          -  [SYS$LDR]EXCEPTION.EXE

          -  [SYS$LDR]EXCEPTION.STB

          -  [SYS$LDR]EXCEPTION_MON.EXE

          -  [SYS$LDR]EXCEPTION_MON.STB


      o  The system could crash at shutdown on GS60; and  a  crash  file
         may  not  be  created.   While  performing  the  shutdown,  the
         following message is displayed in a repeated pattern:

            CPU 0 halted
                 halt code = 2
                 kernel stack not valid halt
                 PC = ffffffff800b764c

            CPU 0 restarting


         Images Affected:

          -  [SYS$LDR]EXCEPTION.EXE

          -  [SYS$LDR]EXCEPTION.STB

          -  [SYS$LDR]EXCEPTION_MON.EXE

          -  [SYS$LDR]EXCEPTION_MON.STB




42  PROBLEMS ADDRESSED IN VMS721H1_SYSLOA-V0200 KIT


      o  A  system   can   crash   with   a   LOCKMGRERR   bugcheck   at
         LCK$SND_CVTREQ_C+00EE8.

         Crashdump Summary Information:
         ------------------------------

-- COVER LETTER --                                             Page 95
                                                         18 March 2002


         Bugcheck Type:     LOCKMGRERR, Error detected by Lock Manager
         Current Process:   _OVRNITE3921
         Current Image:     <not available>
         Failing PC:        FFFFFFFF.8022DB48    LCK$SND_CVTREQ_C+00EE8
         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




43  PROBLEMS ADDRESSED IN VMS721H1_SYSLOA-V0100 KIT


      o  A remote $GETJPI fails with $SYSTEM-F-BADBUFLEN.

         Images Affected:

          -  [SYS$LDR]SYS$CLUSTER.EXE


      o  OpenVMS Alpha systems may crash with a DOUBLDEALO  bugcheck  at
         EXE$DEALLOCATE_C+00108  in  $BRKTHRU  when trying to deallocate
         some P1 pool that has already been deallocated.

         Images Affected:

          -  [SYS$LDR]SYS$CLUSTER.EXE


      o  The  NOAUDIT  bit  could  get  set  incorrectly  for   DETACHED
         processes  being  created  on a remote node in a cluster.  As a
         result, audit  data  for  non-trusted  processes  will  not  be
         captured.

         Images Affected:

          -  [SYS$LDR]SYS$CLUSTER.EXE




44  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)

-- COVER LETTER --                                             Page 96
                                                         18 March 2002


     INSTALLATION RATING:

      INSTALL_1 : To be installed by all customers.



45  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 VMS721H1_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.



     45.1  Special Installation Instructions:

          45.1.1  VMS721H1_RMS-V0600 System Parameter Changes

          As  part  of  the  post  installation   processing   for   the
          VMS721H1_RMS-V0600  ECO  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.

-- COVER LETTER --                                             Page 97
                                                         18 March 2002


          45.1.2  Old Versions of DECWindows Files

          Due  to  the  nature  of  the  problems   corrected   by   the
          VMS721H1_DWMOTMUP-V0100   kit,   Compaq  recommends  that  the
          DECWindows files replaced by this kit be deleted and not  left
          on  the  system.  During installation you will be asked if you
          wish to delete these files.  Files that will be deleted are:

           o  [SYSLIB]DECW$TRANSPORT_COMMON.EXE_OLD

           o  [SYSLIB]DECW$TRANSPORT_DECNET.EXE_OLD

           o  [SYSLIB]DECW$TRANSPORT_LAT.EXE_OLD

           o  [SYSLIB]DECW$TRANSPORT_LOCAL.EXE_OLD

           o  [SYSLIB]DECW$TRANSPORT_TCPIP.EXE_OLD



          45.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/SYS NO_ASK$BACKUP TRUE

           -  $ DEFINE/SYS NO_ASK$BACKUP TRUE

           -  $ DEFINE/SYS INSTALL$PLUS_SHDRIVER [TRUE,FALSE]

           -  Define logical ARCHIVE_DW_MOT_MUP as [TRUE,FALSE]

              Note:

                Defining the logical INSTALL$PLUS_SHDRIVER as TRUE will 
                install the enhanced functionality Volume Shadowing 
                driver image.

                Defining the logical INSTALL$PLUS_SHDRIVER as FALSE will 
                install the standard Volume Shadowing driver image

                Defining the logical ARCHIVE_DW_MOT_MUP as TRUE will 
                delete the replaced DECWindows files (recommended).

                Defining the logical ARCHIVE_DW_MOT_MUP as FALSE will 
                leave the replaced DECWindows files on your system.


           -  Add  the  following  qualifiers  to  the  PRODUCT  INSTALL
              command and add that command to the DCL procedure.

                /PROD=DEC/BASE=AXPVMS/VER=V5.0

-- COVER LETTER --                                             Page 98
                                                         18 March 2002




           -  De-assign the logicals assigned

          For  example,  a  sample   command   file   to   install   the
          VMS721H1_UPDATE kit would be:

          $
          $ DEFINE/SYS NO_ASK$BACKUP TRUE
          $ DEFINE/SYS NO_ASK$REBOOT TRUE
          $ DEFINE/SYS INSTALL$PLUS_SHDRIVER TRUE
          $ DEFINE/SYS ARCHIVE_DW_MOT_MUP TRUE
          $!
          $ PROD INSTALL VMS721H1_UPDATE/PROD=DEC/BASE=AXPVMS/VER=V5.0
          $!
          $ DEASSIGN/SYS NO_ASK$BACKUP
          $ DEASSIGN/SYS NO_ASK$REBOOT
          $ DEASSIGN/SYS INSTALL$PLUS_SHDRIVER
          $ DEASSIGN/SYS ARCHIVE_DW_MOT_MUP
          $!
          $ exit

     Copyright  (c)  Compaq  Computer  Corporation,  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 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 OF LIABILITY, WITH RESPECT TO ANY PATCH
     MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.