Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VMS722_DCL-V0200 Alpha V7.2-2 DCL ECO Summary
*OpenVMS] VMS722_DCL-V0200 Alpha V7.2-2 DCL ECO Summary
New Kit Date: 24-APR-2003
Modification Date: Not Applicable
Modification Type: NEW KIT
Copyright (c) Hewlett-Packard Company 2002,2003. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: DCL
SOURCE: Hewlett-Packard Company
ECO INFORMATION:
ECO Kit Name: VMS722_DCL-V0200
DEC-AXPVMS-VMS722_DCL-V0200--4.PCSI
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 832 Blocks
Kit Applies To: OpenVMS Alpha V7.2-2
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_3
3 - To be installed by customers experiencing the problems
corrected.
Kit Dependencies:
The following remedial kit(s), or later, must be installed BEFORE
installation of this, or any required kit:
VMS722_UPDATE-V0100
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 DCL on OpenVMS Alpha V7.2-2.
This kit addresses the following problems:
PROBLEMS ADDRESSED IN VMS722_DCL-V0200 KIT
o On a fast SMP machine, complex pipe commands running in batch
may hang. In the most common scenario, some of the
subprocesses created by the pipe command are hanging in the
LEF state with the parent process hanging in a HIB state.
Images Affected:[SYSEXE]DCL.EXE
o Exit handlers declared in user images with upcalls enabled may
not run to completion. Network disconnects or <CTRL>Y
interrupts without a CONTINUE could cause this problem.
Images Affected:[SYSEXE]DCL.EXE
o Because of a change to DCL, images that get data input from
command procedure lines do not return the correct exit status
($STATUS). If the image exits with a severity error having a
fatal or warning status and there remain unprocessed data
lines in the command procedure, the exit status is overwritten
with DCL-W-SKPDAT. Below is a procedure showing the behavior
change:
$ SET VERIFY
$ RUN TEMP
!this is random test 1
!this is random test 2
!this is random test 3
!this is random test 4
this is random test 5
that DCL should just skip
$ SAY "HI!"
$ SET NOVERIFY
Results of running command procedure before change:
--------------------------------------------------
$ @temp
$ RUN TEMP
!this is random test 1
%NONAME-F-NOMSG, Message number 00000004
%DCL-W-SKPDAT, image data (records not beginning
with "$") ignored
$
Results of running command procedure after behavior change:
----------------------------------------------------------
$ @temp
$ RUN TEMP
!this is random test 1
%NONAME-F-NOMSG, Message number 00000004
%DCL-W-SKPDAT, image data (records not beginning
with "$") ignored
$ SAY "HI!"
%DCL-W-IVVERB, unrecognized command verb - check validity
and spelling \SAY\
$ SET NOVERIFY
$
Images Affected:[SYSEXE]DCL.EXE
o A file created by DCL will erroneously inherit the file
extension quantity value from a previously opened file. For
example:
$ DIR/FULL LOGIN.COM
.
.
.
File attributes: Allocation: 18, Extend: 5000
** Note that LOGIN.COM has DEQ set to 5000
$ OPEN/READ/SHARE FILE LOGIN.COM
$ CLOSE FILE
$
$ @tt/out=out.txt
_$ put something in file
%DCL-W-IVVERB, unrecognized command verb -
check validity and spelling \PUT\
_$ Exit
$
$ DIR/FULL OUT.TXT
Directory $2$DKB0:[TEST]
OUT.TXT;1 File ID: (8282,1,0)
Size: 1/5004 Owner: [SYSTEM]
Created: 21-AUG-2002 10:35:50.40
Revised: 21-AUG-2002 10:35:57.94 (1)
File attributes: Allocation: 5004, Extend: 5000,
Global buffer count: 0
Client attributes: None
Total of 1 file, 1/5004 blocks.
Images Affected:[SYSEXE]DCL.EXE
o If an upcall enabled image's execution is interrupted with ^y,
and execution of a DCL command procedure is entered as the
first command at the ^Y DCL prompt, an access violation
occurs. For example:
^y
$ @TEST
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=0000000000000004, PC=FFFFFFFF80B4FBEC, PS=0000001B
...
Images Affected:[SYSEXE]DCL.EXE
o The following call to F$GETSYI, on a system that does not
support partitioning, will crash the process:
$ write sys$output f$getsyi("cpu_failover")
Improperly handled condition, bad stack or no handler
specified.
Signal arguments: Number = 0000000000000005
Name = 000000000000000C
0000000000000004
000000007FFAE000
000000007FFAE000
000000007FFAE000
0000000000000012
.
.
.
.
%DCL-S-RETURNED, control returned to process GUY
%SYSTEM-F-ACCVIO, access violation, reason mask=00,
virtual address=000000000000000C, PC=000000000000000C,
PS=7FFAC4C3
Images Affected:[SYSEXE]DCL.EXE
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: 'VMS722_DCL-V0200' or 'DCL'.
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 VMS722_DCL /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
- Add the following qualifiers to the PRODUCT INSTALL
command and add that command to the DCL procedure.
/PROD=DEC/BASE=AXPVMS/VER=V2.0
- De-assign the logicals assigned
For example, a sample command file to install the
VMS722_DCL-V0200 kit would be:
$
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$!
$ PROD INSTALL VMS722_DCL/PROD=DEC/BASE=AXPVMS/VER=V2.0
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ exit
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| DCL.EXE | 73D49A74 | X-18 | 19-FEB-2003 |
| | | 10:20:53.04 |
+----------------------------+----------+-----------------+--------------+
|
