|
|
 |
OpenVMS VAXSYSA02_071 VAX V7.1 System ECO Summary
|
TITLE: OpenVMS VAXSYSA02_071 VAX V7.1 System 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) Compaq Computer Corporation 1998. All rights reserved.
NOTE: The documentation for this kit calls out a dependency on the
VAXMOUN04_071 remedial kit. This MOUNT kit is not currently
available but will be released at a future date.
Modification Date: 18-NOV-98
Modification Type: Updated ECO Kit: Supersedes: VAXSYSA01_071
OP/SYS: DIGITAL OpenVMS VAX
COMPONENT: System Components
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
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXSYSA02_071
ECO Kits Superseded by This ECO Kit: VAXSYSA01_071
VAXSYS04_071
VAXSYS03_071
VAXSYS02_071
ECO Kit Approximate Size: 1098 Blocks
Kit Applies To: OpenVMS VAX V7.1
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_1
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:
VAXF11X03_071
For an explanation of the cause for the following dependencies, see
the MME-related problem descriptions under the section titled
"PROBLEMS ADDRESSED IN VAXSYSA02_071 KIT":
VAXBACK03_071
VAXDISM01_071
VAXINIT01_071
VAXMOUN04_071
VAXMTAA01_071
ECO KIT SUMMARY:
An ECO kit exists for System Components on OpenVMS VAX V7.1.
Problems Addressed in VAXSYSA02_071:
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. Furthermore, candidate processes for Virtual
Balance Set Slot (VBSS) selection can be missed.
Code using the EXE$GL_ABSTIM_TICS cell to time other activity
could get stuck if a reference counter is large (FFFFxxxx) and
the EXE$GL_ABSTIM_TICS value is low due to the overflow
(0000xxxx). Most such checks compare to see if the number of
tics is larger than the reference value, i.e. has the event
come due?
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_071
o VAXDISM01_071
o VAXINIT01_071
o VAXMOUN04_071
o VAXMTAA01_071
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 An image activator error occurred with the status
SS$_VA_IN_USE.
The solution was for the image activator, after cleaning up
from the error, to reattempt to activate the image requested.
Note that since the failure rarely occurs, based on timing of
some unrelated event, a retry should allow image activation to
complete successfully.
Problems addressed in VAXSYSA01_071:
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, the VAXF11X03_071 remedial kit
must also be installed.
Problems Addressed in VAXSYS04_071:
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 VAXSYS03_071:
o Users creating protected subsystems, with subsystem
identifiers granted to executable images, fail to work
properly in manipulating queues via $SNDJBC[W]. Although
the image will have the subsystem identifier granted, it
will be returned with a NOPRIV error.
Problems Addressed in VAXSYS02_071:
o OpenVMS VAX systems using the SYS$SET_SECURITY or SYS$CHANGE_ACL
system services to protect File Objects are inconsistent.
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".
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.
|
Files on this server are as follows:
|
»vaxsysa02_071.README
»vaxsysa02_071.CHKSUM
»vaxsysa02_071.CVRLET_TXT
»vaxsysa02_071.a-dcx_vaxexe
|
