======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_SYS-V0400 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1 : To be installed by all customers. This installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) 2.2 Reboot Requirement: Reboot Required. HP 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. 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: - VMS84I_SYS-V0300 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-V0800 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_SYS-V0400 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 RUN/EXTENT to remote node is not being used. 5.2.1.1 Problem Description: When a user runs an image on a remote node, the value of WSEXTENT that is passed via the "/EXTENT" qualifier does not take effect. For example, when a user runs the following command, the actual WSEXTENT value is not the same as the input, even if the input is within legal limits. $ RUN /EXTENT = /ON = This problem has been fixed. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001239289 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 Possible CPUSPINWAIT deadlock involving MMG and per PCB spinlocks 5.2.2.1 Problem Description: A CPUSPINWAIT deadlock bugcheck can occur involving the MMG and per PCB spinlock for a multithreaded process pagefaulting during times when the nonpaged pool variable list and 64 byte lookaside list are exhausted. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1000828776 QXCM1001242216 QXCM1001307634 5.2.2.2.2 PTR(S) 75-74-378 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 Page 4 5.2.2.4 Work-arounds: Provide adequate nonpaged pool so there will not be a shortage. 5.2.3 Reduce possible Mutex thrashing 5.2.3.1 Problem Description: When many processes attempt to acquire the same mutex for write access at the same time they can thrash consuming large amounts of CPU time and degrading the overall performance of the system. Attempt to reduce the thrashing that can occur in such cases. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases None 5.2.3.2.2 PTR(S) 75-74-398 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 Page 5 5.2.4 Enable Paged Pool lookaside lists by default 5.2.4.1 Problem Description: Enable paged dynamic pool lookaside lists by default to reduce paged dynamic pool variable freelist fragmentation and improve paged pool allocation and deallocation performance. The default SYSGEN parameter PAGED_LAL_SIZE is being changed from 0 to 512 bytes, indicating that packets less than or equal to 512 bytes in size can come from the lookaside lists. Larger packets continue to come from the paged dynamic pool variable freelist. To disable use of the paged dynamic pool lookaside lists PAGED_LAL_SIZE can be set to 0. Images Affected: - [SYS$LDR]SYS$BASE_IMAGE.EXE - [SYSLIB]SDA$SHARE.EXE - [SYSEXE]SYSGEN.EXE - [SYSEXE]SYSBOOT.EXE - [SYSEXE]SYSMAN.EXE - [SYSEXE]SMISERVER.EXE 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases None 5.2.4.2.2 PTR(S) 75-74-330 5.2.4.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 Page 6 5.2.4.4 Work-arounds: SYSGEN parameter PAGED_LAL_SIZE can be changed to the new value as well. 5.2.5 Possible INCONMMGST bugcheck running down RMS global buffer 5.2.5.1 Problem Description: Some sites have occasionally seen INCONMMGST bugchecks in MMG$FIND_GSTE when running down an RMS global buffer. The problem has not been readily reproducible and thus far has not been isolated. But enough is understood to make a possible workaround for the issue until it can be identified and addressed. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases QXCM1001108110 QXCM1001152913 QXCM1001209305 QXCM1001247907 QXCM1001261385 QXCM1001264869 QXCM1001271968 QXCM1001272536 QXCM1001278413 5.2.5.2.2 PTR(S) 75-13-2520 Page 7 5.2.5.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.5.4 Work-arounds: If a single file is triggering the bugcheck a workaround would be to remove RMS global buffering from that file. 5.2.6 Process hang waiting for inner mode special kernel AST 5.2.6.1 Problem Description: Due to a small timing window an inner mode special kernel AST could get queued but never processed. This could result in a process, system, or cluster hang depending on what locks the process may be holding. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 5.2.6.2 Quix and PTR cases reporting this problem: 5.2.6.2.1 Quix Cases QXCM1001287896 QXCM1001019926 QXCM1000956271 5.2.6.2.2 PTR(S) 75-13-2368 5.2.6.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 Page 8 5.2.6.4 Work-arounds: Periodically delivering another kernel mode AST to the process can free it up, such as going into SDA and getting a list of process channels: $ ANALYZE/SYSTEM SDA> SET OUTPUT NL: SDA> SHOW PROCESS/CHANNEL ALL SDA> EXIT 5.2.7 Recursive bugcheck after writing a crash dump on rx2620. 5.2.7.1 Problem Description: On rx2620 with System Firmware version 4.29, recursive bugcheck occurs in the last phase of shutdown, which results in a system hang. This issue is observed after a crash dump is written onto a disk. The following message is displayed on the console when the issue occurs: **** Recursive bugcheck after system halted. **** Use console to reset system. This problem has been fixed. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB 5.2.7.2 Quix and PTR cases reporting this problem: 5.2.7.2.1 Quix Cases QXCM1001149674 5.2.7.2.2 PTR(S) None Page 9 5.2.7.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.7.4 Work-arounds: None 5.2.8 Process loops in EXE$CRMPSC_PFN_64 and can't be deleted 5.2.8.1 Problem Description: Process could loop in EXE$CRMPSC_PFN_64 when it is overlaying an existing PFN mapped section and has a direct I/O outstanding. The process can not be stopped or deleted while it is stuck in this loop. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.8.2 Quix and PTR cases reporting this problem: 5.2.8.2.1 Quix Cases QXCM1001082239 QXCM1001171119 QXCM1001230187 5.2.8.2.2 PTR(S) 75-120-149 5.2.8.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.8.4 Work-arounds: None Page 10 5.2.9 Process hangs waiting for more BYTCNT quota. 5.2.9.1 Problem Description: A process could hang waiting for more byte count quota at an IPL that blocks AST delivery. By blocking AST delivery it also blocks the normal mechanism for returning more byte count quota to the process after the completion of an I/O. If the process also holds a file system lock this could result in a node or cluster hang. This problem has been fixed. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 5.2.9.2 Quix and PTR cases reporting this problem: 5.2.9.2.1 Quix Cases QXCM1001243088 5.2.9.2.2 PTR(S) None 5.2.9.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.9.4 Work-arounds: Providing sufficient BYTLM to the process, so it does not run low or out of BYTLM could avoid this potential issue. 5.2.10 Periodic clock updates can disrupt real time data collection Page 11 5.2.10.1 Problem Description: To maintain an accurate time across power failures or shutdowns, OpenVMS will update the hardware clock 4 times a day. Every 6 hours the hardware clock is synchronized with the current system time, EXE$GQ_SYSTIME. On some older Integrity systems (rx2600) this update can take 20-30 milliseconds to complete. If the system is collecting real-time data this work at high IPL could result in some data loss each time the clock is updated. To avoid this issue OpenVMS now allows control of the periodic update via the dynamic SYSGEN parameter TIME_CONTROL. Two previously unused bits (3 & 4) are being used to control the update behavior. The settings of bit 3 & 4 now cause Integrity based machines to update the hardware clock as follows: 00 - Update every 6 hours, current default behavior (value of 0) 01 - Update every 24 hours (TIME_CONTROL value of 8) 10 - Update every 30 days (value of 16 decimal) 11 - Never update (value of 24 decimal) Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 5.2.10.2 Quix and PTR cases reporting this problem: 5.2.10.2.1 Quix Cases QXCM1001267791 5.2.10.2.2 PTR(S) None 5.2.10.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 Page 12 5.2.10.4 Work-arounds: None 5.2.11 New bits added to SYSGEN parameter DUMPSTYLE. 5.2.11.1 Problem Description: Two bits have been added to the SYSGEN parameter DUMPSTYLE to help control what areas of memory are being written out to the SYSDUMP file. At this time OpenVMS Engineering does not recommend enabling these bits, but may recommend it under special circumstances. Bit 5 of DUMPSTYLE, KEY_ONLY, will dump only system space, active global pages, and current processes. Bit 6 of DUMPSTYLE, SKIP_S2, does not dump S2 system space to the dump file. If this bit is set anything in S2 space, like XFC Data, Lock Manager Dynamic memory, RMS Buffers, System diagnostic buffers (e.g.: TR buffer) will not be written to the dump file and analysis of the dump may be inconclusive without them. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB - [SYSLIB]SDA$SHARE.EXE - [SYS$LDR]SYS$BASE_IMAGE.EXE 5.2.11.2 Quix and PTR cases reporting this problem: 5.2.11.2.1 Quix Cases QXCM1001290315 5.2.11.2.2 PTR(S) None Page 13 5.2.11.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.11.4 Work-arounds: None 5.2.12 System crash with rare INVSECURESTATE bugcheck 5.2.12.1 Problem Description: System crashes with the following INVSECURESTATE and corruption of a nonpaged pool lookaside list associated with a RIGHTSLIST structure that has been doubly deallocated back to pool: Crashdump Summary Information: ------------------------------ Crash Time: 16-APR-2013 06:00:51.49 Bugcheck Type: INVSECURESTATE, Invalid state detected by SECURITY subsystem Node: NODE (Cluster) CPU Type: HP BL870c i2 (1.73GHz/6.0MB) VMS Version: V8.4 Current Process: Current Image: Failing PC: FFFFFFFF.80B44BD0 NSA$FREE_RIGHTS_CHAIN_C+00110 Failing PS: 00000000.00000000 Module: SECURITY (Link Date/Time: 3-SEP-2010 12:46:51.96) Offset: 0002C4D0 This problem has been fixed. Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.STB 5.2.12.2 Quix and PTR cases reporting this problem: Page 14 5.2.12.2.1 Quix Cases QXCM1001278957 5.2.12.2.2 PTR(S) None 5.2.12.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.12.4 Work-arounds: None 5.2.13 Adding time stamps during fork processing. 5.2.13.1 Problem Description: Diagnostic time stamps have been added when processing fork blocks to aid in diagnosing possible issues in CPUSPINWAIT bugchecks. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 5.2.13.2 Quix and PTR cases reporting this problem: 5.2.13.2.1 Quix Cases None 5.2.13.2.2 PTR(S) 75-74-312 Page 15 5.2.13.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.13.4 Work-arounds: None 5.2.14 Possible INCONSTATE booting Itanium satellite node from shadowed system disk. 5.2.14.1 Problem Description: If an Itanium satellite node boots from a shadowed system disk on which the BITMAP.SYS file has a ACE/ACL set, the boot could fail with an INCONSTATE bugcheck at or near SYS$VM+01E510. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.14.2 Quix and PTR cases reporting this problem: 5.2.14.2.1 Quix Cases QXCM1001259876 5.2.14.2.2 PTR(S) None 5.2.14.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.14.4 Work-arounds: Crash can be avoided by clearing ACE/ACL of BITMAP.SYS file. To delete all the ACLs on file BITMAP.SYS, use the below command: $ SET SECURITY/ACL/DELETE SYS$SYSDEVICE:[000000]BITMAP.SYS Page 16 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS84I_SYS patch kits can be found in the following files: o VMS84I_SYS-V0100.RELEASE_NOTES o VMS84I_SYS-V0200.RELEASE_NOTES o VMS84I_SYS-V0300.RELEASE_NOTES Before kit installation, these files can be extracted from the kit via the following commands: o To extract all release notes files at once use: PRODUCT EXTRACT RELEASE_NOTES VMS84I_SYS /VERSION=V4.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_SYS /VERSION=V4.0 - /SELECT=release_note_name[/DESTINATION=destination_directory] The names of individual RELEASE_NOTES files in the kit can be found with: PRODUCT LIST VMS84I_SYS /VERSION=V4.0 /SELECT = *.RELEASE_NOTES 7 FILES PATCHED OR REPLACED: o [SYS$LDR]EXCEPTION.EXE (new image) Image Identification Information Image name: "EXCEPTION" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:10.26 Overall Image Checksum: 73DA03CA o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information Image name: "EXCEPTION_MON" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:14.43 Overall Image Checksum: 73DA03CA Page 17 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information Image name: "IO_ROUTINES" Image file identification: "X-5" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:46:44.91 Overall Image Checksum: 4014A1B9 o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) Image Identification Information Image name: "IO_ROUTINES_MON" Image file identification: "X-5" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:46:54.53 Overall Image Checksum: 64A9BC9D o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) Image Identification Information Image name: "MESSAGE_ROUTINES" Image file identification: "X-5" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:47:00.72 Overall Image Checksum: 2E2247D9 o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information Image name: "PROCESS_MANAGEMENT" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:49.13 Overall Image Checksum: 2D5D83B3 o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) Image Identification Information Image name: "PROCESS_MANAGEMENT_MON" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:52.23 Overall Image Checksum: 249DF9C1 Page 18 o [SYSLIB]SDA$SHARE.EXE (new image) Image Identification Information Image name: "SDA$SHARE" Image file identification: "X-2" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:35.31 Overall Image Checksum: 923885A3 o [SYS$LDR]SECURITY.EXE (new image) Image Identification Information Image name: "SECURITY" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:08.39 Overall Image Checksum: 6A1C5EFE o [SYS$LDR]SECURITY_MON.EXE (new image) Image Identification Information Image name: "SECURITY_MON" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:13.48 Overall Image Checksum: F257F663 o [SYSEXE]SMISERVER.EXE (new image) Image Identification Information Image name: "SMISERVER" Image file identification: "X01-15" Image build identification: "0100000116" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2013 17:21:03.87 Overall Image Checksum: 98EBE88D o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) Image Identification Information Image name: "SYS$BASE_IMAGE" Image file identification: "IA64 XCFR-J2I" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:34:54.37 Overall Image Checksum: B56D23FF Page 19 o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information Image name: "SYS$VM" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:28.25 Overall Image Checksum: 6CF1C692 o [SYSEXE]SYSBOOT.EXE (new image) Image Identification Information Image name: "SYSBOOT" Image file identification: "X-154" Image build identification: "0100000111" linker identification: "Linker I02-37" Link Date/Time: 7-JUN-2013 10:39:11.71 Overall Image Checksum: 66AFDF80 o [SYSEXE]SYSGEN.EXE (new image) Image Identification Information Image name: "SYSGEN" Image file identification: "X-5" Image build identification: "0100000111" linker identification: "Linker I02-37" Link Date/Time: 7-JUN-2013 10:39:07.39 Overall Image Checksum: 23AD8BBC o [SYSEXE]SYSMAN.EXE (new image) Image Identification Information Image name: "SYSMAN" Image file identification: "X01-22" Image build identification: "0100000116" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2013 17:21:02.34 Overall Image Checksum: 83D4EA15 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information Image name: "SYSTEM_PRIMITIVES" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:50.35 Overall Image Checksum: D8B8A2A Page 20 o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) Image Identification Information Image name: "SYSTEM_PRIMITIVES_MIN" Image file identification: "X-5" Image build identification: "0100000117" linker identification: "Linker I02-37" Link Date/Time: 26-SEP-2013 14:38:55.87 Overall Image Checksum: 29DD9AD2 o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXCEPTION_MON.STB (new file) o [SYSEXE]I64VMS$PCSI_INSTALL_MIN.COM (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB (new file) o [SYS$LDR]MESSAGE_ROUTINES.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) o [SYS$LDR]SECURITY.STB (new file) o [SYS$LDR]SECURITY_MON.STB (new file) o [SYS$LDR]SYS$VM.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) 8 INSTALLATION INSTRUCTIONS 8.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 21 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. 8.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_SYS-V0400.ZIPEXE 8.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_SYS[/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. 8.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 22 o To avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT 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 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=V4.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_SYS-V0400 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_SYS/PRODUCER=HP/BASE=I64VMS/VER=V4.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 9 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 Page 23 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.