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 VMS731_UPDATE-V0100 Update Alpha V7.3-1 ECO Summary
TITLE: OpenVMS VMS731_UPDATE-V0100 Update Alpha V7.3-1 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.
 


New Kit Date:       02-JUL-2003
Modification Date:  Not Applicable
Modification Type:  New Kit

Copyright (c) Hewlett-Packard Company 2003.  All rights reserved.

OP/SYS:     OpenVMS Alpha V7.3-1

COMPONENT:  System

SOURCE:     Hewlett-Packard Company

ECO INFORMATION:

     ECO Kit Name:  VMS731_UPDATE-V0100
                    DEC-AXPVMS-VMS731_UPDATE-V0100--4.PCSI
    
     ECO Kits Superseded by This ECO Kits: 
 
         VMS731_ACRTL-V0200         VMS731_IIDRIVER-V0100
         VMS731_BACKUP-V0100        VMS731_LAN-V0500  
         VMS731_CLUSTER-V0100       VMS731_LINKER-V0100  
         VMS731_CPU2208-V0100       VMS731_MSCP-V0100 
         VMS731_CPU2308-V0200       VMS731_PARTITIONING-V0100
         VMS731_CPU270F-V0100       VMS731_PTHREAD-V0100
         VMS731_DCL-V0300           VMS731_QMAN-V0100
         VMS731_DEBUG-V0100         VMS731_RMS-V0200
         VMS731_DIR-V0100           VMS731_RPC-V0100
         VMS731_EV7-V0200           VMS731_SYS-V0300
         VMS731_F11X-V0100          VMS731_TDF-V0100 
         VMS731_FIBRE_SCSI-V0300    VMS731_XFC-V0100
         VMS731_GRAPHICS-V0100

     ECO Kit Approximate Size:  141936 Blocks
     Kit Applies To:  OpenVMS Alpha V7.3-1
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:  INSTALL_1

                           1 - To be installed on all systems running
                                the listed version(s) of OpenVMS.

     Kit Dependencies:

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

     	 VMS731_PCSI-V0100

       In order to receive all the corrections listed in this
       kit, the following remedial kits, or later, should also be installed:

         None



ECO KIT SUMMARY:

An ECO kit exists for System Components on OpenVMS Alpha V7.3-1.  This
kit addresses the following problems:


PROBLEMS ADDRESSED IN VMS731_UPDATE-V0100 KIT

     o  Consolidation of previously released V7.3-1 ECO kits.

        The VMS731_UPDATE-V0100 kit is a consolidation of previously
        released OpenVMS V7.3-1 ECO kits.  The following ECO kits are
        included:

            VMS731_ACRTL-V0200         VMS731_BACKUP-V0100        
            VMS731_CLUSTER-V0100       VMS731_CPU2208-V0100       
            VMS731_CPU2308-V0200       VMS731_CPU270F-V0100       
            VMS731_DCL-V0300           VMS731_DEBUG-V0100
            VMS731_DIR-V0100           VMS731_EV7-V0200           
            VMS731_F11X-V0100          VMS731_FIBRE_SCSI-V0300    
            VMS731_GRAPHICS-V0100      VMS731_IIDRIVER-V0100      
            VMS731_LAN-V0500           VMS731_LINKER-V0100
            VMS731_MSCP-V0100          VMS731_PARTITIONING-V0100  
            VMS731_PTHREAD-V0100       VMS731_QMAN-V0100          
            VMS731_RMS-V0200           VMS731_RPC-V0100           
            VMS731_SYS-V0300           VMS731_TDF-V0100
            VMS731_XFC-V0100

        Following are the issues addressed by the above kits.


NEW FUNCTIONALITY INTRODUCED IN THE VMS731_CPU2308-V0200 KIT

     o  Smart Array 5300 Backplane RAID Controller support for
        Alphaserver GS80/1

        Currently only one Smart Array 5300 Backplane RAID Controller
        can be used on Alphaserver GS80/160/320 systems.  This kit
        provides support for multiple controllers.

        Images Affected: [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE


NEW FUNCTIONALITY INTRODUCED IN THE VMS731_CPU2308-V0100 KIT

     o  Enable the DTAG2 ECC functionality.

        Enable the DTAG2 ECC functionality.  The additional hardware
        support in V7.3-1 enables ECC single-bit error interrupts and
        then properly logs any DTAG2 single-bit errors in the errorlog
        file.  Prior OpenVMS releases (V7.2-1H1, V7.2-2, V7.3) never
        enable this functionality.  The result is that the operating
        system is never notified by the hardware that a single-bit
        DTAG2 error has been detected and corrected by hardware.

        Images Affected: [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE


NEW FUNCTIONALITY INTRODUCED IN THE VMS731_CPU270F-V0100 KIT

     o  Smart Array 5300 Backplane RAID Controller support for
        Alphaserver ES47,

        Currently only one Smart Array 5300 Backplane RAID Controller
        can be used on Alphaserver ES47, ES80 and GS1280 Series
        systems.  This kit provides support for multiple controllers.

        Images Affected: [SYS$LDR]SYS$CPU_ROUTINES_270F.EXE


NEW FUNCTIONALITY INTRODUCED IN THE VMS731_EV7-V0100 KIT

     o  Alphaserver ES47 and GS1280 Series System Support

        HP OpenVMS is pleased to introduce support for the first
        members of the "Next Generation HP AlphaServer Systems" - the
        ES47 and GS1280 Series systems.  In the coming months,
        additional models in this series will be introduced.  Release
        Notes and a full description of this support can be found in
        the following files after this kit is installed:

           o  ES47_GS1280_SUPPORT.PDF

           o  ES47_GS1280_SUPPORT.TXT


        In order to read these files before kit installation, execute
        the following command:

            PRODUCT EXTRACT FILE VMS731_EV7/SELECT=filename -
            [/destination=device-name:[directory-name]


        For more information on the PRODUCT EXTRACT command, see
        system help for PRODUCT.


NEW FUNCTIONALITY ADDRESSED IN THE VMS731_FIBRE_SCSI-V0300 KIT

     o  Support for Emulex LP9802 FibreChannel Adapter

        This kit provides support for the Emulex  LP9802  FibreChannel
        Adapter.

        Images Affected: [SYSEXE]SYS$CONFIG.DAT


NEW FUNCTIONALITY INTRODUCED IN THE VMS731_GRAPHICS-V0100 KIT

     o  ATI RADEON 7500 Graphics adapter support for OpenVMS V7.3-1

        This kit contains the 2D and 3D graphics software to support
        the ATI RADEON 7500 AGP and PCI graphics cards on OpenVMS
        Alpha Version 7.3-1.  The part numbers are as follows:

                     AGP card: 3X-PBXGG-AB
                     PCI card: 3X-PBXGG-AA
                     Open3D license: QL-0ADA9-AA


                         *** NOTE ***

        This kit ships with full support for the AGP card; the PCI
        card is still being tested.  When PCI qualification is
        completed, it will be announced on the "What's New" website.
        You can reach this by clicking on "what's new on our site" on
        the following webpage:

                     http://www.hp.com/go/openvms

        Currently, the PCI card is supported on the AlphaServer DS10.
        Support on other platforms will be announced as they are
        tested.  For updates on support for the AGP and PCI cards,
        refer to the QuickSpecs webpage at:

        http://h18000.www1.hp.com/products/quickspecs/Division/10410.html

        Full release notes for the ATI RADEON 7500 Graphics Support
        are supplied in HTML, PDF, and text format and are located in
        the SYS$HELP directory after this software kit is installed:

               RADEON_7500_V1_README.HTML
               RADEON_7500_V1_README_CONTENTS.HTML
               RADEON_7500_V1_README.PDF
               RADEON_7500_V1_README.TXT


NEW FUNCTIONALITY PROVIDED IN VMS731_LAN-V0100 KIT

     o  Support for the DEGXA PCI Gigabit Ethernet and Broadcom 5703
        LOM

        OpenVMS V7.3-1 supported only the Broadcom 5703 LOM (LAN on
        motherboard) chip on the AlphaServer DS25, and that only in
        1000 mbit full-duplex mode.  This update adds full support for
        10 and 1000 mbit and half-duplex mode for the Broadcom 5703
        LOM as well as full support for the DEGXA-SA (fiber 5703 NIC)
        LOM as well as full support for the DEGXA-SA (fiber 5703 NIC)
        and DEGXA-TA (UTP 5703 NIC).

        Images Affected: [SYS$LDR]SYS$EW5700.EXE


     o  Provide boot support over the Broadcom 5703 LOM and the DEGXA
        NICs

        The DEGXA NICs.  Note that a console firmware update may be
        needed as well.

        Images Affected: [SYS$LDR]SYS$EGBTDRIVER.EXE
                         [SYSEXE]APB.EXE
                         [SYSEXE]DEBUG_APB.EXE
                         [SYSEXE]APB_BOOTP.EXE


NEW FUNCTIONALITY ADDRESSED IN VMS731_PARTITIONING-V0100 KIT

     o  Partitioning Support for ES47/ES80/GS1280 Series Systems

        Hard and soft partitioning capability is being introduced  for
        ES47/ES80/GS1280  Series  Systems.   In  order to use this new
        capability      users      need      to      install      this
        VMS731_PARTITIONING-V0100 kit as well as the V6.5 console set.
        When released, this console  set  will  be  available  at  the
        Alphaserver firmware website:

        http://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html

        Note that the website address is case-sensitive, and  you  may
        need to visit the Interim release area to obtain the firmware.

        Images Affected:[SYSEXE]SMPUTIL.EXE
                        [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE
                        [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE
                        [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.EXE
                        [SYS$LDR]SYSTEM_SYNCHRONIZATION.STB
                        [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.STB
                        [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.STB


PROBLEMS ADDRESSED IN THE VMS731_ACRTL-V0200 KIT

     o  Previous ACRTL kit not compatible with new PCSI functionality

        The VMS731_ACRTL-V0100 kit is not compatible with the newly
        released PCSI UNDO functionality.  This new PCSI functionality
        allows a user to uninstall a patch kit.  If a user was to
        install the VMS731_ACRTL-V0100 patch kit using the new
        PCSI$SAVE_RECOVERY_DATA option and then attempted to uninstall
        the kit using the UNDO feature, the system could be left with
        an incorrect DECC$RTLDEF.TLB file.  This new
        VMS731_ACRTL-V0200 kit re-issues the VMS731_ACRTL-V0100 kit
        with updated installation files that allow safe removal of the
        kit.

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

        Images Affected: POSTUNDO.COM


PROBLEMS ADDRESSED IN VMS731_ACRTL-V0100 KIT

Note:  The first several entries list new features in this ECO kit.
For more information, see the New Features section of the release
notes.

     o  C header files are shipped with this ECO kit.  These files
        will be installed only if needed by your system.

        
     o  You can now set the default (working) directory for child
        processes created by vfork/exec*, using the new RTL function
        decc$set_child_default_dir().

        For more information, see the "New Features" section of the
        release notes for this ECO kit.



     o  64-bit pointer support is added for sendmsg(), recvmsg(),
        getaddrinfo(), and freeaddrinfo().

        For more information, see the "New Features" section of the
        release notes for this ECO kit.



     o  A new feature logical DECC$ALLOW_REMOVE_OPEN_FILES is added
        to control the behavior of remove() on open files.

        For more information, see the "New Features" section of the
        release notes for this ECO kit.



     o  New C RTL functions are provided with this kit.

        The following new C RTL functions are provided with this kit:
          pread()
          pwrite()
          readv()
          _readv64()
          __writev64()
          decc$set_child_default_dir()

        For more information, see the "New Features" section of the
        release notes for this ECO kit.



     o  New socket routine poll() is provided with this kit.

        For more information, see the "New Features" section of the
        release notes for this ECO kit.



     o  Undefined symbol GETADDRINFO_COMPAT43

        In some circumstances, the OpenVMS linker flagged the
        GETADDRINFO_COMPAT43 symbol as undefined.  This is fixed.



     o  64-bit pointers were not supported for some socket routines.

        The following socket routines did not have 64-bit pointer
        support.  Now they do:

              accept()    
              getpeername()
              getsockname()




     o  fwrite() wrote inappropriate records to a file.

        A previous fix to fwrite(), which involved padding short-sized
        records with zeros to align them with bigger records in a
        fixed-length-record file, allowed new records to have a
        carriage return after every single byte, thereby creating a
        large number of spurious records in the file.

        Fix:

        Because this is a change in behavior, a feature logical has
        been added to control the new behavior.  This new feature
        logical, DECC$WRITE_SHORT_RECORDS, supports the previous fix
        to fwrite() (to accommodate short-sized records), while
        retaining the legacy way of writing records to a fixed-length
        file as the default behavior:

             When DECC$WRITE_SHORT_RECORDS is set to "ENABLE",
             short-sized records are padded with zeros to align records
             on record boundaries.

             When DECC$WRITE_SHORT_RECORDS is set to "DISABLE" or when
             it is deassigned, the legacy behavior of writing records is
             implemented.  This is the recommended and default behavior.




     o   was incompatible with local-time function ftw().

        Recent versions of the C RTL, along with header files supplied
        with Version 6.5 of the C compiler, incorrectly made a
        local-time version of the ftw() function the default when
        compiling with the _VMS_V6_SOURCE macro defined.

        Fix:

        This behavior was incompatible with previous C RTL versions,
        and has been restored to default to the UTC-based ftw()
        function under the same circumstances.  Now, to get the
        local-time ftw(), you must compile with
        /DEFINE=__LOCAL_TIME_FTW, in addition to the macros
        _VMS_V6_SOURCE and _DECC_V4_SOURCE.



     o  Spawned process did not inherit file positioning for append
        access mode.

        For spawned processes that are C programs, defining the
        DECC$EXEC_FILEATTR_INHERITANCE feature logical name to a value
        of 1 or ENABLE no longer causes the spawned child process to
        inherit file positioning for all file access modes;
        specifically, append mode does not inherit file positioning.

        Fix:

        For a child process to inherit file positioning for all file
        access modes including append, DECC$EXEC_FILEATTR_INHERITANCE
        must be set to a value of 2:

             $ DEFINE  DECC$EXEC_FILEATTR_INHERITANCE 2

        For a child process to inherit file positioning for all file
        access modes except append, set DECC$EXEC_FILEATTR_INHERITANCE
        to a value of 1:

             $ DEFINE  DECC$EXEC_FILEATTR_INHERITANCE 1

        This change was made in OpenVMS Version 7.3-1.  This ECO
        propagates the fix to OpenVMS Versions 7.3 and 7.2-2.



     o  Incomplete support for 64-bit iconv() has been removed.

        Incomplete support for 64-bit iconv() was mistakenly put into
        recent (Spring 2002) ECO kits and OpenVMS V7.3-1.

        This gave the illusion of 64-bit iconv() support under some
        circumstances (linking with STARLET.OLB).  This was never
        supported, and still is not supported.

        Fix:

        Because 64-bit iconv() is neither functional nor supported,
        this ECO removes DECC$_ICONV64.

        Users compiling with /POINTER=LONG should now expect a
        compiler error message such as the following:

             %CC-W-PTRMISMATCH, In this statement, the referenced 
             type of the pointer value "(char ...)0" is "long pointer 
             to char", which is not compatible with "short pointer to 
             char".



PROBLEMS ADDRESSED IN VMS731_BACKUP-V0100 KIT

     o  During HSM Backup operations a process could hang or
        improperly shelve/unshelve files.

        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 ODS5 files and directories do not
        work.

        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  %MOUNT-F-BADCHKSUM, bad file header checksum error after
        image backup.

        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  Problems restoring subsequent volumes of a multi-tape backup.

        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  BACKUP/IGNORE=INTERLOCK gives READATTR/NOSUCHFILE errors.

        A BACKUP/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 the 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-F-GETCHN/SYSTEM-I-IVIDENT error while performing a
        /IMAGE operation on a disk that is mounted /FOREIGN.

        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  BACKUP-F-CLUSTER error messages during a BACKUP/IMAGE/NOINIT
        operation.

        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



PROBLEMS ADDRESSED IN VMS731_CLUSTER-V0100 KIT

     o  Check MSCP_SERVE_ALL correctly

        Since V7.2, a MSCP_SERVE_ALL value of 4 has not worked
        correctly.  It is supposed to serve only the system disk, but
        it does not serve any disks.  All other values of
        MSCP_SERVE_ALL work correctly.

        This change insures that you can MSCP serve *just* the system
        disk, as is documented with MSCP_SERVE_ALL = 4.

        Images Affected: [SYSEXE]STACONFIG.EXE
                         [SYSEXE]CONFIGURE.EXE



     o  Upgrade from 7.3 LANACP generates PROCGONE - pgflquota

        When updating from OpenVMS V7.3R to V7.3-1R it is possible for
        the LANACP process to get an ACCVIO followed by a PROCGONE
        bugcheck as the LANACP process attempts to terminate and run
        down.  This will cause the upgrade procedure to terminate
        prematurely during the reboot.

        Images Affected: [SYSEXE]STACONFIG.EXE
                         [MANAGE]VMS$INITIAL-050_CONFIGURE.COM



     o  Fix system crash after SCS port-specific MAP stall

        If an SCS data-transfer SCS$MAP request encounters an SCS
        port-specific mapping resource exhaustion ("stall"), the
        system will crash upon attempt to resume the SCS map
        data-transfer setup operation, when such resources become
        available and the stalled operation restarts.

        While many VMS SCS port drivers use port-specific SCS mapping
        resources (S/G-maps, CRCTX$, etc.), only SYS$PADRIVER for the
        SHAC-DSSI-chip/KFESA has an unusually small quantity of SCS
        mapping resources (128 CI buffer descriptors, to be exact).
        It is therefore most likely to encounter this failure.

        Images Affected: [SYS$LDR]SYS$SCS.EXE



PROBLEMS ADDRESSED IN VMS731_CPU2208-V0100 KIT

     O  MCA0:  unit init timeout errors

        When booting OpenVMS V7.3-1 on an ES40, ES45 or DS20e system
        with Memory Channel, users will see initialization failure
        messages from the MCA0 device.  For example:

         %MCA0 CPU00:  18-SEP-2002 14:13:04 unit init timeout occurred.

        This fix corrects the interrupt setup for Memory channel and
        prevents the init timeouts.

        Images Affected: [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE
                         [SYS$LDR]SYS$CPU_ROUTINES_2608.EXE



PROBLEMS ADDRESSED IN VMS731_DCL-V0300 KIT

     O  On a fast SMP machine, complex pipe commands running in batch
        may hang.

        On a fast SMP machine, complex pipe commands running in batch
        may hang.  In the most common scenario, some of the
        subprocesses created by the pipe command are hanging in the
        LEF state with the parent process hanging in a HIB state.

        Images Affected: [SYSEXE]DCL.EXE



     O  system prompt returned from command line

        With security audits/alarms enabled for privilege failure, the
        execution of the PIPE command generates an audit/alarm for
        lack of CMKRNL privilege.

            $ PIPE DIR | SEAR SYS$INPUT LOGIN
              %%%%%%%%%%%  OPCOM  26-MAR-2003 08:57:08.53  %%%%%%%%%%%
              Message from user AUDIT$SERVER on TIGRES
              Security alarm (SECURITY) on TIGRES, system id: 1025
              Auditable event:          Privilege failure
              Event information:        CMKRNL not used to execute 
                $CMKRNL(_64) system service ($CMKRNL or $CMKRNL_64)
              Event time:               26-MAR-2003 08:57:08.53
              PID:                      000000C0
              Process name:             TEST
              Username:                 TEST
              Process owner:            [TEST]
              Terminal name:            RTA1:
              Privileges missing:       CMKRNL


        Images Affected: [SYSEXE]DCL.EXE



     o  System prompt returned from command line

        When invoking an image with a command line, the system prompt
        is returned instead of executing the command that was passed
        on the command line.

        Images Affected: [SYSEXE]DCL.EXE



     o  WRITE SYS$OUTPUT F$GETSYI("cpu_failover") crashes the
        process.

        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   
                                       000000000000004
                                       000000007FFAE000
                                       000000000000004
                                       000000007FFAE000
                           .
                         .
                         .
                         .
          %DCL-S-RETURNED, control returned to process GUY
          %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
          address=000000000000
          000C, PC=000000000000000C, PS=7FFAC4C3

        Images Affected: [SYSEXE]DCL.EXE



PROBLEMS ADDRESSED IN VMS731_DCL-V0200 KIT

     o  PCSI Database updated with non-existant module

        In the VMS731_DCL-V0100 ECO kit, the statement that uses the
        DCLINT.CLD file to update DCLTABLES is incorrect.  This
        results in a non-existant module being entered in the PCSI
        database.  DCLTABLES itself is updated correctly.  Therefore,
        the user's system functions correctly after the kit
        installation but the PCSI database is incorrect.  This problem
        could result in the following warning message if the user
        tries to re-install or upgrade OpenVMS V7.3-1 after installing
        the VMS731_DCL-V0100 ECO kit:

          %PCSI-I-PRCOUTPUT, output from subprocess follows ...
          %CDU-W-NOSUCHVERB, The CLI table does not contain verb name 
          DCL
          %PCSI-E-MODDELERR, error deleting module DCL from library
          DISK$AXPVMS7311:[VMS$C
          OMMON.][SYSLIB]DCLTABLES.EXE
          %PCSI-E-OPFAILED, operation failed
          Terminating is strongly recommended.  Do you want to 
          terminate? [YES]


        The user should answer "NO" to the "Do you want to terminate?"
        question, allowing the installation/upgrade to continue.
        After the installation/upgrade is complete, both DCLTABLES and
        the PCSI database are correct with no incorrect DCL module
        entry.

                               NOTE
                               ----

        If you have installed the VMS731_DCL-V0100 ECO kit, you do not
        need to install the VMS731_DCL-V0200 kit.  This kit does not
        provide any functional changes.  It will not correct the PCSI
        database problem caused by the VMS731_DCL-V0100 kit.  It
        prevents the problem from happening for new users.

        Images Affected: VMS731_DCL.PDF (Installation file)


PROBLEMS ADDRESSED IN VMS731_DCL-V0100 KIT

     o  F$GETSYI lexical did not have an item code that returns
        information about free and used memory as numerical value.

        The F$GETSYI lexical did not have an item code that returns
        information about free and used memory as numerical value.
        F$GETSYI("MAIN_MEMORY") has been available for a long time but
        never documented.  It is also hard to use the returned
        information:

               $ WRITE SYS$OUTPUT F$GETSYI("MAIN_MEMORY")
               0000039000007D8800017EE800020000

        The item codes TOTAL_PAGES, FREE_PAGES, USED_PAGES and
        MODIFIED_PAGES have been added to F$GETSYI.  Now, a procedure
        can make a decisions based on memory usage.

        Here is a small example of new item codes usage:

          $ SHOW MEMORY/PHYSICAL_PAGES
          System Memory Resources on  2-JUL-2002 02:21:42.56

          Physical Memory Usage (pages): Total   Free  In Use Modified
            Main Memory (1024.00MB)       131072 97985 32180  907

          Of the physical pages in use, 7740 pages are permanently
          allocated to OpenVMS.

          $ WRITE SYS$OUTPUT F$GETSYI("TOTAL_PAGES")
          131072
          $ WRITE SYS$OUTPUT F$GETSYI("USED_PAGES")
          32136
          $ WRITE SYS$OUTPUT F$GETSYI("FREE_PAGES")
          98024
          $ WRITE SYS$OUTPUT F$GETSYI("MODIFIED_PAGES")
          912

        Images Affected: [SYSEXE]DCL.EXE



     o  /SEARCH qualifier added to DCL RECALL command

        A selective search of the recall buffer was implemented in
        V7.3-1.  To complete the implementation, the /SEARCH qualifier
        has been added to the DCL command RECALL to enable a search of
        a substring in the recall buffer.  For example:

             SYSTEM> RECALL/ALL
               1 dir sys$sysdevice:[000000]
               2 show device dk
               3 show time

             SYSTEM> RECALL/SEARCH DEV
               1 dir sys$sysdevice:[000000]
               2 show device dk
             SYSTEM>


        Images Affected: [SYSEXE]DCL.EXE
                         [SYSUPD]DCLINT.CLD



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

        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  Serial number information is returned by F$GETSYI as an
        integer and not as a string.

        Serial number information is returned by F$GETSYI as an
        integer and not as a string.  Here is an example of the
        incorrect and correct output :

             $ WRITE SYS$OUTPUT F$GETSYI("SERIAL_NUMBER")
             00000000000037333338303431385941


        After applying this kit the output is:

             $ WRITE SYS$OUTPUT F$GETSYI("SERIAL_NUMBER")
             AY81408337


        Images Affected: [SYSEXE]DCL.EXE
                         [SYS$STARTUP]VMS$CONFIG-050_LMF.COM



     o  The first command entered after a ^Y causes an access
        violation.

        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



PROBLEMS ADDRESSED IN VMS731_DEBUG-V0100 KIT

     o  The Debugger can hang when attempting to view the sources for
        a large application.

        The following DEBUG GUI problems are corrected in this kit:

           o  The Debugger GUI can hang when attempting to source browse
              a large application.  Usually the user also sees the
              following error message:

                X Toolkit Warning:
                Name: cnt_generic_label
                Class: XmLabel
                Invalid XmNlabelString - must be a compound string


           o  The Debugger GUI can hang when manipulating its optional
              views, especially the register view.  Usually the user
              also sees the following error message:

                    Xlib: unexpected asynch reply

           o  An incomplete list of images, modules and routines in the
              Source View

           o  An Xlib synchronization error message, after after which
              the debugger hangs.


        Images Affected: [SYSLIB]DEBUGSHR.EXE



PROBLEMS ADDRESSED IN VMS731_DIR-V0100 KIT

     o  Fix DIRECTORY command display grouped by first letter for
        network operations

        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



PROBLEMS ADDRESSED IN VMS731_EV7-V0200 KIT

     o  Add PCSI UNDO capability

        A new version of the PCSI installation utility has been
        released which allows customers un-install (UNDO) a kit that
        has been installed with the new PCSI utility.  It does this by
        saving any libraries, files and other objects it manipulates
        in a separate directory structure.  PCSI is not aware of
        anything that is done in pre- or post-installation procedures,
        and so will not save anything related to those operations.  To
        correct for this the new PCSI allows the creation of a PRE or
        POST-UNDO command file that runs when a kit is un-installed.

        The VMS731_EV7-V0100 patch kit was issued prior to the release
        of the new PCSI utility.  It contains pre- and
        post-installation procedures but does not contain
        corresponding UNDO files.  Removal of this kit via the new
        PCSI UNDO command could result in system instability.  This
        VMS731_EV7-V0200 kit re-issues the VMS731_EV7-V0100 patch kit
        with the appropriate UNDO files.

                         ** NOTE **

        Aside from additional installation capabilities, the
        VMS731_EV7-V0200 contains no new functionality.  If you have
        installed the VMS731_EV7-V0100 remedial patch kit you do not
        need to install the VMS731_EV7-V0200 kit.

        Images Affected: Installation files


PROBLEMS ADDRESSED IN VMS731_F11X-V0100 KIT

     o  Allow for NO_READ_DATA access to a locked file

        SYS$CHECK_ACCESS uses the FIB option FIB$V_NO_READ_DATA to
        read the ACL/protection attributes of a file object.  When the
        file is opened to not allow read sharing, this service would
        return SS$_ACCONFLICT.  If the service adds the FIB$V_CONTROL
        flag this does not occur.

        The change relaxes the requirement of the need for specifing
        FIB$V_CONTROL, which implies the need write access to the
        file.  This is not the case and FIB$V_NO_READ_DATA prevents
        the file system from mapping the data in the file.

        Also fix $ENQ calls that do not specify an EFN value in V7.2-2
        and V7.3 (already in V7.3-1).

          Specify NOT VAX vs.  EVAX for flowthru to OPAL.

        Images Affected: [SYS$LDR]F11BXQP.EXE



     o  Fix UNXSIGNAL when LAST_FCB is zero on header extension

        An ACCVIO (UNXSIGNAL) can occur during a header extention if
        the LAST_FCB value is zero.  The LAST_FCB value is zero
        because the last header on disk is not yet mapped to an FCB.
        The fix is check to see if the LAST_FCB is zero (null) before
        updating the STVBN field.

        Images Affected: [SYS$LDR]F11BXQP.EXE



     o  Report failing UIC when a diskquota operation fails

        If a diskquota operation fails, the UIC of the current thread
        may not reflect the UIC operation on the file created.  This
        may be due to privileges of the thread or the use of Resource
        Identifiers on a file/directory.

        Images Affected: [SYS$LDR]F11BXQP.EXE


     o  Handle directory record location correctly

        In the case of directory scan, when looking for a directory
        record by number, the operation was not short-cutting a
        comparison operation.  This caused the locating of the record
        to terminate early.  As a result, the proper record was not
        found.  Generally only the first was found

        Images Affected: [SYS$LDR]F11BXQP.EXE



     o  Make lookups obey users knowledge of case-sensitivity

        When on an ODS-5 volume, files with names that do not obey
        strict ODS-2 naming, such as the use of lowercase names or
        ISO-Latin-1 names, may loop on this name.  Certain lookups
        back track to a previous name because for a non-case sensitive
        operation, the lookup finds the same file.

        Images Affected: [SYS$LDR]F11BXQP.EXE


     o  Possible MULTIALLOC failure due to overwriting of map area by
        access times

        Extention headers may have their map area corrupted with a
        volume access time.  This can happen if the access to the file
        is done via the secondary header and not the primary.

        This would only occur ifthe following are true:

           -  the file is badly fragmented

           -  the volume is ODS-5

           -  access times are enabled on the volume.

        The latter two options are not the default initialization
        parameters for a volume.

        Images Affected: [SYS$LDR]F11BXQP.EXE



PROBLEMS ADDRESSED IN VMS731_FIBRE_SCSI-V0300 KIT

     o  Hang during boot while configuring Fibrechannel storage

        A system can hang during boot while configuring Fibrechannel
        storage devices.

        Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE



     o  INCONSTATE, Inconsistent I/O data base bugcheck

        A system can crash with an INCONSTATE, Inconsistent I/O data
        base bugcheck.

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     INCONSTATE, Inconsistent I/O data base
          Current Process:   OPCOM
          Current Image:     $1$DGA9006:[SYS100.SYSCOMMON.]
                             [SYSEXE]OPCOM.EXE
          Failing PC:        FFFFFFFF.804222FC SYS$FGEDRIVER+102FC
          Failing PS:        20000000.00000804
          Module:            SYS$FGEDRIVER (Link Date/Time:
                             15-MAR-2002 20:37:04.71)
          Offset:            000102FC

          Failing Instruction:
          SYS$FGEDRIVER+102FC:  BUGCHK


        Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE



     o  INVTQEFMT, Invalid time queue entry format bugcheck

        A system can crash with an INVTQEFMT, Invalid time queue entry
        format bugcheck.

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     INVTQEFMT, Invalid time queue entry format
          Current Process:   AMDS$COMM
          Failing PC:        FFFFFFFF.80045FCC    FREE_ENTRY_C+006FC
          Failing PS:        20000000.00000803
          Module:            SYSTEM_PRIMITIVES_MIN (Link Date/Time:
                             29-OCT-2002 23:52
          Offset:            00021FCC

          Stack Pointers:
          KSP = 00000000.7FFA1EA0   ESP = 00000000.7FFA6000
          SSP = 00000000.7FFAE000   USP = 00000000.7AFAD770

          Failing Instruction:
          FREE_ENTRY_C+006FC:     BUGCHK

        Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE



     o  INVEXCEPTN, Exception while above ASTDEL bugcheck

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

          Crashdump Summary Information:
          ------------------------------
          Crash Time:         5-DEC-2002 23:48:33.08
          Bugcheck Type:     Exception while above ASTDEL
          Node:              ALPHA3  (Cluster)
          CPU Type:          AlphaServer ES40
          VMS Version:       V7.3-1
          Current Process:   NULL
          Current Image:     
          Failing PC:        FFFFFFFF.8043AAD8    SYS$DKDRIVER+0EAD8
          Failing PS:        20000000.00000804
          Module:            SYS$DKDRIVER    (Link Date/Time: 
                             13-NOV-2002 10:01:29.41)
          Offset:            0000EAD8

          Stack Pointers:
          KSP = FFFFFFFF.A2ED39E8   ESP = FFFFFFFF.C53DF000   
          SSP = FFFFFFFF.C53D9000   USP = FFFFFFFF.C53D9000

          Failing Instruction:
          SYS$DKDRIVER+0EAD8:     LDL             R6,#X000C(R6)


        Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE



     o  Fibre Channed disks are not seen after the system is booted.

        Occasionaly, fibre Channed disks are not seen after the system
        is booted.

        Images Affected: [SYSLIB]IOGEN$FIBRE_CONFIG.EXE


PROBLEMS ADDRESSED IN VMS731_FIBRE_SCSI-V0200 KIT

     o  System can hang when booting from a Fibre Channel disk, that
        is on an Arbitrated Loop.

        Shortly after the first OpenVMS boot message is displayed, a
        system can hang when booting from a Fibre Channel disk, that
        is on an Arbitrated Loop.

        Images Affected: [SYS$LDR]SYS$PGADRIVER.EXE


     o  FibreChannel storage (DG) disks fail over to the MSCP path

        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  MACHINECHK, Machine check while in kernel mode

        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  OpenVMS loses access to a fibrechannel device.

        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  New Facility to allow MSA1000 firmware update.

        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  I/O to one or more disks may stall

        I/O to one or more disks may stall with the following
        symptoms:

           -  WBEM$CPQSTORE (or any other process issuing an
              IO$_DIAGNOSE request) has a busy channel to a DGA device.

           -  The first IO on the port I/O queue to this disk on the
              current path is shown as a:  wrttmkr func,physio,extend IO
              in SDA> SHOW DEV DGAx

           -  The SCSI port descriptor (SPDT), for the Fibre Channel
              adapter of the current path to the disk, shows Total
              Outstanding I/Os and Curr I/Os On All ports to be nnn (
              SDA> CLUE SCSI/PORT= ), where nnn is any number
              greater than 0.

           -  Other processes trying to access any disk via this Fibre
              Channel port seem to hang.  An associated symptoms may be
              that no new logins are possible (access to SYSUAF and/or
              RIGHTSLIST hangs).

           -  The Fibre Channel adapter ring buffer shows mostly
              'WatchDog End' and 'WatchDog Beg' events, but no
              Read/WRITE IOCB events.


        Images Affected: [SYS$LDR]SYS$PGADRIVER.EXE



     o  DIR-E-TAPEPOSLOST errors

        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  Request completes with a transferred-byte-count of up to 511
        bytes more than were requested.

        A request can complete with a transferred-byte-count of up to
        511 bytes more than were requested.  The effect of this bug is
        application-dependent but has been seen to cause repeated
        PEDRIVER port initializations.

        Images Affected: [SYS$LDR]SYS$DKDRIVER.MAR



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

        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  8MM tape unit, like a TKZ9E-SW, will log an error during
        driver initialization

        An 8MM tape unit, like a TKZ9E-SW, will log an error during
        driver initialization.

        Images Affected: [SYS$LDR]SYS$MKDRIVER.EXE



     o  Possible Fibre Channel Data Corruption

          1.  It is possible for a command retry to fail with a bad
              status but a non-zero byte count of more or less data than
              it asked for.  The problem is that the SCDRP$L_TRANS_BCNT
              field was not being zeroed prior to every command being
              issued.

          2.  When an other-than-perfect FastPath command completes, it
              posts a transferred-byte count of SCDRP$L_BCNT.  This
              allows it use the stale byte count described in item 1.
              Even when the command completes successfully, this code
              lets the request complete with the pad byte count in it,
              causing it to report up to 511d more bytes than were
              requested.


        Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
                         [SYS$LDR]SYS$FGEDRIVER.EXE
                         [SYS$LDR]SYS$PKQDRIVER.EXE
                         [SYS$LDR]SYS$PGADRIVER.EXE


     o  A customer who uses the USERD1 SYSGEN parameter may see
        debug output.

        A customer who uses the USERD1 SYSGEN parameter may see debug
        output.

        Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
                         [SYS$LDR]SYS$FGEDRIVER.EXE
                         [SYS$LDR]SYS$PKQDRIVER.EXE
                         [SYS$LDR]SYS$PGADRIVER.EXE



     o  Restoring a multivolume saveset fails.

        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  INCONSTATE bugcheck at SYS$PGADRIVER+0A7F4

        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



PROBLEMS ADDRESSED IN VMS731_FIBRE_SCSI-V0100 KIT

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

          Crashdump Summary Information
          -----------------------------
          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  Fastskip algorithm could be inadvertently turned off

        As a result of mount verification on SCSI tapes, the fastskip
        algorithm could be inadvertently turned off.

        Images Affected: [SYS$LDR]SYS$MKDRIVER.EXE


     o  Unnecessary console messages from FGEDRIVER.

        The user will see unnecessary console messages from FGEDRIVER.

        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  Paths to FibreChannel disks become permanently unavailable
        without notification or error log entries.

        Paths to FibreChannel disks can become permanently unavailable
        without notification to the user and without any error log
        entries being written.

        Images Affected: [SYS$LDR]SYS$FGEDRIVER
                         [SYS$LDR]SYS$PGADRIVER



     o  Disk drives that support the SCSI-3 SPC3 standard cannot be
        mounted.

        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  Invalid FC-LA field when using FC$SDA to examine the FCP ring
        buffer.

        When using FC$SDA to examine the FCP ring buffer, if the
        request was sent FastPath, the FC-LA field is always 0, which
        is an invalid value for FC-LA.

        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 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  When using FC$SDA to display STDTs, some useful fields (such
        as the newQueue Full handling cells and the target reset
        count) are missing.

        When using FC$SDA to display STDTs, some useful fields (such
        as the new Queue Full handling cells and the target reset
        count) are missing.  Also, FC$SDA has no support for an FC
        STDT /ALL command.

        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  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.802F4148    
                             LCK$RCV_RM_BXFER_C+001F8

          Failing PS:        18000000.00000804
          Module:            SYS$CLUSTER   (Link Date/Time:  
                             4-MAR-2002 15:21:35.69)
          Offset:            0001C148

          Failing Instruction:
          LCK$RCV_RM_BXFER_C+001F8:       BUGCHK


          R0  =  00000000.00002044   %SYSTEM-F-INSFSPTS,
                 insufficient SPTEs available


        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  System can crash with an INVEXCEPTN at SYS$FGEDRIVER+177E0
        (ERS$PLOGI_IND+3E0)

        The System can crash with an INVEXCEPTN at
        SYS$FGEDRIVER+177E0.  (ERS$PLOGI_IND+3E0)

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
          Current Process:   NULL
          Current Image:     
          Failing PC:        FFFFFFFF.804157E0  SYS$FGEDRIVER+177E0
          Failing PS:        18000000.00000804
          Module:            SYS$FGEDRIVER    (Link Date/Time:
                             18-SEP-2002 10:30:49.38)
          Offset:            000177E0

          Failing Instruction:
          SYS$FGEDRIVER+177E0:  LDQ_U  R19,#X001C(R1)


        Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE



     o  Data underflow on Fast Path IO will cause SS$_NOTQUEUED
        errors to be logged, and cause a visible mount verification.

        Data underflow on Fast Path IO will cause SS$_NOTQUEUED errors
        to be logged, and cause a visible mount verification.

        Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE


     o  Frequent quorum disk mount verification.

        The user may see frequent mount verifications.  These can have
        several causes:

           -  Frequent quorum disk mount verification can occur when the
              quorum disk has a relatively heavy I/O load applied to it.
              This is not a problem when the quorum disk is used as
              recommended,meaning with no significant I/O load.
              However, in some customer clusters this recommendation is
              ignored.

           -  Frequent TX/RX DMA failures can occur which result in
              mount verifications.

        Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
                         [SYS$LDR]SYS$FGEDRIVER.EXE
                         [SYS$LDR]SYS$PGADRIVER.EXE


     o  Disk goes into Mountverify

        If the system can not allocate a KPB for a Fast Path IO, an IO
        may not finish, putrtjgthe disk ina Mountverify state.

        Images Affected: [SYS$LDR]SYS$PKQDRIVER.EXE
                         [SYS$LDR]SYS$PKADRIVER.EXE



     o  Fibre Channel storage not configured

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

        Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
                         [SYS$LDR]SYS$PGADRIVER.EXE


     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.  For example:

          $ INIT $7$MKC0: TEST0
          $ MOUNT/FOREIGN $7$MKC0:
            %MOUNT-I-MOUNTED, TEST0 mounted on _$7$MKC0: (UTRA41)
          $ BACK/LOG TEST.TXT TP:TEST0/SAV
            %BACKUP-S-COPIED, copied USER1:[USER]TEST.TXT;1
          $ DISMOUNT/NOUNLOAD TP
          $ MOUNT/FOREIGN TP
            %MOUNT-I-MOUNTED, TEST0 mounted on _$7$MKC0: (UTRA41)
          $BACK/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



PROBLEMS ADDRESSED IN VMS731_IIDRIVER-V0100 KIT

     o  IIDRIVER fix for revision D04 server management card on DS20E

        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



PROBLEMS ADDRESSED IN VMS731_LAN-V0500 KIT

     o  Previous LAN kit not compatible with new PCSI functionality

        The VMS731_LAN-V0400 kit is not compatible with the newly
        released PCSI UNDO functionality.  This new PCSI functionality
        allows a user to uninstall a patch kit.  If a user was to
        install the VMS731_LAN-V0400 patch kit using the new
        PCSI$SAVE_RECOVERY_DATA option and then attempted to uninstall
        the kit using the UNDO feature, the system could be left in an
        unbootable state.  This new VMS731_LAN-V0500 kit re-issues the
        VMS731_LAN-V0400 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 VMS731_LAN-V0500 kit.  If
        you have already installed the VMS731_LAN-V0400 patch kit,
        there is no need to install the VMS731_LAN-V0500 kit.

        Images Affected: POSTUNDO.COM


PROBLEMS ADDRESSED IN VMS731_LAN-V0400 KIT

     o  Writeboot not done after installation of VMS731_LAN-V0300 kit

        The VMS731_LAN-V0300 patch kit did not perform a writeboot
        after installing the APB.EXE file.  The previous kit also did
        not make a contiguous copy of the APB.EXE file or diasable
        FILEMOVE.  These problems could cause the system to become
        unbootable.

                          **** NOTE ****

        Successfully rebooting the system after installation of the
        VMS731_LAN-V0300 kit does not guarantee your system will not
        experience boot problems in the future.  In order to avoid
        boot problems you must install this kit or perform a
        contiguous copy and writeboot manually.  The APB.EXE file must
        also have MOVEFILE disabled.

        To perform these steps manually, execute the following
        commands from a privileged account:

          1.  Perform a contiguous copy of APB.EXE

              $ COPY/CONTIGUOUS SYS$COMMON:[SYSEXE]APB.EXE -
                                SYS$COMMON:[SYSEXE]APB.EXE


          2.  Disable MOVEFILE on APB.EXE

              $ SET FILE/NOMOVE SYS$COMMON:[SYSEXE]APB.EXE


          3.  Enter MCR WRITEBOOT and answer the questions as shown:

              $ MCR WRITEBOOT
              Update VAX portion of boot block (default is Y) : No
              Update AXP portion of boot block (default is Y) : Yes
              Enter AXP boot file : SYS$COMMON:[SYSEXE]APB.EXE
              $


        If you have installed the VMS731_LAN-V0300 kit and execute
        these corrective steps, there is no need to install this
        VMS731_LAN-V0400 patch kit.

        Images Affected: [SYSEXE]APB.EXE


PROBLEMS ADDRESSED IN VMS731_LAN-V0300 KIT

     o  SYS$CONFIG.DAT in incorrect directory

        Previous VMS731 LAN patch kits placed SYS$CONFIG.DAT in the
        SYS$COMMON:[SYS$LDR] directory.  This is incorrect.  The image
        should be placed in the SYS$COMMON:[SYSEXE] directory.

        Images Affected: [SYSEXE]SYS$CONFIG.DAT


PROBLEMS ADDRESSED IN VMS731_LAN-V0200 KIT

     o  Allow link partner sufficient time to notice the link state
        change and participate in the auto-negotiation process.

        Increase the time allowed for fiber auto-negotiation from 200
        milliseconds to 5 seconds to give the link partner sufficient
        time to notice the link state change and participate in the
        auto-negotiation process.

        Images Affected: [SYS$LDR]SYS$EW5700.EXE
                         [SYS$LDR]SYS$EGBTDRIVER.EXE
                         [SYSEXE]APB.EXE
                         [SYSEXE]DEBUG_APB.EXE
                         [SYSEXE]APB_BOOTP.EXE


     o  Difficulty completing auto-negotiation

        When doing fiber auto-negotiation, do not call ew$check_link
        to check the link state since the link state is determined in
        the auto-negotiation, and ew$check_link resets the auto-
        negotiation context.  What was happening was that during
        transmit processing, the check link routine was called to see
        if the link was now up (when the link was down).  The transmit
        request was processed in the middle of the auto-negotiation
        sequence which then restarted the sequence.  This made it
        difficult to complete auto-negotiation because it was getting
        restarted in the middle.

        Images Affected: [SYS$LDR]SYS$EW5700.EXE
                         [SYS$LDR]SYS$EGBTDRIVER.EXE
                         [SYSEXE]APB.EXE
                         [SYSEXE]DEBUG_APB.EXE
                         [SYSEXE]APB_BOOTP.EXE


     o  Set wait time to set up PCI subsystem ID registers to 750
        milliseconds

        When shutting down (crash or normal shutdown), after reset,
        wait 750 milliseconds to give enough time for the firmware to
        set up the PCI subsystem ID registers, so the boot driver
        properly identifies the type of device.  The firmware
        initially fills in the registers with bogus values and then
        fills them in correctly, so if the boot driver looks at them
        too soon, it may think the device is a fiber rather than
        copper or vice versa.

        Images Affected: [SYS$LDR]SYS$EW5700.EXE
                         [SYS$LDR]SYS$EGBTDRIVER.EXE
                         [SYSEXE]APB.EXE
                         [SYSEXE]DEBUG_APB.EXE
                         [SYSEXE]APB_BOOTP.EXE


     o  Driver can miss an updated ring entry

        Add a memory barrier between looking at the status block and
        the transmit ring context entry, to cure a problem where the
        driver can miss an updated ring entry and think there are one
        fewer entries in the ring.  This can result in a bugcheck when
        the transmit entry expect and actual are compared.

        Images Affected: [SYS$LDR]SYS$EW5700.EXE
                         [SYS$LDR]SYS$EGBTDRIVER.EXE
                         [SYSEXE]APB.EXE
                         [SYSEXE]DEBUG_APB.EXE
                         [SYSEXE]APB_BOOTP.EXE


     o  EIDRIVER did not consistently report a link down condition.

        Images Affected: [SYS$LDR]SYS$EIDRIVER.EXE



     o  Random corruption on transmits with DEFPAs

        Images Affected: [SYS$LDR]SYS$FWDRIVER.EXE



     o  Transmit queue accumulates large numbers of transmit
        requests, exhausting all of pool.

        When the cable is disconnected, the DEGXA (Tigon 3 Gigabit
        Ethernet device) driver completes transmit requests with error
        status as expected.  However, it may complete the requests
        very slowly, one per second.  If an application does not limit
        the number of outstanding transmits it issues, the transmit
        queue in the driver may accumulate large numbers of transmit
        requests, eventually exhausting all of pool.  One such
        application is DECnet-Plus.  Pool is not actually lost, it
        just gets consumed by outstanding transmit requests.  

        Images Affected: [SYS$LDR]SYS$EW5700.EXE


PROBLEMS ADDRESSED IN VMS731_LAN-V0100 KIT

     o  EIDRIVER runtime driver changes

        The following two EIDRIVER runtime driver changes have been
        made:

           o  If large numbers of TCP/IP telnet sessions are active,
              EIDRIVER may crash if the number of transmit segments for
              a transmit request reaches the limit and the last segment
              crosses a page boundary.  This fix corrects an off-by-one
              check in the driver.

           o  Transmit or receive requests issued through the QIO
              interface which specify 64-bit buffers are returned with
              error status.  This fix sets a flag in the driver function
              table that that says 64-bit addresses are supported.

        Images Affected: [SYS$LDR]SYS$EIDRIVER.EXE


     o  EW1000A runtime driver changes

        The following two EW1000A runtime driver changes have been
        made:

           o  Transmit or receive requests, issued through the QIO
              interface which specify 64-bit buffers, are returned with
              error status.  This fix sets a flag in the driver function
              table that that says 64-bit addresses are supported.

           o  On rare occasions, the DEGPA firmware fails to write the
              proper data into a receive return entry.  The DEGPA driver
              verifies that the return entry contains the expected data
              and if it does not match what is expected, the driver
              crashes the system with a NETDLLERR bug check.  A driver
              change is now implemented to detect this exact condition
              and reset and restart the DEGPA rather than crash the
              system.  The driver will still crash the system if the
              return entry data does not match and it does not detect
              the condition where the DEGPA has failed to update the
              return entry.  So we avoid crashing in the benign error
              case.


        Images Affected: [SYS$LDR]SYS$EW1000A.EXE


     o  EW5700A runtime driver change

        The following EW5700A runtime driver change has been made:

           o  OpenVMS V7.3-1 only supported the Broadcom 5703 LOM (LAN
              on motherboard) chip on the AlphaServer DS25, and that,
              only in 1000 mbit full-duplex mode.  This update adds full
              support for 10 and 1000 mbit and half-duplex mode for the
              Broadcom 5703 LOM as well as full support for the DEGXA-SA
              (fiber 5703 NIC) and DEGXA-TA (UTP 5703 NIC).


        Images Affected: [SYS$LDR]SYS$EW1000A.EXE


PROBLEMS ADDRESSED IN VMS731_LINKER-V0100 KIT

     o  Increase the RMS I/O related parameters when doing I/O to the
        image file and map.

        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



PROBLEMS ADDRESSED IN VMS731_MSCP-V0100 KIT

     o  SCSERROR crash when serving TMSCP-speaking tape devices

        A SCSERROR bugcheck will occur on the server when serving a
        native TMSCP-speaking tape device (e.g.  HSJ-based or
        DSSI-based tape) via SCS over NI.

          Crashdump Summary Information
          -----------------------------
          Bugcheck Type: SCSERROR, Fatal condition detected 
                         in SCS layer or SCS port
          Current Image:     $20$DKA100:[SYSO.SYSCOMMON.][SYSEXE]
                             DIRECTORY.EXE
          Failing PC:        FFFFFFFF.84320A08  PPC.BUFNAM_INV+00088
          Failing PS:        28000000.00000804
          Module:            SYS$PEDRIVER (Link Date/Time:
                             18-JUL-2002 20:02:47.24)
          Offset:            00018A08


        Images Affected: [SYS$LDR]TMSCP.EXE



PROBLEMS ADDRESSED IN VMS731_PARTITIONING-V0100 KIT

     o  Wrong node handle selected for transition operations.

        If a user attempts to create a hard or soft partition, other
        than 0, in an ES47/ES80/GS120 Series system configuration, and
        does not have the VMS731_PARTITIONING-V0100 kit installed, the
        wrong node handle will be selected for transition operations.
        This could result in state errors rather than random
        operations.

        An error message such as the following may be displayed during
        the booting of the secondary partition:

        %SMP-F-CPUBAD, CPU #xx palcode revision does not match that
        of the primary

        A SHOW CPU command for that instance will also display the
        wrong ownership and state information.

        Images Affected: [SYSEXE]SMPUTIL.EXE
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.EXE
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION.STB
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.STB
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.STB


     o  System Crash

        Extensive, concurrent display by multiple CPUs to the console
        could corrupt the console message cache and could adversely
        affect the fork queue resulting in system crashes.

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     INVEXCEPTN, Exception while above
                             ASTDEL
          Current Process:   INVALQUEUE00000
          Failing PC:        FFFFFFFF.800468FC
                             EXE$PRIMITIVE_FORK_C+0004C
          Failing PS:        20000000.00001604
          Module:            SYSTEM_PRIMITIVES_MIN (Link Date/Time:
                             20-NOV-2002 15:11:53.24)
          Offset:            0001E8FC


        Images Affected: [SYSEXE]SMPUTIL.EXE
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.EXE
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION.STB
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.STB
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.STB


PROBLEMS ADDRESSED IN VMS731_PTHREAD-V0100 KIT

     o  Decthreads Bugcheck - non-ready thread selected

        There is a window between the setting of the initial thread's
        state to ready, but before it has been inserted into the list
        of ready threads.  If the initial thread returns from
        servicing ASTs during this window and that return is to a
        point where the initial thread is waiting on a
        still-outstanding condition variable wait operation, the
        thread's state may be set to BLOCKED.  When the attempt is
        then made to insert the thread into the ready queue, a
        bugcheck results.  This problem may affect applications with
        upcalls enabled.

        This change removes calls to do undeferrals at the point in
        the code path when this window occurs.

        Bugcheck Extract:

          DECthreads bugcheck (version T3.19-044), terminating execution.
          % Reason:  selected a non-ready thread 1 (0x7BC94888), state 1


        Images Affected: [SYSLIB]PTHREAD$DBGSHR.EXE
                         [SYSLIB]PTHREAD$RTL.EXE




     o  Failed to analyze a code path which allowed a change of state
        in the initial thread at a point where that state was assumed
        to be consistent.


    o  "system-f-stkovf" stack overflow errors

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

        Under certain conditions, if an application AST arrives while
        the Java garbage collector is running a process hang can
        occur.  The problem is that 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.  With this fix, AST delivery is now
        deferred while the garbage collector is running.

        Images Affected: [SYSLIB]PTHREAD$DBGSHR.EXE
                         [SYSLIB]PTHREAD$RTL.EXE


     o  Threaded application can hang on a system with multiple
        kernel threads enabled.

        A bug in the way DECthreads responded to topology changes (CPU
        stop or start) could have caused a threaded application to
        hang on a system with multiple kernel threads enabled.

        Images Affected: [SYSLIB]PTHREAD$DBGSHR.EXE
                         [SYSLIB]PTHREAD$RTL.EXE


PROBLEMS ADDRESSED IN VMS731_QMAN-V0100 KIT

     o  'invalid device name' when autostart queues are started.

        When, initializing and starting a telnet symbiont queue with
        the /AUTOSTART_ON qualifier, the queue manager running on an
        OpenVMS Alpha version V7.3-1 system, fails with an "invalid
        device name" error as shown below.

        LATEST> init/que/start/proc=tcpip$telnetsym/auto=latest::
        "16.32.144.67:9100" test4
        %%%%%%%%%%%  OPCOM  26-SEP-2002 09:33:42.46  %%%%%%%%%%%
        Message from user SYSTEM on LATEST
        TCPIP$TELNETSYM - (TEST4) Invalid /ON="host:port" format

        %%%%%%%%%%%  OPCOM  26-SEP-2002 09:33:42.58  %%%%%%%%%%%
        Message from user SYSTEM on LATEST
        %QMAN-I-QUENOTSTART, queue TEST4 could not be started
        on node LATEST

        %%%%%%%%%%%  OPCOM  26-SEP-2002 09:33:42.58  %%%%%%%%%%%
        Message from user SYSTEM on LATEST
        -QMAN-I-QUEAUTOOFF, queue TEST4 is now autostart inactive

        %%%%%%%%%%%  OPCOM  26-SEP-2002 09:33:42.58  %%%%%%%%%%%
        Message from user SYSTEM on LATEST
        -SYSTEM-F-IVDEVNAM, invalid device name

        %SYSTEM-F-IVDEVNAM, invalid device name

        Images Affected: [SYSEXE]QMAN$QUEUE_MANAGER.EXE



     o  Suppress needless audit events after submit

        If auditing alarms are enabled for the queue class, submitting
        a batch job by a non priviledged user, produces an unnecessary
        CONTROL access audit failure message as below:

          %%%%%%%%%%%  OPCOM   9-SEP-2002 14:53:07.76  %%%%%%%%%%%
          Message from user AUDIT$SERVER on NFFM01
          Security alarm (SECURITY) and security audit (SECURITY)
          on NFFM01, system id: 1985
          Auditable event:          Object access
          Event time:               9-SEP-2002 14:53:07.76
          PID:                      202002F6
          Source PID:               2024C65C
          Username:                 FTEXAWE
          Process owner:            [SEC,FTEXAWE]
          Object class name:        QUEUE
          Object name:              NFFM01_BATCH
          Object owner:             [SYSTEM]
          Object protection:        SYSTEM:M, OWNER:D, GROUP:R, WORLD:S
          Access requested:         CONTROL
          Status:                   %SYSTEM-F-NOPRIV, insufficient
                                    privilege or object protection violation


        Images Affected: [SYSEXE]QMAN$QUEUE_MANAGER.EXE



PROBLEMS ADDRESSED IN VMS731_RMS-V0200 KIT

     o  Fix for directory not found (RMS-E-DNF) errors when copying
        to a spooled device.

        RMS fix for directory not found errors when copying to a
        spooled device.

        Copying a file to a spooled device will result in the
        following errors under OpenVMS Alpha V7.3-1:

          %COPY-E-OPENOUT, error opening TTA0:[DIR]FILE.EXT;1 as output
          -RMS-E-DNF, directory not found
          -SYSTEM-W-NOSUCHFILE, no such file

        These errors are the result of a change to the RMS directory
        path cache code in support of merging Posix support into RMS.
        For spooled devices, RMS was applying defaults to missing
        portions of the file specification, including a defaulted
        directory.  Prior to the V7.3-1 change, this was a harmless
        operation since the directory portion was ignored for a
        spooled device.  With the added Posix support, the defaulted
        directory specification is now validated resulting in the
        directory not found error.  Since spooled files are not
        entered into a directory, a change has been implemented to
        bypass the validation of the directory for a spooled device.

                               CAUTION

        While the following is not directly related to this fix, from
        the reports that we received from the field of this problem,
        it appears that some users may need a reminder of the proper
        procedures they should use when setting a device /SPOOLED.
        The user setup error that can occur if proper procedures are
        not followed is not new to OpenVMS V7.3-1.  We are simply
        taking this opportunity to share the proper procedures so this
        user setup problem can be avoided.

        The target queue of the spooling operation must either be
        explicitly specified on the SET command line, or a queue with
        the same name as the spooled device must exist.
        When issuing a $SET DEVICE/SPOOLED command, failure to
        explicitly specify a target queue name will default the queue
        name to that of the spooled device.  Failure to specify a
        valid existing queue name will result in subsequent attempts
        to copy to the device to fail with a file deaccess failure
        (RMS-E-DAC) during the close operation.

        The following is an example of implicitly specifying the queue
        name as "LTA69":

             $ SET DEVICE/SPOOLED LTA69:

        In this example, the queue name has been derived from the
        device name since it was not explicitly specified.  Failure to
        ensure that the implicit queue name (LTA69) exists will cause
        all subsequent use of the spooled device to fail with a
        deaccess failure.

        This is the same as issuing the following command:

             $ SET DEVICE/SPOOLED=(LTA69,SYS$SYSDEVICE:) LTA69:

        The following is an example of explicitly specifying the queue
        name:

             $ SET DEVICE/SPOOLED=('QUEUE_NAME',SYS$SYSDEVICE:) LTA69:

        An example of an explicit specification where the queue name
        is "LATQUE" might be:

             $ SET DEVICE/SPOOLED=(LATQUE,SYS$SYSDEVICE:) LTA69:

        Failure to ensure that the specified queue exists (either
        implicit or explicit), will result in the errors seen below.
        This example presumes that the LTA69 queue does not exist:

             $ SET DEVICE/SPOOLED LTA69:
             $ COPY LOGIN.COM LTA69:

             %COPY-E-CLOSEOUT, error closing LTA69: as output
             -RMS-E-DAC, ACP file deaccess failed during $CLOSE
             -SYSTEM-F-NOTPRINTED, failed to queue spool file for print

        Images Affected:  [SYS$LDR]RMS.EXE



     o  RMS:  Fix to prevent a SSRVEXCEPT bugcheck under rare
        occasions with RU journaling enabled.

        RMS fix to prevent a SSRVEXCEPT bugcheck when RU journaling is
        enabled for a file.

        A System Service Exception may occur under rare circumstance
        when RU journaling is enabled on a file.  The failure is due
        to the access of an invalid page (access violation).

        Images Affected: [SYS$LDR]RMS.EXE



PROBLEMS ADDRESSED IN VMS731_RMS-V0100 KIT

     o  RMS:  Fix for user  buffer  size  exceeding  terminal  driver
        limit  (in  particular  if  SYSGEN parameter MAXBUF > 32K and
        Telnet session)

        RMS fix for a user buffer size exceeding the  terminal  driver
        limit (in particular if the SYSGEN parameter MAXBUF is greater
        than 32K and the session is a Telnet session).

        The specific error returned by a terminal  driver  to  RMS  is
        SS$_IVBUFLEN;  RMS  returns  to  the  caller  RMS-F-QIO in the
        RAB$L_STS  and  the  system  error  (SYS-F-IVBUFLEN)  in   the
        RAB$L_STV.   However, if this error is returned to a C runtime
        library call for a read I/O to a terminal, it is  more  likely
        the  symptom visible to users will be a C program failing with
        a a generic C IO error.

        An RMS change was implemented in Alpha V7.3-1 that may  result
        in a larger I/O transfer size being used for "reads" from unit
        record devices (mainly terminals) than  the  previous  smaller
        default  RMS  intermediate  buffer  size.   The larger size is
        based on the size of the user's record buffer specified in the
        RAB (RAB$W_USZ or RAB64$Q_USZ) for the read.

        Under certain conditions, the larger  size  can  result  in  a
        limit   imposed  by  at  least  one  driver  (TTDRIVER)  being
        exceeded.  Drivers are free to set  a  limit  arbitrarily;  in
        this  case  the  limit  imposed  is  32767.  When the limit is
        exceeded, an SS$_IVBUFLEN  fatal  error  is  returned  by  the
        driver.

        One example of the combination of conditions that can  trigger
        this problem is as follows:

           -  System is accessed via Telnet (TNDRIVER) or SET  HOST/LAT.
              This  results  in the particular TT driver with this limit
              being used for the terminal I/O.  A regular SET HOST  uses
              another  terminal  driver and does not encounter the limit
              check.

           -  The read request to this  particular  TT  driver  is  made
              through RMS with the user buffer size specified in the RAB
              (RAB$W_USZ  or  RAB64$Q_USZ)  being  greater  than  32767.
              While  this  could  be  done  from any application issuing
              calls to RMS,  there  is  a  high  probability  that  a  C
              application  with  a  C  runtime library call to read data
              from a terminal (e.g.  getc, gets) may be involved if  the
              SYSGEN  parameter  MAXBUF on the impacted system is set to
              greater than 32K.

              The C runtime  library  uses  a  heuristic  involving  the
              SYSGEN  parameter  MAXBUF value (MAXBUF less 512 bytes) to
              set the buffer size  in  the  RAB  passed  to  RMS.   This
              parameter  ships with a default of 8192 (with a maximum of
              64000).  However, some systems increase this parameter  to
              the  maximum  for  tuning purposes.  This results in the C
              runtime library  heuristic  setting  a  user  buffer  size
              greater  than  32K.   There is nothing substantively wrong
              with the C runtime library or any application specifying a
              user buffer size greater than 32K.

        For  this  particular  example,  a  proactive  measure  or  an
        immediate  workaround  to  the  problem  is  to set the MAXBUF
        SYSGEN parameter down to 32K.  This is a dynamic parameter  so
        no  reboot  is required.  We are not aware of any applications
        that would break by setting MAXBUF down  to  32K.   Once  this
        remedial  kit  is  applied, the SYSGEN parameter MAXBUF can be
        reset above 32K.

        Images Affected: [SYS$LDR]RMS.EXE
                         [SYSLIB]SDARMS$SHARE.EXE



     o  RMS:  Fix for incorrect record returned  for  a  reverse  key
        search on a secondary key.

        RMS fix for an incorrect record returned  for  a  reverse  key
        search  on  a  secondary  key  using  a partial key (just some
        leading characters).

        As a side-effect of calling a sequence of  common  lower-level
        routines  to unpack a compressed key or segmented primary key,
        the potential exists that an RMS internal scratch  key  buffer
        may  be overwritten.  This results in the target secondary key
        value being replaced with the primary key associated with  the
        primary  record  being  unpacked.   The full set of conditions
        necessary for this to occur are rare.

        While no user data is compromised by the overwriting,  if  the
        copy  of  the  target  secondary  key value gets replaced, the
        search from thereon uses this  particular  primary  key  value
        rather  than  the  target secondary key value as its criterion
        for the secondary key search.  In such a case if  the  forward
        search  for a match reaches the end-of-the-key without finding
        either an exact match or a "mismatch" (a record with a  higher
        key  value), it will return the last record at the end of that
        secondary key as the match.

        Images Affected: [SYS$LDR]RMS.EXE



PROBLEMS ADDRESSED IN VMS731_RPC-V0100 KIT

     o  DCE$DCED process aborts with SYSTEM-F-ACCVIO

        The DCE$DCED process aborts with SYSTEM-F-ACCVIO when a
        command procedure containing dce_login and ACMSxp commands is
        executed in an infinite loop.

        Images Affected: [SYSLIB]DCE$LIB_SHR.EXE



     o  Question on RPC and TCPware

        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  FATAL rpc recv CNRCVR.C;1 563 0x0e41db40

        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  DCE V3.0 Client example programs ACCVIO when compiled with
        -tracelog_manager

        DCE client example programs, located at
        [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  DCE V3.0 Client Configuration Fails with "Invalid I/O Channel
        error"

        DCE V3.0 Client Configuration fails with the below error
        (socket) post_net_channel_qio

          *** FATAL ERROR at SOCKDNETIV.C;14946 ***
          %SYSTEM-F-OPCCUS, opcode reserved to customer
          fault at PC=FFFFFFFF80A5E7F4,PS=0000001B 

        Images Affected: [SYSLIB]DCE$SOCKSHR_DNET_IV.EXE
                         [SYSLIB]DCE$SOCKSHR_DNET_OSI.EXE


     o  DCE$CDSADVER process hangs in the client configuration phase

        While configuring the DCE as a client, the dce$cdsadver
        process goes into the hang state, leading to the configuration
        hang.

        Images Affected: [SYSLIB]DCE$SOCKSHR_IP.EXE



     o  Fixed fatal exception in rpc receiver thread module CNRCVR

        The application process reports "FATAL rpc recv CNRCVR.C;1"
        leading to an hang situation.  The applications were to
        restart.

        Images Affected: [SYSLIB]DCE$LIB_SHR.EXE



     o  "FATAL rpc cn_state CNSCLSM.C;1" reported by the application
        program

        A "FATAL rpc cn_state CNSCLSM.C an Illegal state transition
        detected in CN server call state machine" error has been
        reported in the DCE application.  The message does not display
        the correct state and event of the state machine.

        Images Affected: [SYSLIB]DCE$LIB_SHR.EXE



     o  DCE Security Issue:  tickets fail to reauthenticate

        The thread responsible for the ticket refresh operation waits
        forever to unlock a mutex, leading to expiration of the self
        credentials.

        Images Affected: [SYSLIB]DCE$LIB_SHR.EXE



     o  DCOM$RPCSS process was aborting with the RMS fatal error

        For each client request of the DCOM application, one persona
        is left out after the client completion.  After running for
        several hours the personas accumulate and the DCOM$RPCSS
        process aborts with the RMS fatal error.

        Images Affected: [SYSLIB]DCE$LIB_SHR.EXE



PROBLEMS ADDRESSED IN VMS731_SYS-V0300 KIT

     o  System crash caused by NPP corruption

        Recent changes to handle segmented data capturing from remote
        processes failed to detect possible data overrun conditions.
        If a buffer of insufficient size is passed to the service, the
        resulting overrun could result in NPP corruption.  Customer's
        experiencing a crash due to the data overrun would see
        corruption in NNP as the cause.  Programs that pass data
        buffers too small to contain the data items request,
        JPI$_RIGHTLIST items in particular, can trigger this crash.

        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  Processes calling LIB$SPAWN without specifying the flag of
        NOWAIT can hang in HIBernation state in supervisor mode.

        After applying VMS731_SYS-V0200 patch kit, threaded processes
        calling LIB$SPAWN without specifying the flag of NOWAIT can
        hang in HIBernation state in supervisor mode.  The user AST
        queue (PCB$L_ASTQFL_U) will have the PCB$L_WAKE_ACB queued to
        it, waiting to be delivered, but blocked by the higher mode.

        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  ANAL/PROC can not walk the stack

        An ANALYZE/PROCESS command can result in the following error:

             %SDA-W-EXCLDATA, data excluded from dump due to
             insufficient privilege

        Images Affected: [SYSLIB]IMGDMP.EXE
                         [SYSLIB]SDA$SHARE.EXE



     o  DBG> SHOW CALLS command gives no useful information

        When analyzing a process dump produced using DCL "SET
        PROCESS/DUMP=NOW", the "DBG> SHOW CALLS" command gives no
        useful information.  Only system call frames are displayed.

        Images Affected: [SYSLIB]IMGDMP.EXE



     o  System service exception bugcheck while using JAVA

        Using JAVA, an attempt to merge activate an image using a
        logical name, in a secondary kernel thread, access violates
        with a system service exception.  The exception is due to
        accessing a stale context pointer.  If that shareable image is
        then dynamically invoked with lib$find_image_symbol, using a
        logical that points to a second logical which points to the
        image (an extra level of indirection), then the process gets
        deleted, causing the bugcheck.

        Images Affected: [SYS$LDR]IMAGE_MANAGEMENT.EXE



     o  Dump compression can cause lost data.

        There is a problem with dump compression that can cause lost
        data.  This is seen most often when trying to COPY/DECOMPRESS
        the dump, but it is also possible to get incorrect data out of
        the dump during analysis.  In addition, SDA can get stuck in a
        CPU-bound loop trying to COPY/DECOMPRESS certain dumps.

        Images Affected: [SYSLIB]IMGDMP.EXE
                         [SYSLIB]SDA$SHARE.EXE
                         [SYS$LDR]EXCEPTION.EXE
                         [SYS$LDR]EXCEPTION_MON.EXE
                         [SYS$LDR]EXCEPTION.STB
                         [SYS$LDR]EXCEPTION_MON.STB


     o  The new SDA will not recognize old dumps and vice-versa.

        The layout of the dump header changed between OpenVMS V7.3 and
        V7.3-1.  Now, a DUMPEMPTY error is given rather than an
        INCDUMPFORM error.  Because of this the new SDA will not
        recognize old dumps and vice-versa.

        Images Affected: [SYSLIB]SDA$SHARE.EXE



     o  ACCVIO when using SDA

        SDA overruns its buffer for storing page headings.  This leads
        to ACCVIOs.  

        Images Affected: [SYSLIB]SDA$SHARE.EXE


     o  SDA cannot traverse pool fragments spread across multiple
        RADs and does not always recognize VCRPs

        Images Affected: [SYSLIB]SDA$SHARE.EXE


     o  Non-fatal INCONSTATE bugcheck errorlog entries

        After installation of the VMS731_SYS-V0200 patch kit,
        uniprocessor systems experience numerous non-fatal INCONSTATE
        bugcheck errorlog entries.  Setting BUGCHECKFATAL to 1 to
        induce a crash indicates an INCONSTATE bugcheck at
        SYSDEVICE+0013A4.

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:    INCONSTATE, Inconsistent I/O data base
          CPU Type:         AlphaServer 4100 5/300 2MB
          VMS Version:      V7.3-1
          Current Process:  NET$ACP
          Current Image:    DSA0:[SYS0.SYSCOMMON.][SYSEXE]NET$ACP.EXE;1
          Failing PC:       FFFFFFFF.801213A4  SYSDEVICE+013A4
          Failing PS:       00000000.00000B00
                                          ^ IPL = 11. .GT. 2
          Module:           SYSDEVICE (Link Date/Time:
                                      1-OCT-2002 16:16:21.09)
          Offset:           000013A4

        Note that the system only crashes if BUGCHECKFATAL is set.
        Otherwise, it will log non-fatal INCONSTATE bugcheck errorlog
        entries.

        Images Affected: [SYS$LDR]SYSDEVICE.EXE
                         [SYS$LDR]SYSTEM_PRIMITIVES.EXE
                         [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE
                         [SYS$LDR]SYSTEM_PRIMITIVES.STB
                         [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB


     o  Memory access difficult in a full dump.

        When doing a SET PROCESS, if the process is not current, the
        null process's PTBR (Page Table Base Register) is used, which
        is -1.  This makes memory access very difficult in a full
        dump.

        Images Affected: [SYSLIB]SDA$SHARE.EXE


     o  SS$_RSDMNOTFOU - Resource domain not found errors

        When creating many resource domain IDs via
        $SET_RESOURCE_DOMAIN with RSDM$_JOIN_DOMAIN, subsequent calls
        to end that association with RSDM$_LEAVE could result in the
        error SS$_RSDMNOTFOU (resource domain not found) on some IDs.

        Images Affected: [SYS$LDR]LOCKING.EXE



     o  ACBs not saved

        An image dump does not save the ACBs (Asynchronous Control
        Block) associated with a kernel thread being dumped.

        Images Affected: [SYSLIB]IMGDMP.EXE



     o  Corrupt IMCBs and/or KFERESs cause SDA to fail

        SDA walks IMCBs (Image Control Blocks) and examines KFERES
        (Known File Entry section descriptor) structures connected to
        IMCBs when reading symbol files, symbolizing addresses, and
        executing the MAP or SHOW PROCESS/IMAGE[=ALL] commands.  If
        IMCBs and/or KFERESs are corrupt, SDA can fail in a myriad of
        ways, including a compute-bound loop.

        Images Affected: [SYSLIB]SDA$SHARE.EXE


     o  An SDA copy command can get stuck in a loop.

        An SDA copy command can get stuck in a loop.  For Example:

          SYSTEM> mcr sda
          Enter name of dump file >
          %SDA-I-USEMASTER, accessing dump file via _$1$DGA6005:, 
          master member of shadow set _DSA18:

          OpenVMS (TM) Alpha system dump analyzer
          ...analyzing a compressed selective memory dump...

          Dump taken on 16-DEC-2002 15:41:58.44
          INVPTEFMT, Invalid page table entry format

          SDA> COPY $1$dga5011:[dump]INVPTEFMT_qtv18_16-dec.dmp
          Copy Status: copying block 35783 (of 2084576 total blocks)
          Copy Status: copying block 77566 (of 2084576 total blocks)
          Copy Status: copying block 129423 (of 2084576 total blocks)
          Copy Status: copying block 256423 (of 2084576 total blocks)
          Copy Status: copying block 429355 (of 2084576 total blocks)
          Copy Status: copying block 546703 (of 2084576 total blocks)
                               .
                               .
                               .

        Images Affected: [SYSLIB]SDA$SHARE.EXE



     o  INVSECURESTATE system crash

        Several multi-threaded servers have experienced a condition
        where the reference counts of various persona structures have
        fallen out of sync.  The security subsystem triggers an
        INVSECURESTATE system crash when this condition is detected by
        the sanity checks.

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     INVSECURESTATE, Invalid state detected
                             by SECURITY subsystem
          Current Process:   TNT_SERVER
          Current Image:     $1$DUA0:[SYS3.SYSCOMMON.][SYSEXE]
                             TNT$SERVER.EXE
          Failing PC:        FFFFFFFF.801A8E94    
                             NSA$ASSUME_PERSONA_C+00064
          Failing PS:        10000000.00000000
          Module:            SECURITY    
                             (Link Date/Time: 13-SEP-2000 06:39:51.16)
          Offset:            00006E94


        Images Affected: [SYS$LDR]SECURITY.EXE
                         [SYS$LDR]SECURITY_MON.EXE



     o  SMTP mail delivery process hang

        After installing the DEC-AXPVMS-VMS731_SYS-V0200--4.PSCI ECO
        kit, process hangs could occur when using SMTP mail.  When
        sending a mail message via SMTP, the mail is delivered but the
        process handling SMTP mail delivery hangs on creating the mail
        notification.  The mail delivery notification is never sent
        and any subsequent SMTP mail accumulates, unsent, in the
        queue.  The process hangs occur because BRKTHR tries to
        allocate memory from P1 space.  If it is unsuccessful, it
        tries to allocate from P0 space.  This is when the hangs
        occur.

        This kit removes the code fix for V7.3-1 that caused this
        problem to occur.  This fix was originally done to solve the
        following problem.  Since this fix is being removed, this
        problem could re-occur:

           o  The system can crash with a SSRVEXCEPT bugcheck when an
              image exits before the $BRKTHRU has been delivered to some
              of its targets.  Note that occurrance of this problem is
              rare and can only occur if:

               -  A user program must use the asynchronous version of
                  the system call $BRKTHRU -- using the synchronous
                  form, $BRKTHRUW, prevents this)

               -  The P1 allocation area sized by the SYSGEN parameter
                  CTLPAGES must be exhausted

               -  The program must then exit before the $BRKTHRU call
                  has finished sending messages to all the appropriate
                  terminals.


        Note that the third issue cannot happen if the synchronous
        form of the $BRKTHRU call, $BRKTHRUW, is used.

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

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

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


        Images Affected: [SYS$LDR]IO_ROUTINES.EXE
                         [SYS$LDR]IO_ROUTINES.STB
                         [SYS$LDR]IO_ROUTINES_MON.EXE
                         [SYS$LDR]IO_ROUTINES_MON.STB



     o  Mount verification abort errors

        Mount verification can abort when a tape, mounted on a
        dual-path controller is dismounted.  For example:

        Mount a tape on a dual-path controller:

            SYSTEM>>> MOUNT/FOREIGN $2$MUA140:
            %MOUNT-I-MOUNTED, TEST mounted on _$2$MUA140: (MOUSE)
            SYSTEM>>> DISMOUNT $2$MUA140:

        The dismount will hang for TAPE_MVTIMEOUT seconds.  
        Show the device from another session:

          SYSTEM>>> SHOW DEVICE $2$MUA140:

            Device             Device      Error Volume Free   Trans Mnt
            Name               Status      Count Label  Blocks Count Cnt
            $2$MUA140: (MOUSE) MountVerify     0 TEST        0     1   0
                               mounted
                               dismount
                               cached alloc
                               foreign

        If TAPE_MVTIMEOUT expires the following message is received:

            %%%%%%  OPCOM  16-JAN-2003 12:12:14.87  %%%%%%
            Mount verification has aborted for device
            $2$MUA140: (MOUSE, CAT)

        Other symptoms are that the drive can not be mounted on
        another node using the secondary controller if
        mountverification has aborted.

        Images Affected: [SYS$LDR]IO_ROUTINES.EXE
                         [SYS$LDR]IO_ROUTINES.STB
                         [SYS$LDR]IO_ROUTINES_MON.EXE
                         [SYS$LDR]IO_ROUTINES_MON.STB



PROBLEMS ADDRESSED IN VMS731_SYS-V0200 KIT

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

        A program using C signals is aborted with the  condition  code
        set to the C signal value.

        Images Affected: [SYS$LDR]EXCEPTION.EXE
                         [SYS$LDR]EXCEPTION.STB
                         [SYS$LDR]EXCEPTION_MON.EXE
                         [SYS$LDR]EXCEPTION_MON.STB



     o  The system can crash with  a  SSRVEXCEPT,  Unexpected  system
        service exception 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


        Images Affected: [SYS$LDR]IO_ROUTINES.EXE
                         [SYS$LDR]IO_ROUTINES.STB
                         [SYS$LDR]IO_ROUTINES_MON.EXE
                         [SYS$LDR]IO_ROUTINES_MON.STB



     o  A process may hang waiting  for  the  completion  of  an  RMS
        $FLUSH operation.

        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.  For  this  problem
        to  occur  there  has  to  be  a  lot  of cluster-wide $GETJPI
        activity.  A typical stack of  the  hung  process  looks  like
        this:

          Process Stacks (on CPU 00)
          --------------------------
          Current Operating Stack (SUPERVISOR):
                 00000000.7FFABD90 00000000.00000004
                 00000000.7FFABD98 00000000.00000000
                 00000000.7FFABDA0 00000000.00000001
                 00000000.7FFABDA8 00000000.00000002
          SP =>  00000000.7FFABDB0 00000000.0000001D
                 00000000.7FFABDB8 00000000.7FFABEA4
                 00000000.7FFABDC0 FFFFFFFF.98D490D0 SYS$SYNCH
                 00000000.7FFABDC8 00000000.00000000
                 00000000.7FFABDD0 00000000.00000002
                 00000000.7FFABDD8 00000000.0000001D
                 00000000.7FFABDE0 00000000.7FFABEA4
                 00000000.7FFABDE8 00000000.7FFABE18
                 00000000.7FFABDF0 00000000.00000000
                 00000000.7FFABDF8 FFFFFFFF.DF2A59A8 RMS+299A8
                 00000000.7FFABE00 00000000.7AF21AE0
                 00000000.7FFABE08 00000000.7FFABE10
                 00000000.7FFABE10 FFFFFFFF.DF3042E0  RMS+882E0
                 00000000.7FFABE18 00000000.80814501  DECW$XMLIBSHR12+8E501
                 00000000.7FFABE20 00000000.00010001  RMS$_SUC
                 00000000.7FFABE28 FFFFFFFF.DF2A6764  SYS$FLUSH_C+000A0
                 00000000.7FFABE30 FFFFFFFF.DF304560  SYS$FLUSH
                 00000000.7FFABE38 00000000.7FFABEE0
                 00000000.7FFABE40 00000000.00000000
                 00000000.7FFABE48 00000000.7FFABE50
                 00000000.7FFABE50 FFFFFFFF.DF304560  SYS$FLUSH
                 00000000.7FFABE58 00000000.7FFABE9C
                 00000000.7FFABE60 00000003.0000001D
                 00000000.7FFABE68 00000004.00018001  RMS$_STALL
                 00000000.7FFABE70 00000000.7AF4FB64
                 00000000.7FFABE78 00000000.00000000
                 00000000.7FFABE80 00000000.7FFABEE0
                 00000000.7FFABE88 00000000.7AF21AE0
                 00000000.7FFABE90 00000000.0000000E
                 00000000.7FFABE98 80814401.7FFAC4E2  DECW$XMLIBSHR12+8E401
                 00000000.7FFABEA0 01000000.00000000  PTE$M_TYP0
                 00000000.7FFABEA8 00000000.00000000
                 00000000.7FFABEB0 00000000.00000000
                 00000000.7FFABEB8 00000000.00000000
                 00000000.7FFABEC0 00000000.00000000
                 00000000.7FFABEC8 00000000.00000000
                 00000000.7FFABED0 00000000.00000000
                 00000000.7FFABED8 00000000.00000000
                 00000000.7FFABEE0 00000000.7AF21AE0
                 00000000.7FFABEE8 00000000.00000000
                 00000000.7FFABEF0 00000000.03C2834A
                 00000000.7FFABEF8 FFFFFFFF.800F6AD0  EXE$AST_RETURN
                 00000000.7FFABF00 00000000.00000002
                 00000000.7FFABF08 00000000.00040428  XZA_XPCCTRL_M_RESBSY+
                 00000000.7FFABF10 00000000.0000FF80  DAP$K_CTLMENU_I+00070
                 00000000.7FFABF18 00000000.00000000
                 00000000.7FFABF20 00000000.00011480  V_SMP$BUGCHK_HALT_CPU
                 00000000.7FFABF28 00000000.00040128  XZA_XPCCTRL_M_RESBSY+
                 00000000.7FFABF30 FFFFFFFF.98D48940  EXEC_ASTDEL_C
                 00000000.7FFABF38 00000000.7FFABF40
                 00000000.7FFABF40 FFFFFFFF.98D48940  EXEC_ASTDEL_C
                 00000000.7FFABF48 00000000.00000000
                 00000000.7FFABF50 FFFF8000.00000000
                 00000000.7FFABF58 FFFFFFFF.98D490D0  SYS$SYNCH
                 00000000.7FFABF60 00000000.00040088  XZA_XPCCTRL_M_RESBSY+
                 00000000.7FFABF68 00000000.7AE55330
                 00000000.7FFABF70 00000000.00000001
                 00000000.7FFABF78 40A03800.00000000
                 00000000.7FFABF80 00000000.0000002B
                 00000000.7FFABF88 40000000.00000000  IRP$M_FILE_FLUSH
                 00000000.7FFABF90 00000000.00000000
                 00000000.7FFABF98 00000000.00000000

        There are signs of SYS$FLUSH code on the  stack,  as  well  as
        pieces of AST delivery.  Most of the time, the flush occurs on
        a batch logfile, but other  flush  operations  may  suffer  as
        well.

        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  INVEXCEPTN bugcheck when the swapper is the current process.

        A system that supports NUMA and has  RAD_SUPPORT  enabled  can
        crash  with  bugcheck  code INVEXCEPTN 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 [SYS$LDR]SYS$VM.STB



     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  Lookup of a device may fail.

        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.

        The DCL command $ SET VOLUME/REBUILD is an example of this, as
        well   as   a   lookup   via   the  runtime  library  function
        LIB$FIND_IMAGE_SYMBOL.  For example:

          $ SHOW DEVICE $8$DUA10

          Device               Device         Error  Volume
          Name                 Status         Count  Label  

          $8$DUA10: (UTRAMP)   Mounted Alloc  0      TEST1 

          Free     Trans   Mnt
          Blocks   Count   Cnt

          2050506      1     1

          $ 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

        This happens if we get DDB's (Device Data Block) organized  in
        this way:

          System: UTRAMP
          DDB:    DUA   UCB: 00000000 2P_UCB: 00000000 Alloclass:   0
          DDB:    DIA   UCB: 80DCEE40 2P_UCB: 00000000 Alloclass:   8
          DDB:    DUA   UCB: 80DCDD00 2P_UCB: 00000000 Alloclass:   8
          DDB:    MUA   UCB: 80E8E280 2P_UCB: 00000000 Alloclass:   0


        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  Starting  up  Pathworks  Advanced  server  may  fail  with  a
        SS$_BADPARAM error

        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
                         [SYS$LDR]SYSLDR_DYN.STB



    o  System can crash with a SSRVEXCEPT bugcheck

       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  When using $GETJPI to request rightslist information about  a
        process, incorrect information is returned.

        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.

        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.

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

        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
                         [SYS$LDR]SHELL8K.STB



     o  Nonpaged pool usage may increase over time due to a leak  of
        process control blocks (PCB).

        Nonpaged pool usage may increase over time due to  a  leak  of
        process  control  blocks  (PCB).   This leak only occurs under
        very specific circumstances which are not that common  and  it
        only  affects  NUMA  platforms  with RAD_SUPPORT enabled.  The
        platform  has  to  be  "sub-optimally"  configured  with  RADs
        without private memory.

        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  System may crash with a INVTQEFMT bugcheck

        The system may crash  with  a  INVTQEFMT  bugcheck  during  an
        insert of a timer queue element (TQE).

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     INVTQEFMT, Invalid time queue entry
                             format
          Failing PC:        FFFFFFFF.8004AB60 EXE_STD$TIMEOUT_C+006A0
          Failing PS:        10000000.00000800
          Module:            SYSTEM_PRIMITIVES_MIN  (Link Date/Time:
                             18-JUL-2002 20:01:15.20)
          Offset:            00020B60

          Failing Instruction:
          EXE_STD$TIMEOUT_C+006A0:    BUGCHK


        Images Affected: [SYS$LDR]LOCKING.EXE
                         [SYS$LDR]LOCKING.STB


     o  System can crash with a  WSLXVANMAT  bugcheck  during  image
        rundown.

        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

        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  Process gets deleted as a result  of  an  EXEC  mode  system
        service exception.

        In the following scenario, a process  can  be  deleted,  as  a
        result of an EXEC mode system service exception.

          1.  Statically linked to a shareable image.

          2.  That   image   is   then    dynamically    invoked    with
              lib$find_image_symbol  using  a  logical  that points to a
              second logical.

          3.  The second logical points to the image (an extra level  of
              indirection)

        Images Affected: [SYS$LDR]IMAGE_MANAGEMENT.EXE




     o  System crash  with  an  INVEXCEPTN,  Exception  while  above
        ASTDEL bugcheck

        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  Process can exit with the status SYS$_UNWIND (920)

        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  Application performance issues.

        Under certain conditions, a process waiting on a mutex may not
        be  woken  up  when the mutex is unlocked.  This can result in
        application performance issues.

        Images Affected: [SYS$LDR]SYSTEM_PRIMITVES.EXE
                         [SYS$LDR]SYSTEM_PRIMITVES.STB
                         [SYS$LDR]SYSTEM_PRIMITVES_MIN.EXE
                         [SYS$LDR]SYSTEM_PRIMITVES_MIN.STB




     o  Implement fairness algorithm for dynamic spinlocks.

        Currently, the  fairness  algorithm  only  applies  to  static
        spinlocks,  but ignores dynamic spinlocks and portlocks.  This
        is becoming a serious performance issue now with more and more
        dynamic spinlocks in use (XFC, TCPIP etc.).

        Images Affected: [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION.STB
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE
                         [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.STB


     o  System can crash with an INCONSTATE, Inconsistent  I/O  data
        base bugcheck.

        The system can crash with an INCONSTATE, Inconsistent I/O data
        base bugcheck.

          Crashdump Summary Information
          -----------------------------
          Bugcheck Type:     INCONSTATE, Inconsistent I/O data base
          Failing PC:        FFFFFFFF.802F2224    SYS$VCC+0C224
          Failing PS:        28000000.00000804
          Module:            SYS$VCC    (Link Date/Time:
                             18-JUL-2002 20:09:40.91)

          Offset:            0000C224


        Images Affected: [SYS$LDR]LOCKING.EXE
                         [SYS$LDR]LOCKING.STB


     o  Performance Enhancement

        With TCPIP and LAN becoming fastpath capable, we will now have
        fastpath  related routines being called and passed in a cloned
        UCB.  The DCL command $ SET DEVICE/PREFER=x  BG0  is  such  an
        example,  as  it  intends to change the fastpath preferred CPU
        for the template device, but gets  a  channel  assigned  to  a
        cloned  UCB.   Currently  it is hard to figure out, if a given
        UCB is a cloned UCB or not.  This leads to  a  degradation  in
        performance.

        Images Affected: [SYS$LDR]IO_ROUTINES.EXE
                         [SYS$LDR]IO_ROUTINES.STB
                         [SYS$LDR]IO_ROUTINES_MON.EXE
                         [SYS$LDR]IO_ROUTINES_MON.STB
                         [SYS$LDR]IMAGE_MANAGEMENT.EXE
                         [SYS$LDR]IMAGE_MANAGEMENT.STB


     o  Performance Enhancement

        Systems  with  heavy  mailbox  activity  experience   a   high
        contention  on  the static MAILBOX spinlock, namely in routine
        EXE$CANCEL.  T his results in a performance degradation.

        Images Affected: [SYS$LDR]IO_ROUTINES.EXE
                         [SYS$LDR]IO_ROUTINES.STB
                         [SYS$LDR]IO_ROUTINES_MON.EXE
                         [SYS$LDR]IO_ROUTINES_MON.STB
                         [SYS$LDR]SYSDEVICE.EXE


     o  Performance Enhancement

        Additional SMP performance improvements to cut down  on  SCHED
        spinlock contention.

        Images Affected: [SYS$LDR]IMAGE_MANAGEMENT.EXE
                         [SYS$LDR]IMAGE_MANAGEMENT.STB
                         [SYS$LDR]PROCESS_MANAGEMENT.EXE
                         [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
                         [SYS$LDR]PROCESS_MANAGEMENT_MON.STB
                         [SYS$LDR]SYS$VM.EXE
                         [SYS$LDR]SYS$VM.STB


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

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     INVEXCEPTN, Exception while above
                             ASTDEL
          Failing PC:        FFFFFFFF.800BAAFC SMP$ACQUIREL_C+0002C
          Failing PS:        38000000.00000801
          Module:            SYSTEM_SYNCHRONIZATION (Link Date/Time:
                             18-JUL-2002 20:07:57.50)
          Offset:            0002EAFC

          Failing Instruction:
          RMS+56630:      LDL             R26,#X0008(R6)


        Images Affected: [SYSLDR]LOCKING.EXE
                         [SYSLDR]LOCKING.STB



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

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
          Current Process:   NULL
          Current Image:     
          Failing PC:        FFFFFFFF.8058E630    RMS+56630
          Failing PS:        10000000.00000804
          Module:            RMS    (Link Date/Time:
                             18-JUL-2002 19:59:04.73)
          Offset:            00056630

        Images Affected: [SYS$LDR]IO_ROUTINES.EXE
                         [SYS$LDR]IO_ROUTINES.STB
                         [SYS$LDR]IO_ROUTINES_MON.EXE
                         [SYS$LDR]IO_ROUTINES_MON.STB


     o  A system can hang or crash with an INVEXCEPTN bugcheck

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

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     OPERCRASH, Operator forced system crash
          Current Process:   NULL
          Current Image:     
          Failing PC:        FFFFFFFF.8013813C    SCH$CLASS_IDLE_C+000BC
          Failing PS:        00000000.00000003
          Module:            PROCESS_MANAGEMENT    (Link Date/Time: 28-MAR-2002
          14:21:36.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
                         [SYS$LDR]PROCESS_MANAGEMENT_MON.STB



     o  A system can hang or crash with an INVEXCEPTN bugcheck

        Usnig JAVA, an attempt to merge  activate  an  image  using  a
        logical  name,  in  a  secondary  kernel  thread,  will access
        violate due to an access to a stale context pointer.   If  the
        shareable     image     is     dynamically     invoked    with
        lib$find_image_symbol, using a logical that points to a second
        logical,  which  points  to  the  image  (an  extra  level  of
        indirection), the process gets deleted (bug check with  system
        service exception).

        Images Affected: [SYS$LDR]IMAGE_MANAGEMENT.EXE
                         [SYS$LDR]IMAGE_MANAGEMENT.STB



FUNCTIONALITY ADDRESSED IN VMS731_SYS-V0100 KIT

     o  V6.3 Console Firmware Support

        This kit  supports  OpenVMS  Alpha  Version  7.3-1  and  Alpha
        systems  running Alpha Firmware Version 6.3.  Install this kit
        if you plan to use  CPU  migration.   In  addition,  this  kit
        introduces Hot Add and extended Hot Swap features with OpenVMS
        Version 7.3-1.

        After kit installation, information  describing  this  support
        can be found in the following files:

           o  [SYSHLP]V63_FIRMWARE_SUPPORT.PDF

           o  [SYSHLP]V63_FIRMWARE_SUPPORT.TXT


        To access these files before the kit is installed, execute the
        following commands:

        PRODUCT EXTRACT FILE VMS731_SYS/SELECT=V63_FIRMWARE_SUPPORT.PDF
        PRODUCT EXTRACT FILE VMS731_SYS/SELECT=V63_FIRMWARE_SUPPORT.TXT


PROBLEMS ADDRESSED IN VMS731_TDF-V0100

     o  Delay Daylight Savings time adjustment for Java

        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  Multi-threaded process looping at daylight savings forward
        time change.

        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  %LOGIN-F-DISUSER, account is disabled error message

        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




PROBLEMS ADDRESSED IN VMS731_XFC-V0100 KIT

     o  Multiple bug fixes and enhancements

        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.  This
              problem was identified during a code inspection of the XFC
              truncate processing and never observed on a customer
              system.

           -  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 elapsed
              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]XFC$SDA.EXE
                         [SYSLIB]XFC$SDA_ALPHA.EXE
                         [SYS$LDR]SYS$XFCACHE.EXE
                         [SYS$LDR]SYS$XFCACHE_MON.EXE



INSTALLATION NOTES:

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.

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


Special Installation Instructions:

     o  %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.


     o  Changes in VMS731_PARTITIONING-V0100 kit require  V6.5
        Console

        Users also need to install the V6.5 console in  order  to  use
        the  partitioning  capability  provided  in this kit.  See the
        section   entitled    "New    functionality    addressed    in
        VMS731_PARTITIONING-V0100  kit"  for more information.  If you
        do not wish to use this functionality  there  is  no  need  to
        install the new console.

     o  Scripting of Answers to Installation Questions

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

           -  $ DEFINE/SYS NO_ASK$BACKUP TRUE

           -  $ DEFINE/SYS NO_ASK$REBOOT TRUE

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

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


           -  De-assign the logicals assigned

        For example, a sample command file to install the
        VMS731_UPDATE-V0100 kit would be:

          $
          $ DEFINE/SYS NO_ASK$BACKUP TRUE
          $ DEFINE/SYS NO_ASK$REBOOT TRUE
          $!
          $ PROD INSTALL VMS731_UPDATE/PROD=DEC/BASE=AXPVMS/VER=V1.0
          $!
          $ DEASSIGN/SYS NO_ASK$BACKUP
          $ DEASSIGN/SYS NO_ASK$REBOOT
          $!
          $ exit


All trademarks are the property of their respective owners.

Files on this server are as follows:
»dec-axpvms-vms731_update-v0100--4.README
»dec-axpvms-vms731_update-v0100--4.CHKSUM
»dec-axpvms-vms731_update-v0100--4.pcsi-dcx_axpexe
privacy statement using this site means you accept its terms