OpenVMS ALPOPCO01_062 Alpha V6.2 OPCOM ECO Summary

TITLE: OpenVMS ALPOPCO01_062 Alpha V6.2 OPCOM 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) Compaq Computer Corporation 1999.  All rights reserved.

Modification Date:  6-FEB-99
Modification Type:  Updated Kit - Supersedes the V6.2* part of ALPOPCO01_070

PRODUCT:    OpenVMS Alpha

COMPONENT:  OPCOM (OPCOM.EXE, REPLY.EXE, REQUEST.EXE)

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  ALPOPCO01_062
     ECO Kits Superseded by This ECO Kit:  ALPOPCO01_070 (V6.2* Only)
     ECO Kit Approximate Size:  864 Blocks
     Kit Applies To:  OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3
     System/Cluster Reboot Necessary:  No
     Rolling Re-boot Supported:  Not Applicable
     Installation Rating:  INSTALL_3 - To be installed on all systems
                                       running the listed versions of
                                       OpenVMS which are experiencing the
                                       problems described. 
     Kit Dependencies:

       The following remedial kit(s) must be installed BEFORE
       installation of this kit:

         None 

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

         None 


ECO KIT SUMMARY:

An ECO kit exists for OPCOM, REPLY, and REQUEST on OpenVMS Alpha V6.2
through V6.1-1H3.  This kit addresses the following problems: 

Problems Addressed in the ALPOPCO01_062 Kit:

  o  On OPCOM restart, the log file was not restarted.

  o  REQUEST did not accept a string with a length greater than 128
     characters. 

  o  OPCOM crashed with a SSRVEXCEPTN error.

  o  Raising exceptions, while in kernel mode only, leads to a system
     crash (SSRVEXCEPT error) in the CLUSCOMM_COD_ALLOCATE module.


Problems Addressed in the ALPOPCO01_070 Kit:

  o  In certain circumstances, FAILING_OPCOM and OPCOM run on the system
     at the same time.  They both go into a $HIBER state waiting for
     incoming messages. 


INSTALLATION NOTES:

The system/cluster does not need to be rebooted after this kit is
pinstalled.  The images OPCOM.EXE, REPLY.EXE, and REQUEST.EXE are
replaced during installation using INSTALL REPLACE.  However, the OPCOM
process should be stopped using the STOP OPCOM command.  If this command
fails, then STOP/ID= (pid is process ID) can be used instead. 

Next, the logical OPC$OPCOM_STARTED should be deassigned, which is done
by using the command: 

     DEASSIGN/SYSTEM/USER OPC$OPCOM_STARTED

Once OPCOM is stopped (no OPCOM process is active), the following command
will restart OPCOM: 

     @SYS$SYSTEM:STARTUP OPCOM

Files on this server are as follows:

»alpopco01_062.README
»alpopco01_062.CHKSUM
»alpopco01_062.CVRLET_TXT
»alpopco01_062.a-dcx_axpexe