Australia - Updated: 24-SEP-2003
hp.com home products and services support and drivers solutions how to buy
» contact hp
hp.com home hp OpenVMS ECOs

IMPORTANT NOTICE

The online distribution of OpenVMS and related product patches is being migrated to the HP ITRC (Information Technology Resource Center) patch distribution site. The new ITRC patch server will allow OpenVMS customers to take advantage of many enhanced features for patch searching and distribution.

Beginning August 1, 2003, OpenVMS and related Layered Product, publicly available patches will be available from the HP ITRC web site at

http://itrc.hp.com/service/patch/mainPage.do

The same patches will still be available from the existing patch server in Colorado Springs (http://www.support.compaq.com/patches/) through the end of October 2003, to give customers sufficient time to update their bookmarks and make the transition to the HP ITRC web site.

ECO kits will also be available by raw FTP from (ftp://ftp.itrc.hp.com/).

PLEASE UPDATE YOUR BOOKMARKS AND REGISTER ON THE NEW SITE NOW

Note: if you're having trouble connecting to the ITRC site, please delete any cookies for "itrc.hp.com" from your browser and try again. Report any difficulties with or suggestions to MrVMS

» Sydney CSC home page

Navigation
» ECOinfo main index
» Search ECOs
» Search FTP site
» Browse FTP site

ECO Indexes
» Chronological Index
» Indexed by Version
» Indexed by Rating
» Alpha Indexed by Name
» VAX Indexed by Name
» On Hold List

Associated Links
» OpenVMS Home Page
» OpenVMS News
» DIA/WIS Web Service

Feedback
» mail to CSC
.
Sydney Customer Support Centre OpenVMS ECO information
    Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)

VAXSYS19_061 VAX V6.1 SYSTEM ECO Summary

To obtain this kit please call the Customer Support Centre or use the FTP site

Search for this ECO kit and dependencies
Search the Compaq FTP web site this kit (exact match)
Search the Compaq FTP web site this or related ECOs

    
    
    Copyright (c) Compaq Computer Corporation 1998, 1999.  All rights reserved.
    
    Modification Date:  15-APR-1999
    Modification Type:  Information regarding non-fatal error added.
    
    OP/SYS:     DIGITAL OpenVMS VAX
    
    COMPONENT:  EXEC_INIT
                IO_ROUTINES
                PAGE_MANAGEMENT
                PROCESS_MANAGEMENT
    
    SOURCE:     Compaq Computer Corporation
    
    ECO INFORMATION:
    
         ECO Kit Name:  VAXSYS19_061
         ECO Kits Superseded by This ECO Kit:  VAXSYS06_070 (For V6.1 only)
                                               VAXSYS18_061
         ECO Kit Approximate Size:  522 Blocks
         Kit Applies To:  OpenVMS VAX V6.1
         System/Cluster Reboot Necessary:  Yes
         Rolling Re-boot Supported:  Yes
         Installation Rating:  INSTALL_3
                               3 - To be installed on all systems running
                                   the listed versions of OpenVMS which
                                   are experiencing the problems described.
    
         Kit Dependencies:
    
           The following remedial kit(s) must be installed BEFORE
           installation of this kit:
    
             VAXSHAD09_061
    
           In order to receive all the corrections listed in this
           kit, the following remedial kits should also be installed:
    
             None
    
    NOTE: The following error will be returned during installation if
          the kit is downloaded from ftp://ftp.service.digital.com or
          from DSNlink:
    
           %DCL-W-IVOPER, unrecognized operator in expression - check spelling
            and syntax \.5""\
    
           This error will not cause the installation to fail nor will it
           cause any other system errors.
    
    
    ECO KIT SUMMARY:
    
    An ECO kit exists for several system components on OpenVMS VAX V6.1.
    This kit addresses the following problems:
    
    Problems Addressed in VAXSYS19_061:
    
      o  The kit VAXSYS18_061 was missing the image EXEC_INIT.EXE.
         This image is included in this kit.
    
      o  Three fixes from the kit VAXSYS06_070 were not documented in
         VAXSYS18_061 even though the fixes were included.  These fixes
         are documented in this kit under fixes included from
         VAXSYS06_070 for OpenVMS V6.1.
    
    
    Problems Addressed in VAXSYS18_061:
    
      o  OpenVMS VAX systems using the SYS$SET_SECURITY or SYS$CHANGE_ACL
         system services to protect File Objects are inconsistent.
    
      o  The image PROCESS_MANAGEMENT would not LINK properly due to an
         undefined symbol, SCH$GL_MAXPIX.
    
      o  OpenVMS could potentially create processes in the same group
         UIC with the same process name.
    
         On OpenVMS VAX systems, SS$_NOSLOT could be returned when
         there is one process entry slot left, the last one used.
    
      o  SECREFNEG bugchecks can occur when running heavy loads on SMP
         systems.  The SECREFNEG bugcheck  occurs when the reference
         count on a section is decremented; the count ends up negative,
         rather than at zero.
    
      o  A potential problem exists when a batch job process termination
         message is sent to the JOB_CONTROL process.  If the Job Controller's
         mailbox is full at the time the message is sent, the message
         could be dropped and lost.  The result could be that SHOW QUEUE
         shows "executing" jobs with no associated process on the system.
    
      o  A BADPRCPGFLC bugcheck occurs if a process is created before
         the first pagefile that was installed lives to create/touch/delete
         more than 2^20 pages.
    
      o  If the quorum disk, that is on an HSD10 or served by another
         member of the cluster, becomes unavailable and then a single
         system is rebooted, the system will hang during SYSINIT.  This
         quorum disk is put into mount verification.  The system will
         not exit and it will remain hung in mount verification until
         the quorum disk is again available.  This problem happens
         regardless of the number of votes and status of "quorum".
    
    
    Problems Addressed in VAXSYS06_070:
    
      o  Possible crash due to not enough system pages locked into
         system working set.
    
      o  A process remains forever in RWAST state during $DELTVA.  All
         XQP activity for a given volume can also be blocked, cluster
         wide.
    
      o  Processes can get "stuck" in RWMPB state.
    
    
    Problems Addressed in VAXSYS04_070:
    
      o  Data inconsistencies can occur during a transfer where LBNs
         are split across volumes.
    
    
    Problems Addressed in VAXSYS05_062:
    
      o  Occasional crashes in IOC$DISMOUNT with INCONSTATE or SSRVEXCEPT.
    
      o  Asking GETDVI for a volume name would return bad data for a
         template device that had the mounted bit set.  Depending on
         the random address for the VCB, the system may crash.
    
    
    Problems Addressed in VAXSYS04_062:
    
      o  An ALLOCATE/GENERIC command erroneously returns the message
         "no such device available".
    
    
    RELATED ARTICLES:
    
    Detailed articles describing the problems listed above may exist in
    the OPENVMS Databases.  To view these articles, open the appropriate
    product database and perform a query using either of the following
    search strings: 'VAXSYS19_061' or 'VAXSYS'.
    
    
    ECO KIT ORDERING INSTRUCTIONS:
    
    If after an evaluation you wish to obtain this kit, request it
    electronically using the appropriate Advanced Electronic Services
    (AES) Service Tool.  If you are not familiar with how to request
    kits electronically, open the DIA, WIS or DSNLINK database and
    review the article entitled:
    
         [AES] How To Electronically Request ECO Kits Using Service Tools
    
    
    INSTALLATION NOTES:
    
    The images in this kit will not take effect until the system is
    rebooted.  If there are other nodes in the VMScluster, 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.
      
      ==========================================================================
      |                     Table of Kit Image Information                     |
      +----------------------------+----------+-----------------+--------------+
      |                            | Overall  | Image File      | Image Link   |
      | Image Name                 | Checksum | Identification  | Date/Time    |
      +----------------------------+----------+-----------------+--------------+
      | EXEC_INIT.EXE              |%X5D3D0FF4| X-24            |  6-FEB-1998  |
      |                                       |                 | 15:42:47.02  |
      +----------------------------+----------+-----------------+--------------+
      | IO_ROUTINES.EXE            |%X0769579B| X-24            |  6-FEB-1998  |
      |                                       |                 | 15:42:50.21  |
      +----------------------------+----------+-----------------+--------------+
      | PAGE_MANAGEMENT.EXE        |%X859FC82E| X-24            |  6-FEB-1998  |
      |                                       |                 | 15:42:34.64  |
      +----------------------------+----------+-----------------+--------------+
      | PROCESS_MANAGEMENT.EXE     |%X77AAB509| X-24            |  6-FEB-1998  |
      |                                       |                 | 15:42:24.21  |
      +----------------------------+----------+-----------------+--------------+
    
privacy statement using this site means you accept its terms feedback to the webmaster
VMS rules VMS rocks OpenVMS rules OpenVMS rocks