Kit Name: DEC-AXPVMS-VMS732_SYS-V1300--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V7.3-2 Approximate Kit Size: 8903 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - rolling reboot Superseded Kits: VMS732_SYS-V1200 Mandatory Kit Dependencies: VMS732_UPDATE-V1100 or later VMS732_PCSI-V0300 or later Optional Kit Dependencies: None. Checksums: VMS732_SYS-V1300.ZIPEXE Checksum: 1999208580 DEC-AXPVMS-VMS732_SYS-V1300--4.PCSI$COMPRESSED Checksum: 1678635305 VMS732_SYS-V1300.ZIPEXE MD5 Checksum: 4A190FE7D6CB11E3C3364897D71A08C9 DEC-AXPVMS-VMS732_SYS-V1300--4.PCSI$COMPRESSED MD5 Checksum: 433AE2CA1634E6924BAD29FEC4351A3A ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS732_SYS-V1300 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 ALPHA V7.3-2 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - VMS732_SYS-V1200 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS732_PCSI-V0300 - VMS732_UPDATE-V1100 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 VMS732_SYS-V1300 KIT 5.1 New functionality addressed in this kit Not Applicable. 5.2 Problems addressed in this kit 5.2.1 VMS732_SYS-V1200 Patch Kit Release Notes Incorrect 5.2.1.1 Problem Description: The release notes shipped with the VMS732_SYS-V1200 patch kit included a description of a new $GETDVI item code and an associated requirement to install the VMS732_DCL-V0800 patch kit. This description is not applicable to OpenVMS V7.3-2 and has been removed. Images Affected: - None. 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) None. 5.2.1.2.2 QAR(s) None. 5.2.1.3 Problem Analysis: See problem description. Page 3 5.2.1.4 Release Version of OpenVMS that will contain this change: Not applicable. 5.2.1.5 Work-arounds: None. 5.2.2 Memory Does Not Get Dumped 5.2.2.1 Problem Description: When writing a full dump, if there are exactly 32 physical memory fragments, BUGCHECK zeroes the memory map at the wrong time and no memory gets dumped. If bit 1 in SYSGEN parameter DUMPSTYLE is set (verbose console output), there will be repeated messages of the form: "** Dumping unknown memory (PFN range 00000000.00000000 to FFFFFFFF.FFFFFFFF)... The resulting dump will be is unreadable; SDA reports "%SDA-F-DUMPINCOMPL, the dump file write was not completed". Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) None. 5.2.2.2.2 QAR(s) 75-118-64 Page 4 5.2.2.3 Problem Analysis: See problem description. 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.2.5 Work-arounds: None. 5.2.3 Possible System Crash 5.2.3.1 Problem Description: The system can crash when either a tape or a disk in mount verification is dismounted. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) None. 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: A register was not preserved. Page 5 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.3.5 Work-arounds: None. 5.2.4 System Crash in NSA$SIZE_NSAB 5.2.4.1 Problem Description: The system can crash in NSA$SIZE_NSAB if certain bad data is included in the item list to $AUDIT_EVENT, or if the item list is not terminated. Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY_MON.STB 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) None. 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: See problem description. 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 Page 6 5.2.4.5 Work-arounds: None. 5.2.5 INVEXCEPTN SCH$POSTEF_SCHED Bugcheck 5.2.5.1 Problem Description: On multithreaded process, the system can crash with an "INVEXCEPTN SCH$POSTEF_SCHED" bugcheck. 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.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) QXCM1000385036,WFM1213687533-121 5.2.5.2.2 QAR(s) None. 5.2.5.3 Problem Analysis: The INVEXCEPTN bugcheck occurs when the code tries to queue PCB$L_POSTEF_ACB to a multithreaded process (with upcalls enabled) before the field has been completely set up (and is still 0). 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.5.5 Work-arounds: None. Page 7 5.2.6 Audit Server Hang 5.2.6.1 Problem Description: In rare circumstances, and during times of heavy event auditing, the system can hang. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 5.2.6.2 CLDs, and QARs reporting this problem: 5.2.6.2.1 CLD(s) QXCM1000361205,WFM3215964188-325 5.2.6.2.2 QAR(s) None. 5.2.6.3 Problem Analysis: The Audit_Server process can hang waiting for the I/O Mutex being held by another process that is deleting a device and trying to write the deletion event into the Audit_Server's full mailbox. 5.2.6.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.6.5 Work-arounds: Avoid auditing of device creation and deletion activies. 5.2.7 F$DEVICE Searches Can Take a Long Time Page 8 5.2.7.1 Problem Description: The lexical function F$DEVICE (and by extension, the system service SYS$DEVICE_SCAN) can be used with a wild card device specification to return the names of all devices on a system. The use of matching device classes and device types can be used to limit the output to those devices matching either of those criteria. In the case of a system with a large number of network or mailbox devices, a wildcard search for all disk devices can take a very long time. This change optimizes the searching logic to skip over long lists of non-matching devices. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 5.2.7.2 CLDs, and QARs reporting this problem: 5.2.7.2.1 CLD(s) QXCM1000337994;WFM3214812945-326 5.2.7.2.2 QAR(s) None. 5.2.7.3 Problem Analysis: See problem description. 5.2.7.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.7.5 Work-arounds: None. Page 9 5.2.8 Process Hang 5.2.8.1 Problem Description: Occasionally a process will hang in RMS rundown at IPL 2, waiting for a blocked AST to complete. If the process also holds a lock, other processes on the system may hang waiting for the lock to be released. Images Affected: - [SYS$LDR]SYSLDR_DYN.EXE - [SYS$LDR]SYSLDR_DYN.STB 5.2.8.2 CLDs, and QARs reporting this problem: 5.2.8.2.1 CLD(s) QXCM1000359860,WFM3215439147-323 5.2.8.2.2 QAR(s) None. 5.2.8.3 Problem Analysis: SYSDELPRC invokes the user rundown routines and expects to be returned to at IPL 0. However, at return, the IPL is 2. 5.2.8.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.8.5 Work-arounds: None. 5.2.9 MC SYSMAN IO AUTOCONFIGURE System Crash Page 10 5.2.9.1 Problem Description: When the MPDEV_POLLER and MPDEV_D3 sysgen parameters are set, the system can crash when an "MC SYSMAN IO AUTOCONFIGURE" command is issued. Images Affected: - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB - [SYS$LDR]MULTIPATH_MON.EXE - [SYS$LDR]MULTIPATH_MON.STB 5.2.9.2 CLDs, and QARs reporting this problem: 5.2.9.2.1 CLD(s) QXCM1000369587 5.2.9.2.2 QAR(s) None. 5.2.9.3 Problem Analysis: The MPDEV_FLUSH code ( mpdev$get_next_flush_candidate) looks through the IODB and selects UCB only if the UCB matches the following criteria: o UCB must not be marked MNTVERIP o UCB must not be foreign mounted o Primary UCB must not be marked pathverip For each UCB that is selected, the MPDEV_FLUSH code (mpdev$do_next_flush_io) queues the IRP (IO$_FLUSH_ERROR) into UCB$Q_DK_IRP_LIST for error flushing. The MPDEV_FLUSH code queued the IO$_FLUSH_ERROR IRP into a UCB that was not fully configured. 5.2.9.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 Page 11 5.2.9.5 Work-arounds: None. 5.2.10 Unable to Delete Global Section with Bad Page 5.2.10.1 Problem Description: Occasionally a global section gets stuck on the delete pending list and is never deleted. This can occur if, sometime in the past, an I/O error occurred trying to write out the section and, because of this, it had a page placed onto the bad page list. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.10.2 CLDs, and QARs reporting this problem: 5.2.10.2.1 CLD(s) QXCM1000192113 5.2.10.2.2 QAR(s) None. 5.2.10.3 Problem Analysis: See problem description. 5.2.10.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.10.5 Work-arounds: None. Page 12 5.2.11 Performance Improvement 5.2.11.1 Problem Description: With this change, customers running very busy systems with a high demand zero page fault rate will see improved performance. 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.11.2 CLDs, and QARs reporting this problem: 5.2.11.2.1 CLD(s) None. 5.2.11.2.2 QAR(s) None. 5.2.11.3 Problem Analysis: The idle loop in the OpenVMS Scheduler performs a function known as page zeroing. When a demand zero page fault occurs, if a pre-zeroed page already exists, then the page fault can be handled much faster since the zeroing of the page does not need to occur as part of the pagefault. The idle loop had been assigning time slices to zero pages to avoid all CPUs performing this function concurrently. On a large system, without much idle CPU time, this may result in the page zeroing occurring very slowly. For non-Rad based systems, the idle loop will no longer time slice the page zeroing function. This will allow any idle CPU to perform page zeroing if idle. The goal here is to increase the rate at which pages can be zeroed. Page 13 5.2.11.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.11.5 Work-arounds: None. 5.2.12 System Crash with CLUEXIT Bugcheck 5.2.12.1 Problem Description: In an OpenVMS Cluster, there is the potential for lock manager $DEQ ALL operations to overwhelm another node in the cluster with DEQ messages. When this occurs, it is possible that either the cluster connections will break and reform or that a system may crash with a CLUEXIT bug check. Images Affected: - [SYS$LDR]LOCKING.EXE - [SYS$LDR]LOCKING.STB - [SYS$LDR]SYS$CLUSTER.EXE - [SYS$LDR]SYS$CLUSTER.STB - [SYS$LDR]SYS$CLUSTER_MON.EXE - [SYS$LDR]SYS$CLUSTER_MON.STB 5.2.12.2 CLDs, and QARs reporting this problem: 5.2.12.2.1 CLD(s) None. 5.2.12.2.2 QAR(s) 70-3-8878,QXCM1000360250,WFM3215947250-321 5.2.12.3 Problem Analysis: See problem description. Page 14 5.2.12.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.12.5 Work-arounds: None. 5.2.13 System Crash with INVSECURESTATE Bugcheck 5.2.13.1 Problem Description: The system can crash with an INVSECURESTATE bugcheck. 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 CLDs, and QARs reporting this problem: 5.2.13.2.1 CLD(s) QXCM1000369887 5.2.13.2.2 QAR(s) None. 5.2.13.3 Problem Analysis: Inside EXE$KTHREAD_DELETE_SELF, there was no call to synchronize the PSBs in use and operate on the correct PSB. 5.2.13.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 Page 15 5.2.13.5 Work-arounds: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS732_SYS ECO kits can be found in the following files: o VMS732_SYS-V100.RELEASE_NOTES o VMS732_SYS-V200.RELEASE_NOTES o VMS732_SYS-V300.RELEASE_NOTES o VMS732_SYS-V400.RELEASE_NOTES o VMS732_SYS-V500.RELEASE_NOTES o VMS732_SYS-V600.RELEASE_NOTES o VMS732_SYS-V700.RELEASE_NOTES o VMS732_SYS-V800.RELEASE_NOTES o VMS732_SYS-V900.RELEASE_NOTES o VMS732_SYS-V1000.RELEASE_NOTES o VMS732_SYS-V1100.RELEASE_NOTES o VMS732_SYS-V1200.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 VMS732_SYS/VERSION= - /DESTINATION= destination_directory o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS732_SYS/VERSION= V13.0 - /SELECT=[SYSUPD]release_note_name/DESTINATION=destination_directory 7 FILES PATCHED OR REPLACED: o [SYS$LDR]EXCEPTION.EXE (new image) Image Identification Information Page 16 image name: "EXCEPTION" image file identification: "X-4" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:40.30 linker identification: "A11-50" Overall Image Checksum: 2332477990 o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information image name: "EXCEPTION_MON" image file identification: "X-4" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:40.85 linker identification: "A11-50" Overall Image Checksum: 4030391921 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information image name: "IO_ROUTINES" image file identification: "X-4" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:46.27 linker identification: "A11-50" Overall Image Checksum: 3320538417 o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) Image Identification Information image name: "IO_ROUTINES_MON" image file identification: "X-4" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:47.71 linker identification: "A11-50" Overall Image Checksum: 3804679693 o [SYS$LDR]LOCKING.EXE (new image) Image Identification Information image name: "LOCKING" image file identification: "X-4" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:49.17 linker identification: "A11-50" Overall Image Checksum: 782040179 o [SYS$LDR]MULTIPATH.EXE (new image) Image Identification Information image name: "MULTIPATH" image file identification: "X-4" Page 17 image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:51.96 linker identification: "A11-50" Overall Image Checksum: 3563535049 o [SYS$LDR]MULTIPATH_MON.EXE (new image) Image Identification Information image name: "MULTIPATH_MON" image file identification: "X-4" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:52.34 linker identification: "A11-50" Overall Image Checksum: 1124153403 o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT" image file identification: "X-4" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:08.34 linker identification: "A11-50" Overall Image Checksum: 3374199883 o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT_MON" image file identification: "X-4" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:14.39 linker identification: "A11-50" Overall Image Checksum: 3628092181 o [SYS$LDR]SECURITY.EXE (new image) Image Identification Information image name: "SECURITY" image file identification: "X-7" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:19.96 linker identification: "A11-50" Overall Image Checksum: 3051755837 o [SYS$LDR]SECURITY_MON.EXE (new image) Image Identification Information image name: "SECURITY_MON" image file identification: "X-7" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:21.79 Page 18 linker identification: "A11-50" Overall Image Checksum: 901013509 o [SYS$LDR]SYS$CLUSTER.EXE (new image) Image Identification Information image name: "SYS$CLUSTER" image file identification: "X-4" image file build identification: "XBCV-0060111007" link date/time: 29-NOV-2006 10:14:40.57 linker identification: "A11-50" Overall Image Checksum: 524108919 o [SYS$LDR]SYS$CLUSTER_MON.EXE (new image) Image Identification Information image name: "SYS$CLUSTER_MON" image file identification: "X-4" image file build identification: "XBCV-0060111007" link date/time: 29-NOV-2006 10:14:41.70 linker identification: "A11-50" Overall Image Checksum: 1278214544 o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information image name: "SYS$VM" image file identification: "X-4" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:35.51 linker identification: "A11-50" Overall Image Checksum: 3929678652 o [SYS$LDR]SYSLDR_DYN.EXE (new image) Image Identification Information image name: "SYSLDR_DYN" image file identification: "X-4" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:07.54 linker identification: "A11-50" Overall Image Checksum: 2239531815 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES" image file identification: "X-4" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:20.65 linker identification: "A11-50" Overall Image Checksum: 2718132510 Page 19 o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES_MIN" image file identification: "X-4" image file build identification: "XBEQ-0060111060" link date/time: 2-FEB-2007 08:31:16.20 linker identification: "A11-50" Overall Image Checksum: 2308316750 o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXCEPTION_MON.STB (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB (new file) o [SYS$LDR]LOCKING.STB (new file) o [SYS$LDR]MULTIPATH.STB (new file) o [SYS$LDR]MULTIPATH_MON.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$CLUSTER.STB (new file) o [SYS$LDR]SYS$CLUSTER_MON.STB (new file) o [SYS$LDR]SYS$VM.STB (new file) o [SYS$LDR]SYSLDR_DYN.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) 8 INSTALLATION INSTRUCTIONS Page 20 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. 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 VMS732_SYS-V1300.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 VMS732_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. Page 21 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 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=DEC/BASE=AXPVMS/VER=V13.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS732_SYS-V1300 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS732_SYS/PRODUCER=DEC/BASE=AXPVMS/VER=V13.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! Page 22 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2007 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, 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.