HP Services Software Patches - a1ada_eco01031

 
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 1996.  All rights reserved.

PRODUCT:    ALL-IN-1 Office Server Options for OpenVMS AXP and 
            OpenVMS VAX, V3.1

COMPONENT:  AIDA Server 

OP/SYS:     OpenVMS Alpha V6.1 or later
	    OpenVMS VAX V5.5-2 or later

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  A1ADA_ECO01031
     ECO Kits Superseded by This ECO Kit:  None

     NOTE:  This ECO kit was previously packaged as saveset 
            A1_FIX038031.A.  It obsoletes the patch kits 
            A1_FIX030031.A and A1_FIX038031.A.

     ECO Kit Approximate Size:  3078 Blocks
     System Reboot Necessary:  No


ECO KIT SUMMARY:

An ECO kit exists for ALL-IN-1 Office Server Options for OpenVMS AXP and
OpenVMS VAX Version 3.1 on OpenVMS Alpha V6.1 or later and OpenVMS VAX
V5.5-2 or later. 

This ECO kit contains a selection of code-level fixes for the 'AIDA'
component of ALL-IN-1 Version 3.1.  If a patched system is later
upgraded to TLC V2.5, the fixes supplied by patch A1ADA_ECO01031 will be
lost.  Under these circumstances this patch kit should be reapplied
after the upgrade. 

The A1ADA_ECO01031 Release Notes contain a complete explanation of this 
release.  Below is a brief description:

  o  AIDA server problems on OpenVMS VAX and OpenVMS Alpha V6.2

     TeamLinks users are unable to access system distribution lists
     resident on ALL-IN-1 V3.1 systems running OpenVMS VAX or OpenVMS
     Alpha V6.2 or later.  This problem only occurs when Distributed
     Directory Services (DDS) is also being accessed by the AIDA server.
     Similarly TeamLinks users are unable to access certain datasets,
     where these are being referenced using the users default VMS
     privileges. 

  o  AIDA Server problems due to low resources

     This patch introduces a resource monitor to watch resource
     utilization levels, and issue warnings to the log file when they
     reach set boundaries.

     The monitor runs periodically, once a minute by default.  To change 
     this length of this period, use the logical OA$AIDA_QUOTA_INTERVAL. 
     For its value, specify the length, in seconds, of the monitor period 
     you want to use.  For example, to set the monitor period to 90
     seconds, define the logical name as follows:

        $ DEFINE/SYSTEM/EXECUTIVE OA$AIDA_QUOTA_INTERVAL "90"

     Define this value to "0" to suppress the quota monitoring tool
     altogether.

     The level of remaining resources required before messages are
     logged is 5% by default, but this can be changed using the logical 
     OA$AIDA_QUOTA_WARNING_LEVEL.  Values between 1 and 99 (inclusive)
     are allowed.  Out of range values will result in the default being
     applied.  After the message has been logged 5 times the logging is
     turned off and a reply is issued to the ALL-IN-1 manager to warn
     that the server is low on resources and that the log file should be
     checked.  This reply is issued once in every 10 times that the
     monitor runs. 

     For example, to set the warning level to 10% , define the logical
     name as follows: 

        $ DEFINE/SYSTEM/EXECUTIVE OA$AIDA_QUOTA_WARNING_LEVEL "10"

     You will need to restart the AIDA Server for this change to become
     effective.


INSTALLATION NOTES:

Before you install patch A1ADA_ECO01031, you must shut down ALL-IN-1.

Use the Shutdown ALL-IN-1 (SDA) option on the ALL-IN-1 Administration
menu (ADM) of the Management subsystem.  This will automatically shut
down your sender and fetcher processes and all servers.

See the ALL-IN-1 Management Guide for more details. TeamLinks users
will be temporarily unable to access the ALL-IN-1 file cabinet.

There are several stages to installing an ALL-IN-1 IOS V3.1 patch
kit, which vary according to the configuration of the target system
and the contents of each patch kit.

There will always be a primary installation - typically supplying
revised object modules (.OBJs), revised script files (.SCPs) or
revised named data for ALL-IN-1 forms (.FRMs).

This patch kit supplies revised image files and therefore you will 
need to perform a primary installation AND a second architecture
installation (if you have a mixed architecture VMScluster).

To install this patch, log into the SYSTEM account and use the
command procedure SYS$UPDATE:VMSINSTAL.COM as follows:

   $ SET DEFAULT SYS$UPDATE
   $ @VMSINSTAL A1ADA_ECO01031 'device'

where 'device' is the name of the device on which the distribution
medium will be mounted or the device:directory where you have already
copied the kit to.

When the installation has completed successfully repeat the above
procedure on your second architecture system (if you run ALL-IN-1 on
a mixed architecture VMScluster).

Once you have installed A1ADA_ECO01031, do the following:

   Restart ALL-IN-1 by executing the following command

      $ @SYS$STARTUP:A1V31START

   If you run ALL-IN-1 on an Open VMScluster system, execute the
   startup command procedure on every node of your VMScluster 
   where ALL-IN-1 is used.

Files on this server are as follows:

»a1ada_eco01031.README
»a1ada_eco01031.CHKSUM
»a1ada_eco01031.CVRLET_TXT
»a1ada_eco01031.a-dcx_axpexe
»a1ada_eco01031.a-dcx_vaxexe