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
» 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_F11X-V0100 Alpha V7.3-1 F11BXQP ECO Summary
TITLE: OpenVMS VMS731_F11X-V0100 Alpha V7.3-1 F11BXQP 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:       24-JAN-2003
Modification Date:  Not Applicable
Modification Type:  NEW KIT

Copyright (c) Compaq Computer Corporation 2002,2003.  All rights reserved.

OP/SYS:     OpenVMS Alpha 


SOURCE:     Compaq Computer Corporation


     ECO Kit Name:  VMS731_F11X-V0100
     ECO Kits Superseded by This ECO Kit:  None
     ECO Kit Approximate Size:  960 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 by all customers.

     Kit Dependencies:

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

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



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


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


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.


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_F11X /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  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:



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


        -  De-assign the logicals assigned

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

          $ exit

All trademarks are the property of their respective owners.
Files on this server are as follows:
privacy statement using this site means you accept its terms