|
|
 |
HP Services Software Patches - vaxsys07_070
|
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, 1998. All rights reserved.
PRODUCT: DIGITAL OpenVMS VAX
COMPONENT: PAGE_MANAGEMENT.EXE
EXEC_INIT.EXE
PROCESS_MANAGEMENT.EXE
IO_ROUTINES.EXE
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXSYS07_070
ECO Kits Superseded by This ECO Kit: VAXSYS06_070 (For VAX V7.0 *ONLY*)
VAXSYS04_070 (For VAX V7.0 *ONLY*)
VAXSYS02_070 (For VAX V7.0 *ONLY*)
ECO Kit Approximate Size: 522 Blocks
Kit Applies To: OpenVMS VAX V7.0
System/Cluster Reboot Necessary: Yes
Rolling Reboot Supported: Yes
Installation Rating: 1 - To be installed on all systems running
the listed version(s) of OpenVMS.
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 various system components on OpenVMS VAX V7.0.
This kit addresses the following problems:
Problems addressed in VAXSYS07_070:
o OpenVMS VAX systems using the SYS$SET_SECURITY or SYS$CHANGE_ACL
system services to protect File Objects are inconsistent.
o The image PROCESS_MANAGEMENT would not LINK properly due to an
undefined symbol, SCH$GL_MAXPIX.
o OpenVMS could potentially create processes in the same group
UIC with the same process name.
On OpenVMS VAX systems, SS$_NOSLOT could be returned when
there is one process entry slot left, the last one used.
o SECREFNEG bugchecks can occur when running heavy loads on SMP
systems. The SECREFNEG bugcheck occurs when the reference
count on a section is decremented; the count ends up negative,
rather than at zero.
o A potential problem exists when a batch job process termination
message is sent to the JOB_CONTROL process. If the Job Controller's
mailbox is full at the time the message is sent, the message could
be dropped and lost. The result could be that SHOW QUEUE shows
"executing" jobs with no associated process on the system.
o If a quorum disk that is on an HSD10 or is served by another
member of the cluster, becomes unavailable and then a single
system is rebooted, the system will hang during SYSINIT. This
quorum disk is put into mount verification. The system will
not exit and it will remain hung in mount verification until
the quorum disk is again available. This problem happens
regardless of the number of votes and status of "quorum".
Problems addressed in VAXSYS04_070:
o Data inconsistencies can occur during a transfer when logical
block numbers (LBNs) are split across volumes.
o An 'ALLOCATE/GENERIC' DCL command erroneously returns the message
"no such device available".
Problems addressed in VAXSYS06_070:
o Crash may occur due to not enough system pages locked into system
working set.
Problems addressed in VAXSYS02_070:
o A process remains forever in RWAST state during $DELTVA. All
XQP activity for a given volume can also be blocked, clusterwide.
o Processes can get "stuck" in RWMPB state.
INSTALLATION NOTES:
The images in this kit will not take effect until the system is
rebooted. If there are other nodes in the VMScluster, they must
also be rebooted in order to make use of the new image(s).
If it is not possible or convenient to reboot the entire cluster at
|
Files on this server are as follows:
|
|
Files on this server are as follows:
|
»vaxsys07_070.README
»vaxsys07_070.CHKSUM
»vaxsys07_070.CVRLET_TXT
»vaxsys07_070.a-dcx_vaxexe
|
