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

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

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

connection tools
» nameserver lookup
» traceroute
» ping

Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS731_RMS-V0200 Alpha V7.3-1 RMS ECO Summary
TITLE: OpenVMS VMS731_RMS-V0200 Alpha V7.3-1 RMS 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:       22-OCT-2002
Modification Date:  25-OCT-2002
Modification Type:  Processed with correct links

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

OP/SYS:     OpenVMS Alpha


SOURCE:     Compaq Computer Corporation


     ECO Kit Name:  VMS731_RMS-V0200
     ECO Kits Superseded by This ECO Kit:  VMS731_RMS-V0100
     ECO Kit Approximate Size:  2608 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) must be installed BEFORE
       installation of this kit:


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



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


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


        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:


        The following is an example of explicitly specifying the queue


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


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


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:


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

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