======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_MANAGE-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. 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-V0700 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None Page 2 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS84I_MANAGE-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 SYSMAN> DISKQUOTA SHOW command failing with SYSTEM-F-NOIOCHAN error. 5.2.1.1 Problem Description: SYSMAN> DISKQUOTA SHOW command executed with non-existing UIC results in SYSMAN failing with SMI-E-INVUIC error as shown below. SYSMAN> DISKQUOTA SHOW [nonexisting_uic] %SYSMAN-I-NODERR, error returned from node FDSD08 -SMI-E-INVUIC, invalid UIC specified If this command is executed repeatedly, SYSMAN fails with "SYSTEM-F-NOIOCHAN" error when the number of repetitions exceeds the value specified by CHANNELCNT system parameter. SYSMAN> DISKQUOTA SHOW [nonexisting_uic] %SYSMAN-I-NODERR, error returned from node FDSD08 -SYSTEM-F-NOIOCHAN, no I/O channel available This problem has been fixed. Images Affected: - [SYSLIB]SMI$OBJSHR.EXE - [SYSLIB]SMI$SHR.EXE - [SYSEXE]SYSMAN.EXE - [SYSEXE]SMISERVER.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001198007 Page 3 5.2.1.2.2 PTR(S) None. 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.1.4 Work-arounds: None 5.2.2 SYSMAN not reporting error messages. 5.2.2.1 Problem Description: SYSMAN does not report any error messages when 1. MC SYSMAN RESERVED_MEMORY EXTEND command executed without /RAD qualifier. 2. Any error occured when creating the device name using MC SYSMAN IO CREATE_WWID command. This problem has been fixed. Images Affected: - [SYSLIB]SMI$OBJSHR.EXE - [SYSLIB]SMI$SHR.EXE - [SYSEXE]SYSMAN.EXE - [SYSEXE]SMISERVER.EXE 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1001198066, QXCM1001202702 5.2.2.2.2 PTR(S) None. Page 4 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.2.4 Work-arounds: None 5.2.3 SYSMAN truncates long commands without displaying any message. 5.2.3.1 Problem Description: Commands longer than 255 characters, when entered in the SYSMAN prompt get truncated without providing any status message. For Example: SYSMAN> do define/system lengthtest "DISK$12[COMMON.INTDRV.ENG_IMAGES], DISK$12:[COMMON.INTDRV.ENG_IMAGES.TEST_DIRECTORY1], DISK$12:[COMMON.INTDRV.ENG_IMAGES.TEST_DIRECTORY1], DISK$12:[COMMON.INTDRV.ENG_IMAGES.TEST_DIRECTORY1], DISK$12:[COMMON.INTDRV.ENG_IMAGES.TEST_DIRECTORY1], DISK$12:[COMMON.INTDRV.ENG_IMAGES.TEST_DIRECTORY1], DISK$12:[COMMON.INTDRV.ENG_IMAGES.TEST_DIRECTORY1]" %SYSMAN-I-OUTPUT, command execution on node BANFF %DCL-I-SUPERSEDE, previous value of LENGTHTEST has been superseded SYSMAN> do sh log lengthtest %SYSMAN-I-OUTPUT, command execution on node BANFF "LENGTHTEST" = "DISK$12:[COMMON.INTDRV.ENG_IMAGES],DISK$12:[COMMON. INTDRV.ENG_IMAGES.TEST_DIRECTORY1], DISK$12: [COMMON.INTDRV.ENG_IMAGES.TEST_DIRECTORY1], DISK$12: [COMMON.INTDRV.ENG_IMAGES.TEST_DIRECTORY1], DISK$12:[COMMON.INTDRV.ENG_IMAGES.TE" (LNM$SYSTEM_TABLE) SYSMAN> This problem has been fixed. Images Affected: - [SYSLIB]SMI$OBJSHR.EXE - [SYSLIB]SMI$SHR.EXE - [SYSEXE]SMISERVER.EXE - [SYSEXE]SYSMAN.EXE Page 5 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1001279879 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 Integrity After V8.4 5.2.3.4 Work-arounds: None 5.2.4 SYSMAN crashes while executing commands in the SYSMAN prompt,when the SYSMANINI logical is defined. 5.2.4.1 Problem Description: After installing VMS84I_SYS-V0400 or VMS84A_SYS-V0400, on defining the SYSMANINI logical to a valid initialization file causes subsequent SYSMAN commands to crash as seen below: $TYPE SYS$LOGIN:SYSMANINI_FILE.COM set profile/priv=all $ $MCR SYSMAN SYSMAN> SET ENVIRONMENT %SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=0000000020202020, PC=0000000000053792,PS=0000001B Improperly handled condition, image exit forced. Signal arguments: Number = 0000000000000005 Name = 000000000000000C 0000000000000004 0000000020202020 0000000000053792 000000000000001B Register dump: R0 = 0000000000000000 R1 = FFFFFFFF843C6A00 R2 = 0000000000000238 R3 = 0000000020202020 R4 = 000000007FFCF818 R5 = 000000007FFCF8B0 R6 = 0000000010000001 R7 = 0000000000000001 R8 = 000000000000000C R9 = 0000000000000005 R10 = 0000000000000000 R11 = 0000000000107130 SP = 000000007ACF3900 TP = 000000007B4EE1C8 R14 = FFFFFFFF800EAB00 R15 = 000000000000000C R16 = 0000000000000004 R17 = 0000000020202020 R18 = 0000000000000000 R19 = FFFFFFFF800EA830 R20 = FFFFFFFF8034A570 Page 6 R21 = 0000000000000003 R22 = 0000000000053792 R23 = 0000000020202027 R24 = 0000000000000001 R25 = 0000000000000005 R26 = 000000000001F124 R27 = 000000007ACF383C R28 = 0000000000000040 R29 = 0000000000000001 R30 = 000000000001F128 R31 = 0000000000000003 PC = 0000000000053792 BSP/STORE = 000007FDBFFD4740 / 000007FDBFFD4740 PSR = 0000141308026010 IIPA = FFFFFFFF800EA480 B0 = 00000000000537A0 B6 = FFFFFFFF8034A570 B7 = FFFFFFFF821B9510 Interrupted Frame RSE Backing Store, Size = 14 registers R32 = 000000000001E3BC R33 = 0000000000053EC0 R34 = C00000000000099B R35 = 000000007FFCF818 R36 = 000000007FFCF8B0 R37 = 0000000010000001 R38 = 000000007ACF3870 R39 = 0000000000000007 R40 = 000000000001E3BC R41 = 00000000000540E0 R42 = C00000000000099B R43 = 00000000002F0000 R44 = 0000000020202020 R45 = 0000000000000001 Images Affected: - [SYSEXE]SYSMAN.EXE 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001319241 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 Integrity after V8.4 5.2.4.4 Work-arounds: None 6 FILES PATCHED OR REPLACED: o [SYSLIB]SMI$OBJSHR.EXE (new image) Image Identification Information Image name: "SMI$OBJSHR" Image file identification: "X40-A9" Image build identification: "0100000121" linker identification: "Linker I02-37" Link Date/Time: 22-NOV-2013 13:45:35.16 Overall Image Checksum: 2014119F Page 7 o [SYSLIB]SMI$SHR.EXE (new image) Image Identification Information Image name: "SMI$SHR" Image file identification: "X01-04" Image build identification: "0100000121" linker identification: "Linker I02-37" Link Date/Time: 22-NOV-2013 13:45:32.71 Overall Image Checksum: 517CA5CD o [SYSEXE]SMISERVER.EXE (new image) Image Identification Information Image name: "SMISERVER" Image file identification: "X01-15" Image build identification: "0100000121" linker identification: "Linker I02-37" Link Date/Time: 22-NOV-2013 13:45:38.66 Overall Image Checksum: ABD0114D o [SYSEXE]SYSMAN.EXE (new image) Image Identification Information Image name: "SYSMAN" Image file identification: "X01-22" Image build identification: "0100000121" linker identification: "Linker I02-37" Link Date/Time: 22-NOV-2013 13:45:37.22 Overall Image Checksum: A8F047B7 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. 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. Page 8 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_MANAGE-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_MANAGE[/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 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 Page 9 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_MANAGE-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_MANAGE/PRODUCER=HP/BASE=I64VMS/VER=V1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2013 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. 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, Page 10 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.