OpenVMS VAXCLIU04_071 VAX V7.1 SHWCLSTR ECO Summary
TITLE: OpenVMS VAXCLIU04_071 VAX V7.1 SHWCLSTR ECO Summary
New Kit Date : 17-MAY-2001
Modification Date: Not Applicable
Modification Type: Updated Kit Supersedes VAXCLIU03_071
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
For OpenVMS savesets, the name of the compressed saveset
file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
saveset is copied to your system, expand the compressed
saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
For PCSI files, once the PCSI file is copied to your system,
rename the PCSI file to kitname-dcx_axpexe.pcsi, then it can
be expanded by typing RUN kitname-dcx_axpexe.pcsi. The resultant
file will be the PCSI installation file which can be used to install
the ECO.
Copyright (c) Compaq Computer Corporation 2001. All rights reserved.
OP/SYS: OpenVMS VAX
COMPONENT: CLIUTL - SHWCLSTR.EXE
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXCLIU04_071
ECO Kits Superseded by This ECO Kit: VAXCLIU03_071
ECO Kit Approximate Size: 1470 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 by all customers.
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:
VAXRMS02_071
ECO KIT SUMMARY:
An ECO kit exists for the DCL command 'SHOW CLUSTER' (SHWCLSTR) on
OpenVMS VAX V7.1. This kit addresses the following problems:
NEW FUNCTIONALITY ADDRESSED IN VAXCLIU04_071 KIT:
o New qualifier /CONTENTION_POLICY added to SET RMS_DEFAULT (and
SHOW RMS_DEFAULT display) to address locking fairness issues.
The new Alpha global buffer read-mode lock support introduced
in V7.2-1H1 is functionally compatible with both VAX and older
Alpha releases. Operations in mixed clusters produce correct
results. However, there is a locking fairness issue that may
arise with mixed cluster operations.
In a mixed cluster environment with very high contention for
specific buckets, it is possible for accesses to write-shared
files on nodes using read-mode bucket locking to dominate
access to a bucket. Nodes without this support might be
unable to access the bucket for a protracted period of time.
It is also possible to observe comparable behavior on all
OpenVMS versions when dealing with accesses to write-shared
files without global buffers enabled -- even on a standalone
system. A similar fairness issue between lock conversions and
new lock requests may be observed in which the new lock
requests may remain ungranted for an extended period of time.
This kit provides an interface for RMS support for a new
option to improve fairness under high contention conditions
for write-shared files. The option is controlled using the
/CONTENTION_POLICY qualifier to the DCL command SET
RMS_DEFAULT. The option may be set at a process or system
level. Since selecting this option may noticeably increase
locking overhead and since many applications will never
encounter this issue, the default system behavior leaves this
option disabled. A future lock management enhancement should
make this fairness workaround unnecessary for later releases.
The following are valid PROCESS keywords (/SYSTEM not
specified) for SET RMS_DEFAULT/CONTENTION_POLICY:
NEVER Never use the higher overhead option
to improve fairness for any write-shared
files accessed by this process; minimal
overhead.
SOMETIMES Use this option for fairer bucket
access (but higher overhead) to any
write-shared files with global buffers
enabled that are accessed by this process.
ALWAYS Use this option for fairer bucket
access (but higher overhead) to all
write-shared files accessed by this process.
SYSTEM_DEFAULT (Default) Use system setting. Note
that this keyword is disallowed with /SYSTEM.
The following are valid SYSTEM keywords (/SYSTEM specified):
NEVER (Default) Never use the higher
overhead option to improve fairness
for any write-shared files accessed
on the system; minimal overhead.
SOMETIMES Use this option for fairer bucket
access (but higher overhead) to any
write-shared files with global
buffers enabled that are accessed
on the system.
ALWAYS Use this option for fairer bucket
access (but higher overhead) to all
write-shared files accessed on the
system.
Images Affected: [SYSEXE]SET.EXE
[SYSEXE]SHOW.EXE
[SYSMSG]CLIUTLMSG.EXE
[SYSLIB]DCLTABLES.EXE (SET.CLD replaced)
PROBLEMS ADDRESSED IN VAXCLIU04_071 KIT:
o Issuing a SHOW DEVICE /SERVED command may yield an
inconsistent display on a multi-processor system if a SET
DEVICE /SERVED command is issued at the same time. The system
could crash if queues are updated while HOW DEVICE /SERVED
code is traversing the queues at elevated IPL and the update
causes an access violation or pagefault.
Images Affected: [SYSEXE]SHOW.EXE
o The "/PROTECTION" and "/OWNER" qualifiers of the "$ SET
SECURITY" command update the file modification date. The
"/DEFAULT" qualifier modifies file attributes as well, but
does not update the file modification date.
See the output below of three commands using three different
qualifiers. Note that the time stamp changes between the
first and second examples, but does not change between the
second and third examples.
PANTHR $ DIR/SEC/DAT=(MOD) BOB*.TXT
Directory IX_SFW:[PIXFUN2.DAT]
BOBZ.TXT;1 26-FEB-1999 11:57:16.03 [SYSTEM] ( RWED,RWED,,)
BOBZ2.TXT;1 26-FEB-1999 12:00:10.17 [SYSTEM] ( RWED,RWED,,)
Total of 2 files.
PANTHR $ SET SECURITY/PROTECTION=(W:RE) BOBZ.TXT
PANTHR $ DIR/SEC/DAT=(MOD)
BOB*.TXT Directory IX_SFW:[PIXFUN2.DAT]
BOBZ.TXT;1 26-FEB-1999 12:03:43.85 [SYSTEM] ( RWED,RWED,,RE)
BOBZ2.TXT;1 26-FEB-1999 12:00:10.17 [SYSTEM] (
RWED,RWED,,)
Total of 2 files.
PANTHR $ SET SECURITY/DEFAULT BOBZ*.TXT;*
PANTHR $ DIR/SEC/DAT=(MOD) BOB*.TXT Directory IX_SFW:[PIXFUN2.DAT]
BOBZ.TXT;1 26-FEB-1999 12:03:43.85 [300,0] ( RWED,RWED,,)
(IDENTIFIER=CW_PROD_DEV,ACCESS=READ+EXECUTE)
(IDENTIFIER=CW_PROD_NDM,ACCESS=READ+WRITE+EXECUTE+DELETE)
BOBZ2.TXT;1 26-FEB-1999 12:04:16.18 [300,0] ( RWED,RWED,,)
(IDENTIFIER=CW_PROD_DEV,ACCESS=READ+EXECUTE)
(IDENTIFIER=CW_PROD_NDM,ACCESS=READ+WRITE+EXECUTE+DELETE)
Total of 2 files.
Images Affected: [SYSEXE]SETSHOSECUR.EXE
o When submitting a job to a queue, there is an option to retain
the job in the batch queue for a specified time after its
completion. The SUBMIT/RETAIN=UNTIL command option was
improperly coded in V7.1.
Images Affected: [SYSEXE]SUBMIT.EXE
o When an unpriviledged user attempts to access a queue and is
denied, the event is neither alarmed nor audited.
Images Affected: [SYSEXE]SUBMIT.EXE
Problems Addressed in the VAXCLIU03_071 Kit:
o The previous remedial kit, VAXCLIU01_071, did not fully
correct the problems listed. This kit contains all the fixes.
Problems Addressed in the VAXCLIU01_071 Kit:
o System crashes with a PGFIPLHI, Pagefault with Interrupt Priority
Level (IPL) too high, after entering a SHOW CLUSTER/CONT command
and adding PORT class information.
Crash FOOTPRINT: From SDA> CLUE CRASH
Crash Time: 28-APR-1997 09:41:36.33
Bugcheck Type: PGFIPLHI, Pagefault with IPL too high
Node: XXXX (Clustered)
CPU Type: VAX
VMS Version: V6.2
Current Process: XXXX
Current Image: $1$DUA50:[SYS4.SYSCOMMON.][SYSEXE]SHWCLSTR.EXE
Failing PC: 00000000 00061080
Failing PS: 2C000000 00000803
Module: SHWCLSTR
Offset: 00061080
Offset: 00061080
o Modified date and time format for the SHOW CLUSTER utility. Signed
integer fields can now be displayed.
o For date/time display elements, the SHOW CLUSTER command shows only
the last two digits of the year. This can be seen by executing
any of the following 'Add' commands in SHOW CLUSTER/CONTINUOUS:
SHOW CLUSTER/CONTINUOUS
Add> ADD FORMED
Add> ADD LAST_TRANSITION
Add> ADD TRANSITION
If the system time is set to sometime in the year 2000, the year
is displayed as "00".
This change allows year to be displayed as a full four digit number.
INSTALLATION NOTES:
This kit requires a system reboot. Compaq strongly recommends that
a reboot is performed immediately after kit installation to avoid
system instability
If you have other nodes in your OpenVMS cluster, 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:
vaxcliu04_071.README
vaxcliu04_071.CHKSUM
vaxcliu04_071.CVRLET_TXT
vaxcliu04_071.a-dcx_vaxexe
vaxcliu04_071.CVRLET_TXT
|
