|
|
 |
HP Services Software Patches - vaxcmar04_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) Digital Equipment Corporation 1996, 1997. All rights reserved.
PRODUCT: OpenVMS VAX
COMPONENTS: CMA$RTL.EXE
CMA$OPEN_RTL.EXE
CMA$ECO_DROP.COM (If desired, this command file may be
used to remove the ECO and restore the
original files and libraries if the
previous versions were not purged
during the installation.)
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXCMAR04_062
ECO Kits Superseded by This ECO Kit: VAXCMAR03_062
VAXCMAR02_062
VAXCMAR01_062
VAXCMAR01_061
ECO Kit Approximate Size: 900 Blocks
Saveset A - 90 Blocks
Saveset B - 360 Blocks
Saveset C - 432 Blocks
Kit Applies To: OpenVMS VAX V6.1, V6.2
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 CMA$OPEN_RTL.EXE and CMA$RTL.EXE on OpenVMS VAX V6.1
and V6.2. This kit addresses the following problems:
Problems Addressed in the VAXCMAR04_062 Kit:
o Paths to initiate time slicer for the pthread api and the exception
returning api failed to enable the time slicer.
Problems Addressed in the VAXCMAR03_062 Kit for OpenVMS VAX V6.2 ONLY:
o Prior to this change, the DECthreads time-slicer would be
operational regardless of whether any threads had actually been
created. This change delays enabling the time-slicer until the
first thread create operation. Hence products which only
occasionally use threads do not have to pay the time-slice penalty
when threads are never used. Note that once enabled, the
time-slicer stays enabled for the process until the program which is
using threads exits. This causes system performance problems for
systems which utilize a large number of ACMS processes.
Problems Addressed in VAXCMAR02_062:
o When CMA$NOCACTUSSTACK is defined, cactus stack linking is disabled.
This was done under a logical, as disabling cactus stack linking has
the unpleasant side effect of disabling the ability to use
DEBUG. There is a class of customers who require the cactus stack
linking and can't be impacted by this change, but SWIFT customers
require that we disable cactus stack linking.
Problems Addressed in the VAXCMAR01_062 Kit:
o A non-Fatal exception that is raised is not caught in V6.2. This
non-fatal exception was caught in V6.1.
Problems Addressed in the VAXCMAR01_061 Kit:
o When using the DECthreads call cma_delay or any timed condition
wait, threads may hang.
INSTALLATION NOTES:
The system does not need to be rebooted after this kit is installed.
However, if you have other nodes in your OpenVMS VMScluster, they
should be rebooted or you should install this kit on each system in
order to make use of the new image(s).
|
Files on this server are as follows:
|
»vaxcmar04_062.README
»vaxcmar04_062.CHKSUM
»vaxcmar04_062.CVRLET_TXT
»vaxcmar04_062.a-dcx_vaxexe
»vaxcmar04_062.b-dcx_vaxexe
»vaxcmar04_062.c-dcx_vaxexe
|
