OpenVMS VAXOPCO02_062 VAX V6.2 OPCOM/REPLY/REQUEST ECO Summary
TITLE: OpenVMS VAXOPCO02_062 VAX V6.2 OPCOM/REPLY/REQUEST ECO Summary
Modification Date: 25-FEB-99
Modification Type: Updated Kit: Supersedes VAXOPCO01_062
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.
OP/SYS: DIGITAL OpenVMS VAX
COMPONENT: OPCOM
REPLY
REQUEST
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXOPCO02_062
ECO Kits Superseded by This ECO Kit: VAXOPCO01_062
VAXOPCO01_070 for OpenVMS
VAX V6.2 *ONLY*
ECO Kit Approximate Size: 288 Blocks
Kit Applies To: OpenVMS VAX V6.2
System/Cluster Reboot Necessary: No
Rolling Re-boot Supported: Not Applicable
Installation Rating: INSTALL_3
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 VAX V6.2.
Problems addressed in VAXOPCO02_062:
o The previous kit did not contain all documented fixes.
Problems addressed in VAXOPCO01_062:
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 VAXOPCO01_070 for OpenVMS VAX V6.2:
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
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
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
vaxopco02_062.README
vaxopco02_062.CHKSUM
vaxopco02_062.CVRLET_TXT
vaxopco02_062.a-dcx_vaxexe
|
