======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_DCL-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 2.2 Reboot Requirement: No reboot is necessary after installation of this kit, however, there are additional steps that must be performed in order to use the images provided by this kit. Refer to the section titled Special Installation Instructions for required post-installation actions. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS for Integrity Servers V8.4 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS84I_PCSI-V0400 - VMS84I_UPDATE-V0600 Page 2 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS84I_DCL-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Process crashes after CTRL-Y followed by few DCL built-in commands 5.2.1.1 Problem Description: CTRL-Y context is not restored correctly after execution of commands on V8.4. Thus resulting in stack corruption and finally crashing the process. For example process crashes with the below sequence of commands. $ HELP CTRL-Y $ X=1 $ SHOW SYMBOL X $ CONTINUE This problem has been fixed. Images Affected: - [SYSEXE]DCL.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001179410 5.2.1.2.2 PTR(s) None Page 3 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.1.4 Work-arounds: None 5.2.2 LIB$SPAWN fails sometime when called from a user program 5.2.2.1 Problem Description: LIB$SPAWN fails sometime when called from a user program with the following error %RMS-F-DEV, error in device name or inappropriate device type for operation This problem has been fixed. Images Affected: - [SYSEXE]DCL.EXE 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1001203573 5.2.2.2.2 PTR(s) None 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.2.4 Work-arounds: None Page 4 5.2.3 Interactive processes are aborted due to various unexpected access violations 5.2.3.1 Problem Description: Interactive processes fails sometimes with access violations shown below. %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000094754, PC=000000006754F4C1, PS=0000001B Improperly handled condition, image exit forced. Signal arguments: Number = 0000000000000005 Name = 000000000000000C 0000000000000000 0000000000094754 000000006754F4C1 000000000000001B Register dump: R0 = 0000000000000000 R1 = 00000000677C4000 R2 = 0000000000000009 R3 = 0000000000094754 R4 = 000000007FFCF818 R5 = 000000007FFCF8B0 R6 = 0000000000000980 R7 = 0000000000000001 R8 = 00000000673AC980 R9 = 0000000067D963E8 R10 = 00000000000067D9 R11 = 00000000673AC994 SP = 00000000673AC880 TP = 0000000067C2A1C8 R14 = 000000006754DBD0 R15 = 000000007FFD06F0 R16 = 0000000000000000 R17 = 0000000000000001 R18 = 00000000675C67F8 R19 = 00000000673AC988 R20 = 00000000673AC988 R21 = 0000000067D963E8 R22 = 00000000675C67F0 R23 = 00000000673AC9A8 R24 = 0000000000000008 R25 = 0000000000000003 R26 = 0000000000054038 R27 = 00000000673AC988 R28 = 0000000000000000 R29 = 00000000673AC920 R30 = 0000000000005FC8 R31 = 0000000000030940 PC = 000000006754F4C1 BSP/STORE = 000007FDBFFD46D0 / 000007FDBFFD4470 PSR = 00001213084AE010 IIPA = 000000006754F4C0 B0 = 000000006754DC70 B6 = FFFFFFFF801DC260 B7 = 000000006754DBD0 Interrupted Frame RSE Backing Store, Size = 21 registers R32 = 00000000673AC990 R33 = 00000000673AC8C8 R34 = 00000000673AC988 R35 = 00000000673AC994 R36 = 0000000000054038 R37 = 0000000000010000 R38 = 0000000000000000 R39 = 0000000000000001 R40 = 00000000677C4000 R41 = 0000000000000000 R42 = 00000000673AC9A8 R43 = 0000000000054038 R44 = 0000000000010000 R45 = 000000006754DC70 R46 = C000000000000287 R47 = 00000000677C4000 R48 = 0000000000030940 R49 = 00000000673AC988 R50 = 0000000067D963E8 R51 = 00000000673AC960 R52 = FFFFFFFF803CA580 This problem has been fixed. Images Affected: - [SYSEXE]DCL.EXE Page 5 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1001226191, QXCM1001240391 5.2.3.2.2 PTR(s) None 5.2.3.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.3.4 Work-arounds: None 5.2.4 Commands which depend on "JOB_LOGIN" time shows unexpected results 5.2.4.1 Problem Description: Some of the commands which depend on "JOB_LOGIN" time shows unexpected results.This is because JOB_LOGIN time is incorrectly calculated when called from a sub process. For example: 1. F$CVTIME lexical $ WRITE SYS$OUTPUT F$CVTIME("JOB_LOGIN") 2012-05-22 17:13:51.31 $ SPAWN WRITE SYS$OUTPUT F$CVTIME("JOB_LOGIN") %DCL-S-SPAWNED, process SWEENEY_2504 spawned %DCL-S-ATTACHED, terminal now attached to process SWEENEY_2504 1858-11-17 00:00:54.84 %DCL-S-RETURNED, control returned to process SWEENEY 2. DIR/SINCE $ DIR/DATE=CREATED LOGIN.COM Directory DKA0:[TEST123] LOGIN.COM;9 1 5-OCT-2011 12:14:44.41 LOGIN.COM;8 1 22-MAR-2010 10:08:31.36 LOGIN.COM;7 1 22-MAR-2010 10:07:45.18 LOGIN.COM;6 1 22-MAR-2010 10:07:17.63 Total of 4 files, 4 blocks. $ DIR/DATE=CREATED LOGIN.COM/CREATED/SINCE=JOB_LOGIN %DIRECT-W-NOFILES, no files found $ SPAWN DIR/DATE=CREATED LOGIN.COM/CREATED/SINCE=JOB_LOGIN %DCL-S-SPAWNED, process TEST123__35318 spawned %DCL-S-ATTACHED, terminal now attached to process TEST123__35318 Page 6 Directory DKA0:[TEST123] LOGIN.COM;9 1 5-OCT-2011 12:14:44.41 LOGIN.COM;8 1 22-MAR-2010 10:08:31.36 LOGIN.COM;7 1 22-MAR-2010 10:07:45.18 LOGIN.COM;6 1 22-MAR-2010 10:07:17.63 Total of 4 files, 4 blocks. %DCL-S-RETURNED, control returned to process TEST1 23__35922< br>$ Images Affected: - [SYSEXE]DCL.EXE 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001218013 5.2.4.2.2 PTR(s) None 5.2.4.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.4.4 Work-arounds: None 5.2.5 The lexical function F$GETSYI does not return correct information for LCKMGR* sysgen parameters 5.2.5.1 Problem Description: The lexical function F$GETSYI incorrectly formats the item codes of LCKMGR* family. If the value set is an ODD number it returns TRUE and FALSE otherwise. Images Affected: - [SYSEXE]DCL.EXE Page 7 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases QXCM1001196103 , QXCM1000472401 5.2.5.2.2 PTR(s) None 5.2.5.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.5.4 Work-arounds: None 6 FILES PATCHED OR REPLACED: o [SYSEXE]DCL.EXE (new image) Image Identification Information Image name: "DCL" Image file identification: "X-55" Image build identification: "0100000086" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2012 12:39:40.87 Overall Image Checksum: 88EC702D 7 INSTALLATION INSTRUCTIONS 7.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. Page 8 o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 7.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS84I_DCL-V0100.ZIPEXE 7.3 Installation Command 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 VMS84I_DCL[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. The kit location may be a tape drive, CD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 7.4 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 logical name definitions and commands: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE Page 9 o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of that operation. There is no need to also save files as *.*_OLD: $ DEFINE/JOB ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=HP/BASE=I64VMS/VER=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_DCL-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_DCL/PRODUCER=HP/BASE=I64VMS/VER=V1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! 7.5 Special Installation Instructions: If this kit is being installed in a clustered environment with a shared system disk, in order for all members of the cluster that share the system disk to make use of the new image, you must execute the following command on each node that is sharing the system disk: INSTALL REPLACE SYS$SYSTEM:DCL.EXE Once installed, users will need to log out and log in back to use the new image. (C) Copyright 2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Page 10 Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.