OpenVMS VAXOPCO01_071 VAX V7.1 OPCOM ECO Summary

TITLE: OpenVMS VAXOPCO01_071 VAX V7.1 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:  New Kit

PRODUCT:    OpenVMS VAX

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

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXOPCO01_071
     ECO Kits Superseded by This ECO Kit:  
     ECO Kit Approximate Size:  288 Blocks
     Kit Applies To:  OpenVMS VAX V7.1
     System/Cluster Reboot Necessary:  No
     Rolling Re-boot Supported:  Not Applicable
     Installation Rating:  INSTALL_3

     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 VAX V7.1. 
This kit addresses the following problems: 

Problems Addressed in the VAXOPCO01_071 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. 


INSTALLATION NOTES:

The system/cluster does not need to be rebooted after this kit is
installed.  However, the OPCOM process should be shutdown and restarted
in order for all kit changes to take effect. 

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


All trademarks are the property of their respective owners.

Colorado Site
Georgia Site

vaxopco01_071.README
vaxopco01_071.CHKSUM
vaxopco01_071.CVRLET_TXT
vaxopco01_071.a-dcx_vaxexe