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_EV7-V0200 EV7 Alpha 7.3-1 ECO Summary
TITLE: OpenVMS VMS731_EV7-V0200 EV7 Alpha 7.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:       27-JUN-2003
Modification Date:  Not Applicable
Modification Type:  New Kit

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

OP/SYS:     OpenVMS Alpha 


SOURCE:     Hewlett-Packard Company


     ECO Kit Name: VMS731_EV7-V0200
     ECO Kits Superseded by This ECO Kit:  VMS731_EV7-V0100
     ECO Kit Approximate Size:  22080 Blocks                    
     Kit Applies To:  OpenVMS Alpha V7.3-1
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:  INSTALL_2
                           2 - To be installed by all customers using the following 

		           ES47 or GS1280 Series systems.               

     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 EV7 on OpenVMS Alpha V7.3-1. This kit addresses the following


     o  The VMS731_EV7-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_EV7-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 in an
        unbootable state.  This new VMS731_EV7-V0200 kit re-issues the
        VMS731_EV7-V0100 kit with updated installation files that
        allow safe removal of the kit.

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

        Images Affected: Installation files


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

         For more information on the PRODUCT EXTRACT command, see
         system help for PRODUCT.  This kit also includes ECO
         corrections from the following kits:


      o  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
         %PCSI-E-MODDELERR, error deleting module DCL from library
         %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.


         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)


      o  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



         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:

         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.


         Images Affected:[SYSEXE]DCL.EXE

      o  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

              1 dir sys$sysdevice:[000000]
              2 show device dk

         Images Affected:[SYSEXE]DCL.EXE

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

         File attributes:    Allocation: 18, Extend: 5000

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

         $ 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.  Here is an example of the incorrect and
         correct output :


         After applying this kit the output is:


         Images Affected:[SYSEXE]DCL.EXE

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

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

         Images Affected:[SYSEXE]DCL.EXE


      o  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

          -  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

         Images Affected:[SYS$LDR]RMS.EXE

      o  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


      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
         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  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  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
         Current Process:   STACONFIG
         Current Image:     STACONFIG.EXE
         Failing PC:        FFFFFFFF.80029F14
         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 can become permanently unavailable
         without notification to the user and without any error log
         entries being written.

         Images Affected:[SYS$LDR]SYS$FGEDRIVER

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

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

      o  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

      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

      o  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

         Images Affected:[SYS$LDR]SYS$DKDRIVER.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    
         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

      o  The System can crash with an INVEXCEPTN at SYS$FGEDRIVER+177E0.

         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.

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

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

         Images Affected:[SYS$LDR]SYS$DKDRIVER.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_EV7 /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  SAVE_RECOVERY_DATA Warning messages

        When installing this kit  on  a  system  that  does  not  have
        recovery data saved from previous installations, if you do not
        use the /SAVE_RECOVERY_DATA qualifier, the  installation  will
        provide  a warning and give you the opportunity to change your
        mind and save the recovery data.

        When installing this kit on a system that does  have  recovery
        data saved from previous installations, PCSI will give you the
        opportunity to terminate the installation.  Note that  if  you
        choose   to  continue  you  will  still  be  given  the  above
        opportunity to change your mind and save the recovery data.

        This double check of recovery data selection on  systems  that
        already  have  recovery  data saved is an artifact of how PCSI
        handles pre- and post- installation files.

     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
        VMS721_EV7-V0100 kit would be:

          $ exit

        Note that if you do not use the /SAVE_RECOVERY_DATA qualifier
        the installation will stop with a warning.

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