OpenVMS VAXSYSA02_062 OpenVMS VAX V6.2 SYSTEM ROUTINES ECO Summary
TITLE: OpenVMS VAXSYSA02_062 OpenVMS VAX V6.2 SYSTEM ROUTINES ECO Summary
Modification Date: 14-APR-1999
Modification Type: Reference to VAXY2K01_062 updated.
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.
*OpenVMS] VAXSYSA02_062 OpenVMS VAX V6.2 SYSTEM ROUTINES ECO Summary
Copyright (c) Compaq Computer Corporation 1998. All rights reserved.
NOTE: The following error will be returned during installation if
the kit is downloaded from ftp://ftp.support.compaq.com :
%DCL-W-IVOPER, unrecognized operator in expression - check spelling
and syntax \.5""\
This error will not cause the installation to fail nor will it
cause any other system errors.
OP/SYS: DIGITAL OpenVMS VAX
COMPONENT: ERRORLOG
EXCEPTION
EXEC_INIT
IMAGE_MANAGEMENT
IO_ROUTINES
LOCKING
MESSAGE_ROUTINES
PAGE_MANAGEMENT
PROCESS_MANAGEMENT
SYSLDR_DYN
SYSTEM_PRIMITIVES
SYSTEM_PRIMITIVES_MIN
WORKING_SET_MANAGEMENT
EXCEPTION.STB
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXSYSA02_062
ECO Kits Superseded by This ECO Kit: VAXSYSA01_062
VAXSYS11_062
VAXSYS10_062
VAXSYS08_062
ECO Kit Approximate Size: 1062 Blocks
Kit Applies To: OpenVMS VAX V6.2
System/Cluster Reboot Necessary: Yes
Rolling Re-boot 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:
VAXCLUSIO01_062, VAXY2K01_062 (or its supersedent kit)
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
For an explanation of the cause for the following dependencies,
see the MME-related problem descriptions under the section
titled:
PROBLEMS ADDRESSED IN VAXSYSA02_062 KIT:
VAXINIT01_062
VAXBACK03_062
VAXMTAA03_062
VAXDISM02_062
VAXMOUN03_062
ECO KIT SUMMARY:
An ECO kit exists for SYSTEM ROUTINES on OpenVMS VAX V6.2. This kit
addresses the following problems:
PROBLEMS ADDRESSED IN VAXSYSA02_062:
o If a system has been up for 497.1 days without rebooting,
the system cell EXE$GL_ABSTIM_TICS (number of 10 millisecond
tics since boot) will overflow. This problem can cause some
processes to remain indefinitely in the RWMPB or COMO
scheduling state.
o A possible system crash occurs during Host Based RAID Unbinds
with MME code enabled. A mailbox read synchronization problem
causes the crash.
This problem only occurs when a host-based RAID UNBIND command
is done while an MME-based application is running. This problem
can occur in several different code areas of the operating system.
In order to eliminate all known instances of this problem, the
following remedial kits (or their supersedants) will also need
to be installed:
o VAXBACK03_062
o VAXDISM02_062
o VAXINIT01_062
o VAXMOUN03_062
o VAXMTAA03_062
o A process using MME could potentially "miss" the VOL1 label
on a tape. Also, a process could "hang" trying to send a
message to the MME process.
o The performance counter PMS$GL_NPAGDYNEXPS (cell) was never
incremented above its initial value of zero. It can be
displayed by SDA>CLUE MEM/STAT.
o A system may bugcheck with an NSABLOST error when:
1. A MAIL application uses a MAIL$USER_GET_INFO utility
routine call to acquire user mail information.
2. When privileged user audits were enabled for SYSNAM.
The problem can be replicated with the MAIL utility command:
MAIL> SHOW FORWARD/USER=*
PROBLEMS ADDRESSED IN VAXSYSA01_062:
o Updates to application ACE get lost. Customer code locks the
ACL, reads their ACE, updates a count field, re-writes the ACE,
and unlocks the ACL. The change to the count gets lost. In
order to get this full fix you must also install the
VAXF11X04_062 remedial kit.
PROBLEMS ADDRESSED IN VAXSYS11_062:
o An application (DSM) hangs with processes going into an RWMBX
state after calling GETLKI to get the parent ID of a lock.
Later, the processes go into RWNPG. DEFMBXBUFQUO has been
increased in case DSM does not specify the sizes of its
mailboxes.
PROBLEMS ADDRESSED IN VAXSYS10_062:
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 A BADPRCPGFLC bugcheck occurs if more than 2^20 pagefile pages
are used and only a single pagefile is installed.
PROBLEMS ADDRESSED IN VAXSYS04_062 KIT
o An ALLOCATE/GENERIC command erroneously returns the message "no
such device available".
PROBLEMS ADDRESSED IN VAXSYS08_062 KIT
o Crash caused by R1 corruption.
Year 2000
Y2K
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
this time, a rolling re-boot may be performed.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
vaxsysa02_062.README
vaxsysa02_062.CHKSUM
vaxsysa02_062.CVRLET_TXT
vaxsysa02_062.a-dcx_vaxexe
|
