======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_SYS-V0600 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-V0500 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-V1000 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-V0600 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Wrong device name mentioned when deleting LTA port spooled to device 5.2.1.1 Problem Description: When an LTA port that is spooled to a device is deleted, its informational message displays that the spool device is being deleted instead of just the LTA port. This issue has been fixed. Images Affected: - [SYSLIB]LAT$SHR.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001213554 5.2.1.2.2 PTR(S) 75-126-264 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 Page 3 5.2.1.4 Work-arounds: None 5.2.2 "SDA> CLUE FRU" command doesn't populate the active CPU count. 5.2.2.1 Problem Description: When ELV translator is used to interpret the CLUE$FRU.SYS file generated by "SDA> CLUE FRU" command, the value of the field "Number of CPU"s in Active Set" shows up as zero. Images Affected: - [SYSLIB]CLUE$SDA.EXE 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases None 5.2.2.2.2 PTR(S) 75-130-65 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 Alignment faults in the SYS$UTC_SERVICES module. 5.2.3.1 Problem Description: Alignment faults in the SYS$UTC_SERVICES module occured during the DECnet communication. Images Affected: - [SYS$LDR]SYS$UTC_SERVICES.EXE Page 4 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1001315603 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 ERRFMT process stops after sending "ERRFMT - I bring you bad news..." 5.2.4.1 Problem Description: After installing OpenVMS, the ERRFMT process could stop after sending the email subject "ERRFMT - I bring you bad news...". It has been seen with DVD boots and some systems. Incorrect parameter passing in code was causing erroneous behavior such as dereferencing of unrelated process pages thereby resulting in ERRFMT mails or sometimes an ERRFMT process crash. This problem has been fixed. Images Affected: - [SYSEXE]ERRFMT.EXE 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases None Page 5 5.2.4.2.2 PTR(S) 75-120-1327 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 5.2.5 DELETE/TREE fails to delete directories 5.2.5.1 Problem Description: DELETE/TREE fails to delete directories even after having delete access via any needed ACLs. This issue has been fixed. Images Affected: - [SYSEXE]DELETE.EXE 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases QXCM1001327303 5.2.5.2.2 PTR(S) 75-116-563 75-126-398 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: None Page 6 5.2.6 VMSINSTAL.COM leaves VMSINSTAL$STATS process in LEF state 5.2.6.1 Problem Description: Issuing CTRL/Y during the product installation using VMSINSTAL.COM terminates the product installation with unexpected error and leaves the VMSINSTAL$STATS process in LEF state. This blocks any subsequent product installation. This issue has been fixed. Images Affected: - [SYSUPD]VMSINSTAL.COM 5.2.6.2 Quix and PTR cases reporting this problem: 5.2.6.2.1 Quix Cases QXCM1001338594 5.2.6.2.2 PTR(S) None 5.2.6.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.6.4 Work-arounds: None 5.2.7 Multithreaded JDBC process hangs trying to connect to Oracle Rdb (tm) when using V7.3 RDB$COSIP image 5.2.7.1 Problem Description: A multithreaded JDBC process hangs trying to connect to Oracle Rdb (tm) when using the V7.3 RDB$COSIP image. V7.3 RDB$COSIP uses SYS$ACMW for authentication and the ACME_SERVER process could end up in a compute loop waiting for the caller. This issue has been fixed. Page 7 Images Affected: - [SYS$LDR]ACME.EXE 5.2.7.2 Quix and PTR cases reporting this problem: 5.2.7.2.1 Quix Cases QXCM1001328821 5.2.7.2.2 PTR(S) 75-126-417 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 Fix timing window that can case process to hang 5.2.8.1 Problem Description: Under rare circumstances a process can end up looping in an AST routine trying to temporarily lock a page in memory (using the ATOMIC_WRITE_KEEP_IN_WS macro). If this AST interrupted other code that is using the same mechanism it can end up looping in this macro. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB Page 8 5.2.8.2 Quix and PTR cases reporting this problem: 5.2.8.2.1 Quix Cases QXCM1001395741 5.2.8.2.2 PTR(S) None 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 5.2.9 Fix SECURITY_RIGHTS packet leak 5.2.9.1 Problem Description: System crashed with CLUEXIT due to nonpaged pool exhaustion caused by leakage of SECURITY_RIGHTS packets. This issue is fixed. Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY_MON.STB 5.2.9.2 Quix and PTR cases reporting this problem: 5.2.9.2.1 Quix Cases QXCM1001352295 QXCM1001379259 Page 9 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: None 5.2.10 In OpenVMS version V8.4 rare cluster hang seen during system shutdown or boot up. 5.2.10.1 Problem Description: An OpenVMS V8.4 cluster hang has been seen occasionally during system shutdown or boot while using host-based mini-merge (HBMM) for the system disk shadow set, shared by multiple systems.This was occurring during a bitmap update operation when a write bitmap message got lost and the device remained in a write locked state. In OpenVMS V8.3-1H1 and in previous versions, master bitmap update messages were sent one at a time, updating each remote master bitmap sequentially. In OpenVMS V8.4, these remote master bitmap update operations were made parallel.We have reverted back the code that performs parallel bitmap updates to sequential. This problem has been fixed. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.STB 5.2.10.2 Quix and PTR cases reporting this problem: Page 10 5.2.10.2.1 Quix Cases QXCM1001274678 QXCM1001297622 QXCM1001307342 QXCM1001342943 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 5.2.10.4 Work-arounds: None. 5.2.11 Infoserver boot/installation process can hang 5.2.11.1 Problem Description: Infoserver boot/installation process can hang with "specified service unavailable error" even if service is available. Images Affected: - [SYS$LDR]SYS$DADDRIVER.EXE - [SYS$LDR]SYS$DADDRIVER.STB 5.2.11.2 Quix and PTR cases reporting this problem: 5.2.11.2.1 Quix Cases None 5.2.11.2.2 PTR(S) 75-72-69 Page 11 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 Process hang waiting for inner mode special kernel AST 5.2.12.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. This issue 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.12.2 Quix and PTR cases reporting this problem: 5.2.12.2.1 Quix Cases QXCM1001387681 5.2.12.2.2 PTR(S) 75-13-2368 5.2.12.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 Page 12 5.2.12.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: $ ANAL/SYSTEM SDA> SHOW PROCESS/CHANNEL ALL SDA> EXIT 5.2.13 OpenVMS V8.4 INCON_SCHED crash at EXE$INFORM_TM_AST_C+00730 5.2.13.1 Problem Description: Under rare conditions it is possible for the Inner Mode Semaphore ownership depth of a multi-threaded process to become out of synch during AST delivery, resulting in an INCON_SCHED bugcheck at EXE$INFORM_TM_AST_C+00730. This issue 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.13.2 Quix and PTR cases reporting this problem: 5.2.13.2.1 Quix Cases QXCM1001397583 QXCM1001344424 5.2.13.2.2 PTR(S) 75-126-434 5.2.13.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 Page 13 5.2.13.4 Work-arounds: None 5.2.14 OpenVMS running as a guest Operating system on HP Integrity fails to boot. 5.2.14.1 Problem Description: OpenVMS guest boot fails with image loading error messages as shown below. %VMS_LOADER-W-Warning: Unable to load file SYS$LOADABLE_IMAGES:SYS$NETWORK_SERVICES.EXE in CreateMemorydisk. Status = 0x124 This issue is fixed. Images Affected: - [SYS$LDR]SYS$MEMORYDISK.DAT 5.2.14.2 Quix and PTR cases reporting this problem: 5.2.14.2.1 Quix Cases None 5.2.14.2.2 PTR(S) PTR 75-130-40 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: None 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 Page 14 o VMS84I_SYS-V0300.RELEASE_NOTES o VMS84I_SYS-V0400.RELEASE_NOTES o VMS84I_SYS-V0500.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=V6.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_SYS /VERSION=V6.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=V6.0 /SELECT = *.RELEASE_NOTES 7 FILES PATCHED OR REPLACED: o [SYS$LDR]ACME.EXE (new image) Image Identification Information Image name: "ACME" Image file identification: "X-5" Image build identification: "0100000167" linker identification: "Linker I02-37" Link Date/Time: 29-MAY-2015 15:08:44.13 Overall Image Checksum: C3398391 o [SYSLIB]CLUE$SDA.EXE (new image) Image Identification Information Image name: "CLUE$SDA" Image file identification: "X-71" Image build identification: "0100000105" linker identification: "Linker I02-37" Link Date/Time: 12-APR-2013 11:44:16.65 Overall Image Checksum: FE673015 o [SYSEXE]DELETE.EXE (new image) Image Identification Information Image name: "DELETE" Page 15 Image file identification: "X-05" Image build identification: "0100000171" linker identification: "Linker I02-37" Link Date/Time: 3-JUL-2015 14:35:01.12 Overall Image Checksum: AF6469D6 o [SYSEXE]ERRFMT.EXE (new image) Image Identification Information Image name: "ERRFMT" Image file identification: "X-23" Image build identification: "0100000128" linker identification: "Linker I02-37" Link Date/Time: 27-FEB-2014 17:06:12.25 Overall Image Checksum: 2E07C213 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 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information Image name: "IO_ROUTINES" Image file identification: "X-5" Image build identification: "0100000167" linker identification: "Linker I02-37" Link Date/Time: 29-MAY-2015 15:08:58.90 Overall Image Checksum: 6E92E186 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: "0100000167" Page 16 linker identification: "Linker I02-37" Link Date/Time: 29-MAY-2015 15:09:12.16 Overall Image Checksum: CEAB8D9B o [SYSLIB]LAT$SHR.EXE (new image) Image Identification Information Image name: "LAT$SHR" Image file identification: "LAT$SHR V2.0" Image build identification: "0100000129" linker identification: "Linker I02-37" Link Date/Time: 24-MAR-2014 13:38:58.25 Overall Image Checksum: 36446126 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: "0100000167" linker identification: "Linker I02-37" Link Date/Time: 29-MAY-2015 15:09:48.63 Overall Image Checksum: 385F616A 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: "0100000167" linker identification: "Linker I02-37" Link Date/Time: 29-MAY-2015 15:09:56.85 Overall Image Checksum: CEF11C9D o [SYSLIB]SDA$SHARE.EXE (new image) Image Identification Information Image name: "SDA$SHARE" Image file identification: "X-2" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:53:48.72 Page 17 Overall Image Checksum: 2389685D o [SYS$LDR]SECURITY.EXE (new image) Image Identification Information Image name: "SECURITY" Image file identification: "X-5" Image build identification: "0100000167" linker identification: "Linker I02-37" Link Date/Time: 29-MAY-2015 15:07:54.55 Overall Image Checksum: BD5291B5 o [SYS$LDR]SECURITY_MON.EXE (new image) Image Identification Information Image name: "SECURITY_MON" Image file identification: "X-5" Image build identification: "0100000167" linker identification: "Linker I02-37" Link Date/Time: 29-MAY-2015 15:08:18.91 Overall Image Checksum: 88775F95 o [SYSEXE]SMISERVER.EXE (new image) Image Identification Information Image name: "SMISERVER" Image file identification: "X01-15" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:53:55.06 Overall Image Checksum: B3A64ED o [SYS$LDR]SWIS$DEBUG.EXE (new image) Image Identification Information Image name: "SWIS$DEBUG" Image file identification: "X-5" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:55:31.00 Overall Image Checksum: 6B25B3D6 o [SYSLIB]SWIS$SDA.EXE (new image) Image Identification Information Image name: "SWIS$SDA" Image file identification: "X-2A1" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:55:33.15 Overall Image Checksum: 81C15147 Page 18 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: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:29:41.12 Overall Image Checksum: 8358BD5D o [SYS$LDR]SYS$DADDRIVER.EXE (new image) Image Identification Information Image name: "SYS$DADDRIVER" Image file identification: "X-5" Image build identification: "0100000169" linker identification: "Linker I02-37" Link Date/Time: 12-JUN-2015 15:38:37.57 Overall Image Checksum: 72EF0DAC o [SYS$LDR]SYS$UTC_SERVICES.EXE (new image) Image Identification Information Image name: "SYS$UTC_SERVICES" Image file identification: "DTSS T0.0-000" Image build identification: "0100000126" linker identification: "Linker I02-37" Link Date/Time: 24-JAN-2014 10:33:28.01 Overall Image Checksum: 1CD4B7DC o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information Image name: "SYS$VM" Image file identification: "X-5" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:54:45.90 Overall Image Checksum: 3E175CF2 o [SYSEXE]SYSBOOT.EXE (new image) Image Identification Information Image name: "SYSBOOT" Image file identification: "X-154" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:53:50.20 Overall Image Checksum: 22B8B7B1 Page 19 o [SYSEXE]SYSGEN.EXE (new image) Image Identification Information Image name: "SYSGEN" Image file identification: "X-5" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:53:48.59 Overall Image Checksum: 4F07F1F9 o [SYSEXE]SYSMAN.EXE (new image) Image Identification Information Image name: "SYSMAN" Image file identification: "X01-22" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:53:48.93 Overall Image Checksum: AA73A266 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information Image name: "SYSTEM_PRIMITIVES" Image file identification: "X-5" Image build identification: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:55:20.11 Overall Image Checksum: 341149A3 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: "0100000141" linker identification: "Linker I02-37" Link Date/Time: 17-SEP-2014 16:55:32.88 Overall Image Checksum: A2038794 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) Page 20 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]SWIS$DEBUG.STB (new file) o [SYS$LDR]SYS$DADDRIVER.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) o [SYSUPD]VMSINSTAL.COM (new file) o [SYS$LDR]SYS$MEMORYDISK.DAT (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. 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. Page 21 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-V0600.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 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 Page 22 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=V6.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_SYS-V0600 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=V6.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2015 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 Page 23 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.