OpenVMS VAXAUDS02_070 VAX V7.0 Audit Server ECO Summary

 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
       The name of the compressed file will be kit_name-dcx_vaxexe
       for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
 
       Once the file is copied to your system, it can be expanded
       by typing RUN compressed_file.  The resultant file will
       be the OpenVMS saveset or PCSI installation file which
       can be used to install the ECO.
 
Copyright (c) Digital Equipment Corporation 1997, 1998.  All rights reserved.

OP/SYS:     DIGITAL OpenVMS VAX 

COMPONENT:  Audit Server 

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXAUDS02_070 
     ECO Kits Superseded by This ECO Kit:  VAXAUDS01_070 (For OpenVMS VAX
                                                          V7.0 *ONLY*)
     ECO Kit Approximate Size:  180 Blocks
     Kit Applies To:  OpenVMS VAX V7.0
     System/Cluster Reboot Necessary:  No

     Installation Rating:   3 - To be installed on all systems running
                                the listed versions of OpenVMS which
                                are experiencing the problems described.

     NOTE:  In order to receive the full fixes listed in this kit,
            the following remedial kits also need to be installed:

              None 


ECO KIT SUMMARY:

An ECO kit exists for the Audit Server on OpenVMS VAX V7.0.  
This kit addresses the following problems:

Problems addressed in the VAXAUDS02_070 kit:

  o  When the AUDIT_SERVER is requested to exit, typically due to a
     system shutdown, it could potentially hang in "HIBernation
     state not processing any messages in MBA3:".  This problem
     could potentially cause other processes to go into RWMBX state
     when the mailbox fills up and then hang the system.

  o  The AUDIT_SERVER process could potentially corrupt saved
     registers on the stack by overwriting them with the lock status
     value of 00000001.

     A second problem manifests itself as two hung AUDIT_SERVER
     processes in a VMScluster, both stuck in Local Event Flag
     (LEF) waiting for the other to release a different doorbell
     lock.  When this problem occurs, processes may begin backing
     up in the RWMBX state trying to write new messages to MBA3:.

  o  SET AUDIT/SERVER=NEW_LOG file will not always work as
     expected, sometimes not at all and sometimes only from one
     node in the cluster.


Problems addressed in the VAXAUDS01_070 kit for OpenVMS VAX V7.0: 

  o  The AUDIT_SERVER allocated extra space for the log file
     and the extra space was not removed when a new log file 
     was created.  The old log file is now truncated when a 
     new file is created.


INSTALLATION NOTES:

The images in this kit will not take effect until the system is
rebooted or the AUDIT_SERVER is stopped and restarted.  However,
if the system is experiencing the problems described in this
remedial kit, stopping the AUDIT_SERVER may cause the system
to hang.  If that happens the system must be rebooted to recover.

To stop and restart the AUDIT_SERVER:

  $SET AUDIT/SERVER=EXIT   (to stop)

  $SET AUDIT/SERVER=START  (to restart)


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


This patch can be found at any of these sites:


Colorado Site


Georgia Site




Files on this server are as follows:

vaxauds02_070.README
vaxauds02_070.CHKSUM
vaxauds02_070.CVRLET_TXT
vaxauds02_070.a-dcx_vaxexe