OpenVMS ALPSYS17_061 Alpha V6.1 Process Management 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) Digital Equipment Corporation 1996. All rights reserved.
*******************************************************************
* CAUTION *
*******************************************************************
* For the corrections in this ECO to take effect, the system must *
* be rebooted. If this ECO is installed but the system is NOT *
* rebooted, the system may crash with a BADVECTOR bugcheck when *
* using DEBUG. This is due to the installation procedure *
* performing an "INSTALL REPLACE SYS$LIBRARY:SYS$SSISHR.EXE" *
* which causes a mismatch problem until the system is rebooted. *
*******************************************************************
PRODUCT: OpenVMS Alpha
COMPONENT: Process Management - PROCESS_MANAGEMENT.EXE
SYS$SSISHR.EXE
SYS$PUBLIC_VECTORS.EXE
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: ALPSYS17_061
ECO Kits Superseded by This ECO Kit: ALPSYS11_061
AXPSYS10_061 (AXPSYS)
AXPSYS09_061
AXPSYS06_061
AXPSYS04_061
AXPSYS02_061
AXPSYS01_061
ECO Kit Approximate Size: 821 Blocks
Kit Applies To: OpenVMS Alpha V6.1, V6.1-1H1, V6.1-1H2
System/Cluster Reboot Necessary: Yes
ECO KIT SUMMARY:
An ECO kit exists for Process Management on OpenVMS Alpha V6.1 through
V6.1-1H2. This kit addresses the following problems:
Problems Addressed in the ALPSYS17_061
o Although the ALPSYS11_061 documentation states that the system
must be rebooted, some customers are not doing so immediately.
This causes a problem when using DEBUG. A BADVECTOR error is
issued and the system crashes. The problem does not occur if
the system is rebooted. The crash occurs because the kit does
an INSTALL/REPLACE on the SYS$SSISHR.EXE image which results in
image mismatch problems if the system is not re-booted.
Problems Addressed in the ALPSYS11_061
o The common idle loop counters have a severe performance
degradation on Alpha 4000 SMP configurations.
Problems Addressed in the AXPSYS10_061
o Process hangs and is often impossible to kill or stop.
Problems Addressed in the AXPSYS09_061
o Because installation of the AXPSYS06_061 ECO kit will
exacerbate problems corrected by the AXPRMS02_061 ECO kit,
after installation of the AXPSYS06_061 kit users should also
install the AXPRMS02_061 kit.
Problems Addressed in the AXPSYS06_061
o The PROCESS_MANAGEMENT.EXE image included in remedial kit
AXPSYS04_061 did not fix the problems listed.
Problems Addressed in the AXPSYS04_061
o A process is hung in LEF state, with an outstanding I/O
operation and a kernel mode AST queued to the process. Kernel
mode ASTs are disabled.
Problems Addressed in the AXPSYS02_061
o Applications that call the wait form of system services cause a
hang. The cause is that the service has finished
asynchronously but the application is still waiting in LEF.
The problem has been found to be generally applicable to all
system services that have a wait form counterpart.
Problems Addressed in the AXPSYS01_061
o On systems running OpenVMS Alpha V6.1, when a process with a
non-zero CPU limit SPAWNs one or more subprocesses, each SPAWN
halves the CPU limit (as expected), but on returning from the
SPAWN the unused CPU time isn't credited back to the parent
process. After some number of successful SPAWNs the process
will receive a %SYSTEM-F-EXCPUTIME error and will not allow the
user to continue. The user will have to log out and log back
in to start another process.
INSTALLATION NOTES:
In order for the corrections in this kit to take effect, the system
must be rebooted. If the system is a member of a VMScluster, the
entire cluster should be rebooted.
CAUTION:
The System MUST be rebooted after successful installation of the
kit. If you do not reboot, the system may crash with a BADVECTOR
bugcheck when using DEBUG. The problem does not occur if the
system is rebooted. The crash occurs because the kit does an
INSTALL/REPLACE on the SYS$SSISHR.EXE image which results in image
mismatch problems if the system is not re-booted.
If you have other nodes in your VMScluster, they should also be
rebooted in order to make use of the new image(s).
Note: Installation of this kit will exacerbate problems corrected
by the the AXPRMS02_061 kit. After installation of this kit
is complete, the AXPRMS02_061 kit should be installed. This kit
should be installed aftet the ALPSYS11_061 installation but before
the system is rebooted. Otherwise you will need to reboot twice.
Files on this server are as follows:
alpsys17_061.README
alpsys17_061.CHKSUM
alpsys17_061.CVRLET_TXT
alpsys17_061.a-dcx_axpexe
|
