Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp


more options
 
hp.com home
End of Jump to page title
HP Services software patches
Jump to content


» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

patches by topic
» DOS
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS73_UPDATE-V0200 Update Alpha V7.3 ECO Summary
TITLE: OpenVMS VMS73_UPDATE-V0200 Update Alpha V7.3 ECO Summary
 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
 
       For OpenVMS savesets, the name of the compressed saveset
       file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
       kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
       saveset is copied to your system, expand the compressed
       saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
 
       For PCSI files, once the PCSI file is copied to your system,
       rename the PCSI file to kitname.pcsi-dcx_axpexe or
       kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
       RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe.  The
       resultant file will be the PCSI installation file which can be
       used to install the ECO.
 

 

             ECO NUMBER:     VMS73_UPDATE-V0200
             PRODUCT:        OpenVMS Alpha OPERATING SYSTEM V7.3
             UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3



New Kit Date:       27-AUG-2003
Modification Date:  28-AUG-2003
Modification Type:  Kit Released with Correct PCSI Name


                                COVER LETTER


1  KIT NAME:

     VMS73_UPDATE-V0200


2  KITS SUPERSEDED BY THIS KIT:


      o  VMS73_AMACRO-V0100

      o  VMS73_APB-V0200

      o  VMS73_BACKUP-V0200

      o  VMS73_CLIUTL-V0200

      o  VMS73_CLUSTER-V0200

      o  VMS73_CPU2308-V0100

      o  VMS73_DCL-V0300

      o  VMS73_DDTM-V0100

      o  VMS73_DEBUG-V0100

      o  VMS73_DECW_XTERM-V0100

      o  VMS73_DELETE-V0100

      o  VMS73_DIR-V0100

      o  VMS73_DRIVER-V0300

      o  VMS73_F11X-V0100

      o  VMS73_FIBRE_SCSI-V0500

      o  VMS73_GRAPHICS-V0100

      o  VMS73_IIDRIVER-V0100

      o  VMS73_INIT-V0100

      o  VMS73_IOGEN-V0100

      o  VMS73_LAN-V0400

      o  VMS73_LIBRTL-V0200

      o  VMS73_LINKER-V0300

      o  VMS73_MANAGE-V0200

      o  VMS73_MIME-V0100

      o  VMS73_MONTOR-V0100

      o  VMS73_MSCP-V0100

      o  VMS73_PPPD-V0200

      o  VMS73_PTHREAD-V0300

      o  VMS73_REGISTRY-V0100

      o  VMS73_REM-V0100

      o  VMS73_RMS-V0400

      o  VMS73_RPC-V0100

      o  VMS73_RTPAD-V0100

      o  VMS73_SHADOWING-V0200

      o  VMS73_SYS-V0500

      o  VMS73_SYSINI-V0100

      o  VMS73_SYSLOA-V0300

      o  VMS73_TDF-V0100

      o  VMS73_UPDATE-V0100

      o  VMS73_XFC-V0300



3  KIT DEPENDENCIES:

     3.1  The following remedial kit(s), or  later,  must  be  installed
          BEFORE installation of this, or any required kit:

     VMS73_PCSI-V0100


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


     4.2  Files patched or replaced:


      o  [SYSEXE]ALPHA_MACRO.EXE (new image)

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

      o  [SYSEXE]APB.EXE (new image)

      o  [SYSEXE]AUDIT_SERVER.EXE (new image)

      o  [SYSEXE]BACKUP.EXE (new image)

      o  [SYSLIB]BACKUPSHR.EXE (new image)

      o  [SYSEXE]CIA.EXE (new image)

      o  [SYSMSG]CLIUTLMSG.EXE (new image)

      o  [SYSEXE]CONFIGURE.EXE (new image)

      o  [SYSEXE]CONVERT.EXE (new image)

      o  [SYSLIB]CONVSHR.EXE (new image)

      o  [SYSEXE]CREATE.EXE (new image)

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

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

      o  [SYSEXE]DCE$DCED.EXE (new image)

      o  [SYSEXE]DCL.EXE (new image)

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

      o  [SYSLIB]DEBUGSHR.EXE (new image)

      o  [SYSEXE]DEBUG_APB.EXE (new image)

      o  [SYSEXE]DECW$DWT_FONT_DAEMON.EXE (new image)

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

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

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

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

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

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

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

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

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

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

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

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

      o  [SYSEXE]DECW$SETSHODIS.EXE (new image)

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

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

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

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

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

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

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

      o  [SYSEXE]DELETE.EXE (new image)

      o  [SYSEXE]DIRECTORY.EXE (new image)

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

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

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

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

      o  [SYSHLP.UNSUPPORTED]FC$CP.EXE (new image)

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

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

      o  [SYSLIB]IMGDMP.EXE (new image)

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

      o  [SYSEXE]INIT.EXE (new image)

      o  [SYSEXE]INSTALL.EXE (new image)

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

      o  [SYSLIB]LIBRTL_INSTRUMENTED.EXE (new image)

      o  [SYSEXE]LINK.EXE (new image)

      o  [SYSEXE]LMCP.EXE (new image)

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

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

      o  [SYSLIB]MOUNTSHR.EXE (new image)

      o  [SYSHLP.UNSUPPORTED]MSA_UTIL.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  [SYSEXE]PPPD$UTIL.EXE (new image)

      o  [SYSMSG]PRGDEVMSG.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  [SYSEXE]RECLAIM.EXE (new image)

      o  [SYSEXE]REG$CP.EXE (new image)

      o  [SYSEXE]REGISTRY$SERVER.EXE (new image)

      o  [SYSEXE]REMACP.EXE (new image)

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

      o  [SYSEXE]RTPAD.EXE (new image)

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

      o  [SYSEXE]SHADOW_SERVER.EXE (new image)

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

      o  [SYSEXE]SHOW.EXE (new image)

      o  [SYSEXE]SHWCLSTR.EXE (new image)

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

      o  [SYSEXE]SMISERVER.EXE (new image)

      o  [SYSLIB]SPISHR.EXE (new image)

      o  [SYSEXE]STACONFIG.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_2308.EXE (new image)

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

      o  [SYSEXE]SYS$DAYLIGHT_SAVING.EXE (new image)

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

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

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

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

      o  [SYS$LDR]SYS$EBDRIVER.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$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)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

      o  [SYSEXE]SYSBOOT.EXE (new image)

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

      o  [SYSEXE]SYSINIT.EXE (new image)

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

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

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

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

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

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

      o  [SYSEXE]TDF$SET_TIMEZONE.EXE (new image)

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

      o  [SYSEXE]TPSERV.EXE (new image)

      o  [SYSEXE]VMOUNT.EXE (new image)

      o  [SYSEXE]VPM.EXE (new image)

      o  [SYSEXE]VPM_SERVER.EXE (new image)

      o  [SYSUPD]BACKUP.CLD (new file)

      o  [SYSUPD]COPY.CLD (new file)

      o  [SYSHLP.EXAMPLES]DAYLIGHT_SAVINGS.COM (new file)

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

      o  [000000]DEC-AXPVMS-VMS-V0703-1-2.PCSI$DESCRIPTION (new file)

      o  [SYSUPD]DIRECTORY.CLD (new file)

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

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

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

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

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

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

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

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

      o  [SYSEXE]IPCDEF.STB (new file)

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

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

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

      o  [SYSEXE]MIME$HELP.HLB (new file)

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

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

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

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

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

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

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

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

      o  [SYSLIB]STARLET.MLB (new file)

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

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

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

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

      o  [SYSLIB]SYS$STARLET_C.TLB (new file)

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

      o  [SYS$LDR]SYS$XFCACHE.DSF (new file)

      o  [SYSLIB]SYS$XFCACHE.STB (new file)

      o  [SYSHLP]XFC$SDA.HLB (new file)

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

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

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

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

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

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

      o  [SYS$STARTUP]VMS$INITIAL-050_CONFIGURE.COM (new file)

      o  [SYS$LDR]VMSKITBLD.DAT



5  PROBLEMS ADDRESSED IN VMS73_UPDATE-V0200 KIT


      o  The VMS73_UPDATE-V0200 kit is a consolidation of previously
         released OpenVMS V7.3 ECO kits.  The following ECO kits are
         included:

           VMS73_AMACRO-V0100          VMS73_APB-V0200             
           VMS73_BACKUP-V0200          VMS73_CLIUTL-V0200          
           VMS73_CLUSTER-V0200         VMS73_CPU2308-V0100         
           VMS73_DCL-V0300             VMS73_DDTM-V0100            
           VMS73_DEBUG-V010            VMS73_DECW_XTERM-V0100      
           VMS73_DELETE-V0100          VMS73_DIR-V0100             
           VMS73_DRIVER-V0300          VMS73_F11X-V0100            
           VMS73_FIBRE_SCSI-V0500      VMS73_GRAPHICS-V0100        
           VMS73_IIDRIVER-V0100        VMS73_INIT-V0100            
           VMS73_IOGEN-V0100           VMS73_LAN-V0400             
           VMS73_LIBRTL-V0200          VMS73_LINKER-V0300          
           VMS73_MANAGE-V0200          
           VMS73_MIME-V0100            VMS73_MONTOR-V0100          
           VMS73_MSCP-V0100            VMS73_PPPD-V0200            
           VMS73_PTHREAD-V0300         VMS73_REGISTRY-V0100        
           VMS73_REM-V0100             VMS73_RMS-V0400             
           VMS73_RPC-V0100             VMS73_RTPAD-V0100           
           VMS73_SHADOWING-V0200       VMS73_SYS-V0500             
           VMS73_SYSINI-V0100          VMS73_SYSLOA-V0300          
           VMS73_TDF-V0100             VMS73_UPDATE-V0100          
           VMS73_XFC-V0300

         Following are the problems addressed by the above kits.  Note
         that the problems addressed by the VMS73_UPDATE-V0100 kit can
         be found in a separate file,
         [SYSHLP]VMS73_UPDATE-V0100_CVRLET.TXT.


6  PROBLEMS ADDRESSED IN VMS73_AMACRO-V0100 KIT


      o  The AMACRO compiler does not properly sign-extend the result of
         a  BITL  instruction.   If either of the operands to BITL comes
         from a quadword operation (like  EVAX_LDQ),  then  the  missing
         sign-extension  will  cause the BITL instruction to produce the
         wrong result.

         Images Affected:

          -  [SYSEXE]ALPHA_MACRO.EXE


      o  CMPW of values that are more than 32767  apart  will  give  the
         wrong result.

         Images Affected:

          -  [SYSEXE]ALPHA_MACRO.EXE


      o  AMACRO's floating point support macros do not correctly  handle
         double-precision floating point immediate operands require more
         than 7 digits of precision.

         Images Affected:

          -  [SYSLIB]STARLET.MLB



7  PROBLEMS ADDRESSED IN VMS73_APB-V0200 KIT


      o  The VMS73_APB-V0100 kit is not compatible with the newly
         released PCSI PRODUCT UNDO PATCH functionality.  This new PCSI
         functionality allows a user to uninstall a patch kit.  If a
         user was to install the VMS73_APB-V0100 patch kit using the new
         PROD INSTALL /SAVE_RECOVERY_DATA option and then attempted to
         uninstall the kit using the PRODUCT UNDO PATCH feature, the
         system could be left in an unbootable state.  This new
         VMS73_APB-V0200 kit re-issues the VMS73_APB-V0100 kit with
         updated installation files that allow safe removal of the kit.

         Note that this is the only change in this new APB patch kit.
         There are no new APB changes in the VMS73_APB-V0200 kit.  If
         you have already installed the VMS73_APB-V0100 patch kit, there
         is no need to install the VMS73_APB-V0200 kit.

         Images Affected:

          -  POSTUNDO.COM


8  PROBLEMS ADDRESSED IN VMS73_APB-V0100 KIT


      o  The Compaq Professional Workstation XP1000  cannot  boot  as  a
         satellite  node  into  a  cluster.   Instead, they hang/timeout
         waiting for the disk server.

         Images Affected:

          -  [SYSEXE]APB.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


      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:

          -  [SYSEXE]APB.EXE



9  PROBLEMS ADDRESSED IN VMS73_BACKUP-V0200 KIT


      o  After a BACKUP/LIST of a save-set on a disk mounted /FOREIGN,
         further access to the disk fails with a %SYSTEM-F-VOLINV error.
         The disk is inaccessible until it is dismounted, or until
         BACKUP is used to create another save-set on it.

         Images Affected:

          -  [SYSLIB]BACKUPSHR.EXE


      o  When using BACKUP to copy a directory tree, if the first file
         copied into the destination parent directory is a directory
         file which has a directory limit, then a directory version
         limit is improperly placed on the destination parent directory.

         Images Affected:

          -  [SYSLIB]BACKUPSHR.EXE


      o  If an application repetitively makes calls to backup$start
         (greater than, say, 35,000) a %backup-f-insbufspace,
         insufficient buffer space error is received.

         Images Affected:

          -  [SYSEXE}BACKUP.EXE

          -  [SYSLIB]BACKUPSHR.EXE


      o  If ODS-5 files are converted to ODS-2, the following problems
         can occur:

          o  A BACKUP/IMAGE of the disk with the /NOALIAS switch will
             not pick up the directory structure of any of the files and
             directories which were created during the time when the
             disk was an ODS-5 structure.  I.E., file and directories
             would be listed in a log file such as:

             %BACKUP-S-COPIED, copied DKA100:[]ODS5TEST.DIR
             %BACKUP-S-COPIED, copied DKA100:[]50AIPECO1NOTES.TXT
             %BACKUP-S-COPIED, copied DKA100:[]COMPAQ.TXT
             %BACKUP-S-COPIED, copied DKA100:[]DECEVENT_VMS_VAX.TXT
             %BACKUP-S-COPIED, copied DKA100:[]ESCALFMC.TXT
             %BACKUP-S-COPIED, copied DKA100:[]FATDIR.TXT
             %BACKUP-S-COPIED, copied DKA100:[]FATDRIVE.TXT


          o  When trying to add ACL's to previously created ODS-5 files,
             the following error occurs:

             %SET-I-NOALIAS, $11$DUA431:[FMCDBS]SDBXD1.JIM;1 is an alias
             entry; file not modified.


          o  Previously created ODS-5 directories with files still in
             them can be deleted with no error occurring.

          o  An ANALYZE/DISK will report the following error on
             previously created ODS-5 files which have been deleted
             after the disk was converted.

                  %ANALDISK-W-LOSTHEADER, file (18,1,1) JP.TXT
                  not found in a directory



         Images Affected:

          -  [SYSLIB]BACKUPSHR.EXE


      o  When BACKUP tries to save a shelved file, the QIO does not
         return and both BACKUP and HSM hang.  Also, when using XABITM
         to tell RMS that no caching via the XAB$_CACHING_ATTRIBUTE and
         XAB$_CACHING_OPTIONS items was done, HSM does not work
         correctly if the order was XABITM -> XABPRO

         Images Affected:

          -  [SYSEXE]BACKUP.EXE

          -  [SYSLIB]BACKUPSHR.EXE


      o  Incremental restores of or to an ODS-5 disk may get the
         following error sequence:

            %BACKUP-E-INCENTERR, error creating directory entry, etc...
            -SYSTEM-W-DUPFILENAME, duplicate file name
            %RMS-F-SYN, file specification syntax error


         Images Affected:

          -  [SYSEXE]BACKUP.EXE

          -  [SYSLIB]BACKUPSHR.EXE


      o  During an image save, BACKUP scans alias directories causing
         multiple copies of the primary files to be saved.  This
         increases the time to do the image save and the size of the
         saveset.

         Images Affected:

          -  [SYSEXE]BACKUP.EXE

          -  [SYSLIB]BACKUPSHR.EXE


      o  When multiple input specifiers are entered on the command line
         and wildcards are used for all file name parameters except the
         version (e.g.  *.*;), it is possible that all files could be
         saved/copied instead of just the latest version.

         Images Affected:

          -  [SYSEXE]BACKUP.EXE

          -  [SYSLIB]BACKUPSHR.EXE


      o  After an image backup, if the disk is re-mounted the following
         error may occur:

            %MOUNT-F-BADCHKSUM, bad file header checksum

         This can especially occur if the disk is mounted as a shadowset
         member.

         Images Affected:

          -  [SYSLIB]BACKUPSHR.EXE


      o  Customers running BACKUPs to tape drives that support Fast Skip
         positioning commands (characteristic of most directly connected
         DLT tape drives), and who are running MME applications, such as
         MTI's MMSUBSYS, may experience problems restoring subsequent
         volumes of a multi-tape backup.

         If tape labels are provided on the BACKUP command line for each
         of the continuation tapes, then the continuation tapes are
         created correctly.  However, if a 'scratch' tape is used, the
         continuation tape will be created with an incorrect HDR1
         record, rendering it unsuitable for future restore operations.

         No errors or warning messages will be displayed during tape
         creation, but on restore, the following error will be seen:

              %BACKUP-I-WRONGVOL, ALPHA3$MKD0:[000000]SY2_IMG.; is not the
              next volume in the set


         Images Affected:

          -  [SYSLIB]BACKUPSHR.EXE


      o  A BACKUP/XQP/IGNORE=INTERLOCK command could result in
         intermittent READATTR/NOSUCHFILE errors.

         When using a /IGNORE=INTERLOCK switch with BACKUP, files are
         accessed with NOLOCK since the use of the qualifier implies
         target files will be open.  A read operation with NOLOCK access
         (which causes the windows to be created/completed) will force
         the XQP to re-build the FCB chain.  In order to do so, the
         extension FCB chain is deleted and then rebuilt.  If, at the
         same time, another process comes along with a read attributes
         call, the XQP will find that the extension FCB chain is missing
         and not find the extension FCB for the header.  The XQP assumes
         that the caller is trying to get to the extension header
         directly and returns a NOSUCHFILE error.  There is nothing that
         the XQP can do in this case.  Another process is forcing the
         FCB chain to be rebuilt and because of the nolock access, the
         XQP cannot trust the chain.

         BACKUP attempts recovery (retry) from a READATTR error, when a
         "no such file" error is returned from the XQP when reading an
         extension header, with open, fragmented files (/IGN=INTERLOCK
         is used).

         The fix is to retry the same extension header 3 times.  If any
         of those access attempts are successful, continue to move
         forward through the file while logging the number of attempts.
         If the retry count is exhausted the file is no longer
         considered a target and the READATTR/NOSUCHFILE error will be
         reported.  A new message has been added that reports the retry
         count.

         Following are a few examples of possible message sequences:

          o  Success example 1:  Recovered from the first and only
             error.

             %BACKUP-W-READATTRRETRY, 1 READATTR error occurred reading
             $4$DKA310:[READATTR]1XQPXR_FRAGMENT.DAT;1


          o  Success example 2:  17 retries to save the file, though it
             was saved successfully.

             %BACKUP-W-READATTRRETRY, 17 READATTR errors occurred reading
             $4$DKA310:[READATTR]1XQPXR_FRAGMENT.DAT;1


          o  Failure, example 1:  A failing sequence where no successful
             retries occurred before eventually failing on the same
             extheader 3 times.

             %BACKUP-E-READATTR, error reading attributes for
             $4$DKA310:[READATTR]1XQPXR_FRAGMENT.DAT;1
             -SYSTEM-W-NOSUCHFILE, no such file
             %BACKUP-W-READATTRRETRY, 1 READATTR error occurred reading
             $4$DKA310:[READATTR]1XQPXR_FRAGMENT.DAT;1


          o  Failure Example 2:  A failing sequence of 3 successful
             retries while moving forward through the file on different
             EXTHDRS, but eventually, unable to recover from the fourth
             READATTR detected.

             %BACKUP-E-READATTR, error reading attributes for
             $4$DKA310:[READATTR]2XQPXR_FRAGMENT.DAT;1
             -SYSTEM-W-NOSUCHFILE, no such file
             %BACKUP-W-READATTRRETRY, 4 READATTR errors occurred reading
             $4$DKA310:[READATTR]2XQPXR_FRAGMENT.DAT;1


         The larger th size, more fragmented and interactive the open
         file, the lesser the chance of success.  Use of
         /IGNORE=INTERLOCK implies open files are to be processed.  If
         messages for files are paired (both READATTR/READATTRRETRY are
         reported) then the file did not get saved completely.  Success
         is a READATTRRETRY message only.

         Images Affected:

          -  [SYSEXE]BACKUP.EXE

          -  [SYSLIB]BACKUPSHR.EXE


      o  BACKUP may fail with BACKUP-F-GETCHN/SYSTEM-I-IVIDENT error
         while performing a /IMAGE operation on a disk that is mounted
         /FOREIGN.  For example:

         SYSTEM>BACKUP/IMAGE/IGN=NOBACK DR8015 DR8016
         %BACKUP-F-GETCHN, error getting device characteristics for
         $1$DGA8016:
         -SYSTEM-F-IVIDENT, invalid identifier format


         Images Affected:

          -  [SYSEXE]BACKUP.EXE

          -  [SYSLIB]BACKUPSHR.EXE


      o  A BACKUP-F-CLUSTER error message can be received during a
         BACKUP/IMAGE/NOINIT operation.  Particularly after
         pre-initializing a large output device with a small cluster
         value and a large/max header/ number of files.

         Images Affected:

          -  [SYSEXE]BACKUP.EXE

          -  [SYSLIB]BACKUPSHR.EXE




10  PROBLEMS ADDRESSED IN VMS73_BACKUP-V0100 KIT


      o  BACKUP ignores files with ^00 in the filename

         Images Affected:

          -  [SYSEXE]BACKUP.EXE

          -  [SYSLIB]BACKUPSHR.EXE


      o  When BACKUP operations are done on a system with many resources
         and where either the authorized privileges or SYSGEN PQL values
         are very large, an ACCVIO could occur.

         Images Affected:

          -  [SYSEXE]BACKUP.EXE

          -  [SYSLIB]BACKUPSHR.EXE


      o  BACKUP fails  when  the  input  saveset  is  referenced  via  a
         searchlist.  For example:

         $ DIR VDE$SYSTEM:*.BCK

         Directory SYS$COMMON:[VDE]

         VDE$UPLOAD.BCK;1

         Total of 1 file.

         $ BACKUP VDE$SYSTEM:VDE$UPLOAD.BCK/SAVE/LIST

         Listing of save set(s)

         %BACKUP-F-OPENIN, error opening
         CLU$COMMON:[VDE.ALP_IMAGES]VDE$UPLOAD.BCK; as input
         -RMS-E-FNF, file not found


         Images Affected:

          -  [SYSEXE]BACKUP.EXE

          -  [SYSLIB]BACKUPSHR.EXE


      o  BACKUP fails  with  a  %BACKUP-E-POSITERR,  -SYSTEM-F-ILLIOFUNC
         error combination with RMT or INFOSERVER remotely accessed tape
         devices.  Particularly when only a /LIST and no  /DENSITY/MEDIA
         qualifiers are supplied in the BACKUP command line.

         Images Affected:

          -  [SYSEXE]BACKUP.EXE

          -  [SYSLIB]BACKUPSHR.EXE




11  PROBLEMS ADDRESSED IN VMS73_CLIUTL-V0200 KIT


      o  A SHOW SYS/PROCESS/STATE=RWxxx command  will  ACCVIO  if  RWINS
         processes are present on the system.

         $ SHOW SYS/PROCESS/STATE=RWINS

         %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
         address=0000000004F2
         2A58, PC=0000000000041E84, PS=0000001B


         Improperly handled condition, image exit forced.
         Signal arguments: Number = 0000000000000005
         Name = 000000000000000C
         0000000000000000
         0000000004F22A58
         0000000000041E84
         000000000000001B


         Images Affected:

          -  [SYSEXE]SHOW.EXE


      o  A SHOW MEM/CACH=VOLU command results in a LIB-E-BADBLOSIZ error
         if  TOPQIO or TOPHITRATE are selected and there are no files to
         display.

         $ SHOW MEM/CACH=(VOLU=$4$DKA400,TOPQIO)
           System Memory Resources on  7-APR-2002 16:51:07.32

         Extended File Cache Top QIO File Statistics:
         %LIB-E-BADBLOSIZ, bad block size


         Images Affected:

          -  [SYSEXE]SHOW.EXE


      o  On a system with many disks, a SHOW DEVICE/FULL command returns
         a  %SYSTEM-F-BADPARAM  error after displaying information about
         some of the disks.

         Images Affected:

          -  [SYSEXE]SHOW.EXE


      o  When  a  $SHOW  DEV  or  $SHOW  DEV  D  command  is  issued   a
         LIB-F-BADBLOADR  error  is returned.  This error is mainly seen
         when the SHOW command  is  performed  on  a  system  with  many
         multipath devices or volume sets.

         Images Affected:

          -  [SYSEXE]SHOW.EXE


      o  Users with SECURITY privilege (and no others) get a  SS$_NOPRIV
         error when performing $ SHOW INTRUSION or $ DELETE/INTRUSION.

         Images Affected:

          -  [SYSEXE]CIA.EXE


      o  SHOW CLUSTER/OUTPUT and SHOW CLUSTER/CONTINUOUS  commands  fail
         to properly write the output file if:

          o  There are a large numbers  of  nodes  (OpenVMS  and/or  HSx
             nodes)

          o  The display is less than 132 characters wide.

         Instead, the output is truncated after  the  first  page,  even
         though additional nodes should be displayed on the second page.

         Images Affected:

          -  [SYSEXE]SHWCLSTR.EXE


      o  When doing a  SHOW  PROCESS/ID=xxxx  command,  if  the  process
         resides  on  a VAX cluster member, a SYSTEM-F-INCOMPAT error is
         displayed.

         Images Affected:

          -  [SYSEXE]SHOW.EXE




12  PROBLEMS ADDRESSED IN VMS73_CLUSTER-V0200 KIT


      o  The VMS73_CLUSTER-V0100 kit  erroneously  referred  to  OpenVMS
         versions  V7.3R and V7.2-1R rather than the correct versions of
         V7.3 and V7.2-1.  This kit  corrects  that  information.   Note
         that  this kit is a documentation correction only.  If you have
         installed the VMS73_CLUSTER-V0100 ECO kit, you do not  need  to
         install the VMS73_CLUSTER-V0200 ECO kit.



13  PROBLEMS ADDRESSED IN VMS73_CLUSTER-V0100 KIT


      o  After upgrading from V7.2-1 to V7.3 a system can crash  with  a
         PROCGONE  bugcheck  during  boot.   R0  in  the  bugcheck would
         contain the error 1C04A, %RMS-E-DNF, directory not found.   The
         boot  process  is  looking  for  the  LANACP.EXE  image  in the
         non-existent directory DSA0:[SYSEXE].

         Crashdump Summary Information
         -----------------------------
         Bugcheck Type:     PROCGONE, Process not in system
         VMS Version:       V7.3
         Current Process:   LANACP
         Current Image:     
         Failing PC:        FFFFFFFF.8025CB20 EXE$EXIT_INT_C+001E0
         Failing PS:        18000000.00000001
         Module:            IMAGE_MANAGEMENT  (Link Date/Time:
                            17-MAR-2001 03:27:48.69)
         Offset:            0000EB20


         Images Affected:

          -  [SYSEXE]SYSINIT.EXE


      o  System does not start up, because there are not enough votes to
         start the cluster when the quorum disk is not found.

         Images Affected:

          -  [SYSEXE]SYSINIT.EXE

          -  [SYSEXE]STACONFIG.EXE

          -  [SYSEXE]CONFIGURE.EXE

          -  [SYS$STARTUP]VMS$INITIAL-050_CONFIGURE.COM




14  PROBLEMS ADDRESSED IN VMS73_CPU2308-V0100 KIT


      o  When  a  670  machine  check  (Processor  Uncorrectable  Error)
         occurs,  a System Error Frame Subpacket is erroneously appended
         to the machine check frame in the error log file.

         Images Affected:

          -  [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE


      o  When a GS series system takes a 660 machine check crash, and  a
         galaxy  remote  machine check occurs when the node is rebooting
         from the 660 machine check, the more useful machine check  dump
         is overwritten by the galaxy remote machine check dump.

         Images Affected:

          -  [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE


      o  Kernal Stack Not Valid Halt

         Images Affected:

          -  [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE


      o  After logging a DTAG error, the user  may  see  recurring  DTAG
         hardware errors reported.

         Images Affected:

          -  [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE




15  PROBLEMS ADDRESSED IN VMS73_DCL-V0300 KIT


      o  When unprocessed record lines are encountered in an input
         command file, DCL overwrites image failure status with the
         warning DCL-W-SKPDAT.  The overwrite of the status should only
         happen when images exited with a successful status.

         Images Affected:

          -  [SYSEXE]DCL.EXE


      o  A file created by DCL will erroneously inherit the file
         extension quantity value from a previously opened file.  For
         example:

         $ DIR/FULL LOGIN.COM
                   .
                   .
                   .
         File attributes:    Allocation: 18, Extend: 5000

         ** Note that LOGIN.COM has DEQ  set to 5000

         $ OPEN/READ/SHARE FILE LOGIN.COM
         $ CLOSE FILE
         $
         $ @tt/out=out.txt
         _$ put something in file
         %DCL-W-IVVERB, unrecognized command verb -
         check validity and spelling \PUT\
         _$  Exit
         $
         $ DIR/FULL OUT.TXT

         Directory $2$DKB0:[TEST]

         OUT.TXT;1                     File ID:  (8282,1,0)
         Size:            1/5004       Owner:    [SYSTEM]
         Created:    21-AUG-2002 10:35:50.40
         Revised:    21-AUG-2002 10:35:57.94 (1)
         File attributes:    Allocation: 5004, Extend: 5000,
                             Global buffer count: 0
         Client attributes:  None
         Total of 1 file, 1/5004 blocks.


         Images Affected:

          -  [SYSEXE]DCL.EXE


      o  If an upcall enabled image's execution is interrupted with ^y,
         and execution of a DCL command procedure is entered as the
         first command at the ^Y DCL prompt, an access violation occurs.
         For example:

         ^y
         $ @TEST
         %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
         address=0000000000000004, PC=FFFFFFFF80B4FBEC, PS=0000001B
         ...


         Images Affected:

          -  [SYSEXE]DCL.EXE


      o  When running the XQP exercisor test, the test procedure
         displays the input prompt instead of executing a command passed
         on the command line invoking the image.  For example:

          $ xqpxr do 'p1' [xqpxr] xqpxr_test.dat -         
            /numf=1-
            /sizf=500-
            /rndf-
            /exte=14-
            /rnde-
            /plac=vbn-
            /dirc=1-
            /dura=00:03:00.0-
            /adda-
            /acec=4-
            /rnda-
            /oper=(build,randio)-
            /iotc=1
           XQPXR>


         Images Affected:

          -  [SYSEXE]DCL.EXE


      o  The following call to F$GETSYI, on a system that does not
         support partitioning, will crash the process:


         $ write sys$output f$getsyi("cpu_failover")

          Improperly handled condition, bad stack or no handler 
          specified.
          Signal arguments:   Number = 0000000000000005
                              Name   = 000000000000000C
                                       0000000000000004
                                       000000007FFAE000
                                       000000007FFAE000
                                       0000000000000012
                                 .
                                 .
                                 .
                                 .
         %DCL-S-RETURNED, control returned to process GUY
         %SYSTEM-F-ACCVIO, access violation, reason mask=00,
         virtual address=000000000000000C, PC=000000000000000C,
         PS=7FFAC4C3

         Images Affected:

          -  [SYSEXE]DCL.EXE




16  PROBLEMS ADDRESSED IN VMS73_DCL-V0200 KIT


      o  When the DCL PIPE command is issued in  batch  mode,  it  skips
         over  the DCL statement immediately following the PIPE command.
         This occurs when the ";" separator is  followed  by  a  command
         sequence containing an "@filespec" command.

         Images Affected:

          -  [SYSEXE]DCL.EXE


      o  Running the pipe command in a loop may result  in  one  of  the
         following problems:

          o  DOUBLDEALO user mode bugchecks

          o  ACCVIO in various symbol manipulation routines

          o  SYMOVF error message


         Images Affected:

          -  [SYSEXE]DCL.EXE


      o  A process that has spawned several jobs, using a combination of
         SPAWN/WAIT  and SPAWN/NOWAIT commands, stays in state HIB after
         all the spawned subprocesses have completed.

         Images Affected:

          -  [SYSEXE]DCL.EXE




17  PROBLEMS ADDRESSED IN VMS73_DCL-V0100 KIT


      o  When an image run by a  DCL  procedure  includes  a  line  that
         generates  a  skipped  data warning immediately after the image
         line, the status from the image run is returned in R0  and  the
         warning is not caught by DCL.

         Images Affected:

          -  [SYSEXE]DCL.EXE


      o  Attempting to execute the TCPIP$CONFIG.COM procedure results in
         an ACCVIO abnormally terminating the process.

         Images Affected:

          -  [SYSEXE]DCL.EXE


      o  The PIPE command may cause a SYSTEM-F-MBTOOSML  error  message.
         This  is caused by the command overflowing the mailbox handling
         the  data  between  the  subprocesses.   Raising   the   SYSGEN
         parameter DEFMBXMXMSG has no effect.

         Images Affected:

          -  [SYSEXE]DCL.EXE


      o  Support for the /PASSIVE qualifier has been added.

         /PASSIVE

             /PASSIVE=option

             Controls whether the FTP client or server initiates the
             data connection.  If this qualifier is not specified,
             the Internet Protocol appropriate value is used (OFF for
             IPv4, ON for IPv6).
             
             The underlying TCP/IP Networking product must recognize
             this qualifier and must support FTP passive in order for
             this qualifier to have an effect.

             Options:

             OFF      The FTP server initiates the data connection.

             ON       The FTP client initiates the data connection.

                      This is often used where a firewall between 
                      the FTP client and server prevents the server 
                      from making an outbound connection.

                      ON is the default value if only /PASSIVE is
                      specified.

         Images Affected:

          -  [CLD]COPY.CLD

          -  [CLD]DIRECTORY.CLD




18  PROBLEMS ADDRESSED IN VMS73_DDTM-V0100 KIT


      o  

          o  INSF_NONPAGED, Insufficient nonpaged pool system crashes in
             a variety of (victim) images because most of non-paged pool
             is consumed by IPC buffers allocated by DECdtm.  These IPBs
             consistently have the following characteristics:

              o  IPB$W_SIZE contains 140

              o  IPB$B_EVENT contains 03,(DATA)

              o  IPB$L_SEND_LEN     contains      4C      (value      of
                 lm$k_max_write_size)

              o  IPB$L_REPLY_LEN contains A00 (value of lmsvmsg$k_bln)

              o  IPB$L_FLAGS contains 421,

              o  IPB$L_STATUS contains 01,

              o  IPB$L_ALIAS contains the address of an LM_LCB structure
                 which is also on the free list


          o  The IPC trace log shows a repeat pattern:

             START:

              o  IPC$_LINK

              o  EV_LINK

              o  IPC$_ACCEPT

              o  EV_ACCEPT

              o  IPC$_GETBUF

             The IPB specified in the following two entries  is  one  of
             the  leaked buffers and does not appear in any of the other
             trace entries.

              o  IPC$_SEND

              o  EV_DATA

              o  EV_DATA

              o  IPC$_UNLINK

              o  EV_DISC

              o  EV_DISC_COMP


             END:


              o  IPC$_RELBUF


          o  Accessing the DECdtm log file via LMCP shows this error:

               $ MCR LMCP LMCP> SHOW LOG SYSTEM$foobar.LM$JOURNAL

                %LMCP-E-VERS_MISMATCH, version mismatch for transaction
                log format - operation aborted



         Images Affected:

          -  [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE


      o  The system can crash  due  to  a  forced  DDTMBUG  bugcheck  in
         SYS$TRANSACTION_SERVICES.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     DDTMBUG, DDTM has detected an invalid
                            condition
         Failing PC:        FFFFFFFF.801D3AA0
                           SYS$TRANSACTION_SERVICES+0BAA0
         Failing PS:        20000000.00000203
         Module:            SYS$TRANSACTION_SERVICES
                           (Link Date/Time: = 4-MAY-2001 18:05:37.03)
         Offset:            0000BAA0


         Images Affected:

          -  [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE


      o  Some DECdtm initialization does not occur.

         Images Affected:

          -  [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE


      o  When upgrading from V7.2 to V7.3 and above customers  will  see
         this  error  with  DDTM  journal  files  containing transaction
         records; the files are neither empty nor corrupted.

         Directory of SYS$COMMON:[SYSMGR]

         SYS$COMMON:[SYSMGR]SYSTEM$BLAH.LM$JOURNAL;1
         End of file block 4002 / Allocated 4005
         Log Version 1.0
         Transaction log UID:   CA9A3F01-0F93-11D4-95AD-08002B27DF8E
         Penultimate Checkpoint: 0000000BE639 0039
         Last Checkpoint:        0000000BF02E 002E
         %SYSTEM-W-ENDOFFILE, end of file
         %LMCP-W-FILE_EMPTY, transaction log contains no valid record 
                             data
         %LIB-F-BADBLOADR, bad block address


         This does not occur if the journal file  is  newly  created  on
         V7.3 and is empty, because there is no "Last Checkpoint".

         Images Affected:

          -  [SYSEXE]LMCP.EXE




19  PROBLEMS ADDRESSED IN VMS73_DEBUG-V0100 KIT


      o  The Debugger can hang when attempting to view the sources for a
         large application.  The user may also see the following error
         message:

           X Toolkit Warning:
           Name: cnt_generic_label
           Class: XmLabel

           Invalid XmNlabelString - must be a compound string


         Images Affected:

          -  [SYSLIB]DEBUGSHR.EXE




20  PROBLEMS ADDRESSED IN VMS73_DECW_XTERM-V0100 KIT


      o  Several FONTS (such as Hebrew) cause a process crash trying  to
         start  the  FONT_DAEMON  (process DECW$FD).  Users will see the
         following error message:

         %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
         address=000000B9CA8`, PC=000000000003A328, PS=0000001B


         Images Affected:

          -  [SYSEXE]DECW$DWT_FONT_DAEMON.EXE




21  PROBLEMS ADDRESSED IN VMS73_DELETE-V0100 KIT


      o  A   PURGE/LOG   ::[...]*.*   command   results    in    a
         SYSTEM-F-ACCVIO.

         SYSTEM-F-ACCVIO, Access violation, Reason mask=00,
         virtual address=00000000304c4154, PC=FFFFFFFF804C1CDC, 
         PS=0000001B


         Images Affected:

          -  [SYSEXE]DELETE.EXE




22  PROBLEMS ADDRESSED IN VMS73_DIR-V0100 KIT


      o  When a DIRECTORY/FULL command specifies a remote filespec for
         an indexed file, (for example,
         0""::SYS$SYSTEM:SYSUAF.TEMPLATE), the Prolog, number of keys
         and number of areas fields are missing.  For example:

         File organization: Indexed


         In contrast, when the file is displayed locally, the following
         line is displayed by a DIRECTORY/FULL comand:

         File organization: Indexed, Prolog: 3, Using 4 keys in 3 areas


         Images Affected:

          -  [SYSEXE]DIRECTORY.EXE


      o  For network operations, the directory command display is
         grouped by the first letter if "_" is specified before the node
         name/address, and all files are in the same directory.  That
         first letter is missing from all the file names and appears at
         the end of the title line for the directory.  For example:

         ALPHAI> dir _63.775"user password"::

         Directory 63.775"user password"::$1$DKB200:[GAYATRI]L


         OGIN.COM;11      1/4         9-DEC-1998 14:46:52.45 (RWED,RWED,RE,)
         OGIN.LOG;122     2/4        10-DEC-1998 15:48:11.49 (RWED,RWED,RE,)
         OGIN.LOG;111     2/4        10-DEC-1998 15:47:39.80 (RWED,RWED,RE,)
         OGIN.LOG;100     2/4         9-DEC-1998 15:12:52.29 (RWED,RWED,RE,)
         OGIN.LOG;99      1/4         9-DEC-1998 15:11:51.42 (RWED,RWED,RE,)
         OGIN.LOG;88      2/4         9-DEC-1998 15:08:20.12 (RWED,RWED,RE,)
         OGIN.LOG;77      1/4         9-DEC-1998 15:06:56.59 (RWED,RWED,RE,)
         OGIN.LOG;66      1/4         9-DEC-1998 15:05:37.43 (RWED,RWED,RE,)
         OGIN.LOG;55      1/4         9-DEC-1998 15:01:49.56 (RWED,RWED,RE,)
         OGIN.LOG;44      1/4         9-DEC-1998 15:00:28.54 (RWED,RWED,RE,)
         OGIN.LOG;33      1/4         9-DEC-1998 14:59:07.54 (RWED,RWED,RE,)
         OGIN.LOG;22      2/4         9-DEC-1998 14:53:26.12 (RWED,RWED,RE,)
         OGIN.LOG;11      2/4         9-DEC-1998 14:53:10.96 (RWED,RWED,RE,)

                 Total of 13 files, 19/52 blocks.

         Directory 63.775"user password"::$1$DKB200:[GAYATRI]X

         .LOG;11          2/4        31-MAR-1999 14:25:12.91 (RWED,RWED,RE,)

                 Total of 1 file, 2/4 blocks.


         Images Affected:

          -  [SYSEXE]DIRECTORY.EXE



23  PROBLEMS ADDRESSED IN VMS73_DRIVER-V0300 KIT


      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$TUDRIVER.EXE


      o  An ACCVIO occurs when using PREFER with a /FORCE qualifier.

         For example:

         $ PREFER $1$DUA15: /HOST=HSC000 /FORCE
         %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
         address=0000000C,
         PC =0000000C, PSL=0000000F


         If the command is executed without  the  /FORCE  qualifier,  no
         ACCVIO occurs:

         $ PREFER $1$DUA15: /HOST=HSC000


         Images Affected:

          -  [SYS$LDR]SYS$DUDRIVER.EXE


      o  Fix a couple of minor problems with the display of trace data.

          o  Channels specified in the SHOW/SET TRACE  command  are  not
             saved  in  the correct spot in the management command.  The
             structure used to copy them was CHACT$ when it should  have
             been TRACEACT$.

          o  The output filename (for  /OUT=file)  was  not  initialized
             correctly,   in_file_name  was  being  cleared  instead  of
             out_file_name.


         Images Affected:

          -  [SYSEXE]SCACP.EXE


      o  When a multivolume backup is unable to span multiple tapes, the
         following error message occurs:

         %RMU-E-POSITERR, error positioning $3$MKA603:[000000]MAIN.RBF;
         -SYSTEM-F-IVDENS, invalid density


         Images Affected:

          -  [SYS$LDR]SYS$TUDRIVER.EXE


      o  The system may hang after a tape unit  does  a  failover  to  a
         second  controller.  Another symptom may be a CPUSPINWAIT crash
         on a SMP system.  The hang  occurs  at  routine  DUTU$MOVE_IODB
         when   a   chain   of   UCB's   is   followed,  via  the  field
         UCB$L_CDDB_LINK, while the field  points  to  the  UCB  itself.
         Normally the last field in the chain of UCB's should be zero.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     CPUSPINWAIT, CPU spinwait timer expired
         Current Process:   BATCH_1006249
         Current Image:     DSA1010:[RUN]GEM.EXE
         Failing PC:        FFFFFFFF.80088384    SMP$TIMEOUT_C+00064
         Failing PS:        18000000.00000803
         Module:            SYSTEM_SYNCHRONIZATION_MIN
                            (Link Date/Time:22-MAR-2001 01:01:40.01)
         Offset:            00000384


         Images Affected:

          -  [SYS$LDR]SYS$TUDRIVER.EXE

          -  [SYS$LDR]SYS$DUDRIVER.EXE


      o  SHOW CLUSTER and SDA SHOW CONNECTIONS can correctly  report  up
         to  8 SMCI ports.  The reason for this is that, PBDRIVER uses a
         multiport scheme to handle its connections.   In  other  words,
         UCB  unit  numbers are coupled with the GALAXY instance number,
         making unit numbers  greater  than  the  standard  ZERO  as  in
         traditional SCS port drivers.  SCS reports the port name in the
         PB field PB$T_LPORT_NAME (format PBx0) which is only 4 bytes in
         length.  In all cases, the unit number is set to zero.  This is
         incorrect for SMCI ports.

         Images Affected:

          -  [SYS$LDR]SYS$PBDRIVER.EXE


      o  In routine DU$INSERT_RESTARTQ, certain CDRPS (MVIRP, shadowing)
         were  being  posted  with DEVOFFLINE instead of being queued to
         the restart queue.  Many of these CDRPs had  mapping  registers
         active,  and  posting  them  unmapped  them while still active.
         This caused a variety of  symptoms,  such  as  IOMACHINECHECKS,
         unrecognized SCA messages and INCONSTATE errors.

         Images Affected:

          -  [SYS$LDR]SYS$DUDRIVER.EXE

          -  [SYS$LDR]SYS$TUDRIVER.EXE




24  PROBLEMS ADDRESSED IN VMS73_DRIVER-V0200 KIT


      o  When the CD-ROM is booted  on  an  ES40,  the  following  error
         message is returned after the initial boot messages:

         %SYSBOOT-I-GCTMINOR, GCT used with minor revision mismatch
         expected 00000005.00000001 - seen: 00000005.00000002

         %SYSBOOT-F-LDFAIL,unable to load SYS$BASE_IMAGE.EXE,status=00000054

         halted CPU = 0
         halt code = 5
         HALT instruction executed
         PC = 1d5e8
         boot failure


         Images Affected:

          -  [SYS$LDR]SYS$DQDRIVER.EXE


      o  When mounting an ATAPI device an ATA init_device_param  command
         attempts to set the disk geometry.  This command is illegal for
         ATAPI devices but it takes 15 seconds before the drive  reports
         the error.

         Images Affected:

          -  [SYS$LDR]SYS$DQDRIVER.EXE




25  PROBLEMS ADDRESSED IN VMS73_F11X-V0100 KIT


      o  A synchronization issue between RMS's read of  directory  files
         for  wildcard  operations  and concurrent XQP activity has been
         identified  and  corrected.   Prior  to  this  change,  it  was
         possible  that  RMS  could  obtain  an  inconsistent  view of a
         directory file when reading it into its internal  cache.   This
         could  result in spurious RMS-E-FNF (file not found) errors.  A
         synchronization mechanism has been implemented between the  XQP
         and  RMS  in  order  to  ensure  that  a  consistent  view of a
         directory is achieved.

         Images Affected:

          -  [SYS$LDR]F11BXQP.EXE


      o  

         The system can crash with a "MAPCNTZER, Attempted  to  generate
         zero length map pointer" bugcheck.

         Crashdump Summary:
         ------------------
         Bugcheck Type:     MAPCNTZER, Attempted to generate zero
                            length map pointer
         Current Process:   _TNA69:
         Current Image:     DSA0:[SYS0.SYSCOMMON.][SYSEXE]SYSGEN.EXE
         Failing PC:        FFFFFFFF.A89F6B98    MAKE_POINTER_C+00044
         Failing PS:        30000000.00000000
         Module:            F11BXQP
                            (Link Date/Time: 24-AUG-2000 07:20:45.47)
         Offset:            00026B98

         R3 = 00000000.00000000 <<< value of COUNT - ARG1: block count

         SDA> CLUE STACK

         Stack Frame:
         PV       00000000.7B009230  FFFFFFFF.A8A28390 MAKE_POINTER
         Entry Point                 FFFFFFFF.A89F6B54 MAKE_POINTER_C
                  00000000.7B009238  00000000.0090AE6C
         return PC 00000000.7B009240 FFFFFFFF.A89F1DBC EXTEND_C+00978
                                                       ^^^^^^^ caller
         saved R2      00000000.7B009248  FFFFFFFF.A8A275D0  EXTEND
         saved R3      00000000.7B009250  00000000.00000000
         saved R8      00000000.7B009258  00000000.00000000
         saved FP      00000000.7B009260  00000000.7B009270


         Images Affected:

          -  [SYS$LDR]F11BXQP.EXE


      o  On Multi-Path devices, a MONITOR DISK/ITEM=QUEUE_LENGTH command
         will show a high queue length.  It will stay high until reboot.
         The queue length on a switched path device, as seen  from  SDA,
         will show as negative.

         Images Affected:

          -  [SYS$LDR]F11BXQP.EXE




26  NEW FUNCTIONALITY ADDRESSED IN VMS73_FIBRE_SCSI-V0500 KIT


      o  This kit provides support for the  Emulex  LP9802  FibreChannel
         Adapter.

         Images Affected:

          -  [SYSEXE]SYS$CONFIG.DAT




27  PROBLEMS ADDRESSED IN VMS73_FIBRE_SCSI-V0500 KIT


      o  A BACKUP command from a client system to a TMSCP served SCSI
         tape may complete with success, but the resulting saveset
         cannot be read by BACKUP.

         $ INIT $7$MKC0: TEST0
         $ MOUNT/FOREIGN $7$MKC0:
         %MOUNT-I-MOUNTED, TEST0 mounted on_$7$MKC0: (UTRA41)
         $ BACKUP/LOG LOGIN.COM TP:TEST0/SAV
         %BACKUP-S-COPIED,copied USER1:[TEST]LOGIN.COM;1
         $ DISMOUNT/NOUNLOAD TP
         $ MOUNT/FOREIGN TP
         %MOUNT-I-MOUNTED, TEST0 mounted on _$7$MKC0: (UTRA41)
         $ BACKUP/LIST TP:
         Listing of save set(s)

         %BACKUP-F-LABELERR, error in tape label processing on
         $7$MKC0:[000000].; -SYSTEM-W-ENDOFFILE, end of file                


         Images Affected:

          -  [SYS$LDR]SYS$MKDRIVER.EXE


      o  If a fibre channel device is power cycled or disconnected from
         the fabric, OpenVMS may permanently lose access to the device.

         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE


      o  This kit provides a utility that will allow customers to update
         the firmware in an MSA1000 series Fibre SCSI raid controller.
         The utility can also do some diagnostics.

         Images Affected:

          -  [SYSHLP.UNSUPPORTED]MSA_UTIL.EXE


      o  During upgrade of fiber switches DSGGC-AA switch 8 EL from
         version 2.1.9m to 2.6.0c, a system can experience an INCONSTATE
         crash at SYS$FGEDRIVER+1096C in fg$resume_uctx routine:

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INCONSTATE, Inconsistent I/O data base
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.8037696C SYS$FGEDRIVER+1096C
         Failing PS:        00000000.00000804
         Module:            SYS$FGEDRIVER (Link Date/Time:
                            24-AUG-2001 00:13:27.27)
         Offset:            0001096C

         Failing Instruction:
         SYS$FGEDRIVER+1096C:   BUGCHK


         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE


      o  FibreChannel storage (DG) disks fail over to the MSCP path due
         to the local direct paths becoming permanently inaccessible.

         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE


      o  A system with an LP89802 can crash with the following error.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     MACHINECHK, Machine check while
                            in kernel mode
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.80011690
                            EXE$SYSTEM_CORRECTED_ERROR_C+00510
         Failing PS:        20000000.00001F04
         Module:            SYS$CPU_ROUTINES_270F
                            (Link Date/Time: 20-NOV-2002 15:11:40.36)
                           Offset:            00003690
         Failing Instruction:
         EXE$SYSTEM_CORRECTED_ERROR_C+00510:     BUGCHK

         Stack Pointers:
         KSP = FFFFFFFF.F0819C60   ESP = FFFFFFFF.F081B000
         SSP = FFFFFFFF.F0805000   USP = FFFFFFFF.F0805000

         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE


      o  FibreChannel storage fails to configure on boot.

         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE


      o  All accesses to a shadow disk return SS$_IVADDR errors after
         adding a member to the shadow set.

         Images Affected:

          -  [SYS$LDR]SYS$DKDRIVER.EXE


      o  DIR-E-TAPEPOSLOST errors when can occur when a DIRECTORY
         command is used on skip-filemark-capable tape drives.

         Images Affected:

          -  [SYS$LDR]SYS$MKDRIVER.EXE


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

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INCONSTATE, Inconsistent I/O data base
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.C8344B24 SYS$FGEDRIVER+12B24
         Failing PS:        10000000.00000804
         Module:            SYS$FGEDRIVER
                            (Link Date/Time: 28-MAR-2002 14:28:09.10)
         Offset:            00012B24


         Images Affected:

          -  [SYS$LDR]SYS$PGADRIVER.EXE


      o  A system can hang when backing up files to and SDLT with V35 or
         V46 firmware.

         Crashdump Summary:
         ------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.80047904
                            EXE_STD$QUEUE_FORK_C+00084
         Failing PS:        20000000.00001504
         Module:            SYSTEM_PRIMITIVES_MIN
         Offset:            0001B904


         Images Affected:

          -  [SYS$LDR]SYS$PKWDRIVER.EXE


      o  When restoring a multivolume saveset created with a command
         similar to the following BACKUP command:

         $ MOUNT/FOREIGN ALPHA3$MKD0:
         $ BACKUP/IMAGE SY2:ALPHA3$MKD0:SY2_IMG/save_set/EXACT_ORDER

         The restore operation fails because BACKUP is requesting and
         waiting for the wrong tape to be loaded.

         Images Affected:

          -  [SYS$LDR]SYS$MKDRIVER.EXE


      o  SYS$PKSDRIVER.EXE has the ability to re-initialize the KZPSA
         adapter when the the adapter indicates (via an ADAPTER
         MISCELLANEOUS interrupt) that its firmware has crashed.  Under
         certain circumstances, this re-initialization can fail and
         result in a system crash.  This is usually caused by a bad
         KZPSA module or other hardware.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.803D51FC SYS$PKSDRIVER+031FC
         Failing PS:        28000000.00000804
         Module:            SYS$PKSDRIVER (Link Date/Time:
                            17-MAR-2001 03:31:19.38)
         Offset:            000031FC

         Stack Pointers:
         KSP = FFFFFFFF.B0881A28   ESP = FFFFFFFF.B06E7000
         SSP = FFFFFFFF.B06D5000   USP = FFFFFFFF.B06D5000

         Failing Instruction:
         SYS$PKSDRIVER+031FC:    LDQ        R22,#X0010(R7)


         Images Affected:

          -  [SYS$LDR]SYS$PKSDRIVER.EXE


      o  The system loses connection to the SAN based quorum disk,
         causing the system to hang.  Most processes are in RWCAP state.

         Images Affected:

          -  [SYS$LDR]SYS$DKDRIVER.EXE


      o  If a fibre channel device is power cycled or disconnected from
         the fabric, OpenVMS may permanently lose access to the device.

         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE


      o  The system can crash with a fatal INCONSTATE bugcheck at
         SYS$PGADRIVER+0A7F4

         Crashdump Summary Information
         -----------------------------
         Bugcheck Type:     INCONSTATE, Inconsistent I/O
                            data base
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.804067F4
                            SYS$PGADRIVER+0A7F4
         Failing PS:        08000000.00000804
         Module:            SYS$PGADRIVER (Link Date/Time:
                            13-NOV-2002 10:01:38.48)
         Offset:            0000A7F4

         Stack Pointers:
         KSP = FFFFFFFF.8131B7C8   ESP = FFFFFFFF.93EB1000
         SSP = FFFFFFFF.93EAB000   USP = FFFFFFFF.93EAB000


         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE

          -  [SYS$LDR]SYS$PGADRIVER.EXE




28  PROBLEMS ADDRESSED IN VMS73_FIBRE_SCSI-V0400 KIT


      o  Poor tape performance can occur due to skip-by-filemark being
         disabled.  A $ SHOW DEVICE/FULL command will show fastskip
         support disabled.

         Images Affected:

          -  [SYS$LDR]SYS$MKDRIVER.EXE


      o  On write operations, RZ1EF-CB disk firmware reports an
         incorrect transferred byte count.  This results in undetected
         disk corruption.

         Images Affected:

          -  [SYS$LDR]SYS$DKDRIVER.EXE


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

         Crash Dump Summary
         ------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Image:     $1$DGA510:[PRG]LPARTREQ.EXE;6
         Failing PC:        FFFFFFFF.80405E60
                            SYS$PGADRIVER+0BE60
         Failing PS:        38000000.00000804
         Module:            SYS$PGADRIVER (Link Date/Time:
                            24-AUG-2001 00:12:20.64)
         Offset:            0000BE60


         Images Affected:

          -  [SYS$LDR]SYS$PGADRIVER.EXE


      o  When booting from a Fibre Channel disk, the system may
         experience a boot hang.

         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE


      o  The user will see unnecessary console messages from FGEDRIVER.

         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE


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

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   SRV1075_05_5
         Failing PC:        FFFFFFFF.80079514  EXE$KP_RESTART_C+00034
         Failing PS:        08000000.00000804
         Module:            SYSTEM_PRIMITIVES_MIN (Link Date/Time:
                            28-MAR-2002 14:22:47.68)
         Offset:            00047514

         Failing Instruction:
         EXE$KP_RESTART_C+00034:  LDL   R28,#X0010(R16)


         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE


      o  A system can crash with an INVEXCEPTN bugcheck

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above
                            ASTDEL
         Current Process:   STACONFIG
         Current Image:     STACONFIG.EXE
         Failing PC:        FFFFFFFF.80029F14
                            IOC$DEALLOC_CNT_RES_NOSYNC_C+00154
         Failing PS:        20000000.00000B04
         Module:            SYSTEM_PRIMITIVES_MIN (Link Date/Time:
                            28-MAR-2002 14:22:47.68)
         Offset:            00001F14


         Images Affected:

          -  [SYS$LDR]SYS$PKQDRIVER.EXE


      o  Disk drives that support the SCSI-3 SPC3 standard cannot be
         mounted.  When an attempt is made to mount such drives the
         error log records "invalid inquiry" messages.

         Images Affected:

          -  [SYS$LDR]SYS$DKDRIVER.EXE


      o  During a hard reset the system can experience 64-byte LAL
         corruption or an ACCVIO system crash.

         Images Affected:

          -  [SYS$LDR]SYS$DKDRIVER.EXE

          -  [SYS$LDR]SYS$MKDRIVER.EXE

          -  [SYS$LDR]SYS$GKDRIVER.EXE

          -  [SYS$LDR]SYS$PKRDRIVER.EXE

          -  [SYS$LDR]SYS$FGEDRIVER.EXE

          -  [SYS$LDR]SYS$PGADRIVER.EXE

          -  [SYSLIB]FC$SDA.EXE


      o  A boot/configuration hang can occur if an FGx device does not
         come online.

         Images Affected:

          -  [SYS$LDR]SYS$DKDRIVER.EXE

          -  [SYS$LDR]SYS$MKDRIVER.EXE

          -  [SYS$LDR]SYS$GKDRIVER.EXE

          -  [SYS$LDR]SYS$PKRDRIVER.EXE

          -  [SYS$LDR]SYS$FGEDRIVER.EXE

          -  [SYS$LDR]SYS$PGADRIVER.EXE

          -  [SYSLIB]FC$SDA.EXE


      o  During system boot, fibre channel storage devices may not be
         configured.

         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE

          -  [SYS$LDR]SYS$PGADRIVER.EXE

          -  [SYS$LDR]FC$GLOBALS.STB

          -  




29  PROBLEMS ADDRESSED IN VMS73_FIBRE_SCSI-V0300 KIT


      o  In the event of an unrecoverable SCSI error  occurring  on  the
         last  block of a transfer, a system with SCSI Fast Path enabled
         (the default) may see one disk block of corruption.  The  error
         will not appear in the error log, but the data will be bad.

         Images Affected:

          -  [SYS$LDR]SYS$PKQDRIVER.EXE


      o  When booting, a shadowed system disk can hang the cluster.

         Images Affected:

          -  [SYS$LDR]SYS$DKDRIVER.EXE


      o  The following recommended command line has been added  to  Help
         for FC$CP:

             $  MCR SYS$ETC:FC$CP FGA 3 1 8  ! Or FGB, etc.


         Images Affected:

          -  [SYSHLP.UNSUPPORTED]FC$CP.EXE


      o  The help output for FC$CP.EXE shows a filename of FC$IC.   This
         should be FC$CP.

         Images Affected:

          -  [SYSHLP.UNSUPPORTED]FC$CP.EXE


      o  The system can  crash  with  a  SSRVEXCEPT,  Unexpected  system
         service exception" bugcheck.
                           
         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     SSRVEXCEPT, Unexpected system service
                            exception
         CPU Type:          AlphaServer 2100 4/233
         Failing PC:        FFFFFFFF.801CB968
                            NSA$REFERENCE_RIGHTS_CHAIN_C+00008
         Failing PS:        10000000.00000201
         Module:            SECURITY
                            (Link Date/Time: 5-AUG-2001 01:12:10.86)
         Offset:            0000B968


         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE


      o  heavy IO load may cause multiple port errors on GS80, GS160  or
         GS320 systems with a KZPEA controller.  Disk mount verifies may
         also occur as a result of IO's timing out and  causing  a  SCSI
         bus   reset.   Excessive  IO  timeouts  could  result  to  data
         corruption.  The error log will show an Asynchronous  Device=20
         Attention  from  the  KZPEA  Adapter with a Type/Subtype string
         of=20 "0x0401".

         Images Affected:

          -  [SYS$LDR]SYS$PKADRIVER.EXE


      o  If a "BACKUP/MEDIA=COMPACTION" operation is in  progress  on  a
         Fibre  Channel  tape  on  one node, and another node enters the
         cluster,  that  booting  process  switches  the   BACKUP   into
         uncompressed mode.

         A related symptom does not require Fibre Channel or a  cluster.
         If  a  compressed  BACKUP  is  working and the tape experiences
         transient power failure, the drive may not return to compressed
         mode.

         Images Affected:

          -  [SYS$LDR]SYS$MKDRIVER


      o  When backing up files to SCSI QIC  tapes  (such  as  TZK11  and
         TZK10), the user may see the following error:

           SYSTEN-F-IVDENS, invalid density


         Images Affected:

          -  [SYS$LDR]SYS$MKDRIVER.EXE


      o  When a Fibre Channel disk is being brought back online, after a
         controller  failover,  the  user may see a variety of problems,
         ranging from process hangs, system hangs,  and  system  crashes
         with  a  variety  of bugchecks.  All systems using disks served
         from the affected HSG controllers will be affected.

         The nature of this problem is two fold.

          o  It completely shuts  down  the  HSG  controller.   Anything
             accessing  that  HSG  will  hang until their I/O times out.
             This will cause any number of failures from all  the  disks
             becoming unavailable.

          o  It consumes a number of resources on the systems.  A  crash
             will  result  from  what  ever  critical  resource runs out
             first.


         If the wrong equilibrium is reached, the systems can appear  to
         hang  forever.   It is possible, but not likely, that they will
         also recover with no intervention.

         Images Affected:

          -  [SYS$LDR]SYS$DKDRIVER.EXE


      o  The system can crash with an "INCONSTATE, Inconsistent I/O data
         base" bugcheck at SYS$FGEDRIVER+8C3C.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INCONSTATE,
                             Inconsistent I/O data base
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.802DAC3C SYS$FGEDRIVER+08C3C
         Failing PS:        18000000.00000804
         Module:            SYS$FGEDRIVER
                            (Link Date/Time:  5-DEC-2001 14:41:56.69)
         Offset:            00008C3C


         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE

          -  [SYSLIB]FC$SDA.EXE


      o  The system may hang on boot.  When this problem occurs the user
         loses  complete  control of the system.  A CRTL-P will not give
         the user the console prompt.  The only way to unhang the system
         is  via a power cycle.  When the system hangs, the last console
         output will look something like this:

         FGB0-I-OP_FW, operational firmware revision: CS3.a81A4 n
         l%FGeB0-I-OP_SLI_1 _FW-, SLI-1 firmware revision:  C1D3.81A4
         %FGB0-I-iOP_SLI_2_FW, nSLI-2 firmware revision: C2D3.81A4


         This  output  looks  odd  because   it   contains   interleaved
         characters from another driver.  This happens because the Fibre
         Channel Driver is writing to the console from  the  non-primary
         CPU.   FGE  Driver only writes this message to the console when
         bit 1 of USERD1 is set.  The user can avoid this  problem  with
         the old driver by not setting this bit in the SYSGEN variable.

         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE


      o  An INIT command, when used on SCSI tapes, can take a  1/2  hour
         or  more  to  quit  if  no  tape  is in the unit, or no tape is
         loading.

         Images Affected:

          -  [SYS$LDR]SYS$MKDRIVER.EXE


      o  After executing a HSV110 controller restart, the  system  loses
         connection to the disks on the HSV110.

         Images Affected:

          -  [SYS$LDR]SYS$FGEDRIVER.EXE


      o  Attempting to mount a TLZ09 gives a DRVERR error.

         Images Affected:

          -  [SYS$LDR]SYS$PKADRIVER.EXE


      o  A tape drive can log many errors between volume changes.

         Images Affected:

          -  [SYS$LDR]SYS$PKADRIVER.EXE


      o  This change generally enhances the handling  of  Fibre  Channel
         tape  bridges  and  in  particular  allows  SCSI  tapes  to  be
         configured behind a Network Storage Router.

         Images Affected:

          -  [SYSLIB]SMI$OBJSHR.EXE

          -  [SYSLIB]IOGEN$FIBRE_CONFIG.EXE




30  NEW FUNCTIONALITY ADDED IN THE VMS73_GRAPHICS-V0100 KIT

     30.1  PowerStorm 300/350 OpenVMS Graphics Support

     This document contains the release  notes  for  PowerStorm  300/350
     Graphics  Support  Version  2.0  for OpenVMS.  Specific information
     about this support can be found  in  the  P300_350_V2_README  file.
     This file is available in the following formats:

        File                         Format
        -------------------          ------------------
      
        P300_350_V2_README.TXT           Text
        P300_350_V2_README.PDF           Acrobat Reader  
        P300_350_V2_README.HTML          HTML
        P300_350_V2_README_CONTENTS.HTML HTML


     These files can be found at SYS$COMMON:[SYSHLP]


     30.2  New ELSA GLoria Synergy DDX image

     A new device dependent  X  server  image  is  provided  to  improve
     performance  on  EV6 (21264) based platforms containing ELSA GLoria
     Synergy     graphics      modules.       A      new      procedure,
     SYS$MANAGER:DECW$DEVICE_CONFIG_P2.COM,  is  executed  automatically
     during DECwindows startup.  The new procedure will, on  appropriate
     platforms,  define  a logical name that will redirect the server to
     use the new P2 device  dependent  X  code,  DECW$SERVER_DDX_P2.EXE.
     DECW$SERVER_DDX_GZ.EXE  will continue to be used on older platforms
     containing ELSA GLoria Synergy graphics modules.

     Image(s) Affected:

      -  [SYSLIB]DECW$SERVER_DDX_P2.EXE



31  GENERAL GRAPHICS PROBLEMS ADDRESSED IN THE VMS73_GRAPHICS-V0100 KIT


      o  Attempts to use the MIT-SHM Shared Memory Extension  fail  with
         the following error:

         X Error of failed request:  BadAccess (attempt to access private
         resource denied)
          Major opcode of failed request:  131 (MIT-SHM)
          Minor opcode of failed request:  1 (X_ShmAttach)
          Serial number of failed request:  11
          Current serial number in output stream:  12


         Images Affected:

          -  [SYSLIB]DECW$SERVER_DIX.EXE


      o  In OpenVMS  V7.3,  the  default  decwindows  transport  can  be
         specified          via         the         logical         name
         DECW$SETDISPLAY_DEFAULT_TRANSPORT.  However,  any  SET  DISPLAY
         commands   will   now  change  the  transport  to  the  default
         transport,  not  the  transport  previously   specified.    For
         example,

         $ show display

             Device:    WSA24:  [super]
             Node:      NODE1
             Transport: DECNET
             Server:    0
             Screen:    0

         $ show log DECW$SETDISPLAY_DEFAULT_TRANSPORT
            "DECW$SETDISPLAY_DEFAULT_TRANSPORT" = 
                                   "tcpip" (LNM$SYSTEM_TABLE)
         $ set displ/node=NODE2
         $ show display

             Device:    WSA24:  [super]
             Node:      NODE2
             Transport: tcpip
             Server:    0
             Screen:    0

         $ set display/screen=1
         $ show display

                Device:    WSA24:  [super]
                Node:      NODE1
                Transport: tcpip
                Server:    0
                Screen:    1

         The DECW$SETDISPLAY_DEFAULT_TRANSPORT default transport setting
         should only be used with the "$set display/create" qualifier.

         Images Affected:

          -  [SYSEXE]DECW$SETSHODIS.EXE


      o  Under some circumstances the DECwindows server can abort during
         startup.  The SYS$MANAGER:DECW$SERVER_0_ERROR.LOG file contains
         the error message "failed to initialize core devices".

         Images Affected:

          -  [SYSLIB]DECW$SERVER_DIX.EXE


      o  When drawing connected line segments with the line width set to
         1, the pixel at the join point between two line segments is not
         drawn in some cases.

         Images Affected:

          -  [SYSLIB]DECW$SERVER_DIX.EXE


      o  The system may crash with an SSRVEXCEPT or PGFIPLHI bugcheck on
         SMP   systems  when  terminating  client  processes  which  are
         connected using the local transport.

         Images Affected:

          -  [SYSLIB]DECW$TRANSPORT_LOCAL.EXE




32  ELSA PROBLEMS ADDRESSED IN THE VMS73_GRAPHICS-V0100 KIT


      o  When  an  X/Motif  application  issues  an  XDrawRectangle   or
         XDrawRectangles  request  with  a  negative  x  coordinate, the
         coordinate is incorrectly treated as a large  positive  number,
         resulting in spurious lines being drawn on the screen.

         Images Affected:

          -  [SYSLIB]DECW$SERVER_DDX_GZ.EXE


      o  If the DECwindows  server  is  started  with  the  pixel  depth
         (DECW$SERVER_PIXEL_DEPTH  logical  name)  set to 16, the server
         will crash.  This problem is seen with the ELSA Gloria  Synergy
         graphics  controller  (SN-PBXGK-BB),  only when using the older
         DECW$SERVER_DDX_GZ.EXE server image.

         Images Affected:

          -  [SYSLIB]DECW$SERVER_DDX_GZ.EXE


      o  When  using  the  ELSA  Gloria  Synergy   graphics   controller
         (SN-PBXGK-BB)  in  8  bit mode, the DECwindows server can crash
         when copying data from the screen to a pixmap.   This  is  most
         often  seen  when  performing  a  drag-and-drop operation.  The
         server can crash in several different  locations  depending  on
         the  timing  of  the  operation.   Another  symptom of the same
         problem is that the server can return spurious BadAlloc  errors
         (server resources exhausted).

         Images Affected:

          -  [SYSLIB]DECW$SERVER_DDX_GZ.EXE


      o  There are screen corruption problems when using the ELSA Gloria
         Synergy graphics controller (SN-PBXGK-BB):

          o  Spurious  horizontal  lines  are  displayed  when   drawing
             diagonal lines in 8 bit mode.

          o  When dragging a window on the screen with  "display  window
             contents  during  move" enabled and the screen backdrop set
             to Background, remnants of the window are  left  behind  on
             the backdrop.

         Images Affected:

          -  [SYSLIB]DECW$SERVER_DDX_P2.EXE


      o  When  using  the  ELSA  Gloria  Synergy   graphics   controller
         (SN-PBXGK-BB)  and  running  applications  which write a lot of
         data to the screen (such as rapidly scrolling text in a DECterm
         window), the system clock loses time.

         Images Affected:

          -  [SYS$LDR]SYS$GZDRIVER.EXE

          -  [SYS$LDR]SYS$GZVDRIVER.EXE


      o  User messages enabled  in  the  console  variable  BOOT_OSFLAGS
         (bit<17>  = 1) or on the console BOOT command line (e.g., >>> B
         -FL 0,20000) may cause a system crash  or  hang  while  booting
         with  an ELSA GLoria Synergy graphics controller (SN-PBXGK-BB),
         a JIB graphics controller (3X-DEPVD-AA), or a Trifecta graphics
         controller  (3X-DEPVZ-AA), especially on an SMP system with the
         console variable CONSOLE set to SERIAL.

         Images Affected:

          -  [SYS$LDR]SYS$GZDRIVER.EXE

          -  [SYS$LDR]SYS$GZVDRIVER.EXE


      o  Some monitors like the Compaq P75 & P700, fail  to  synchronize
         when  the Trifecta graphics controller (3X-DEPVZ-AA) or the JIB
         graphics controller (3X-DEPVD-AA) attempts to  put  the  screen
         into  standby  mode.   The  problem  manifests  itself with the
         screen going partly black; you may see a  partial  display  and
         the screen may blink and/or click.

         Images Affected:

          -  [SYS$LDR]SYS$GZDRIVER.EXE

          -  [SYS$LDR]SYS$GZVDRIVER.EXE




33  TGA2 (POWERSTORM 4D20/3D30) PROBLEMS IN THE VMS73_GRAPHICS-V0100 KIT


      o  When  booting  with  a  PowerStorm  3D30  (SN-PBXGB-AA)  or   a
         PowerStorm  4D20  (SN-PBXGB-CA)  graphics  controller  and  the
         SYSGEN parameter POOLCHECK enabled, the system may  crash  with
         an ACCVIO bugcheck.

         Images Affected:

          -  [SYS$LDR]SYS$GYCDRIVER.EXE




34  VX1 PROBLEMS ADDRESSED IN THE VMS73_GRAPHICS-V0100 KIT


      o  Screen corruption problems occur when using the  3Dlabs  Oxygen
         VX1 graphics controller (SN-PBXGF-AB):

          o  Video corruption is produced when  dragging  certain  icons
             around  the CDE desktop.  For example, after moving an icon
             from the Application Manager window to  the  desktop,  each
             subsequent  move  of  the  icon  on  the  desktop (backdrop
             required), leaves behind unintended pixels.

          o  

             With selected backdrops, video corruption is produced  when
             dragging objects around the CDE desktop.  For example, when
             dragging a  window  around  the  desktop  with  the  "GRAY"
             backdrop  selected,  remnants  of the left and right window
             borders are left behind on  the  desktop  in  the  form  of
             spurious vertical lines.


         Images Affected:

          -  [SYSLIB]DECW$SERVER_DDX_P3.EXE


      o  With the 3Dlabs Oxygen VX1  graphics  controller  (SN-PBXGF-AB)
         and either 8 or 16 bits per pixel selected, extra pixels may be
         drawn around the edges of objects.

         Images Affected:

          -  [SYSLIB]DECW$SERVER_DDX_P3.EXE


      o  With the 3Dlabs Oxygen VX1 graphics  controller  (SN-PBXGF-AB),
         the  Monitor  utility  may  show  excessive  time in "Interrupt
         State" when the screen saver is active.

         Images Affected:

          o  [SYS$LDR]SYS$GFDRIVER.EXE



35  P350 PROBLEMS ADDRESSED IN THE VMS73_GRAPHICS-V0100 KIT


      o  Occasionally  the  DECwindows  server  would  crash   when   an
         application  did extensive creation and deletion of 3D contexts
         interspersed  with  extensive  2D  drawing,  including   window
         creation and destruction.

         Images Affected:

          o  [SYSLIB]DECW$SERVER_DIX.EXE

          o  [SYSLIB]DECW$OPENGLPEERRI.EXE


      o  Running the Viewperf 6.1.2 MedMCAD test causes  an  application
         crash  when  using LOCAL transport or a server crash when using
         network transport.

         Images Affected:

          o  [SYSLIB]DECW$SERVER_RIDDGL.EXE

          o  [SYSLIB]DECW$OPENGLPEERRI.EXE


      o  When 3D contexts using  a  network  connection  are  destroyed,
         their  buffers  are not being properly deallocated.  The result
         is that, as applications create and delete  3D  contexts,  over
         time   the  server's  virtual  memory  undergoes  unconstrained
         growth.

         Images Affected:

          o  [SYSLIB]DECW$SERVER_DDX_GB.EXE


      o  Certain OpenGL  viewing  transformations  result  in  incorrect
         placement of primitives drawn.

         Images Affected:

          o  [SYSLIB]DECW$OPENGLPEERRI.EXE

          o  [SYSLIB]DECW$SERVER_RIDDGL.EXE


      o  The following problems are corrected:

          -  Repeated calls to glXMakeCurrent with a network  connection
             caused  a  slow but steady increase in the server's virtual
             memory space.

          -  Drawing polygons or triangles in  GL_LINE  mode  along  the
             bottom  or  right  edge  of the OpenGL viewport resulted in
             extra lines being drawn along the edge of the viewport.

          -  When a single OpenGL context was  used  to  render  to  two
             different  windows, sometimes the display in one window was
             corrupted.

          -  Stippled line  strips  with  sub-pixel  segments  were  not
             rendered by OpenGL.

          -  In some instances, the DECwindows server  would  hang  when
             rendering certain horizontal lines as filled rectangles.

          -  In some instances, the DECwindows server  would  hang  when
             rendering certain polygons.

          -  Drop-down menu items became blank when the mouse was  moved
             over a menu tear-off line.

          -  In some instances, pixel  corruption  would  occur  when  a
             window was moved over a highlighted item.


         Images Affected:

          o  [SYSLIB]DECW$OPENGLSHR_V11.EXE

          o  [SYSLIB]DECW$OPENGL_PROTOCOL_V11.EXE

          o  [SYSLIB]DECW$OPENGLPEERRI.EXE

          o  [SYSLIB]DECW$SERVER_DDX_GB.EXE

          o  [SYSLIB]DECW$SERVER_RIDDGL.EXE

          o  [SYSLIB]DECW$SVEXT_GLX_P350.EXE


      o  Some  programs  using   GLUT   (OpenGL   Utility   Toolkit)   -
         specifically  the glutIdleFunc function - would loop infinitely
         and/or ignore keyboard/mouse input.

         Images Affected:

          o  [SYSLIB]DECW$OPENGLUTSHR.EXE


      o  XFillRectangle calls with  extremely  out-of-range  coordinates
         sometimes  resulted  in erroneous drawing artifacts outside the
         window.

         Images Affected:

          o  [SYSLIB]DECW$SERVER_DDX_GB.EXE

          o  [SYSLIB]DECW$SERVER_RIDDGL.EXE



36  PROBLEMS ADDRESSED IN VMS73_IIDRIVER-V0100 KIT


      o  A cost reduced version of the server management card (Rev D04)
         was introduced for the DS20E system.  Because this version does
         not include EEPROM, it requires IIDRIVER to send a different
         I2C command to fetch the temperature.

         Images Affected:

          -  [SYS$LDR]SYS$IIDRIVER.EXE




37  PROBLEMS ADDRESSED IN VMS73_INIT-V0100 KIT


      o  If the command INIT/SHADOW=(ddc1:, ddc2:, ddc3:) is  performed,
         disks  ddc2:   and  ddc3:   are  not  initialized properly.  In
         particular, the BADBLK.SYS file is wrong.  Therefore,  attempts
         to  ANALYZE/DISK  ddc2:  will fail with "%ANALDISK-W-MULTALLOC"
         errors.

         Images Affected:

          -  [SYSLIB]INIT$SHR.EXE

          -  [SYSEXE]INIT.EXE




38  PROBLEMS ADDRESSED IN VMS73_IOGEN-V0100 KIT


      o  In the following scenario, mounting a device will fail with a
         %MOUNT-F-DEVOFFLINE error message:

         1.  A unit is deleted via the HSZ or HSG console, or fails such
             that mounting it causes a %MOUNT-F-UNSAFE error message

         2.  SYSMAN> IO AUTOCONFIGURE is run after the problem is
             corrected

         The next mount of the device will fail with a
         %MOUNT-F-DEVOFFLINE error message.  A $SHOW DEV/FULL will show
         a duplicate, unusable path (UCB) for the device.

         Images Affected:

          -  [SYSLIB]IOGEN$SHARE.EXE



39  PROBLEMS ADDRESSED IN VMS73_LAN-V0400 KIT


      o  The VMS73_LAN-V0300 kit is not compatible with the newly
         released PCSI PRODUCT UNDO PATCH functionality.  This new PCSI
         functionality allows a user to uninstall a patch kit.  If a
         user was to install the VMS73_LAN-V0300 patch kit using the new
         PROD INSTALL /SAVE_RECOVERY_DATA option and then attempted to
         uninstall the kit using the PRODUCT UNDO PATCH feature, the
         system could be left in an unbootable state.  This new
         VMS73_LAN-V0400 kit re-issues the VMS73_LAN-V0300 kit with
         updated installation files that allow safe removal of the kit.

         Note that this is the only change in this new LAN patch kit.
         There are no new LAN changes in the VMS73_LAN-V0400 kit.  If
         you have already installed the VMS73_LAN-V0300 patch kit, there
         is no need to install the VMS73_LAN-V0400 kit.

         Images Affected:

          -  POSTUNDO.COM




40  PROBLEMS ADDRESSED IN VMS73_LAN-V0300 KIT


      o  The receiving side of a transmit request  to  the  EBA  (Galaxy
         Shared  Memory  LAN)  device may crash because the PFN count is
         incorrect.  The transmit side now updates the PFN count  before
         updating the pointers given to the other instance in the Galaxy
         (that is the target of the  transmit  request),  eliminating  a
         race condition in the driver.

         Images Affected:

          -  [SYS$LDR]SYS$EBDRIVER.EXE


      o  If the cluster code (PEDRIVER) is using the EBA (Galaxy  Shared
         Memory  LAN)  device,  it  may choose another slower LAN device
         rather than the shared memory LAN device.  This change sets the
         device  line  speed  to  30000  so  that  PEDRIVER chooses this
         interconnect over other slower interconnects.

         Images Affected:

          -  [SYS$LDR]SYS$EBDRIVER.EXE


      o  Occasionally, a transmit request  to  the  EIA  (82558,  82559,
         82559ER,  DE600,  DE602 PCI Ethernet) device is not seen by the
         device.  This causes the transmit to be delayed until the  next
         transmit  request  is  given  to  the device.  Under heavy load
         conditions, this is not noticeable.  Under light load, this  is
         seen  as  a  transmit that may take seconds to complete.  Where
         the device is used as a cluster  interconnect,  the  result  is
         transmit retries and virtual circuit closures.

         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  With the EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet)
         device,  if  the  link  partner redoes auto-negotiation (switch
         powered off, for example), the driver does  not  force  a  link
         transition  when  appropriate,  resulting  in  the link partner
         selecting half-duplex mode when it  should  select  full-duplex
         mode.    Also,   the  requested  settings  are  not  advertised
         correctly  resulting  in  difficulty  auto-negotiating  to  the
         intended speed and duplex mode.

         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  The EIA (82558, 82559,  82559ER,  DE600,  DE602  PCI  Ethernet)
         device  driver  is  treating  the  console environment variable
         EIx0_MODE   setting   of   "twisted-pair"   as    "Full-Duplex,
         Twisted-pair",  so  it  should select half-duplex 10 mbit mode,
         but selects full-duplex instead.

         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  The EIA (82558, 82559,  82559ER,  DE600,  DE602  PCI  Ethernet)
         device  is not being set up correctly, generally resulting in a
         duplex  mode  mismatch  problem,  if  the  console  environment
         variable, EIx0_MODE is set to FastFD.

         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  The EIA (82558, 82559,  82559ER,  DE600,  DE602  PCI  Ethernet)
         device occasionally reads an invalid buffer descriptor from the
         receive ring.  When this happens a machine  check  occurs  with
         resulting  system  crash, often with an "invalid scatter-gather
         map" error.

         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  Add support for the Intel 82559ER chip and the DE602-BB NIC.

         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  Resolve a system crash with the  EIA  (82558,  82559,  82559ER,
         DE600,  DE602  PCI  Ethernet) device driver and with IP traffic
         (generally involving a lot of telnet  connections).   When  the
         number of segments comprising a transmit packet request exceeds
         15,  the  driver  copies  the  remaining  segments   into   one
         additional   segment.    If  this  segment  is  not  physically
         contiguous, therefore requiring two additional segments instead
         of  one,  the driver corrupts the stack and causes an INVEXCPTN
         system crash.  The problem is that the check for maximum number
         of segments is off by one.

         Images Affected:

          -  [SYS$LDR]SYS$EIDRIVER.EXE


      o  Fix a  few  problems  with  auto-negotiation  by  DE500-BA  PCI
         Ethernet  devices to improve the ability of the DE500-BA driver
         to  auto-negotiate  to  the  correct  setting.   This  includes
         adjusting  the  timing  of various auto-negotiation events, and
         restarting auto-negotiation when appropriate.

         Images Affected:

          -  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE


      o  On rare occasions, it is possible for the Tulip driver to reset
         the  Tulip  chip,  but  not wait long enough after reset before
         touching the device resulting in a machine check system  crash.
         The solution is to increase the amount of time after a reset to
         guarantee that the device has sufficient time to  reset  itself
         after a reset.  The Tulip driver includes support for the Tulip
         chip, DE425 EISA NIC, and the PCI Ethernet NICs  DE434,  DE435,
         DE500-XA, DE500-AA, DE500-BA, DE504-BA.

         Images Affected:

          -  [SYS$LDR]SYS$ERDRIVER.EXE

          -  [SYS$LDR]SYS$EWDRIVER.EXE

          -  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE


      o  The DEGPA firmware included in the device driver for the  DEGPA
         PCI  Gigabit  Ethernet  NIC  cannot deal with a transmit buffer
         that is within 12 bytes of a 4 gigabyte boundary.   This  could
         lead  to  data  corruption.   This  problem  only  affects  the
         AlphaServer   4100,   AlphaServer   DS20,   AlphaServer   ES40,
         AlphaServer  GS80  and  GS160,  and system upgrades such as the
         DS25, ES45, and only those systems with at least 4 gigabytes of
         memory.   The fix is to avoid the problem by copying the buffer
         to a special buffer that is not  near  such  a  boundary.   The
         number  of  times  the  workaround is invoked is tallied in the
         internal     driver      counters      (MC      LANCP      SHOW
         DEVICE/INTERNAL_COUNTERS)  called "4GB workarounds", so you can
         see if the condition ever does occur.

         Images Affected:

          -  [SYS$LDR]SYS$EW1000A.EXE


      o  Increase the amount of time given for reset by  the  DEGPA  PCI
         Gigabit  Ethernet device driver of the Tigon II chip.  The time
         is increased from 80 to 640  milliseconds.   On  some  systems,
         insufficient reset time occasionally results in a machine check
         system crash when the driver touches the device after a reset.

         Images Affected:

          -  [SYS$LDR]SYS$EW1000A.EXE


      o  When a user (protocol) is stopped,  the  user  context  is  not
         reset  correctly  by  the  DEGPA  PCI  Gigabit  Ethernet device
         driver.  This results in the  inability  to  restart  the  user
         without  rebooting  the  system.   For  example,  if  DECnet is
         stopped and restarted it may fail to restart.

         Images Affected:

          -  [SYS$LDR]SYS$EW1000A.EXE


      o  The multicast addresses list is not  given  to  the  DEGPA  PCI
         Gigabit  Ethernet  device  again  after  the  driver resets the
         device to clear a transmit timeout condition.  This can  happen
         if  the  cable  is  unplugged with transmits outstanding to the
         device.  The consequence is that multicast  traffic  stops  for
         all  users  (protocols)  until  another  user  is started or an
         existing user is stopped and restarted.

         Images Affected:

          -  [SYS$LDR]SYS$EW1000A.EXE


      o  On DEC 7000 systems, with the DEFPA PCI FDDI device, which  use
         mailbox  hardware  to read and write registers, the error bits,
         which the driver should clear, are not being cleared  properly.
         This  may  result  in  a  machine check system crash because of
         stale error bits.

         Images Affected:

          -  [SYS$LDR]SYS$FWDRIVER.EXE


      o  For all LAN devices, modify the  VCI  transmit  path  (used  by
         PEDRIVER,  DECnet-Plus, TCP/IP, LAST, LAT and others) to verify
         the  transmit  request  is  not  too  long,  incrementing   the
         "Transmit too long" error counter and returning error status to
         the  offending  application.   This  improves  the  ability  to
         diagnose  application  problems  by  identifying the failure to
         transmit in the device counters and making it more visible.

         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


      o  For all LAN devices, modify the VCI interface to  allow  a  VCI
         user to enable promiscuous mode.

         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


      o  For all LAN devices, remove the  limitation  of  255  multicast
         addresses  enabled  for  a device.  This may improve efficiency
         somewhat by decreasing the multicast filtering work done by the
         LAN  driver.   Only the Gigabit Ethernet devices take advantage
         of this capability.

         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


      o  When a DECnet-Plus NCL  command,  "SHOW  FDDI  STATION  *  ALL"
         request is processed by the LAN driver network management code,
         if the requested device returns counters  data  asynchronously,
         it  is  possible  that  R3  is  destroyed during the LAN driver
         processing.  This results in an  INVEXCPTN  crash  in  NCL.EXE.
         The  problem  is  that  R3  is  not preserved cross the call to
         obtain  counters,  when  it  should  be.   This   affects   any
         DECnet-Plus  network  managed device that returns counters data
         asynchronously to a counters request, which is all XMI and  all
         FDDI adapters.

         Images Affected:

          -  [SYS$LDR]NET$CSMACD.EXE

          -  [SYS$LDR]NET$FDDI.EXE


      o  Improve the boot messages for the EIA (82558,  82559,  82559ER,
         DE600, DE602 PCI Ethernet), ERA (Tulip, DE422 EISA, DE425 EISA,
         DE205  ISA  Ethernet),  and  EWA  (PCI  Tulip,  DE434,   DE435,
         DE500-XA, DE500-AA, DE500-BA PCI Ethernet) LAN devices, so that
         more details are available to diagnose boot failures.

         Images Affected:

          -  [SYS$LDR]SYS$EWBTDRIVER.EXE

          -  [SYS$LDR]SYS$ERBTDRIVER.EXE

          -  [SYS$LDR]SYS$EIBTDRIVER.EXE

          -  [SYSEXE]APB.EXE

          -  [SYSEXE]DEBUG_APB.EXE


      o  Add  support  for  booting  the  Alpha  Personal   Workstation,
         XP-1000, over the embedded 21143 chip.

         Images Affected:

          -  [SYS$LDR]SYS$EWBTDRIVER.EXE

          -  [SYS$LDR]SYS$ERBTDRIVER.EXE

          -  [SYSEXE]APB.EXE

          -  [SYSEXE]DEBUG_APB.EXE


      o  The boot driver for  the  DE500  PCI  Ethernet  device  is  not
         restarting  auto-negotiation  after resetting the device, which
         results in the  link  partner  (generally  an  auto-negotiating
         10/100  switch)  selecting half-duplex mode and the boot driver
         selecting full-duplex mode.  The  duplex  mode  mismatch  slows
         satellite booting considerably.

         Images Affected:

          -  [SYS$LDR]SYS$EWBTDRIVER.EXE

          -  [SYSEXE]APB.EXE

          -  [SYSEXE]DEBUG_APB.EXE




41  PROBLEMS ADDRESSED IN VMS73_LIBRTL-V0200 KIT


      o  Multithread programs using the DEC C  RTL  routine  malloc  and
         free  experience  a  synchonization  failure.   These DEC C RTL
         routines in turn use  the  LIBRTL  Routines  LIB$VM_MALLOC  and
         LIB$VM_FREE.   Symptoms could be varied, but are most likely to
         result in an access violations (ACCVIO).

         For an application to see this problem it would  have  to  have
         all of the following characteristics:

         - Calls the DEC C RTL routines malloc and free -  Multithreaded
         -  Compiled  with  the  /REENTRANCY=MULTITHREAD switch - Linked
         /THREADS_ENABLE=(MULTIPLE_KERNEL_THREADS,UPCALLS) -  Run  on  a
         multiprocessor system with kernel threads enabled.

         This problem was introduced in V7.3 of VMS.  Earlier  versions,
         including all V7.2 variants are not affected.

         The VMS73_LIBRTL-V0100 ECO  kit  was  issued  to  correct  this
         problem  but  the  images contained in that kit did not contain
         the fix.

         Images Affected:

          -  [SYSLIB]LIBRTL.EXE

          -  [SYSLIB]LIBRTL_INSTRUMENTED.EXE



42  PROBLEMS ADDRESSED IN VMS73_LIBRTL-V0100 KIT


      o  The new C compiler  for  V7.3  (Compaq  C  V6.2-008)  generates
         different  code  for  the  __CMP_STORE_QUAD  built-in.  The old
         compiler (V5.7-006) generated a Memory Barrier (MB) instruction
         as part of this operation which the new compiler does not.  The
         Memory Barrier is required for  the  LIB  routines  for  proper
         synchronization,  otherwise  a  packet being put on a free list
         may have an invalid flink when viewed from another processor.

         Images Affected:

          -  [SYSLIB]LIBRTL.EXE

          -  [SYSLIB]LIBRTL_INSTRUMENTED.EXE




43  PROBLEMS ADDRESSED IN VMS73_LINKER-V0300 KIT


      o  This change increases the RMS I/O related parameters when doing
         I/O to the image file and map.  This will result in an increase
         in performance and reduce link time.

         Images Affected:

          -  [SYSEXE]LINK.EXE




44  PROBLEMS ADDRESSED IN VMS73_MANAGE-V0200 KIT


      o  After issuing a $MC SYSMAN IO SHOW DEVICE command on  a  system
         with  many  BG  devices, the system can crash with a SSRVEXCEPT
         bugcheck at SMI$IOGEN_C+00924.  The crash  occurs  because  the
         reserved buffer is too small (16384 bytes)

         Crash Dump Summary
         ------------------
         Bugcheck Type:     SSRVEXCEPT, Unexpected system service
                            exception
         Current Process:   FIELD
         Current Image:     $1$DGA3101:[SYS6.SYSCOMMON.]
                            [SYSEXE]SYSMAN.EXE
         Failing PC:        00000000.000DD460    SMI$IOGEN_C+00910
         Failing PS:        10000000.00000203
         Module:            SMI$OBJSHR
         Offset:            0003B460


         Images Affected:

          -  [SYSLIB]SMI$OBJSHR.EXE


      o  This change generally enhances the handling  of  Fibre  Channel
         tape  bridges  and  in  particular,  allows  SCSI  tapes  to be
         configured behind a Network Storage Router.

         Images Affected:

          -  [SYSLIB]SMI$OBJSHR.EXE

          -  [SYSLIB]IOGEN$FIBRE_CONFIG.EXE




45  PROBLEMS ADDRESSED IN VMS73_MANAGE-V0100 KIT


      o  Customers have questioned why SYSMAN DO commands, issued from a
         local  node,  generate an ALTPRI audit alarm and set a priority
         of 7.  For example:

         Message from user AUDIT$SERVER on NODE1
         Security alarm (SECURITY) on NODE1, system id: 00000
         Auditable event:          Privilege failure
         Event information:        ALTPRI not used to create
         process with elevated priority (RUN/PRIORITY, $CREPRC)
         Event time:                9-JUL-2001 14:49:12.18
         PID:                      21A00427
         Process name:             pname
         Username:                 uname
         Process owner:            [gname,uname]
         Terminal name:            TNA4:
         Image name:               $40$DKA0:[SYS0.SYSCOMMON.]
                                   [SYSEXE]SYSMAN.EXE
         New priority:             7
         Privileges missing:       ALTPRI

         Customers do not understand why there is a  request  to  create
         the  process  at  priority 7.  The subprocess is created at the
         lower priority and functions properly for a client who does not
         have the ALTPRI privilege.

         This change provides the following priority settings:

          o  If the requester has ALTPRI,  use  current  behavior,  i.e.
             create the subprocess at priority 7.

          o  If  the  requester  does  not  have  ALTPRI,   create   the
             subprocess at the requester default priority.

          o  If  default  priority  is  greater  than  7,   create   the
             subprocess at priority 7.

         This maintains the current priority settings on the  subprocess
         creation and eliminates the unnecessary audit alarm.   

         Images Affected:

          -  [SYSLIB]SMI$OBJSHR.EXE


      o  SYSMAN  commands  fail  on  remote  systems  with  insufficient
         privilege  errors.   The  cause  is  that the SMISERVER process
         running on the node that  reported  the  error  does  not  have
         CMKRNL  privilege.   A  restart  of  the  SMISERVER  fixes  the
         problem.

         Images Affected:

          -  [SYSEXE]SMISERVER.EXE      


      o  The USERNAME of the SMISERVER process is not set  back  to  the
         username  of  the  starting  process after a user exits SYSMAN.
         For example:

         Starting username:

         SYSTEM1>sho proc/id=20200218

         9-MAR-2001 13:21:12.00 User: SYSTEM  Process ID:  20200218
                                Node: SYSTEM1 Process name:"SMISERVER"
         SYSTEM1>


         >>> From another system:

         SYSTEM2> mc sysman set env/node=SYSTEM1/user=testusr
         Remote Password:
         %SYSMAN-I-ENV, current command environment:
                 Individual nodes: SYSTEM1
                 At least one node is not in local cluster
                 Username TESTUSR will be used on nonlocal nodes

         SYSMAN> do sho proc
         %SYSMAN-I-OUTPUT, command execution on node SYSTEM1
         9-MAR-2001 13:22:46.81 User: TESTUSR Process ID:  202002E7
                         Node: SYSTEM1 Process name:"SMI$TESTUSR_1"
         SYSMAN>



         >>> SMISERVER process on SYSTEM1 before exiting SYSMAN
              on SYSTEM2

         SYSTEM1>sho proc/id=20200218

         9-MAR-2001 13:24:02.82 User: TESTUSR Process ID:  20200218
                             Node: SYSTEM1 Process name:"SMISERVER"
         SYSTEM1>


         >>> SMISERVER process on SYSTEM1 after exiting SYSMAN
             on SYSTEM2:

         SYSTEM1>sho proc/id=20200218

         9-MAR-2001 13:26:06.02 User: TESTUSR Process ID:  20200218
                             Node: SYSTEM1 Process name:"SMISERVER"

         The username should be "SYSTEM".

         Images Affected:

          -  [SYSEXE]SMISERVER.EXE


      o  This kit affects some tape devices  (tape  drives  and  robots)
         which  are  connected to Fibre Channel via an MDR (Modular Data
         Router).  The affected tape  devices  have  binary  WWIDs  that
         contain embedded byte values between 61h and 7Ah.  For example,
         a WWID of  02000008:500E-09E0-0005-3072  (note  the  last  byte
         value  is  72h).  These devices are detected during a SYSMAN IO
         FIND_WWID command, as verified by the WWID  value  recorded  in
         SYS$SYSTEM:SYS$DEVICES.DAT.    However,   the  devices  do  not
         configure if SYSMAN IO  AUTOCONFIGURE  is  invoked  immediately
         after  the the SYSMAN IO FIND_WWID command.  Only a reboot will
         result in configuring these devices.  The purpose of  this  kit
         is to avoid this need for a reboot.

         Note:  Similar issues  can  arise  when  using  the  SYSMAN  IO
         REPLACE_WWID command.

         Images Affected:

          -  [SYSLIB]SMI$OBJSHR.EXE




46  PROBLEMS ADDRESSED IN VMS73_MIME-V0100 KIT


      o  Mime message corruption can occur  for  messages  created  with
         OpenVMS  Mime  that  have  text  of more than just a few lines.
         Messages appear to be truncated or text may appear  garbled  or
         out of context.  This happens when the textual message part has
         a length (when combined with the Mime header area) that exceeds
         1024 characters.

         Images Affected:

          -  [SYSEXE]MIME.EXE

          -  SYSHLP]MIME.EXE


      o  Multipart messages created with  OpenVMS  Mime  may  cause  the
         error:

         "Invalid boundary marker" when attempting to read (decode)
         the message.


         Images Affected:

          -  [SYSEXE]MIME.EXE

          -  [SYSHLP]MIME$HELP.HLB


      o  The file name (known as the Disposition file  name),  would  be
         added more than once when multiple edits and saves occur.

         Images Affected:

          -  [SYSEXE]MIME.EXE

          -  [SYSHLP]MIME$HELP.HLB


      o  A SYSTEM-F-ACCVIO error can occur when a SAVE is performed on a
         message when a message part has previously been removed.

         Images Affected:

          -  [SYSEXE]MIME.EXE

          -  [SYSHLP]MIME$HELP.HLB


      o  When the MIME> LIST command is used for a message with only one
         main  part,  (a  single  part message), no attachment number is
         listed.  This may confuse  the  user  as  to  which  attachment
         number  to  specify with the EXTRACT command, which requires an
         attachment number.  On-line help has been modified  to  specify
         attachment number one for single part messages, as follows:

         EXTRACT

         Format: EXTRACT/ATTACHMENT=attachment-number [filename]

         NOTE: The /ATTACHMENT qualifier is required with EXTRACT.
         This qualifier specifies the number of the attachment as
         displayed by the LIST command. In a single part message,
         no attachment number is displayed. For this case specify
         attachment number one.


         Images Affected:

          -  [SYSEXE]MIME.EXE

          -  [SYSHLP]MIME$HELP.HLB


      o  

         Error messages can be overwritten or garbled when errors  occur
         while reading a Mime message.

         Images Affected:

          -  [SYSEXE]MIME.EXE

          -  [SYSHLP]MIME$HELP.HLB


      o  Problems occur while attempting to  EXTRACT,  EDIT,  or  REMOVE
         message  parts  due to an improper attachment range check or an
         illegal range of  message  part  numbers  being  accepted  when
         actually  invalid.   Typically  the  symptom is either the part
         fails to extract due to an erroneous error,  or  the  incorrect
         part  is  extracted,  edited,  or  removed.   This  may include
         removal  or  extraction  of  non-message  parts   or   non-leaf
         attachments, such as multipart or multipart alternative parts.

         Images Affected:

          -  [SYSEXE]MIME.EXE

          -  [SYSHLP]MIME$HELP.HLB


      o  When exiting and prompted to save file, a  typographical  error
         would be accepted as a negative response and the file would not
         be saved.

         Images Affected:

          -  [SYSEXE]MIME.EXE

          -  [SYSHLP]MIME$HELP.HLB


      o  While reading a message, the screen may be improperly  restored
         which  causes  the  screen  output  to be displayed improperly.
         This may happen when returning  from  a  spawned  process  that
         provided output to the same screen device, executed commands in
         DCL that caused errors, and so forth.

         Images Affected:

          -  [SYSEXE]MIME.EXE

          -  [SYSHLP]MIME$HELP.HLB


      o  Other miscellaneous errors and  problems  that  were  corrected
         are:

         1.  Certain file errors were  not  being  reported  or  handled
             properly during opening and editing of a message.

         2.  Fix regression where multiple SAVEs  were  not  saving  the
             file and only the first save was being written.

         3.  Code optimization in remove attachment.

         4.  If an error occurred  during  ADD,  the  message  would  be
             corrupted (there was no message recovery)

         5.  Under certain situations  a  message  would  not  be  saved
             during a SAVE, EXIT, CLOSE, NEW, OPEN, and ^Z operation.

         6.  Errors would occur while attempting to use the edit command
             as defined in MIME$MAILCAP.DAT.

         7.  No support for edit of HTML  attachments  (Unix-style  file
             name parsing.

         8.  Errors on,  or  failure  to  read  plain  text  due  to  an
             erroneous content-type parameter match on text style.

         9.  Update this version image IDENT, MIME Version and MIME HELP
             (MIME$HELP.HLB) to V1.7

        10.  Updated MIME HELP


         Images Affected:

          -  [SYSEXE]MIME.EXE

          -  [SYSHLP]MIME$HELP.HLB


      o  For  a  large  MIME  message  (262  Mbyte)  comprised   of   40
         attachments,  attachments  are  not listed properly.  Observing
         the output from the MIME> LIST command and  typing  Control_S/Q
         shows  the  attachments  and  the filenames.  However, manually
         scrolling back to review attachments and filenames results in a
         display  where  attachment  numbers  and/or  most filenames are
         omitted.  In trying  to  duplicate  the  problem,  other  large
         messages with many attachments did not reproduce the problem.

         Images Affected:

          -  [SYSEXE]MIME.EXE

          -  [SYSHLP]MIME$HELP.HLB




47  PROBLEMS ADDRESSED IN VMS73_MONTOR-V0100 KIT


      o  The command MONITOR  RMS/FILE=LOGIN.COM  will  access  violate.
         For example:

         $ monitor rms/file=login.com
         %MONITOR-E-COLLERR, error during data collection
         -SYSTEM-F-ACCVIO, access violation, reason mask=5B,
         virtual address=000000000000001B, PC=000000007ACAF7EC, 
         PS=7ACAF82D    


         Images Affected:

          -  [SYSLIB]MONTORSHR.EXE

          -  [SYSLIB]SPISHR.EXE

          -  [SYSEXE]VPM.EXE

          -  [SYSEXE]VPM_SERVER.EXE




48  PROBLEMS ADDRESSED IN VMS73_MSCP-V0100 KIT


      o  Densities for the TF85, TF86 and TF87 are missing from
         DENSITY_TABLE.  These missing densities may cause
         TMSCP$VMSTOMSCP_DENS to fail to locate a certain density,
         thereby looking beyond allocated memory.  The result is a crash
         at AMAC$EMUL_LOCC_C+0005C, called from TMSCP+05B54 (in R26).

         This change adds the missing densities to DENSITY_TABLE and
         also makes TMSCP$VMSTOMSCP_DENS more robust against missing
         densities.

         Images Affected:

          -  [SYS$LDR]TMSCP.EXE


      o  A system crash may occur if a tape is ANSI mounted and
         mountverification starts:

         Crashdump Summary Information
         -----------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.8011174C
                            MNTVER_STD$GET_CKSUM_BUF_C+001CC
         Failing PS:        00000000.00000804
         Module:            IO_ROUTINES_MON (Link Date/Time:
                            10-NOV-2001 06:14:53.62)
         Offset:            0002B74C

         Failing Instruction:
         MNTVER_STD$GET_CKSUM_BUF_C+001CC:LDQ_U R25,#X0120(R26)


         Images Affected:

          -  [SYS$LDR]TMSCP.EXE


      o  With Fibrechannel tapes, in the event of a connection error,
         one I/O could return an error while subsequent I/Os, that are
         still underway, complete with success.  This causes problems
         for mountverification when attempting to reposition the tape
         for error recovery.  The I/Os that complete after failed I/O
         cause the tape position in the UCB to be updated.  This causes
         out of sequence I/Os to be written to the tape, resulting in
         data corruption which may only be detected by BACKUP's verify
         operation.

         Images Affected:

          -  [SYS$LDR]TMSCP.EXE




49  PROBLEMS ADDRESSED IN VMS73_PPPD-V0200 KIT


      o  PPPD = DISCONNECT TTA0 command fails to disconnect and  returns
         an error similar to the following error message:

         A73KT: PPPD DISCONNECT TTA0:
         %PPPD-E-PPPCONNECTERR, error connecting to PPP device
         %SYSTEM-W-NOSUCHDEV, no such device available
         %PPPD-F-ABORT, fatal error encountered; operation terminated

         Images Affected:

          -  [SYSEXE]PPPD$UTIL.EXE

          -  [SYS$LDR]SYS$PPPDRIVER.EXE


50  PROBLEMS ADDRESSED IN VMS73_PPPD-V0100 KIT


      o  Line table lookup fails when line number is greater than 9.

         Images Affected:

          -  [SYS$LDR]SYS$PPPDRIVER.EXE




51  PROBLEMS ADDRESSED IN VMS73_PTHREAD-V0300 KIT


      o  On  multi-processor  systems,  the  EXEC  uses  the  Inner-Mode
         Semaphore (IMS) to serialize execution of many system services.
         Upcalls are used to allow the threads library  to  execute  one
         thread  while  another  is  blocked  waiting  for the IMS.  The
         services which the threads library uses to switch  threads  are
         themselves  users  of  the  IMS.  Under certain conditions, the
         result is recursion of  IMS-free  upcalls.   If  the  recursion
         persists  long  enough,  a  stack  overflow can occur in a null
         thread which terminates the process.  This can only happen on a
         multiprocessor  system  when use of upcalls and multiple kernel
         threads are enabled.

         Images Affected:

          -  [SYSLIB]PTHREAD$DBGSHR.EXE

          -  [SYSLIB]PTHREAD$RTL.EXE


      o  The    threads    library    uses    $SETIMR    to    implement
         pthread_cond_timedwait  and  pthread_delay_np  operations.  The
         library starts a timer for a given wake-up time, and expects to
         be  awoken  at  that  timer (or perhaps later, if the system is
         busy).  At one customer site, we  observed  that  occasionally,
         the  wake-up  appeared  to  arrive too early (at a system clock
         time which was less than the requested  wake-up  time).   Under
         certain  conditions  these early wake-ups caused the process to
         hang.  The cause of the early wake-ups is thought to be use  of
         NTP which was configured to allow backward time jumps (which is
         not recommended).  If such a backward jump occurs between  when
         the  timer's  target time is reached, and when the library runs
         and reads the system clock, the effective result  is  an  early
         wake-up.

         The library has been enhanced to defend against early wake-ups,
         by requesting a new timer for the original target time.

         Images Affected:

          -  [SYSLIB]PTHREAD$DBGSHR.EXE

          -  [SYSLIB]PTHREAD$RTL.EXE


      o  The public C language header file PTHREAD_EXCEPTION.H was using
         the symbol NULL, without ensuring that this symbol was defined.
         If  a  user  program  is  compiled  with  this  header,  in  an
         environment  which happens to not cause NULL to be defined, the
         following compiler diagnostic will appear:

            %CC-E-UNDECLARED, In this statement, "NULL" is not
            declared.

         The header file has been changed to not use the NULL symbol.

         Images Affected:

          -  [SYSLIB]SYS$STARLET_C.TLB


      o  Fix a locking problem which could cause a threads  bugcheck  at
         context-switch.   The  threads  library  uses internal locks to
         protect shared data.  A thread can  context-switch  away  while
         holding  certain  locks.   The  internal  lock  environment  is
         generally restored when the thread  is  later  context-switched
         back  in.   A  bug  caused the incorrect lock environment to be
         restored under certain conditions.  The result is most often  a
         threads bugcheck "selected a non-ready thread," but other types
         of process crashes could result.

         Following is the introductory part of the bugcheck report:

         %DECthreads bugcheck (version V3.17-019), terminating
          execution.
         %Reason:  selected a non-ready thread 8 (0x000000001E945740) 
                   state running
         %Running on OpenVMS V7.3 on AlphaServer 8400 5/625, 
          2048Mb; 10 CPUs
         % The bugcheck occurred at 29-MAY-2001 22:45:06.03, running 
         % image DSA0:[DB22X.]SERVER.EXE;1 in process 202014EC 
         % (named "MCR Srv"), under username "SYSTEM". AST delivery 
         % is enabled for all modes; no ASTs active. Upcalls are 
         % enabled. Multiple kernel threads are enabled.  The current
         % thread sequence number is 1, at 0x7BC34908


         Images Affected:

          -  [SYSLIB]PTHREAD$DBGSHR.EXE

          -  [SYSLIB]PTHREAD$RTL.EXE


      o  Fix a problem seen in Java that  caused  process  hangs.   This
         requires  an  application  AST to arrive while the Java garbage
         collector is running under  certain  conditions.   The  threads
         library  uses  the  default  thread  to  service  the AST (when
         upcalls  are  enabled,  which  Java  requires).    If   garbage
         collection  is  happening  at the same time, the default thread
         can be left in an incorrect state,  causing  a  hang.   To  fix
         this,  AST delivery is now deferred while the garbage collector
         is running.

         Images Affected:

          -  [SYSLIB]PTHREAD$DBGSHR.EXE

          -  [SYSLIB]PTHREAD$RTL.EXE




52  PROBLEMS ADDRESSED IN VMS73_PTHREAD-V0200 KIT


      o  The  pthread_cond_timedwait()  and   pthread_delay_np()   timed
         operations  could  wait  too  long before timing out.  This can
         happen if the operating system's Time Differential Factor (TDF)
         is   changed,  e.g.,  due  to  a  Daylight  Saving  Time  (DST)
         adjustment.  Documentation for these  timed  operations  states
         that they may in fact return late.  However, that was not meant
         to cover a, for example, one hour delay due to a switch of DST.

         With this change, system-time alterations due  to  general  TDF
         changes  (such  as  a  DST  switch) now have no effect on timed
         thread operations.

         Images Affected:

          -  [SYSLIB]PTHREAD$DBGSHR.EXE

          -  [SYSLIB]PTHREAD$RTL.EXE


      o  This correction fixes a  race  condition  on  a  multiprocessor
         system,  where  thread  scheduling  states can become confused.
         This is a rare condition, and only  happens  when  upcalls  and
         multiple   kernel   threads   are   in  use.   The  only  known
         manifestation of the   problem so far is an  application  hang.
         One  kernel  thread is seen to be in an AST in HIB state, while
         that kernel thread is running a threads library internal "null"
         thread.   Because  an  AST  is  active,  no  more  ASTs will be
         delivered.   If  further  application   progress   depends   on
         servicing subsequent ASTs, the application is hung.

         Images Affected:

          -  [SYSLIB]PTHREAD$DBGSHR.EXE

          -  [SYSLIB]PTHREAD$RTL.EXE


      o  A process can  crash  (probably  in  PTHREAD$RTL,  possibly  in
         user-mode).   This  problem requires the use of multiple kernel
         threads (and thus upcalls) on a multiprocessor system, and  AST
         delivery.   Upon  completion of an application AST, the threads
         library can mistakenly try to run the  default  thread  on  two
         CPUs  concurrently.   If  this  occurs,  the  application  will
         probably ACCVIO quickly.

         Images Affected:

          -  [SYSLIB]PTHREAD$DBGSHR.EXE

          -  [SYSLIB]PTHREAD$RTL.EXE




53  PROBLEMS ADDRESSED IN VMS73_REGISTRY-V0100 KIT


      o  The system  can  crash  with  various  types  of  bugchecks  if
         $Registry  attempts  to  receive  more  data  from the Registry
         server than is allowed by the process' BYTLM quota.

         Images Affected:

          -  [SYS$LDR]SYS$NTA.EXE


      o  Issuing the command:

           $ mc reg$cp export database

         on a new database causes value names to be written incorrectly.

         Images Affected:

          -  [SYSEXE]REG$CP.EXE


      o  Processes can hang if a connection breaks and there  are  timed
         out requests in the Registry request queue.

         Images Affected:

          -  [SYSEXE]SYS$NTA.EXE


      o  When the server is trying to  shut  down,  it  will  ACCVIO  in
         various  places,  but  usually  in a pthread_cleanup_pop() call
         after signaling the datalogcleaner thread.  Usually  the  final
         exit  status  will  be 0x10408014.  The problem is due to queue
         corruption because the mutex locking to protect the  queue  was
         in  the  wrong  place.  It was protecting other operations, but
         not the queue itself.  This fix moves the code which locks  the
         mutex so that it protects the queue.

         Images Affected:

          -  [SYSEXE]REGISTRY$SERVER.EXE




54  PROBLEMS ADDRESSED IN VMS73_REM-V0100 KIT


      o  The following problems have been corrected:

         1.  Stopping and restarting  the  REMACP  process  without  the
             provided  management  utilities  (STOPREM  and  RTTLOAD.COM
             results in a system crash.

             Crashdump Summary Information:
             ------------------------------
             Bugcheck Type:     INVEXCEPTN, Exception while above 
                                ASTDEL
             Current Process:   REMACP
             Current Image:     $1$DGA300:[SYS61.SYSCOMMON.]
                                [SYSEXE]REMACP.EXE;1
             Failing PC:        00000000.0000C278
             Failing PS:        0C000000.00000800
             Module:            REMACP
             Offset:            0000C278


         2.  SET HOST connections are rejected even though  RJOBLIM  has
             not  been  reached.   Stopping  and  restarting  the REMACP
             process temporarily clears the condition.


         Images Affected:

          -  [SYSEXE]REMACP.EXE




55  PROBLEMS ADDRESSED IN VMS73_RMS-V0400 KIT


      o  RMS:  Fix to prevent possible process hangs and system  crashes
         when files with global buffers are accessed.

         An application accessing a file  with  global  buffers  enabled
         might  experience  any  one of several symptoms ranging from an
         IVLOCKID being returned to RMS through a  possible  SSRVEXCEPTN
         due to corruption of an RMS internal control structure.

         Prior to this change, it is  possible  for  an  internal  table
         maintained  by  RMS  (the Global Buffer Interlock Table) within
         its global buffer sections to overflow.  This  can  potentially
         result  in corruption to adjoining control structures.  No user
         data are compromised; however, the  process  may  hang  or  the
         system crash dependent on what is overwritten.  This problem is
         most prevalent on systems where there is  a  high  turnover  of
         processes.

         Images Affected:

          -  [SYS$LDR]RMS.EXE


      o  RMS:  Fix for a lock hang on a global buffer resource.

         The symptoms of the hang are as follows:

          -  A global buffer resource has in its granted queue a process
             PW lock and a system CR lock.

          -  The conversion queue for this resource has a long  line  of
             NL-to-PW  or  NL-to-EX  requests  blocked by the PW granted
             lock.

         This is not a lock manager problem.  The PW global buffer  lock
         holder  is  waiting for the system CR lock to be released.  The
         release  of  the  system  CR  lock  is  dependent  on  a   flag
         (internally managed by RMS) indicating a writer wants access to
         the resource and a reference count maintained  in  an  internal
         RMS  structure.   Until  the system CR lock is released and the
         flag cleared by the last referencer, the process holding the PW
         lock  will  continue  to block any other processes lining up in
         the conversion queue.

         This fix corrects a race  condition  where  if  a  process  was
         interrupted  (stopped  or  aborted by a $delprc) while actively
         using the system CR lock, it was possible for  the  cleanup  of
         the  internal  RMS  structure to be bypassed.  This would cause
         the reference count to get out of sync and result in the system
         CR  lock not getting properly released after a writer requested
         access to the resource.

         Images Affected:

          -  [SYS$LDR]RMS.EXE


      o  RMS:  Avoid an exec-mode infinite loop if RMS ever attempts  to
         add a duplicate key value to a compressed index bucket.

         An index bucket should never have a duplicate key value.  There
         is the potential, however, some inconsistency (corruption) in a
         lower level could result in such an attempt in the  case  of  a
         compressed  key.   A  correction  has  been  added  to  issue a
         nonfatal RMS bugcheck (ISAM) and avoid the loop.

         Images Affected:

          -  [SYS$LDR]RMS.EXE           


      o  RMS:  Fix for some records being potentially skipped over in  a
         reverse key search.

         If the very  last  bucket  in  the  data  bucket  chain  for  a
         particular  key-of-reference  is  empty (no valid records), the
         potential exists for any valid records in the  next-to-the-last
         bucket  (and  only  this  bucket)  being  skipped  over  in the
         backwards scan done by a reverse key search.

         This problem is restricted to a reverse key search.

         Images Affected:

          -  [SYS$LDR]RMS.EXE


      o  RMS:  Correction for circumflex returned  in  resultant  string
         for search error cases.

         When a one-character wildcard % is used in a search, if no file
         is  found (an error is returned), the resultant string returned
         in the user NAM[L] structure has  a  circumflex  (^)  character
         inappropriately  inserted  just  before  the %.  This affects a
         number of DCL utilities which display the resultant string with
         their  error  messages  (e.g.,  DELETE, TYPE, RENAME and COPY).
         For example:

         $ delete %.jnk;*
         %DELETE-W-SEARCHFAIL, error searching for SYS$COMMON:[FOO]^%.JNK;*
         -RMS-E-FNF, file not found

         Images Affected:

          -  [SYS$LDR]RMS.EXE


      o  RMS:  Set the return length of the auxiliary buffer  for  calls
         to SYS$FILESCAN.

         The return length of the auxiliary  buffer  ("retlen"  optional
         parameter)  that  was  passed to SYS$FILESCAN was not being set
         when  the  Field  Flags  argument  ("fldflags"  parameter)  was
         absent.    This   change   sets   the   return   length   value
         unconditionally when one has been requested.

         Images Affected:

          -  [SYS$LDR]RMS.EXE


      o  CONVERT:  Fix for remote file DAP protocol regression.

         The convert utility fails with the  following  error  when  the
         input  file  is a sequential file on a remote foreign (non-VMS)
         system and the output file is a sequential file on a VMS system
         if  and  only  if  /SORT  is explicitly specified or implied by
         /FDL:

             %CONV-F-READERR, Error reading (IBM_filename)
             -RMS-F-BUG_DAP, Data Access Protocol error detected; 
                             DAP code = 0001A008

         The problem is not reproducable using a remote VMS system.

         Images Affected:

          -  [SYSEXE]CONVERT.EXE

          -  [SYSLIB]CONVSHR.EXE




56  PROBLEMS ADDRESSED IN VMS73_RMS-V0300 KIT KIT


      o  Fix for RMS global buffer hang due to abort ($delprc) rundowns.

         An application  may  experience  a  hang  under  the  following
         conditions:

          -  RMS global buffers are enabled on some files.

          -  Many processes are terminated with $delprc (e.g.,  STOP/ID)
             when files are still open.

          -  The application is restarted after the process terminations
             without rebooting the system.


         The symptom for this problem is that during the restart of  the
         application,  a  process enters a tight loop in executive mode.
         Once encountered, a system reboot  is  required  to  clear  the
         problem.

         Images Affected:

          -  [SYS$LDR]RMS.EXE

          -  [SYSLIB]SDARMS$SHARE.EXE

      o  RMS fix for inconsistent secondary key index structure.

         Any application that does a lot of  deleting  or  does  updates
         that change a no duplicate secondary key value to another value
         in an indexed file is a potential candidate for this problem.

         An ANALYZE/RMS_FILE of the indexed file reports  the  following
         error for a secondary key:

           "Index bucket references missing data bucket with VBN nnn"

         The problem may be  that  the  secondary  index  structure  has
         duplicate  index  value  entries  and  there  should  never  be
         duplicates in the index  structure.   If  the  secondary  index
         allows  a  binary  search  (is  uncompressed), records could be
         hidden using an exact secondary key lookup.

         This   problem   results   from   the   entire   space    being
         inappropriately  reclaimed  for the physically last SIDR record
         in some secondary  data  bucket  which  contains  only  deleted
         entries.

         This problem is restricted to an indexed file with a  secondary
         key  that  allows no duplicates.  The primary key contents will
         be intact and correct, and a convert of the file  will  rebuild
         the secondary indexes and leave the file in a consistent state.

         Images Affected:

          -  [SYS$LDR]RMS.EXE


      o  Fix to prevent the CONVERT/RECLAIM utility  from  producing  an
         inconsistent  index  structure  in  an  indexed  file  during a
         reclamation.

         An ANALYZE/RMS_FILE reports the following error:

           "Index bucket references missing data bucket with VBN nnn"

         A level 1 index record associated with a data (level 0)  bucket
         that was reclaimed was not removed from the index bucket, as it
         should have been.

         It is extremely difficult to  detect  in  advance  of  doing  a
         convert/reclaim  whether  an  indexed  file  is vulnerable if a
         reclaim were applied to it.  For example, one condition is that
         one  of  the initial level 1 index buckets associated with data
         buckets  eligible  for  reclamation  has  some  condition  (for
         example, only one index record) that will cause a rollback of a
         removed index record during a reclamation.

         Without the fix, doing a full  convert  (without  the  /RECLAIM
         qualifier) ensures avoiding this problem.

         Images Affected:

          -  [SYSEXE]RECLAIM.EXE                

          -  [SYSEXE]CONVERT.EXE

          -  [SYSLIB]CONVSHR.EXE


      o  Fix to the CONVERT utility to prevent the  signal  of  a  fatal
         read  error  (CONV-F-READERR)  with  an  RMS-S-NORMAL secondary
         status when callable  convert  is  invoked  within  a  threaded
         application.   This  correction  prevents  the  erroneous error
         signal when the end of the input file is reached.

         Although callable convert is not a thread safe application,  it
         is  possible  to  invoke  the  callable interface from within a
         single instance within a single thread.

         Images Affected:

          -  [SYSEXE]CONVERT.EXE

          -  [SYSLIB]CONVSHR.EXE


      o  Fix to the CONVERT utility to  prevent  a  convert  which  uses
         either  network  or  tape  input  from creating an empty output
         indexed file.

         Images Affected:

          -  [SYSEXE]CONVERT.EXE

          -  [SYSLIB]CONVSHR.EXE




57  PROBLEMS ADDRESSED IN VMS73_RPC-V0100 KIT


      o  When a large number of ACMSxp Processing servers are stopped
         and re-started several times in a loop, DCE goes into a hang
         state.

         Images Affected:

          -  [SYSEXE]DCE$DCED.EXE


      o  On cancellation of an RPC-call, the BG devices (Sockets) that
         were allocated are not released.  Several such RPC call
         cancellations can result in a pileup of BG devices leading to a
         resource leak.

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  A memory leak is encountered in DCE/RPC when DCOM is functional
         in unauthenticated mode.

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  Under load, the DCE$DCED process terminates with the following
         error"

         (socket) rpc_socket_disp_select
         *** FATAL ERROR at SOCKDISPATCH.C;1\3755 ***

         %CMA-F-EXCCOP, exception raised; VMS condition code follows
         SYSTEM-F-OPCCUS,opcode reserved to customer
         fault at PC=00000000007043A8,
         PS=0 000001B
         %SYSTEM-F-ABORT, abort


         Images Affected:

          -  [SYSLIB]DCE$SOCKSHR_IP.EXE


      o  The login context specific to application processes expires
         immediately after starting ACMSxp TP system.  The TP System
         makes use of credentials obtained after a dce_login with
         "acmsxp_svr" as the principal name.

         Klist fails with the following error:

         No DCE identity available:  No currently established network
         identity for which context exists (dce / sec)

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  When a command procedure containing dce_login and ACMSxp
         commands is executed in an infinite loop, the DCE$DCED process
         aborts with a SYSTEM-F-ACCVIO error.

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  DCE V3.0 RPC Only configuration fails on systems with TCPWARE
         as the IP product.  The configuration program terminates
         abnormally.

         Images Affected:

          -  [SYSMGR]DCE$RPC_STARTUP.COM


      o  There was a case where a NULL pointer check was not being made
         in RPC Runtime code.  The new image takes care of this problem.

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  When a call to rpc_binding_from_string_binding fails, the
         subsequent calls to this function hang forever.  The new RPC
         Runtime library fixes the bug in
         "rpc_binding_from_string_binding".

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  When running DCOM applications between Windows 2000 and VMS
         systems, several RPC_CN_CREATE_AUTH_INFO messages are logged
         into the DCOM$RPCSS.OUT file leading to exhaustion of disk
         space.  This problem has now been resolved in the new image.
         User will need to define a logical "DCE_DISABLE_LOGGING" to 1
         either system or process wide for disabling the error messages.

         $ DEFINE/SYSTEM/EXEC DCE_DISABLE_LOGGING 1

         or

         $ DEFINE DCE_DISABLE_LOGGING 1

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  Failure to detect or ping an active Windows 2000 Client, while
         running Authenticated DCOM between a Windows 2000 and OpenVMS
         System, would cause the DCOM Server applications to timeout and
         run down after a period of about 10 minutes.

         Several "RPC_CN_AUTH_VFY_CLIENT_REQ" error messages appear in
         DCOM$RPCSS.OUT file in intervals of 2 minutes.

         2001-10-02-17:01:58.468-04:00I0.629 PID#330 ERROR rpc auth
         CNSASSM.C;1 4654 0x01eb9740 RPC_CN_AUTH_VFY_CLIENT_REQ on
         server failed:  invalid handle (dce /rpc)

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  The serviceability logging feature does not log the RPC
         information into the log files, though it creates the file.

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  RPC Fatal Exceptions are reported in DCOM$RPCSS.OUT when
         running DCOM applications, from Windows 2000, after a new
         login.

         DCOM$RPCSS process reports the following exception in the OUT
         file

         2002-04-18-15:04:17.604-04:00I0.113 PID#21370 FATAL rpc 
         recv CNRCVR.C;5
         563 0x015a5740
             (rpc_cn_network_receiver) Unexpected exception was raised


         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  DCE client example programs located in
         [SYSHLP.EXAMPLES.DCE.RPC], generated using the IDL "-trace
         log_manager" option, access violate.  The access violation
         occurs when the symbol RPC_LOG_FILE is defined.

              %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
              address=000000000000 0000, PC=0000000000239F68, PS=0000001B


         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  According to the OSF documentation, when a user defined
         authorization function returns false, the status value from the
         user supplied function is to be returned to the client.  The
         RPC runtime always returns status "rpc_s_mgmt_op_disallowed"
         when the user function returns false.

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE

      o  Cannot configure and start an RPC only configuration on DCE
         V3.0.  Running uuidgen results in the error:

            $ run sys$system:dce$uuidgen
            %UUIDGEN-F-RPC_MESSAGE, Received Error Status: "no IEEE
            802 hardware address"


         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  kdestroy does not delete the credential files at
         DCE$LOCAL:[VAR.SECURITY.CREDS]

         Images Affected:

          -  [SYSLIB]DCE$LIB_SHR.EXE


      o  During startup, whenever a client application imports the
         binding information from the name service database, using the
         rpc call rpc_ns_binding_import_next( ), if there are less than
         thirteen free event flags, the RPC call fails with the 'name
         service unavailable' error.

         Images Affected:

          -  [SYSLIB]DCE$SOCKSHR_IP.EXE




58  PROBLEMS ADDRESSED IN VMS73_RTPAD-V0100 KIT


      o  When running RTPAD, a process can hang in LEF state

         Images Affected:

          -  [SYSEXE]RTPAD.EXE




59  PROBLEMS ADDRESSED IN VMS73_SHADOWING-V0200 KIT


      o  A system can experience many  MountVerifcation  messages  occur
         with no apparent cause and no errors reported.  There is no way
         to identify what is causing these messages

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


      o  In a multi-node cluster, some cluster  members  may  hang  when
         accessing a shadowset if:

          o  The shadowset being accessed has multiple members.

          o  All the shadowset members are local to one of  the  cluster
             nodes.

          o  All the shadowset members  are  being  MSCP-served  by  the
             local node to the other cluster members.

          o  The local node goes down and  remains  down  for  at  least
             MVTIMEOUT seconds.


         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


      o  On multiple member shadow sets  greater  than  18  Gigabyte  in
         size,  if  the  port  driver  returns  an  SS$_DATACHECK  for a
         IO$_WRITEPBLK, the wrong LBNs will be written by the  shadowing
         driver.  This could lead to data corruption.

         Images Affected:

          -  [SYS$LDR]SYS$SHDRIVER.EXE


      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




60  PROBLEMS ADDRESSED IN VMS73_SYS-V0500 KIT


      o  On a multi-processor machine, in a small cluster, when creating
         or  updating  a clusterwide logical name, a process may hang in
         RWSCS state.

         Images Affected:

          -  [SYS$LDR]SYS$CLUSTER.EXE


      o  The  system  can  crash   with   a   BADDALRQSZ   bugcheck   in
         EXE$DEANONPGDSIZ_C.   In  some,  but not all cases, the current
         process is CLUSTER_SERVER.  In cases where the current  process
         is  not  CLUSTER_SERVER,  the  stack  will  have  addresses  in
         EXE$CSP_BRDCST and EXE$ALLOC_CSD.

         Images Affected:

          -  [SYS$LDR]SYS$CLUSTER.EXE


      o  F$GETSYI('RAD_MAX_RADS',node) fails to get the information from
         the  specified  node.  Instead, the command returns information
         from the current node the command is executing on.

         Note that with OpenVMS  versions  before  V7.3-1,  RAD_MAX_RADS
         will  return 1 if there is no RAD support, and will return 8 no
         matter how many QBBs are physically present.   This  limitation
         was documented in the V7.2-1H1R New Features and Release Notes,
         June 2000, section 3.5.6.1.

         Images Affected:

          -  [SYS$LDR]SYSGETSYI.EXE


      o  The system can crash with a FILCNTNONZ bugcheck.

         CrashDump Summary
         -----------------
         Bugcheck Type:     FILCNTNONZ, Open file count nonzero
                            after process rundown
         Current Image:     
         Failing PC:        FFFFFFFF.D269A360
                            PROCESS_MANAGEMENT+3C360
         Failing PS:        18000000.00000000
         Module:            PROCESS_MANAGEMENT (Link Date/Time:
                            18-OCT-2000 07:01:30.44)
         Offset:            0003C360


         Images Affected:

          -  [SYS$LDR]IO_ROUTINES.EXE

          -  [SYS$LDR]IO_ROUTINES_MON.EXE

          -  [SYS$LDR]SYS$CLUSTER.EXE


      o  The system can crash with a CWLNMERR bugcheck.  The failing  PC
         is in the LOGICAL_NAMES executive image.

         Images Affected:

          -  [SYS$LDR]LOGICAL_NAMES.EXE

          -  [SYS$LDR]LOGICAL_NAMES.STB


      o  A program using C signals can be  aborted  with  the  condition
         code set to the C signal value.

         Images Affected:

          -  [SYS$LDR]EXCEPTION.EXE

          -  [SYS$LDR]EXCEPTION_MON.EXE


      o  The system can crash  with  an  SSRVEXCEPT,  Unexpected  system
         bugcheck at EXE$IO_PERFORM_C+00650

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:    SSRVEXCEPT, Unexpected system
                           service exception
         Current Process:  ORA_P10111B1238
         Current Image:    $1$DGA92:[A_ORACLE.ORACLEV7336.RDBMS]SRV.EXE
         Failing PC:       FFFFFFFF.800CBEB0
                           EXE$IO_PERFORM_C+00650
         Failing PS:       30000000.00000203
         Module:           IO_ROUTINES (Link Date/Time:
                           5-NOV-2001 11:49:25.01)
         Offset:           00017EB0

         Failing Instruction:
         EXE$IO_PERFORM_C+00650: LDQ  R18,#X0108(R18)\


         Images Affected:

          -  [SYS$LDR]IO_ROUTINES.EXE

          -  [SYS$LDR]IO_ROUTINES_MON.EXE


      o  An SSREXCEPT bugcheck in MMG_STD$IOLOCK_BUF if it must fault in
         the affected page.

         Section  2.2.1  of  the  OpenVMS  Alpha  Guide   to   Upgrading
         Privileged  Code  Applications describes how device drivers can
         lock  down  multiple  I/O  buffers   using   IRPEs   with   the
         EXE_STD$READLOCK,    WRITELOCK,    or    MODIFYLOCK   routines.
         Unfortunately, when an  IRPE  was  passed  in  and  the  buffer
         required  a  page  fault  this code used the IRP$PS_FDT_CONTEXT
         offset on the IRPE, which is only valid on an IRP.

         The correction for this problem is to  delay  the  use  of  the
         IRP$PS_FDT_CONTEXT  cell  until  after the original IRP pointer
         has been restored by a call to the error call back routine.

         Images Affected:

          -  [SYS$LDR]IO_ROUTINES.EXE

          -  [SYS$LDR]IO_ROUTINES_MON.EXE

          -  [SYS$LDR]IO_ROUTINES.STB

          -  [SYS$LDR]IO_ROUTINES_MON.STB


      o  If there is a lot of cluster-wide $GETJPI activity,  a  process
         may hang waiting for the completion of an RMS $FLUSH operation.
         The I/O request resulting from this may  wait  forever  because
         the IOSB is not filled in.

         Images Affected:

          -  [SYS$LDR]PROCESS_MANAGEMENT.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE


      o  A system that supports NUMA and has  RAD_SUPPORT  enabled,  can
         crash  with  an  INVEXCEPTN  bugcheck  when  the swapper is the
         current  process.    The   failing   PC   is   at   or   around
         MMG$WRTMFYPAG_C+006E4.

         Images Affected:

          -  [SYS$LDR]SYS$VM.EXE


      o  If a "space" pattern string  is  combined  with  an  NEQ  match
         qualifier,  the  expected  results of all processes will not be
         returned.

         Images Affected:

          -  [SYS$LDR]PROCESS_MANAGEMENT.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT.STB

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


      o  Under some circumstances lookup of a device may fail.   If  the
         system  doing the lookup has a zero allocation class specified,
         and attempts  to  access  an  MSCP-served  disk  by  using  the
         NODE$DUA  form, the access may fail because the device will not
         be found.

         This can be  seen  in  the  following  SET  VOLUME/REBUILD  DCL
         example   (SHOW  DEVICE  fields  have  been  edited  for  space
         reasons).

         $ SHOW DEVICE $8$DUA10

         Device               Device           Error    Volume
         Name                 Status           Count    Label
         $8$DUA10: (UTRAMP)   Mounted alloc        0    TEST1

         $ WRITE SYS$OUTPUT F$GETDVI("$8$DUA10:","EXISTS")
           TRUE
         $
         $ WRITE SYS$OUTPUT F$GETDVI("$8$DUA10:","ROOTDEVNAM")
           _UTRAMP$DUA10:
         $
         $ WRITE SYS$OUTPUT F$GETDVI("$8$DUA10:","DEVNAM")
           _UTRAMP$DUA10:
         $
         $ WRITE SYS$OUTPUT F$GETDVI("_utramp$dua10:","EXISTS")
           FALSE
         $
         $ SET VOLUME/REBUILD $8$DUA10:
           %SET-E-NOTSET, error modifying _UTRAMP$DUA10:
           -RMS-F-DEV, error in device name or inappropriate
           device type for operation
           %SET-E-NOTSET, error modifying _UTRAMP$DUA10:
           -SYSTEM-W-NOSUCHDEV, no such device available

         A lookup via the runtime library function LIB$FIND_IMAGE_SYMBOL
         will also show the problem.

         Images Affected:

          -  [SYS$LDR]IO_ROUTINES.EXE

          -  [SYS$LDR]IO_ROUTINES_MON.EXE


      o  PWRK$STREAMSOS_V7.EXE is a big file, about 1760 blocks in size.
         If this file has become very fragmented after installation then
         Advanced server startup may fail  with  a  SS$_BADPARAM  error.
         This  can  occur if PWRK$STREAMSOS_V7.EXE is heavily fragmented
         and has multiple file headers (the following example  has  been
         modified for space reasons):

         $ @sys$startup:pwrk$startup
         The file server will use DECnet, TCP/IP.
         Advanced Server mail notification will use DECnet.
         %SYSTEM-F-BADPARAM, bad parameter value
         %TRACE-F-TRACEBACK, symbolic stack dump follows

         image    module     routine       line
         PWRK$LOADSTREAMS_V7 LOAD  main    7822

                rel PC           abs PC
           000000000000213C 000000000003213C

         image    module     routine       line
         PWRK$LOADSTREAMS_V7 LOAD  __main  0

                rel PC           abs PC
           0000000000000070 0000000000030070

         image    module     routine       line
                                           0
                rel PC           abs PC

           FFFFFFFF802653B4 FFFFFFFF802653B4


         Images Affected:

          -  [SYS$LDR]SYSLDR_DYN.EXE


      o  The system can crash with a SSRVEXCEPT bugcheck when  an  image
         exits  before  the  $BRKTHRU  has been delivered to some of its
         targets.

         Crash Dump Summary:
         -------------------
         Bugcheck Type:     SSRVEXCEPT, Unexpected system
                            service exception
         Current Process:   SDNCC_MBX_MAIN
         Current Image:
         Failing PC:        FFFFFFFF.98B56AAC    IO_ROUTINES+46AAC
         Failing PS:        00000000.00000000
         Module:            IO_ROUTINES (Link Date/Time:
                            17-MAR-2001 03:30:01.24)
         Offset:            00046AAC

         Signal Array:            64-bit Signal Array:
         Arg Count    = 00000005  Arg Count   =          00000005
         Condition    = 0000000C  Condition   = 00000000.0000000C
         Argument #2  = 00000000  Argument #2 = 00000000.00000000
         Argument #3  = 006C41D0  Argument #3 = 00000000.006C41D0
         Argument #4  = 98B56AAC  Argument #4 = FFFFFFFF.98B56AAC
         Argument #5  = 00000000  Argument #5 = 00000000.00000000

         Failing Instruction:
         IO_ROUTINES+46AAC:      LDL     R6,(R7)


         Images Affected:

          -  [SYS$LDR]IO_ROUTINES.EXE

          -  [SYS$LDR]IO_ROUTINES.STB

          -  [SYS$LDR]IO_ROUTINES_MON.EXE

          -  [SYS$LDR]IO_ROUTINES_MON.STB


      o  Entering an empty path into a SET  DEVICE/SWITCH/PATH  command,
         such as:

                SET DEVICE/SWITCH/PATH =""

         will cause the  system  to  bugcheck.   The  SET_DEVICE  system
         service used with a zero path length will also cause the system
         to crash.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   SYSTEM
         Current Image:     $1$DGA100:[SYS7.SYSCOMMON.]
                            [SYSEXE]SET.EXE
         Failing PC:        FFFFFFFF.803A7050
                            MPDEV$MANUAL_SWITCH_C+00290
         Failing PS:        10000000.00000803
         Module:            MULTIPATH (Link Date/Time:
                            18-JUN-2002 08:04:33.18)
         Offset:            00001050

         Stack Pointers:
         KSP = 00000000.7FFA1BA8   ESP = 00000000.7FFA6000
         SSP = 00000000.7FFAC100   USP = 00000000.7AE9B5B0

         Failing Instruction:
         MPDEV$MANUAL_SWITCH_C+00290: LDL R17,#X0010(R6)

         Images Affected:

          -  [SYS$LDR]MULTIPATH.EXE

          -  [SYS$LDR]MULTIPATH.STB

          -  [SYS$LDR]MULTIPATH_MON.EXE

          -  [SYS$LDR]MULTIPATH_MON.STB


      o  If a process uses $GETJPI  to  request  rightslist  information
         about  itself  then  the  information  appears  to  be correct.
         However, if another process  uses  $GETJPI  to  get  rightslist
         information  about  that  same  process  then  the  information
         returned is incorrect.

         Images Affected:

          -  [SYS$LDR]PROCESS_MANAGEMENT.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT.STB

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


      o  Lock manager and nonpaged pool usage may increase over time due
         to  a  memory  leak of lock blocks (LKB) and AST control blocks
         (ACB64).   This  lock  manager  leak  only  occurs  under  very
         specific circumstances which are not that common.  The specific
         circumstances are the $DEQ of  a  process  based  lock  with  a
         pending completion AST that has not yet been delivered.

         Images Affected:

          -  [SYS$LDR]LOCKING.EXE

          -  [SYS$LDR]LOCKING.STB


      o  A call to SYS$GETSYI to return system rights will  only  return
         the  first  right  in  the  rightslist,  regardless of how many
         rights are in the list.

         Images Affected:

          -  [SYS$LDR]SYSGETSYI.EXE


      o  Use of SPAWN or DCL PIPE commands result in the increase of the
         process'  PAGFILCNT  (JIB$L_PGFLCNT).   The  more SPAWN or PIPE
         activity, the higher the PAGFILCNT grows.

         Images Affected:

          -  [SYS$LDR]SHELL8K.EXE


      o  If a global section follows a process  section  in  process  P0
         space  with  the same section index value, the system can crash
         with a WSLXVANMAT bugcheck during image rundown.

         Crash Information:
         ------------------
         Bugcheck Type: WSLXVANMAT, Working set list entry
                        does not match VA
         Failing PC:    FFFFFFFF.8016FEF0    SYS$VM+25EF0
         R1  =  00000000.00000000


         Images Affected:

          -  [SYS$LDR]SYS$VM.EXE

          -  [SYS$LDR]SYS$VM.STB


      o  Multiprocessors making heavy use of RMS  global  buffers  could
         encounter  a  variety  of system crashes related to a corrupted
         system buffer object list, PCB$Q_BUFOBJ_LIST off of the  system
         PCB  (process  control block).  These could include things such
         as:

          o  SSRVEXCEPTN at MMG_STD$INSERT_BOD_C+2C

          o  INVEXCEPTN at EXE$DELETE_BUFOBJ_C+1C0

          o  Nonpaged pool corruption involving BOD  sized  packets  and
             lists

          o  CPUSPINWAIT due to pool corruption with TQE list

          o  Global Buffered File access getting SYS-F-IVLOCKID errors


         Images Affected:

          -  [SYS$LDR]SYS$VM.EXE

          -  [SYS$LDR]SYS$VM.STB


      o  When the lock manager is unable to obtain  physical  memory  to
         allocate  an  RSB,  the  error  path  to return an insufficient
         memory error may result in a system crash.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while
                            above ASTDEL
         Failing PC:        FFFFFFFF.80184888
                            RSDM_OSR_PREPROCESS_C+00658            
         Failing PS:        18000000.00000804
         Module:            LOCKING  (Link Date/Time:
                            28-MAR-2002 09:11:25.76)
         Offset:            00004888

         Failing Instruction:
         RSDM_OSR_PREPROCESS_C+00658: LDL R23,#X00C0(R5)


         Images Affected:

          -  [SYS$LDR]LOCKING.EXE

          -  [SYS$LDR]LOCKING.STB


      o  A process can exit with the status SYS$_UNWIND (920).  If  this
         is  a  detached  process,  this error status can be seen in the
         accounting report by executing the command:

            $ account /since=time/before=time

         where time is the  time  the  detached  process  exited.   This
         problem  can  affect  Oracle 9i RAC LMS processes such that the
         Oracle instance crashes with the error ORA-00484.

         Images Affected:

          -  [SYS$LDR]EXCEPTION.EXE

          -  [SYS$LDR]EXCEPTION.STB

          -  [SYS$LDR]EXCEPTION_MON.EXE

          -  [SYS$LDR]EXCEPTION_MON.STB


      o  The symptoms of this problem can take several different  forms,
         including  exception  bugchecks  and  forced  crashes  of  hung
         systems.      Crashes     have     occurred     at     PC     =
         PROCESS_MANAGEMENT+0AAF8   =   SCH$ONE_SEC_C+00258   in  module
         [SYS]RSE and at PC = LOCKING+0ADE0 =  LCK$QUEUEWAIT_C+00050  in
         module [SYS]SYSENQDEQ.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     OPERCRASH, Operator forced system crash
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.8013813C    SCH$CLASS_IDLE_C+000BC
         Failing PS:        00000000.00000003
         Module:            PROCESS_MANAGEMENT    (Link Date/Time: 28-MAR-2002
         14:21:36.4

         7)
         Offset:            0003213C

         Failing Instruction:
         SCH$CLASS_IDLE_C+000BC:         CMPLE           R2,#X3F,R7


         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     OPERCRASH, Operator forced system crash
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.92637FC8
         Failing PS:        00000000.00001504
         Module:            
         Offset:            00000000

         Failing Instruction:
         FFFFFFFF.92637FC8:      BR       R31,#XFFFF9F


         Images Affected:

          -  [SYS$LDR]PROCESS_MANAGEMENT.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT.STB

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE




61  PROBLEMS ADDRESSED IN VMS73_SYS-V0400 KIT


      o  V7.3 nodes do not correctly handle Quorum  Disks.   The  issues
         can  result  in either CLUEXIT bugchecks or numerous connection
         manager console messages:

             %CNXMAN, Proposing modification of quorum or quorum disk
             membership

         Any cluster with a quorum disk and  V7.3  nodes  requires  this
         fix.

         Images Affected:

          -  [SYS$LDR]SYS$CLUSTER.EXE


      o  SDA can ACCVIO when the SHOW LOCK/POOL command is issued.

           SDA> SHOW LOCK/POOL/SUMMARY
            %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
            address=0000000000678472, PC=0000000000144070, PS=0000001B


         Images Affected:

          -  [SYSLIB]SDA$SHARE.EXE


      o  Doing I/O on a multipath device, when the  current  path  is  a
         secondary,  results  in  an  increase in the UCB$L_OPCNT in the
         primary  as  well  as  the  current  path  UCB.   Although  the
         UCB$L_OPCNT  in the secondary grows faster than in the primary,
         the UCB$L_OPCNT in the primary should not be changing  (except,
         at  most  by  once  per  second  for  polling.)  This is easily
         observed when doing a DIR/SIZE on the system disk.

         A number of customers and third-parties rely on these  counters
         to  be  accurate  in  their  performance  and capacity planning
         tools.

         Images Affected:

          -  SYS$LDR]IO_ROUTINES.EXE

          -  SYS$LDR]IO_ROUTINES_MON.EXE

          -  SYS$LDR]IO_ROUTINES.STB

          -  SYS$LDR]IO_ROUTINES_MON.STB


      o  The Lock Manager can deliver a blocking AST to the system owned
         locks incorrectly.  The window of opportunity for this to occur
         is very small, but if it happens, the system will  often  crash
         with an Invalid exception error.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     SSRVEXCEPT, Unexpected system service
                            exception
         Failing PC:        FFFFFFFF.802059E8    XQP$FCBSTALE_C
         Failing PS:        00000000.00000000
         Module:            F11BXQP
                            (Link Date/Time: 17-MAR-2001 03:16:47.08)
         Offset:            0000D9E8


         Images Affected:

          -  [SYS$LDR]LOCKING.EXE


      o  During installation of an OpenVMS ECO kit,  the  names  of  the
         installed         images         are         written         to
         SYS$COMMON:[SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT.    These    file
         names  should  be  written with _OLD appended to the end of the
         filename along with the name of the kit.   The  VMS73_SYS-V0300
         ECO kit did not do this editing correctly.
         When upgrading  from  V7.3  to  a  later  version  of  OpenVMS,
         operating system files from the previous version of OpenVMS are
         deleted.  The above file name errors will cause  old  operating
         system  files  to  be left on the system after the upgrade.  In
         addition, users will see multiple instances  of  the  following
         installation warning message during the upgrade:

           [SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT
           %UPGRADE-W-NOTOLD2, does not have "_OLD" at end
           %UPGRADE-W-NOTOLD2, file not deleted


         This      change      corrects      the      filenames       in
         [SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT.

         Images Affected:

          -  [SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT




62  PROBLEMS ADDRESSED IN VMS73_SYS-V0300 KIT


      o  The following command should change the path to the disk:

           $SET DEVICE/SWITCH/PATH=   


         Sometimes it does not.

         Images Affected:

          -  [SYS$LDR]MULTIPATH.EXE

          -  [SYS$LDR]MULTIPATH.STB


      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  On Alphaserver GS-series machines running OpenVMS  V7.3,  after
         several console messages indicating pool expansion failure, the
         system  may  hang,  or  crash  with  CPUSPINWAIT  or  CPUSANITY
         bugchecks.

         Images Affected:

          -  [SYS$LDR]SYSTEM_PRIMITIVES.EXE

          -  [SYS$LDR]SYSTEM_PRIMITIVES_MON.STB

          -  [SYS$LDR]SYSTEM_PRIMITIVES.EXE

          -  [SYS$LDR]SYSTEM_PRIMITIVES_MON.STB


      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  The system can crash with an INVEXCEPTN, Exception while  above
         ASTDEL bugcheck:

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   SWAPPER
         Current Image:     
         Failing PC:        FFFFFFFF.80115E0C
                            SCH$REPORT_EVENT_C+0082C
         Failing PS:        10000000.00000800
         Module:            PROCESS_MANAGEMENT
                            (Link Date/Time:  6-JUN-2001 17:31:27.58)
         Offset:            00009E0C


         Images Affected:

          -  [SYS$LDR]PROCESS_MANAGEMENT.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT.STB

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


      o  MOUNT and Mount Verification sanity checks have been relaxed to
         correct the following issues:

          o  A MOUNT/NOWRITE command on a disk on one cluster  will  now
             work  correctly  even  if the disk is mounted with a /WRITE
             qualifier on another  cluster  in  the  SAN  (Storage  Area
             Network).   Previously, depending on the order in which the
             mounts were executed, the mount would fail with  the  error
             message:

             DIFVOLMNT - different volume already mounted on this
                         device.


         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  Queue and other clusterwide operations fail with a SS$_BADPARAM
         bugcheck when a COE-baselevel node is in the cluster.

         Images Affected:

          -  [SYSLIB]SECURESHR.EXE

          -  [SYSLIB]SECURESHRP.EXE


      o  When  called  from  exec  mode,  ACCVIOs  are   returned   from
         SYS$PERSONA_CREATE.

         Images Affected:

          -  [SYSLIB]SECURESHR.EXE

          -  [SYSLIB]SECURESHRP.EXE


      o  A  SSRVEXCEPT  system  crash  can  occur   when   a   call   to
         $PERSONA_CREATE  is  made  for  an  account  with  a [0,0] UIC.
         (Though it is possible to create such an account,  the  account
         is invalid on VMS systems).

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     SSRVEXCEPT, Unexpected system service
                            exception
         Current Process:   BUILDER
         Failing PC:        FFFFFFFF.801CB968    
                            NSA$REFERENCE_RIGHTS_CHAIN_C+00008
         Failing PS:        10000000.00000201
         Module:            SECURITY    (Link Date/Time:
                            5-AUG-2001 01:12:10.86)
         Offset:            0000B968

         Images Affected:

          -  [SYS$LDR]SECURITY.EXE

          -  [SYS$LDR]SECURITY_MON.EXE


      o  On a system that contains a CPU numbered 31, CPU #31 can run  a
         thread  even  if  that  thread has specified, either by setting
         required capabilities or hard affinity, that  it  must  run  on
         another  CPU.   Thus,  some  functions  which  must  run on the
         primary CPU may occasionally be run on CPU #31.  There need not
         actually  be  31  CPUs.   This  bug can cause problems with CPU
         power down/up of any CPU,  with  CPU  assignment  between  soft
         partitions, or garbled or missing console output.

         Images Affected:

          -  [SYS$LDR]PROCESS_MANAGEMENT.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT.STB

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


      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


      o  A system may have one  of  the  following  problems  caused  by
         possible corruption of the process scheduling queues and/or the
         SCH$GQ_PFWQ queue:

          o  Processes stuck in  CUR  but  on  the  PFW  queue  and  not
             executing

          o  Processes stuck in PFW on the PFW queue and not executing

          o  The PFW queue merged in with a COM queue, usually resulting
             in an INCON_SCHED or a CPUSPINWAIT bugcheck.

          o  An INVEXCEPTN at SCH$QEND_C+38 trying to  access  the  cell
             CTL$GL_REPORT_USER_FAULTS.

         Images Affected:

          -  [SYS$LDR]SYS$VM.EXE


      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  non-COE  compliant  OpenVMS  systems  when
         attempting  to display the rights identifiers of a process that
         is granted a valid GID COE identifier.  The following commands,
         lexicals,   (and   respective   system   services),  cause  the
         %SYSTEM-F-IVIDENT system message to be displayed instead of the
         text translation of this COE GID IDENTIFIER:

         1.  F$GETJPI("PID_xxx","PROCESS_RIGHTS")

         2.  F$GETJPI("PID_xxx","RIGHTSLIST")

         3.  $ SHOW PROCESS/ALL

         4.  $ SHOW PROCESS/RIGHTS


         Images Affected:

          -  [SYS$LDR]SECURITY.EXE

          -  [SYS$LDR]SECURITY_MON.EXE

          -  [SYS$LDR]SECURITY.STB

          -  [SYS$LDR]SECURITY_MON.STB


      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  The sys$crmpsc_gdzro_64() returns a  numeric  value  indicating
         that memory is reserved when it is not.

         Images Affected:

          -  [SYS$LDR]SYSTEM_PRIMITIVES.EXE

          -  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE

          -  [SYS$LDR]SYSTEM_PRIMITIVES.STB

          -  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB

          -  [SYS$LDR]SYS$VM.EXE


      o  If a RADCHECK is  done  on  a  system  running  the  DECwindows
         Display  Server  (or  possibly other images that memory map I/O
         space or other pages that do not appear in  the  PFN  database)
         the  system  will  crash  with  an  invalid exception bugcheck.
         Analysis will show the exception is an ACCVIO in image  SYS$VM,
         image MMG$RADCHECK_PROCESS.

         Images Affected:

          -  [SYS$LDR]SYS$VM.EXE


      o  A system can crash with a REFCNTNEG,  PFN  reference  count  is
         negative  bugcheck.   The  PFN database element being mapped is
         pointed to by R15, so, the SDA command:

            FORMAT @^QR15/TYPE=PFN

         can be used to examine the value in  the  PFN$W_BO_REFC  field.
         If  it is greater than or equal to 8000, 32768 decimal, this is
         the cause of the bugcheck.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     REFCNTNEG, PFN reference count is negative
         Current Process:   ORA_CLUS_DBWR
         Current Image:     DSA2:[ORACLE.CODE_V7344.RDBMS]SRV.EXE
         Failing PC:        FFFFFFFF.801131C8
                            MMG_STD$DELBUFOBJPAGES_C+00678
         Failing PS:        04000000.00000800
         Module:            SYS$VM
                            (Link Date/Time: 29-DEC-1999 04:29:36.63)
         Offset:            000251C8

         Images Affected:

          -  [SYS$LDR]SYS$VM.EXE


      o  On NUMA systems, at the end of the system startup, unused  PFNs
         are  released  for the exec data huge page region, and then the
         exec  code  and  resident  code  region  will  be   replicated.
         Customers  having  their  own drivers, which can be reloaded on
         the  fly,  need  to  clear  the   RELEASE_PFNS   bit   in   the
         LOAD_SYS_IMAGES  SYSGEN  parameter  to avoid releasing PFNs for
         the exec data region.  Otherwise the driver reload  fails  with
         an error.

         This change stops release of PFNs for  the  exec  data  region.
         This  allows  customers  to reload drivers on the fly and still
         get the benefit of system code replication.            

         Images Affected:

          -  [SYS$LDR]SYSLDR_DYN.EXE


      o  Connection to an Oracle server can fail:

           ORACLE error---
           ORA-01034: ORACLE not available
           ORA-27123: unable to attach to shared memory segment
           %SYSTEM-E-SECREFOVF, too many section refer
           %SYSTEM-W-UNWIND, unwind currently in progress
           %TRACE-W-TRACEBACK, symbolic stack dump follows
           %SYSTEM-W-UNWIND, unwind currently in progress


         Images Affected:

          -  [SYS$LDR]SYS$VM.EXE

          -  [SYS$LDR]IMAGE_MANAGEMENT.EXE

          -  [SYS$LDR]IMAGE_MANAGEMENT.STB

          -  [SYS$LDR]SYSTEM_PRIMITIVES.EXE

          -  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE

          -  [SYS$LDR]SYSTEM_PRIMITIVES.STB

          -  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB

          -  [SYSEXE]INSTALL.EXE

          -  [SYSLIB]IMGDMP.EXE

          -  [SYSLIB]SDA$SHARE.EXE


      o  A call to $GETJPI  to  return  information  about  the  calling
         process  could  return a SS$_NOPRIV status if that call is made
         while a persona representing a security  profile  that  differs
         from the natural persona (Persona_ID 1) is active.

         Images Affected:

          -  [SYS$LDR]PROCESS_MANAGEMENT.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT.STB

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


      o  Under the following circumstances:

          o  The system is a GS80, GS160, or GS320.

          o  The SYSGEN parameter RAD_SUPPORT has bit  2  set,  enabling
             system space replication.

          o  The SYSGEN parameter GH_RSRVPGCNT  is  set  to  a  non-zero
             value.

         The  system  can  crash  with   an   INVEXCEPTN   bugcheck   at
         LDR_STD$DEALLOC_S2_VA_C+006C4.

         Images Affected:

          -  [SYS$LDR]SYSTEM_PRIMITIVES.EXE

          -  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE

          -  [SYS$LDR]SYSTEM_PRIMITIVES.STB

          -  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.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:

          -  [SYS$LDR]SYSTEM_PRIMITIVES.EXE

          -  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE

          -  [SYS$LDR]SYSTEM_PRIMITIVES.STB

          -  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB


      o  It is possible to  sometimes  get  an  INVEXCEPTN  bugcheck  at
         SCH$QEND_C+001E0 during quantum end processing.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:    INVEXCEPTN, Exception while
                           above ASTDEL
         Current Process:
         Current Image:    
         Failing PC:       FFFFFFFF.800CFB50  SCH$QEND_C+001E0
         Failing PS:       10000000.00000804
         Module:           PROCESS_MANAGEMENT (Link Date/Time:
                           23-JAN-2001 08:37:04.46)
         Offset:            00007B50

         Images Affected:

          -  [SYS$LDR]PROCESS_MANAGEMENT.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT.STB

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


      o  If PERFMON interrupts are not turned off for PCTR0,  PCTR1  and
         PCTR2 during BUGCHECK, and on any STOP/CPU, severe hangs in the
         console can occur.  It could take a power cycle  to  clear  the
         situation.

         Images Affected:

          -  [SYS$LDR]EXCEPTION.EXE

          -  [SYS$LDR]EXCEPTION.EXE

          -  [SYS$LDR]EXCEPTION_MON.EXE

          -  [SYS$LDR]EXCEPTION_MON.STB

          -  [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE

          -  [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.EXE

          -  [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE

          -  [SYS$LDR]SYSTEM_SYNCHRONIZATION.STB

          -  [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.STB

          -  [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.STB


      o  When using the SYS$WAKE system service, if a  PID  or  username
         for  a  process  on  a remote node is specified, a SS$_IVLOGNAM
         error will be returned.

         Images Affected:

          -  [SYS$LDR]SYS$CLUSTER.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT.STB

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


      o  The  system  can  crash  with  a  INVSECURESTATE  bugcheck   at
         NSA$DEREFERENCE_RIGHTS_CHAIN_C+0008C

         Crashdump Summary Information
         -----------------------------

         Bugcheck Type:     INVSECURESTATE, Invalid state detected by
                            SECURITY subsystem
         Current Process:   YERTLE$SRV73
         Current Image:     DSA20:[SYS0.SYSCOMMON.]
                            [SYSEXE]OAFC$SERVER.EXE
         Failing PC:        FFFFFFFF.8019798C
                            NSA$DEREFERENCE_RIGHTS_CHAIN_C+0008C
         Failing PS:        30000000.00000203
         Module:            SECURITY_MON (Link Date/Time:
                            17-OCT-2001 01:01:12.57)
         Offset:            0000B98C

         Images Affected:

          -  [SYS$LDR]SECURITY.EXE

          -  [SYS$LDR]SECURITY_MON.EXE

          -  [SYS$LDR]SECURITY.STB

          -  [SYS$LDR]SECURITY_MON.STB


      o  The system can crash with a KRNLSTAKNV, Kernel stack not valid,
         bugcheck"


         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     KRNLSTAKNV, Kernel stack not valid
         Current Process:
         Current Image:     
         Failing PC:        FFFFFFFF.800243A8
                            SMP$BUGCHK_HALT_CPU_C+001F8
         Failing PS:        00000000.00001F00
         Module:            SYS$CPU_ROUTINES_2208 (Link Date/Time:
                           17-MAR-2001 03:15:26.81)
         Offset:            000163A8


         Images Affected:

          -  [SYS$LDR]PROCESS_MANAGEMENT.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE

          -  [SYS$LDR]PROCESS_MANAGEMENT.STB

          -  [SYS$LDR]PROCESS_MANAGEMENT_MON.STB




63  PROBLEMS ADDRESSED IN VMS73_SYSINI-V0100 KIT


      o  After upgrading from V7.2-1 to V7.3, a system could crash  with
         a  PROCGONE  bugcheck  during  boot.   R0 in the bugcheck would
         contain the error 1C04A, %RMS-E-DNF, directory not found.

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

         Bugcheck Type:     PROCGONE, Process not in system
         Current Process:   LANACP
         Current Image:     
         Failing PC:        FFFFFFFF.8025CB20
                            EXE$EXIT_INT_C+001E0
         Failing PS:        18000000.00000001
         Module:            IMAGE_MANAGEMENT
                            (Link Date/Time: 17-MAR-2001 03:27:48.69)
         Offset:            0000EB20


         Images Affected:

          -  [SYSEXE]SYSINIT.EXE



64  PROBLEMS ADDRESSED IN VMS73_SYSLOA-V0300 KIT


      o  A process, on a multiprocessor machine in a small cluster,  may
         hang  in  RWSCS  state  when creating or updating a clusterwide
         logical name.

         Images Affected:

          -  [SYS$LDR]SYS$CLUSTER.EXE


      o  The  system  can  crash   with   a   BADDALRQSZ   bugcheck   in
         EXE$DEANONPGDSIZ_C   following   an  attempt  to  deallocate  a
         structure whose W_SIZE offset contains 0.  In some, but not all
         cases, the current process is CLUSTER_SERVER.

         Images Affected:

          -  [SYS$LDR]SYS$CLUSTER.EXE




65  PROBLEMS ADDRESSED IN VMS73_SYSLOA-V0200 KIT


      o  The system can crash with a "LOCKMGRERR, Error detected by Lock
         Manager" bugcheck.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     LOCKMGRERR, Error detected by
                            Lock Manager
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.8032F718  LCK$SND_RMVDIR_C+00748
         Failing PS:        28000000.00000804
         Module:            SYS$CLUSTER    (Link Date/Time:
                            16-APR-2001 15:30:01.68)
         Offset:            0002B718


         Images Affected:

          -  [SYS$LDR]SYS$CLUSTER.EXE


      o  OpenVMS V7.3 nodes do not correctly handle Quorum Disks.   This
         can  result  in either CLUEXIT bugchecks or numerous connection
         manager console messages, such as:

            %CNXMAN, Proposing modification of quorum or quorum disk
            membership

         Any cluster with a quorum disk and  V7.3  nodes  requires  this
         fix.

         Images Affected:

          -  [SYS$LDR]SYS$CLUSTER.EXE


      o  After shuting down a member of a cluster, the remaining node(s)
         hang.    This  problem  occurs  only  when  Memory  Channel  is
         available and a quorum disk is present.

         Images Affected:

          -  [SYS$LDR]SYS$CLUSTER.EXE




66  PROBLEMS ADDRESSED IN VMS73_TDF-V0100


      o  Java applications that run continuously through the daylight
         savings time adjustment incur a two hour clock adjustment
         rather than a one hour clock adjustment.  The java application
         must be stopped and restarted to correct the time.

         Images Affected:

          -  [SYSEXE]JBC$JOB_CONTROL.EXE


      o  In the Southern Hemisphere when the time was moved forward at
         the October Daylight Savings Time adjustment, multithreaded
         processes went into a tight CPU loop.  Examples of applications
         showing the problem are DCPS symbiont, decevent, or anything
         using the Java runtime.  Stopping and restarting the processes
         resolved the problem.

         This problem will happen again at the next daylight savings
         time adjustment.

         Images Affected:

          -  [SYSEXE]SYS$DAYLIGHT_SAVING.EXE

          -  [SYSEXE]TDF$SET_TIMEZONE.EXE


      o  Setting the DISUSER flag on the SYSTEM account causes the login
         failure message:

           %LOGIN-F-DISUSER, account is disabled

         to be displayed when the job controller tries and retries
         creating the daylight savings time adjustment process.

         Images Affected:

          -  [SYSEXE]JBC$JOB_CONTROL.EXE




67  PROBLEMS ADDRESSED IN VMS73_XFC-V0300 KIT


      o  Multiple XFC bug fixes and enhancements have been made:

          -  Files written by a DFS client to a disk drive served by a
             cluster node can end up with stale data on the cluster
             nodes not serving the drive.

          -  CPU spinwait bugchecks Some conditions (large numbers of
             non-cached I/Os) can result in a very long internal XFC
             queue.  On very large systems, searching this queue take 30
             or more seconds.  A suggested workaround was to limit the
             XFC cache to 4 or 5 GB.  This is no longer necessary.

             XFC was inadvertently using the FILSYS and SCS spinlocks in
             the wrong order.  The MTAACP (mag tape ACP) also uses both
             spinlocks which can result in a deadlock and subsequent
             cpuspinwait bugcheck.  This problem will not show up with
             backup, but only when doing filesystem access to a tape
             drive (e.g.  copy x.x mta0:  ) and then only if the timing
             was just right.

             It was possible for a XFC file truncate processing to take
             enough time to result in a spinwait bugcheck.

          -  Volume depose speedup A volume dismount requires that all
             files in the cache for that volume be deposed from the
             cache (on the current node).  This operation was operating
             at about 1 file per second resulting in very long times to
             free memory.  In addition, the code deposed the first file
             synchronously which could cause noticeable delays for the
             dismount.

          -  Minimum cache size enforced.  XFC would allow any values
             for VCC_MAX_CACHE including zero.  The result was either
             caching being disabled cluster-wide or a memory management
             bugcheck on the local node during boot.  This fix ensures
             that about 5 MB of memory is always allocated to XFC
             allowing the node to boot (there is also a message output
             on the console).

          -  ASSERTFAIL bugcheck copying file to spooled device on
             standalone nodes.  XFC assumed that all file deletes passed
             through XFC allowing XFC to properly depose the cache.  On
             standalone nodes only, this assumption lead to XFC
             attempting to release a lock it didn't own and crashing
             with an ASSERTFAIL bugcheck.  This typically showed up
             while attempting to copy to a spooled device.  This does
             not occur on nodes in clusters.

          -  Performance data not being updated.  XFC was not calling
             routine pms_std$end_rq() prior to completing disk I/Os.
             This resulted in performance data collectors seeing I/O
             starts, but not I/O completions.

          -  Corrupt LRU queue after truncate During I/O completion, XFC
             cleans up structures associated with the I/O including
             adjusting positions of extents (ECBs) in the LRU queue.
             Occasionally, these elements have either been deallocated
             or used for another I/O which results in a bugcheck.  This
             is an extremely rare event.  It has been seen at one
             internal site almost a year ago and at 3 customer sites.

             The XFC truncate code had an implicit assumption that there
             would not be active I/Os on the file.  The code neglected
             to account for either XFC readahead I/Os or asynchronous
             I/Os issued prior to the call to truncate.  The XFC
             truncate code was completely rewritten to properly
             synchronize with concurrent I/Os to the file being
             truncated.

          -  Public counters overflow The XFC public counter used by the
             DCL command 'SHOW MEMORY/CACHE' were stored in unsigned
             longwords limiting the maximum counts to approximately 4
             billion.  These counters have been increased to unsigned
             quadwords.  In addition, the public interface to the
             internal counters (CACHE$GET_STAT()) has been enhanced to
             return up to 8 bytes of data for each of these counters.

          -  ASSERTFAIL bugchecks in XFC lock processing If a write
             happens for a file which is in read sharing mode, XFC
             attempts to convert the File Arbitration Lock (FAL) from PR
             mode (caching cluster-wide) to PW mode (caching locally
             only).  If this conversion fails, then XFC moves the FAL to
             CW mode and starts a thread to move the FAL back to a
             caching mode.  This thread is called a FAL up conversion.
             During this sequence, it was possible for a blocking AST on
             the FAL to fire.  It would also lead to a FAL up conversion
             being started.  If the timing were just right, then two FAL
             up conversions could be in progress.  One of the two would
             find the FAL in the wrong state and bugcheck (ASSERTFAIL).

          -  ASSERTFAIL in routine XfcLockIsFALHeld () or
             XfcLockReleaseFALViaEX () Under some conditions, it was
             possible that a file truncate operation could happen while
             an I/O was in progress.  The truncate operation would leave
             data in cache for the cache, but with the XFC file
             arbitration lock in a state not allowing valid data.  XFC
             crashed with an ASSERTFAIL bugcheck when this inconsistency
             was discovered.  This has been fixed by a complete rewrite
             of the XFC truncate processing.


          -  Volume and file latencies incorrectly calculated XFC
             provides statistics on average access latencies (via the
             XFC SDA extensions and the CACHE$GET_STATVOL system
             service).

             It does this by accumulating the total latency times as the
             accesses are completed and then, when the average is
             requested, dividing by the number of accesses.
             Unfortunately, the access counts include accesses for which
             the latency could not be determined (because the access
             began on one CPU and finished on another:  the per-CPU
             cycle counter is used to determine the elapse time) and,
             therefore, were not included in the accumulated latency
             value.  XFC's statistics gathering fields already include
             counts of the accesses not counted in the latency
             accumulations.  So, the change is to include those counts
             in the calculations.

          -  Improved performance of non-cached I/Os.  XFC was adding
             overhead to I/Os which weren't being cached - for example
             very large I/Os (6000 blocks).  This extra overhead has
             been removed.

          -  XFC SDA extension enhancements

             1.  Help for XFC SDA extension has been updated.

             2.  The SDA command XFC SHOW FILE command now displays the
                 file name.  In addition, the output of the SDA command
                 XFC SHOW FILE /BRIEF is sorted by volume.



         Images Affected:

          -  [SYSLIB]ALPHA_XFC$SDA.EXE

          -  [SYS$LDR]SYS$XFCACHE.EXE

          -  [SYS$LDR]SYS$XFCACHE_MON.EXE

          -  [SYSLIB]XFC$SDA.EXE

          -  [SYS$LDR]SYS$XFCACHE.DSF

          -  [SYSLIB]SYS$XFCACHE.STB




68  PROBLEMS ADDRESSED IN VMS73_XFC-V0200 KIT


      o  Because of numerous problems  reported  against  XFC  in  V7.3,
         customers  were  instructed to disable XFC for V7.3 until these
         issues could be addressed.  This kit fixes  all  problems  with
         XFC reported by customers as of 16 July 2002.  Once this kit is
         installed XFC can be safely re-enabled.  Note  that  all  these
         issues were corrected for OpenVMS V7.3-1.

         Specific issues addressed are:

         1.  Process or System hangs

              o  XFC internal structures describing cached  files  could
                 be  deleted while an active operation for that file was
                 stalled.   The  stalled  operation   would   never   be
                 restarted.   This  would result in processes being left
                 in RWAST with other processes waiting  for  release  of
                 file system locks.

              o  If a  blocking  AST  was  processed  on  the  XFC  File
                 Arbitration lock while a readahead was in progress, the
                 readahead would be dismissed, but the blocking AST  was
                 not restarted.  This would result in subsequent I/Os to
                 this file stalling.

              o  In a cluster with both VIOC and XFC nodes, XFC queues a
                 NL  (null)  to  CW  (concurrent  write) lock conversion
                 without specifying a lock  conversion  priority.   This
                 results  in  a  deadlock.   This is often seen with the
                 file  arbitration  lock  for  SYSUAF.DAT,   making   it
                 impossible to log into the cluster.

              o  Under some conditions, a readahead I/O is not  properly
                 cleaned  up  after  an  I/O completes with an error.  A
                 subsequent close of the file will hang, waiting for the
                 readahead to complete.

              o  If a file lock transition is in progress at the time  a
                 deaccess  was  started, it is possible for the deaccess
                 not to be restarted.  This results in a process hanging
                 in RWAST state.

              o  Under very low memory conditions, XFC could get into  a
                 state  in which there was not enough memory to make any
                 progress on  I/Os.   This  fix  increases  the  default
                 amount  of  memory  allocated to XFC at boot time to be
                 sufficient to make progress regardless  of  how  little
                 free memory is available at any time.

              o  The server process for  host-based  RAID  can  hang  in
                 mutex  wait  state.   This is caused by the logical I/O
                 processing of XFC not recognizing that it  is  safe  to
                 allow the logical I/O to proceed.

         2.  Stale data in files

             In a cluster, there are several situations under which  XFC
             could  leave  stale  data  in  the  cache  for a file.  The
             symptom would be that a file would appear to have different
             data when viewed from different nodes in a cluster.

              o  File truncate processing would leave data in the  cache
                 for  a  file,  and the file arbitration lock in a state
                 only appropriate for no valid data.

              o  Under some conditions, QIO write updates to files  read
                 using  paging I/O would not be seen on other nodes in a
                 cluster.


         3.  File corruption

              o  Large files copied from IDE CD drives could be corrupt.
                 This  is the result of XFC not honoring the maximum I/O
                 size specified by the driver.

              o  Updates to files on a DFS-served device are  not  being
                 seen.   The  DFS  server  bypasses  the cache for write
                 I/Os.  XFC  was  missing  these  writes  and  therefore
                 leaves stale data in the cache for these files.

              o  An example program that uses fastio to  implement  file
                 copy fails to copy the last block of a file copied from
                 a device that did not support fastio (e.g.  IDE CD or a
                 RAM disk).


         4.  System Crashes

              o  Under heavy loads, XFC would use  a  fork  block  twice
                 resulting  in  a  corrupt fork queue and a system crash
                 (typically a system service exception).

              o  If a blocking AST for a file arbitration lock fired  at
                 exactly  the  same  time as that file was being deposed
                 for dismount, then XFC would eventually  bugcheck  with
                 either  an  XFC ASSERTFAIL bugcheck or a system service
                 exception.

              o  In a cluster, XFC could retain data for  a  file  on  a
                 node  that  was  caching  the  file  when  the file was
                 deleted on a node not caching the file.  This  resulted
                 in  stale  data  in  cache  after the file was deleted.
                 Under some conditions, XFC would call the  file  system
                 with  the  old,  incorrect  highwater  mark information
                 resulting in an XQPERR bugcheck.

              o  Readahead I/Os are sometimes issued after  a  file  has
                 been  deaccessed.   If  the readahead requires either a
                 file system mapping operation or a  window  turn,  then
                 the  system  could  crash  with  either  a NOTWCBIRP or
                 STRNOTWCB bugcheck.

              o  XFC uses an uninitialized variable as the saved IPL  to
                 a  spinlock  release  routine.   On  some  systems  (in
                 particular  AS400),  this  results  in  a  machinecheck
                 bugcheck.

              o  XFC would crash attempting to do  reads  or  writes  to
                 devices not supporting fastio.


         5.  Halt during boot.

             If XFC detects system configurations that  will  not  allow
             XFC   to   run  properly,  XFC  will  halt  the  CPU  [with
             PAL_HALT()].  This  causes  CPUSPINWAIT  bugchecks  on  SMP
             systems that take extra effort to diagnose.  XFC now prints
             a  message  on  the  console  and  adjusts  the  parameters
             MPW_HILIMIT and FREEGOAL to allow booting.

         6.  Set time flushes cache for system disk.

             The $settime() system service would result in XFC  flushing
             all cached data for the system disk.

         7.  RAM disk caching state incorrect.

             By default, XFC mounts RAM disks  NOCACHE.   However,  this
             was  not happening in some circumstances.  XFC now disables
             XFC caching for locally mounted RAM disks.

         8.  RAM disk performance enhancement.

             I/O to a RAM disk is noticeably slowed when XFC  is  turned
             on  for  a  system  even if the disk were mounted /NOCACHE.
             This has now been corrected.

         9.  File sharing performance enhancement.

             If an application writes to a file open on  multiple  nodes
             in  a  cluster,  XFC  stops  caching for that file.  In the
             past, XFC would not resume caching for that  file  even  if
             all the write accessors closed the file.  XFC will now move
             a file back to caching when write accessors close the file.

        10.  Cache hit performance improvement.

             The performance of cache hits has been improved.

        11.  Spurious XFCACHE-W-DATALOSS messages to OPCOM.

             XFC incorrectly assumes that  reads  beginning  beyond  the
             file  high  water  mark  are  an integral number of blocks.
             This results in the following problems:

              o  XFCACHE-W-DATALOSS messages to OPCOM when the  XFC  I/O
                 completion  code  discovered  that  the number of bytes
                 copied did not equal the number of bytes requested.

              o  Potential corruption in user  program  space  when  the
                 bytes beyond the end of the user buffer were zeroed.


        12.  The system can crash with  an  ASSERTFAIL,  "System  ASSERT
             failure detected" bugcheck.

             Crashdump Summary Information:
             ------------------------------
             Bugcheck Type:     ASSERTFAIL, System ASSERT failure detected
             Current Process:   CTM$_0005000C
             Current Image:     $3$DKC203:[SYS1.SYSCOMMON.][SYSEXE]COPY.EXE
             Failing PC:        FFFFFFFF.802EC6E0    XFCLOCKISFALHELD_C+00D60
             Failing PS:        30000000.00000804
             Module:            SYS$XFCACHE    (Link Date/Time: 11-JUN-2002 20:07:42.49)
             Offset:            000086E0

             The bugcheck might be seen doing a backup copy operation on
             large, busy systems.  It might also be seen on memory tight
             systems doing DCL copies.


         Images Affected:

          -  [SYS$LDR]SYS$XFCACHE.EXE

          -  [SYS$LDR]SYS$XFCACHE.DSF

          -  [SYS$LDR]SYS$XFCACHE.STB

          -  [SYS$LDR]SYS$XFCACHE_MON.EXE

          -  [SYS$LDR]SYS$XFCACHE_MON.DSF

          -  [SYS$LDR]SYS$XFCACHE_MON.STB

          -  [SYSLIB]XFC$SDA.EXE




69  KIT INSTALLATION RATING:

     The following kit  installation  rating,  based  upon  current  CLD
     information,  is  provided  to  serve as a guide to which customers
     should apply this remedial kit.  (Reference attached Disclaimer  of
     Warranty and Limitation of Liability Statement)

     INSTALLATION RATING:

      1 : To be installed by all customers.



70  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 VMS73_UPDATE /SOURCE=[location of Kit]

     The kit location may be a tape drive, CD, or a disk directory that
     contains the kit.

     Additional help on installing PCSI kits can be found by typing
     HELP PRODUCT INSTALL at the system prompt


     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.



     70.1  Special Installation Instructions:

          70.1.1  SYSGEN Parameter Changes

          As  part  of  the  post  installation   processing   for   the
          VMS73_RMS-V0400  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.


          70.1.2  Scripting of Answers to Installation Questions

          During installation,  this  kit  will  ask  and  require  user
          response  to  several  questions.  If you wish to automate the
          installation of this kit and avoid having to provide responses
          to  these  questions,  you must create a DCL command procedure
          that includes the following definitions and commands:

           -  Define logical NO_ASK$BACKUP as TRUE

           -  Define logical NO_ASK$REBOOT as TRUE

           -  

              Define logical ARCHIVE_DW_MOT_MUP as TRUE if you  wish  to
              delete  the  replaced  files.   If  you  do  not  want the
              replaced files deleted (NOT recommended by Compaq), define
              this logical as FALSE.

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

                /PROD=DEC/BASE=AXPVMS/VER=V2.0


           -  De-assign the logicals assigned

          For  example,  a  sample   command   file   to   install   the
          VMS73_UPDATE-V0200 kit would be:

          $
          $ DEFINE/SYS NO_ASK$BACKUP TRUE
          $ DEFINE/SYS NO_ASK$REBOOT TRUE
          $ DEFINE/SYS ARCHIVE_DW_MOT_MUP "TRUE"
          $!
          $ PROD INSTALL VMS73_UPDATE/PROD=DEC/BASE=AXPVMS/VER=V2.0
          $!
          $ DEASSIGN/SYS NO_ASK$BACKUP
          $ DEASSIGN/SYS NO_ASK$REBOOT
          $ DEASSIGN/SYS ARCHIVE_DW_MOT_MUP
          $!
          $ exit


          NOTE:
          This kit includes the VS73_DW_MOT_MUP kit.  Defining the
          logical ARCHIVE_DW_MOT_MUP as TRUE will cause the installation
          procedure to delete the previous versions of the DECWindows
          files that this kit installs.  Because of the nature of the
          problem that the VS73_DW_MOT_MUP-V0100 kit corrects, Compaq
          recommends that the old files be deleted and not left on the
          system.  See section 11 of the file
          [SYSHLP]VMS722_UPDATE-V0100_CVRLET.TXT for more information.


          70.1.3  %INSTALL-E-NODELSHRADR Error Message

          During installation you may see the following message:

          %INSTALL-E-NODELSHRADR, unable to delete image with shareable
          address data
          -INSTALL-I-PLSREBOOT, please reboot to install a new version of
          this image

          This is not  a  cause  for  concern.   It  simply  means  that
          DECC$SHR.EXE  was  installed as a resident image, which is the
          standard configuration for OpenVMS  Alpha  systems.   The  new
          image will not take effect until the system is rebooted.



     Copyright (c) Compaq Computer Company, 2002  All  Rights  Reserved.
     Unpublished  rights reserved under the copyright laws of the United
     States.  COMPAQ, the COMPAQ logo, VAX, Alpha, VMS, and OpenVMS  are
     registered  in  the  U.S.   Patent and Trademark Office.  All other
     product  names  mentioned  herein  may  be  trademarks   of   their
     respective companies.

     Confidential computer software.   Valid  license  from  COMPAQ  are
     required  for  possession,  use,  or  copying.  Consistent with FAR
     12.211 and 12.212, Commercial Computer Software, Computer  Software
     Documentation, and Technical Data for Commercial Items are licensed
     to the U.S.  Government under vendor's standard commercial license.

     COMPAQ shall not be liable for technical  or  editorial  errors  or
     omissions  contained  herein.   The information in this document is
     provided as is without warranty of  any  kind  and  is  subject  to
     change  without notice.  The warranties for COMPAQ products are set
     forth in the express limited warranty statements accompanying  such
     products.   Nothing  herein  should be construed as constituting an
     additional warranty.

     DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY

     THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF  ANY  KIND.   ALL
     EXPRESS  OR  IMPLIED  CONDITIONS,  REPRESENTATIONS  AND WARRANTIES,
     INCLUDING ANY IMPLIED  WARRANTY  OF  MERCHANTABILITY,  FITNESS  FOR
     PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE
     EXTENT PERMITTED BY APPLICABLE LAW.  IN NO  EVENT  WILL  COMPAQ  BE
     LIABLE  FOR  ANY  LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT,
     CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER  CAUSED  AND
     REGARDLESS  OF  THE  THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH
     MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.
Files on this server are as follows:
»dec-axpvms-vms73_update-v0200--4.README
»dec-axpvms-vms73_update-v0200--4.CHKSUM
»dec-axpvms-vms73_update-v0200--4.pcsi-dcx_axpexe
privacy statement using this site means you accept its terms