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 VMS73_SYS-V0400 Alpha V7.3 System ECO Summary
TITLE: OpenVMS VMS73_SYS-V0400 Alpha V7.3 System ECO Summary

New Kit Date:       10-APR-2002
Modification Date:  17-APR-2002
Modification Type:  This kit supersedes both VMS73_SYS-V0300 and 
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, then it can
       be expanded by typing RUN kitname.pcsi-dcx_axpexe.  The resultant
       file will be the PCSI installation file which can be used to install
       the ECO.

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

OP/SYS:     OpenVMS Alpha


SOURCE:     Compaq Computer Corporation


     ECO Kit Name:  VMS73_SYS-V0400
     ECO Kits Superseded by This ECO Kit: VMS73_SYS-V0300  
     ECO Kit Approximate Size:  17840 Blocks
     Kit Applies To: OpenVMS Alpha V7.3
     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.

*                           Note                          *
*                                                         *
*  VMS73_SYS-V0400 supersedes the VMS73_SYSLOA-V0200 kit  *
*                                                         *

     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 System components on OpenVMS Alpha V7.3.  
This kit addresses the following problems:


  o  V7.3 nodes do not correctly handle Quorum Disks.   The  issues
     can  result in either CLUEXIT bugchecks or numerous connection
     manager console messages:

       %CNXMAN, Proposing modification of quorum or quorum disk

     Any cluster with a quorum disk and V7.3  nodes  requires  this

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

  o  SDA can ACCVIO when the SHOW LOCK/POOL command is issued.

        %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
        address=0000000000678472, PC=0000000000144070, PS=0000001B

          Images Affected:  [SYSLIB]SDA$SHARE.EXE

  o  Doing I/O on a multipath device, when the current  path  is  a
     secondary,  results  in  an increase in the UCB$L_OPCNT in the
     primary as  well  as  the  current  path  UCB.   Although  the
     UCB$L_OPCNT in the secondary grows faster than in the primary,
     the UCB$L_OPCNT in the primary should not be changing (except,
     at  most  by  once  per  second  for  polling.) This is easily
     observed when doing a DIR/SIZE on the system disk.

     A number of customers and third-parties rely on these counters
     to  be  accurate  in  their  performance and capacity planning

          Images Affected:  SYS$LDR]IO_ROUTINES.EXE

  o  The Lock Manager can deliver a  blocking  AST  to  the  system
     owned  locks  incorrectly.  The window of opportunity for this
     to occur is very small, but if it  happens,  the  system  will
     often crash with an Invalid exception error.

     Crashdump Summary Information:
     Bugcheck Type:     SSRVEXCEPT, Unexpected system service
     Failing PC:        FFFFFFFF.802059E8    XQP$FCBSTALE_C
     Failing PS:        00000000.00000000
     Module:            F11BXQP
                        (Link Date/Time: 17-MAR-2001 03:16:47.08)
     Offset:            0000D9E8

          Images Affected:  [SYS$LDR]LOCKING.EXE

  o  During installation of an OpenVMS ECO kit, the  names  of  the
     installed         images         are         written        to
     names  should  be written with _OLD appended to the end of the
     filename along with the name of the kit.  The  VMS73_SYS-V0300
     ECO kit did not do this editing correctly.

     When upgrading from  V7.3  to  a  later  version  of  OpenVMS,
     operating  system  files  from the previous version of OpenVMS
     are deleted.  The  above  file  name  errors  will  cause  old
     operating  system  files  to  be  left on the system after the
     upgrade.  In addition, users will see  multiple  instances  of
     the following installation warning message during the upgrade:

       %UPGRADE-W-NOTOLD2, does not have "_OLD" at end
       %UPGRADE-W-NOTOLD2, file not deleted

     This      change      corrects      the      filenames      in

          Images Affected: [SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT


  o  The following command should change the path to the disk:


     Sometimes it does not.

          Images Affected:  [SYS$LDR]MULTIPATH.EXE

  o  A system can hang with many processes in MUTEX wait state.

          Images Affected:  [SYS$LDR]IO_ROUTINES.EXE

  o  On Alphaserver GS-series machines running OpenVMS V7.3,  after
     several  console  messages  indicating pool expansion failure,
     the system may hang, or crash with  CPUSPINWAIT  or  CPUSANITY

          Images Affected:  [SYS$LDR]SYSTEM_PRIMITIVES.EXE

  o  The F$PID lexical function in DCL does not  work  as  expected
     when  the  user running the procedure does not have sufficient
     privilege to examine other processes.  The result may be  that
     process  selection  in  combination with F$CONTEXT returns the
     wrong PID.

          Images Affected:  [SYS$LDR]PROCESS_MANAGEMENT.EXE

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

     Crashdump Summary Information:
     Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
     Current Process:   SWAPPER
     Current Image:     
     Failing PC:        FFFFFFFF.80115E0C
     Failing PS:        10000000.00000800
     Module:            PROCESS_MANAGEMENT
                        (Link Date/Time:  6-JUN-2001 17:31:27.58)
     Offset:            00009E0C

          Images Affected:  [SYS$LDR]PROCESS_MANAGEMENT.EXE

  o  MOUNT and Mount Verification sanity checks have  been  relaxed
     to correct the following issues:

       o  A MOUNT/NOWRITE command on a disk on one cluster will  now
          work  correctly  even if the disk is mounted with a /WRITE
          qualifier on another cluster  in  the  SAN  (Storage  Area
          Network).  Previously, depending on the order in which the
          mounts were executed, the mount would fail with the  error

          DIFVOLMNT - different volume already mounted on this

          Images Affected:  [SYS$LDR]IO_ROUTINES.EXE

  o  Queue  and  other   clusterwide   operations   fail   with   a
     SS$_BADPARAM  bugcheck  when  a  COE-baselevel  node is in the

          Images Affected:  [SYSLIB]SECURESHR.EXE

  o  When  called  from  exec  mode,  ACCVIOs  are  returned   from

          Images Affected:  [SYSLIB]SECURESHR.EXE

  o  A  SSRVEXCEPT  system  crash  can  occur  when   a   call   to
     $PERSONA_CREATE  is  made  for  an  account  with a [0,0] UIC.
     (Though it is possible to create such an account, the  account
     is invalid on VMS systems).

     Crashdump Summary Information:
     Bugcheck Type:     SSRVEXCEPT, Unexpected system service
     Current Process:   BUILDER
     Failing PC:        FFFFFFFF.801CB968    NSA$REFERENCE_RIGHTS_CHAIN_C+00008
     Failing PS:        10000000.00000201
     Module:            SECURITY    (Link Date/Time:
                        5-AUG-2001 01:12:10.86)
     Offset:            0000B968

          Images Affected:  [SYS$LDR]SECURITY.EXE

  o  On a system that contains a CPU numbered 31, CPU #31 can run a
     thread  even  if  that thread has specified, either by setting
     required capabilities or hard affinity, that it  must  run  on
     another  CPU.   Thus,  some  functions  which  must run on the
     primary CPU may occasionally be run on CPU  #31.   There  need
     not actually be 31 CPUs.  This bug can cause problems with CPU
     power down/up of any CPU, with  CPU  assignment  between  soft
     partitions, or garbled or missing console output.

          Images Affected:  [SYS$LDR]PROCESS_MANAGEMENT.EXE

  o  If a packet is requested from nonpaged  pool  that  is  larger
     than  nonpaged  pool's  maximum  allowed  size  (NPAGVIR), the
     request fails.  However, nonpaged pool expands to its  maximum
     size, even though the request can not be satisfied.

          Images Affected:  [SYS$LDR]SYSTEM_PRIMITIVES.EXE

  o  A system may have one of  the  following  problems  caused  by
     possible  corruption  of  the process scheduling queues and/or
     the SCH$GQ_PFWQ queue:

       o  Processes stuck in CUR  but  on  the  PFW  queue  and  not

       o  Processes stuck in PFW on the PFW queue and not executing

       o  The  PFW  queue  merged  in  with  a  COM  queue,  usually
          resulting in an INCON_SCHED or a CPUSPINWAIT bugcheck.

       o  An INVEXCEPTN at SCH$QEND_C+38 trying to access  the  cell

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

  o  In an OpenVMS mixed version  clustered  environment,  a  fatal
     invalid identifier format (%SYSTEM-F-IVIDENT) error can result
     in versions of  OpenVMS  that  are  not  OpenVMS  COE  (Common
     Operating Environment) compliant.

     This can occur  on  non-COE  compliant  OpenVMS  systems  when
     attempting to display the rights identifiers of a process that
     is  granted  a  valid  GID  COE  identifier.   The   following
     commands,  lexicals,  (and  respective system services), cause
     the %SYSTEM-F-IVIDENT system message to be  displayed  instead
     of the text translation of this COE GID IDENTIFIER:

       1.  F$GETJPI("PID_xxx","PROCESS_RIGHTS")

       2.  F$GETJPI("PID_xxx","RIGHTSLIST")

       3.  $ SHOW PROCESS/ALL


          Images Affected: [SYS$LDR]SECURITY.EXE

  o  A system can fail to boot with the following error:

         %INIT_IO_DB-F-LOAD_SH_ERROR, Error Loading shadowing
         driver SYS$SHDRIVER.EXE, error = 0x00000870

          Images Affected:  [SYS$LDR]EXEC_INIT.EXE

  o  The sys$crmpsc_gdzro_64() returns a numeric  value  indicating
     that memory is reserved when it is not.

          Images Affected:  [SYS$LDR]SYSTEM_PRIMITIVES.EXE

  o  If a RADCHECK is done  on  a  system  running  the  DECwindows
     Display  Server  (or possibly other images that memory map I/O
     space or other pages that do not appear in the  PFN  database)
     the  system  will  crash  with  an invalid exception bugcheck.
     Analysis will show the exception is an ACCVIO in image SYS$VM,

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

  o  A system can crash with a REFCNTNEG, PFN  reference  count  is
     negative  bugcheck.   The PFN database element being mapped is
     pointed to by R15, so, the SDA command:

           FORMAT @^QR15/TYPE=PFN

     can be used to examine the value in the  PFN$W_BO_REFC  field.
     If it is greater than or equal to 8000, 32768 decimal, this is
     the cause of the bugcheck.

     Crashdump Summary Information:
     Bugcheck Type:     REFCNTNEG, PFN reference count is negative
     Current Process:   ORA_CLUS_DBWR
     Current Image:     DSA2:[ORACLE.CODE_V7344.RDBMS]SRV.EXE
     Failing PC:        FFFFFFFF.801131C8
     Failing PS:        04000000.00000800
     Module:            SYS$VM
                        (Link Date/Time: 29-DEC-1999 04:29:36.63)
     Offset:            000251C8

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

  o  On NUMA systems, at the end of the system startup, unused PFNs
     are  released for the exec data huge page region, and then the
     exec  code  and  resident  code  region  will  be  replicated.
     Customers  having  their own drivers, which can be reloaded on
     the  fly,  need  to  clear  the  RELEASE_PFNS   bit   in   the
     LOAD_SYS_IMAGES  SYSGEN  parameter to avoid releasing PFNs for
     the exec data region.  Otherwise the driver reload fails  with
     an error.

     This change stops release of PFNs for the  exec  data  region.
     This  allows  customers to reload drivers on the fly and still
     get the benefit of system code replication.           

          Images Affected:  [SYS$LDR]SYSLDR_DYN.EXE

  o  Connection to an Oracle server can fail:

         ORACLE error---
         ORA-01034: ORACLE not available
         ORA-27123: unable to attach to shared memory segment
         %SYSTEM-E-SECREFOVF, too many section refer
         %SYSTEM-W-UNWIND, unwind currently in progress
         %TRACE-W-TRACEBACK, symbolic stack dump follows
         %SYSTEM-W-UNWIND, unwind currently in progress

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

  o  A call to $GETJPI to  return  information  about  the  calling
     process  could return a SS$_NOPRIV status if that call is made
     while a persona representing a security profile  that  differs
     from the natural persona (Persona_ID 1) is active.

          Images Affected:  [SYS$LDR]PROCESS_MANAGEMENT.EXE

  o  Under the following circumstances:

       o  The system is a GS80, GS160, or GS320.

       o  The SYSGEN parameter RAD_SUPPORT has bit 2  set,  enabling
          system space replication.

       o  The SYSGEN parameter GH_RSRVPGCNT is  set  to  a  non-zero

     The  system  can  crash  with  an   INVEXCEPTN   bugcheck   at

          Images Affected:  [SYS$LDR]SYSTEM_PRIMITIVES.EXE

  o  Applications that make a call to the  $SNDOPR  system  service
     can  get  a SS$_MBFULL return status.  For example, Oracle/Rdb
     applications can fail with the following error:

             %COSI-F-UNEXPERR, unexpected system error
             -SYSTEM-W-MBFULL, mailbox is full

          Images Affected:  [SYS$LDR]SYSTEM_PRIMITIVES.EXE

  o  It is possible to sometimes  get  an  INVEXCEPTN  bugcheck  at
     SCH$QEND_C+001E0 during quantum end processing.

     Crashdump Summary Information:
     Bugcheck Type:    INVEXCEPTN, Exception while
                       above ASTDEL
     Current Process:
     Current Image:    
     Failing PC:       FFFFFFFF.800CFB50  SCH$QEND_C+001E0
     Failing PS:       10000000.00000804
     Module:           PROCESS_MANAGEMENT (Link Date/Time:
                       23-JAN-2001 08:37:04.46)
    Offset:            00007B50

          Images Affected: [SYS$LDR]PROCESS_MANAGEMENT.EXE

  o  If PERFMON interrupts are not turned off for PCTR0, PCTR1  and
     PCTR2  during  BUGCHECK,  and on any STOP/CPU, severe hangs in
     the console can occur.  It could take a power cycle  to  clear
     the situation.

          Images Affected:  [SYS$LDR]EXCEPTION.EXE

  o  When using the SYS$WAKE system service, if a PID  or  username
     for  a  process  on a remote node is specified, a SS$_IVLOGNAM
     error will be returned.

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

  o  The  system  can  crash  with  a  INVSECURESTATE  bugcheck  at

     Crashdump Summary Information

     Bugcheck Type:     INVSECURESTATE, Invalid state detected by
                        SECURITY subsystem
     Current Process:   YERTLE$SRV73
     Current Image:     DSA20:[SYS0.SYSCOMMON.]
     Failing PC:        FFFFFFFF.8019798C
     Failing PS:        30000000.00000203
     Module:            SECURITY_MON (Link Date/Time:
                        17-OCT-2001 01:01:12.57)
     Offset:            0000B98C

          Images Affected:  [SYS$LDR]SECURITY.EXE

  o  The system can crash  with  a  KRNLSTAKNV,  Kernel  stack  not
     valid, bugcheck"

     Crashdump Summary Information:
     Bugcheck Type:     KRNLSTAKNV, Kernel stack not valid
     Current Process:
     Current Image:     
     Failing PC:        FFFFFFFF.800243A8
     Failing PS:        00000000.00001F00
     Module:            SYS$CPU_ROUTINES_2208 (Link Date/Time:
                        17-MAR-2001 03:15:26.81)
     Offset:            000163A8

          Images Affected:  [SYS$LDR]PROCESS_MANAGEMENT.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 VMS73_SYS-V0400 /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


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