Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VMS721H1_SYS-V0600 Alpha V7.2-1H1 SYSTEM ECO Summary
*OpenVMS] VMS721H1_SYS-V0600 Alpha V7.2-1H1 SYSTEM ECO Summary
New Kit Date: 29-OCT-2002
Modification Date: Not Applicable
Modification Type: NEW KIT
Copyright (c) Compaq Computer Corporation 2002. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: System Executables
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS721H1_SYS-V0600
DEC-AXPVMS-VMS721H1_SYS-V0600--4.PCSI
ECO Kits Superseded by This ECO Kit: VMS721H1_SYS-V0500
ECO Kit Approximate Size: 10320 Blocks
Kit Applies To: OpenVMS Alpha V7.2-1H1
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), or later, must be installed BEFORE
installation of this, or any required kit:
VMS721H1_UPDATE-V0500
In order to receive all the corrections listed in this
kit, the following remedial kits, or later, should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for System components on OpenVMS Alpha V7.2-1H1. This
kit addresses the following problems:
PROBLEMS ADDRESSED IN VMS721H1_SYS-V0600 KIT
o F$GETSYI('RAD_MAX_RADS',node) fails to get the information
from the specified node. Instead, the command returns
information from the current node the command is executing on.
Note that with OpenVMS versions before V7.3-1, RAD_MAX_RADS
will return 1 if there is no RAD support, and will return 8 no
matter how many QBBs are physically present. This limitation
was documented in the V7.2-1H1R New Features and Release
Notes, June 2000, section 3.5.6.1.
Images Affected:[SYS$LDR]SYSGETSYI.EXE
o The system can crash with a FILCNTNONZ bugcheck.
CrashDump Summary
-----------------
Bugcheck Type: FILCNTNONZ, Open file count nonzero
after process rundown
Current Image: <not available>
Failing PC: FFFFFFFF.D269A360
PROCESS_MANAGEMENT+3C360
Failing PS: 18000000.00000000
Module: PROCESS_MANAGEMENT (Link Date/Time:
18-OCT-2000 07:01:30.44)
Offset: 0003C360
Images Affected:[SYS$LDR]IO_ROUTINES.EXE
[SYS$LDR]IO_ROUTINES_MON.EXE
O The system can crash with an INCONSTATE, Inconsistent I/O data
base bugcheck at EXE$FP_ASSIGN_PORT_C+0021C.
Crashdump Summary Information:
------------------------------
Bugcheck Type: INCONSTATE, Inconsistent I/O data base
Current Process: OPS_05B3
Current Image: $1$DUA42:[SYS3.SYSCOMMON.]
[SYSEXE]SMPUTIL.EXE
Failing PC: FFFFFFFF.800BC83C
EXE$FP_ASSIGN_PORT_C+0021C
Failing PS: 20000000.00000803
Module: IO_ROUTINES (Link Date/Time:
22-MAR-2001 00:58:18.18)
Offset: 0000883C
Failing Instruction: EXE$FP_ASSIGN_PORT_C+0021C: BUGCHK
Images Affected:[SYS$LDR]SYSTEM_PRIMITIVES.EXE
[SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE
[SYS$LDR]SYSTEM_PRIMITIVES.STB
[SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE
O The system can crash with a CWLNMERR bugcheck. The failing PC
is in routine TRNLNM, offset 7AC in PSECT
EXEC$HI_USE_PAGEABLE_CODE.
Images Affected:[SYS$LDR]LOGICAL_NAMES.EXE
O A program using C signals can be aborted with the condition
code set to the C signal value.
Images Affected:[SYS$LDR]EXCEPTION.EXE
[SYS$LDR]EXCEPTION_MON.EXE
O The system can crash with an SSRVEXCEPT, Unexpected system
bugcheck at EXE$IO_PERFORM_C+00650
Crashdump Summary Information:
------------------------------
Bugcheck Type: SSRVEXCEPT, Unexpected system
service exception
Current Process: ORA_P10111B1238
Current Image: $1$DGA92:[A_ORACLE.ORACLEV7336.RDBMS]SRV.EXE
Failing PC: FFFFFFFF.800CBEB0
EXE$IO_PERFORM_C+00650
Failing PS: 30000000.00000203
Module: IO_ROUTINES (Link Date/Time:
5-NOV-2001 11:49:25.01)
Offset: 00017EB0
Failing Instruction:
EXE$IO_PERFORM_C+00650: LDQ R18,#X0108(R18)\
Images Affected:[SYS$LDR]IO_ROUTINES.EXE
[SYS$LDR]IO_ROUTINES_MON.EXE
O A user-writen device driver using an IRPE for a second buffer
can result in an SSREXCEPT bugcheck in MMG_STD$IOLOCK_BUF if
it must fault in the affected page.
Section 2.2.1 of the OpenVMS Alpha Guide to Upgrading
Privileged Code Applications describes how device drivers can
lock down multiple I/O buffers using IRPEs with the
EXE_STD$READLOCK, WRITELOCK, or MODIFYLOCK routines.
Unfortunately, when an IRPE was passed in and the buffer
required a page fault this code used the IRP$PS_FDT_CONTEXT
offset on the IRPE, which is only valid on an IRP.
The correction for this problem is to delay the use of the
IRP$PS_FDT_CONTEXT cell until after the original IRP pointer
has been restored by a call to the error call back routine.
Images Affected:[SYS$LDR]IO_ROUTINES.EXE
[SYS$LDR]IO_ROUTINES_MON.EXE
[SYS$LDR]IO_ROUTINES.STB
[SYS$LDR]IO_ROUTINES_MON.STB
O If there is a lot of cluster-wide $GETJPI activity, a process
may hang waiting for the completion of an RMS $FLUSH
operation. The I/O request resulting from this may wait
forever because the IOSB is not filled in.
Images Affected:[SYS$LDR]PROCESS_MANAGEMENT.EXE
[SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
O A system that supports NUMA and has RAD_SUPPORT enabled, can
crash with an INVEXCEPTN bugcheck when the swapper is the
current process. The failing PC is at or around
MMG$WRTMFYPAG_C+006E4.
Images Affected:[SYS$LDR]SYS$VM.EXE
o Under some circumstances lookup of a device may fail. If the
system doing the lookup has a zero allocation class specified,
and attempts to access an MSCP-served disk by using the
NODE$DUA form, the access may fail because the device will not
be found.
This can be seen in the following SET VOLUME/REBUILD DCL
example (SHOW DEVICE fields have been edited for space
reasons).
$ SHOW DEVICE $8$DUA10
Device Device Error Volume
Name Status Count Label
$8$DUA10: (UTRAMP) Mounted alloc 0 TEST1
$ WRITE SYS$OUTPUT F$GETDVI("$8$DUA10:","EXISTS")
TRUE
$
$ WRITE SYS$OUTPUT F$GETDVI("$8$DUA10:","ROOTDEVNAM")
_UTRAMP$DUA10:
$
$ WRITE SYS$OUTPUT F$GETDVI("$8$DUA10:","DEVNAM")
_UTRAMP$DUA10:
$
$ WRITE SYS$OUTPUT F$GETDVI("_utramp$dua10:","EXISTS")
FALSE
$
$ SET VOLUME/REBUILD $8$DUA10:
%SET-E-NOTSET, error modifying _UTRAMP$DUA10:
-RMS-F-DEV, error in device name or inappropriate
device type for operation
%SET-E-NOTSET, error modifying _UTRAMP$DUA10:
-SYSTEM-W-NOSUCHDEV, no such device available
A lookup via the runtime library function
LIB$FIND_IMAGE_SYMBOL will also show the problem.
Images Affected:[SYS$LDR]IO_ROUTINES.EXE
[SYS$LDR]IO_ROUTINES_MON.EXE
o PWRK$STREAMSOS_V7.EXE is a big file, about 1760 blocks in
size. If this file has become very fragmented after
installation then Advanced server startup may fail with a
SS$_BADPARAM error. This can occur if PWRK$STREAMSOS_V7.EXE
is heavily fragmented and has multiple file headers (the
following example has been modified for space reasons):
$ @sys$startup:pwrk$startup
The file server will use DECnet, TCP/IP.
Advanced Server mail notification will use DECnet.
%SYSTEM-F-BADPARAM, bad parameter value
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line
PWRK$LOADSTREAMS_V7 LOAD main 7822
rel PC abs PC
000000000000213C 000000000003213C
image module routine line
PWRK$LOADSTREAMS_V7 LOAD __main 0
rel PC abs PC
0000000000000070 0000000000030070
image module routine line
0
rel PC abs PC
FFFFFFFF802653B4 FFFFFFFF802653B4
Images Affected:[SYS$LDR]SYSLDR_DYN.EXE
PROBLEMS ADDRESSED IN VMS721H1_SYS-V0500 KIT:
o The system can crash with a INVSECURESTATE at
NSA$DEREFERENCE_RIGHTS_CHAIN_C+0008C bugcheck. DOUBLEDEALO
crashes are also possible.
Crash Dump Summary Information
------------------------------
Bugcheck Type: INVSECURESTATE, Invalid state detected by
SECURITY subsystem
Current Image: DSA20:[SYS0.SYSCOMMON.]
[SYSEXE]OAFC$SERVER.EXE;1
Failing PC: FFFFFFFF.8019798C
NSA$DEREFERENCE_RIGHTS_CHAIN_C+0008C
Failing PS: 30000000.00000203
Module: SECURITY_MON (Link Date/Time:
17-OCT-2001 01:01:12.57)
Offset: 0000B98C
Images Affected: [SYS$LDR]SECURITY.EXE
[SYS$LDR]SECURITY_MON.EXE
[SYS$LDR]SECURITY.STB
[SYS$LDR]SECURITY_MON.STB
o The system can crash with a "RNLSTAKNV, Kernel stack not
valid" bugcheck during process or image rundown. The crash is
caused by invalid data in the CTL$GQ_REMOTE_FULLNAME size
field.
Images Affected: [SYS$LDR]PROCESS_MANAGEMENT.EXE
[SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
[SYS$LDR]PROCESS_MANAGEMENT.STB
[SYS$LDR]PROCESS_MANAGEMENT_MON.STB
o Doing I/O on a multipath device, when the current path is a
secondary, results in an increase in the UCB$L_OPCNT in the
primary as well as the current path UCB. Although the
UCB$L_OPCNT in the secondary grows faster than in the primary,
the UCB$L_OPCNT in the primary should not be changing (except,
at most by once per second for polling.) This is easily
observed when doing a DIR/SIZE on the system disk.
A number of customers and third-parties rely on these counters
to be accurate in their performance and capacity planning
tools.
Images Affected: SYS$LDR]IO_ROUTINES.EXE
SYS$LDR]IO_ROUTINES_MON.EXE
SYS$LDR]IO_ROUTINES.STB
SYS$LDR]IO_ROUTINES_MON.STB
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the OPENVMS database(s). To view these articles, open the appropriate
product database and perform a query using either of the following search
strings: 'VMS721H1_SYS-V0600' or 'VMS721H1_SYS'.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
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.
INSTALLATION INSTRUCTIONS:
Install this kit with the POLYCENTER Software installation utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:
PRODUCT INSTALL VMS721H1_SYS /SOURCE=[location of Kit]
The kit location may be a tape drive, CD, or a disk directory that
contains the kit.
Additional help on installing PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt
Special Installation Instructions:
o Scripting of Answers to Installation Questions
During installation, this kit will ask and require user
response to several questions. If you wish to automate the
installation of this kit and avoid having to provide responses
to these questions, you must create a DCL command procedure
that includes the following definitions and commands:
- $ DEFINE/SYS NO_ASK$BACKUP TRUE
- $ DEFINE/SYS NO_ASK$REBOOT TRUE
- Add the following qualifiers to the PRODUCT INSTALL
command and add that command to the DCL procedure.
/PROD=DEC/BASE=AXPVMS/VER=V6.0
- De-assign the logicals assigned
For example, a sample command file to install the
VMS721H1_SYS-V0600 kit would be:
$
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$!
$ PROD INSTALL VMS721H1_SYS/PROD=DEC/BASE=AXPVMS/VER=V6.0
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ exit
All trademarks are the property of their respective owners.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| EXCEPTION.EXE | B6F60C06 | X-3 | 17-JUL-2002 |
| | | 03:47:35.04 |
+----------------------------+----------+-----------------+--------------+
| EXCEPTION_MON.EXE | 35CFE628 | X-3 | 17-JUL-2002 |
| | | 03:56:37.48 |
+----------------------------+----------+-----------------+--------------+
| IO_ROUTINES.EXE | 71E3F46F | X-3 | 17-JUL-2002 |
| | | 04:04:17.41 |
+----------------------------+----------+-----------------+--------------+
| IO_ROUTINES_MON.EXE | 2C721DA4 | X-3 | 17-JUL-2002 |
| | | 04:07:13.57 |
+----------------------------+----------+-----------------+--------------+
| LOGICAL_NAMES.EXE | 7D10F7E5 | X-3 | 17-JUL-2002 |
| | | 04:09:54.46 |
+----------------------------+----------+-----------------+--------------+
| PROCESS_MANAGEMENT.EXE | 9AB316F6 | X-3 | 17-JUL-2002 |
| | | 03:56:26.39 |
+----------------------------+----------+-----------------+--------------+
| PROCESS_MANAGEMENT_MON.EXE | 1052156E | X-3 | 17-JUL-2002 |
| | | 04:04:10.84 |
+----------------------------+----------+-----------------+--------------+
| SECURITY.EXE | 8B34E6B1 | X-5 | 17-JUL-2002 |
| | | 04:07:07.96 |
+----------------------------+----------+-----------------+--------------+
| SECURITY_MON.EXE | D15F4CA8 | X-5 | 17-JUL-2002 |
| | | 04:07:52.58 |
+----------------------------+----------+-----------------+--------------+
| SYS$VM.EXE | 6468B75E | X-3 | 17-JUL-2002 |
| | | 04:11:33.52 |
+----------------------------+----------+-----------------+--------------+
| SYSGETSYI.EXE | AD19DFDB | X-3 | 17-JUL-2002 |
| | | 03:49:12.05 |
+----------------------------+----------+-----------------+--------------+
| SYSLDR_DYN.EXE | 46990068 | X-3 | 17-JUL-2002 |
| | | 03:54:16.91 |
+----------------------------+----------+-----------------+--------------+
| SYSTEM_PRIMITIVES.EXE | DA722C7B | X-3 | 17-JUL-2002 |
| | | 04:05:20.21 |
+----------------------------+----------+-----------------+--------------+
| SYSTEM_PRIMITIVES_MIN.EXE | 7D933347 | X-3 | 17-JUL-2002 |
| | | 04:00:27.29 |
+----------------------------+----------+-----------------+--------------+
Vimal Anand (7866677)
|
