|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: system PRIVILEGED account (root
stage1.cxo.cpqcorp.net)Date: Fri Feb 22 2002 - 03:30:03 CST
*******************************************************************************
* *
* This is an update to an existing patch... *
* *
* Online links can be found at *
* http://ftp.support.compaq.com/patches/public/vms/axp/v7.2-1/dec-axpvms-vms721_dcl-v0300--4.README
*******************************************************************************
TITLE: OpenVMS VMS721_DCL-V0300 Alpha V7.2-1 DCL ECO Summary
New Kit Date: 22-FEB-2002
Modification Date: Not Applicable
Modification Type: Updated Kit Supersedes VMS721_DCL-V0200
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, 2002. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: DCL
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS721_DCL-V0300
DEC-AXPVMS-VMS721_DCL-V0300--4.PCSI
ECO Kits Superseded by This ECO Kit: VMS721_DCL-V0200
ECO Kit Approximate Size: 816 Blocks
Kit Applies To: OpenVMS Alpha V7.2-1
System/Cluster Reboot Necessary: No
Rolling Re-boot Supported: Not Applicable
Installation Rating: INSTALL_3
3 - To be installed on all systems running
the listed versions of OpenVMS which
are experiencing the problems described.
Kit Dependencies:
The following remedial kit(s), or later, must be installed BEFORE
installation of this kit:
VMS721_UPDATE-V0300
VMS721_PCSI-V0100
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for DCL on OpenVMS Alpha V7.2-1.
This kit addresses the following problems:
PROBLEMS ADDRESSED IN VMS721_DCL-V0300 KIT:
o The behavior of fcvtime() before installation of the
VMS721_DCL-V0200 kit is:
$ WRITE SYS$OUTPUT f$cvtime() 2001-10-22 13:10:08.99
The behavior of fcvtime() after installation of the
VMS721_DCL-V0200 kit is:
$ WRITE SYS$OUTPUT f$cvtime()
Signal arguments: Number = 0000000000000005
Name = 000000000000000C
000000000000000
0000000000000004
000000007AFE39AC
0000000000000012
Images Affected: [SYSEXE]DCL.EXE
o When the DCL PIPE command is issued in batch mode, it skips
over the DCL statement immediately following the PIPE command.
This occurs when the ";" separator is followed by a command
sequence containing an "filespec" command.
Images Affected: [SYSEXE]DCL.EXE
o Running the pipe command in a loop might result in one of the
following:
o DOUBLDEALO user mode bugchecks
o ACCVIO in various symbol manipulation routines
o SYMOVF error message
Images Affected: [SYSEXE]DCL.EXE
o A process that has spawned several jobs, using a combination
of SPAWN/WAIT and SPAWN/NOWAIT commands, stays in state HIB
after all the spawned subprocesses have completed.
Images Affected: [SYSEXE]DCL.EXE
PROBLEMS ADDRESSED IN VMS721_DCL-V0200 KIT:
o When a DCL procedure reports a DCL-W-SKPDAT error, it does not
jump to an error handler but instead continues. This occurs
even though the procedure has defined an error handler with an
"on warning goto <label>" statement.
Images Affected: [SYSEXE]DCL.EXE
o After installing VMS721_DCL-V0100 ECO kit, the F$CVTIME
lexical no longer works if the third parameter (output field)
is blank or null. Attempted execution results in an ACCVIO.
For example:
$ WRITE SYS$OUTPUT f$cvtime(,,)
Improperly handled condition, bad stack or no handler specified.
Signal arguments: Number = 0000000000000005
Name = 000000000000000C
0000000000000000
0000000000000004
000000007AFFD9AC
Images Affected: [SYSEXE]DCL.EXE
o Attempting to execute the TCPIP$CONFIG.COM procedure results
in an ACCVIO terminating the process. Following is an example
of the process crash:
$ TCPIP$CONFIG
Checking TCP/IP Services for OpenVMS configuration database files.
Improperly handled condition, bad stack or no handler specified.
Signal arguments: Number = 0000000000000005
Name = 000000000000000C
0000000000000000
0000000000000001
000000007AFC4B50
0000000000000012
Images Affected: [SYSEXE]DCL.EXE
o The PIPE command may overflow the mailbox handling the data
between the subprocesses. This causes a SYSTEM-F-MBTOOSML
error. Raising the SYSGEN parameter DEFMBXMXMSG does not
eliminate the error.
Images Affected: [SYSEXE]DCL.EXE
PROBLEMS ADDRESSED IN VMS721_DCL-V0100 KIT:
o Nested commands reset the SYS$COMMAND input stream after
completing.
Images Affected: [SYSEXE]DCL.EXE
o The F$CONTEXT command returns the wrong status. See example
below:
$ dummy=f$context("process",ctx,"uic","nobrackets","eql")
%DCL-S-NORMAL, normal successful completion
Images Affected: [SYSEXE]DCL.EXE
o The F$DEVICE lexical function will not find some devices.
Even though the TLZ10 is a supported device, the DCL command:
$ WRITE SYS$OUTPUT F$DEVICE("*","TAPE","TLZ10")
results in the following error message:
%DCL-W-IVKEYW, unrecognized keyword - check validity
and spelling
Images Affected: [SYSEXE]DCL.EXE
o The F$CVTIME command returns IVATIME for legal arguments. The
command should return the zero hour of the date included in
the input_time argument of F$CVTIME:
AJAX> b=f$cvtime("24-",,)
AJAX> SHOW SYMBOL b
B = "2001-04-24 00:00:00.00"
If the F$CVTIME command is preceded with a certain F$EXTRACT
command, the F$CVTIME command fails:
AJAX> a=f$extract(0,1,"1234")
AJAX> b=f$cvtime("24-",,)
%DCL-W-IVATIME, invalid absolute time - use
DD-MMM-YYYY:HH:MM:SS.CC format \24-\
Images Affected: [SYSEXE]DCL.EXE
o The DEFINE command corrupts the image context registers, which
prevents $CONTINUE. See partial error display below:
$ CREATE a.a
adsf;kjf;fkj
Interrupt
$ DEFINE aaaaa bbbb
$ CREATE
Improperly handled condition, bad stack or no handler
specified.
Signal arguments: Number = 0000000000000005
Name = 000000000000000C
0000000000010000
7FFAD25200000004
7FFAD25200000004
0000000000000012
Register dump:
R0 = 0000000000000000 R1 = 000000007FFAD788
R2 = 0000000000000000 R3 = 0000000000000004
R4 = 0000000000000000 R5 = 0000000000000000
R6 = 000000007FFAD778 R7 = 000000007FFAD778
R8 = 000000007FFABD48 R9 = 000000007FFABF50
R10 = 000000007FFADFC0 R11 = 000000007FFCE3E0
R12 = 0000000000000000 R13 = 000000007AFD66A0
R14 = FFFFFFFF823EE1C0 R15 = 000000007AFD5990
R16 = 000000000000001B R17 = 000000007FFAD778
R18 = 000000007FFAD778 R19 = 0000000000000000
R20 = 0000000000000000 R21 = FFFFFFFFFFFFFFA8
R22 = 0000000000000000 R23 = 0000000000000001
R24 = 0000000000000000 R25 = 0000000000000000
R26 = 000000007FFADFC0 R27 = 0000000000000008
R28 = 7FFAD25200000004 R29 = 7B0296A60000000B
SP = 000000007FFABD05 PC = 7FFAD25200000004
PS = 0500000000000012
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=000000000000
000C, PC=0000000000000012, PS=00000002
Images Affected: [SYSEXE]DCL.EXE
INSTALLATION NOTES:
No reboot is necessary after successful installation of the kit.
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 VMS721_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=V3.0
- De-assign the logicals assigned
For example, a sample command file to install the
VMS721_DCL-V0300 kit would be:
$
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$!
$ PROD INSTALL VMS721H1_DCL/PROD=DEC/BASE=AXPVMS/VER=V3.0
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$!
$ exit
---
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]