======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_SYS-V0300 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-V0200 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-V0300 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Process may hang during stack expansion and may not respond to STOP/ID command 5.2.1.1 Problem Description: Under certain conditions, when a process"s user stack is filled up and cannot be expanded any further, the process hangs. It cannot be killed using STOP/ID command or force image exit. 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.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001139830 5.2.1.2.2 PTR(S) 75-126-160 Page 3 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 Missing Audit logs for user with "AUDIT" flag set in SYSUAF.DAT 5.2.2.1 Problem Description: The "AUDIT" flag can be set for a user in SYSUAF.DAT to audit user activity. Some of the expected audit events were not getting logged, such as file opens. This fix addresses this problem. Note: As a side effect of this fix, the number of audit entries generated can increase if users have the "AUDIT" flag set in their SYSUAF.DAT record. Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.STB 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1001014184 5.2.2.2.2 PTR(S) 75-13-2471 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: None 5.2.3 Incorrect item codes to SYS$GETDVI or LIB$GETDVI could cause erroneous behavior 5.2.3.1 Problem Description: The system service has been corrected to properly check item code boundary conditions. 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.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1001210972 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 System services $GET_SECURITY and $SET_SECURITY fail with %RMS-F-SYN error for files with long Unicode names Page 5 5.2.4.1 Problem Description: On an ODS-5 volume, filenames can be up to 118 Unicode characters long by OpenVMS Extended File Specifications. $GET_SECURITY and $SET_SECURITY fail with %RMS-F-SYN error if the input object class is FILE and the object name is a filename with more than 40 Unicode characters. The code has been modified to accommodate long unicode names. 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.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-13-2424 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 F$DEVICE does not display TNA devices having unit number greater than 32767 Page 6 5.2.5.1 Problem Description: The code has been modified to display TNA devices having unit number greater than 32767. 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.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases QXCM1001215206 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 Integrity after V8.4 5.2.5.4 Work-arounds: None 5.2.6 Do not wait if SYS$UPDSEC_64W causes no I/O to be issued 5.2.6.1 Problem Description: An Oracle "PQ Slave process" occasionally hangs in LEF state. If SYS$UPDSEC_64W is called to update a global section, but no writes are necessary (because the section pages have not changed, or are part of a reserved memory section, etc), the system service was waiting indefinitely assuming an I/O was issued. Now if the system service returns SS$_NOMODIFIED we know no I/O was issued for the request and can return immediately to the caller. Page 7 Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.6.2 Quix and PTR cases reporting this problem: 5.2.6.2.1 Quix Cases QXCM1001229399 5.2.6.2.2 PTR(S) 75-13-2393, 75-126-276 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 Intermittent hang of multithreaded application 5.2.7.1 Problem Description: Multithreaded application hangs intermittently with most of the threads waiting for inner mode semaphore. The hang was because of race condition while updating a global data structure. This fix resolves the race condition which led to this hang. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB Page 8 5.2.7.2 Quix and PTR cases reporting this problem: 5.2.7.2.1 Quix Cases QXCM1001204927, QXCM1001186742 5.2.7.2.2 PTR(S) None 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 INSQxIL and REMQxIL routines fails with ROPRAND fault 5.2.8.1 Problem Description: This kit fixes a ROPRAND fault returned by INSQxIL and REMQxIL routines. This issue can occur if the header and entry being manipulated are in different address spaces (such as P0 and S0). This problem has been fixed. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB 5.2.8.2 Quix and PTR cases reporting this problem: 5.2.8.2.1 Quix Cases QXCM1001206425 Page 9 5.2.8.2.2 PTR(S) 75-13-2531 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: Use the quadword queuing instructions 5.2.9 System crash involving packets beyond the normal end of nonpaged pool 5.2.9.1 Problem Description: On rare occasions nonpaged pool expansion on multiprocessor systems could result in nonpaged pool extending beyond its NPAGEVIR limit. This could result in packets overlapping the Pool Ring History buffer, thereby leading to nonpaged pool related bugchecks. The timing window in the nonpaged pool expansion routine has been closed. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE 5.2.9.2 Quix and PTR cases reporting this problem: 5.2.9.2.1 Quix Cases QXCM1001198846 5.2.9.2.2 PTR(S) 75-126-259 Page 10 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: Increasing the size of nonpaged pool values for NPAGEDYN and NPAGEVIR so nonpaged pool will not have to expand to the maximum value will work around this potential problem. 5.2.10 System crash with FILCNTNONZ bugcheck 5.2.10.1 Problem Description: This is a workaround to avoid the FILCNTNONZ bugcheck. A FILCNTNONZ bugcheck can occur during process rundown because a channel was left assigned to the process. Rather than forcing a crash for this relatively rare occurrence, change the process name to FILCNTNONZ_xxx (saving the original name on the stack), lower its process priority to 0, and place it in a RWAST wait state to lessen its impact on the system. A reboot will need to be scheduled sometime in the future to clear out any processes stuck in this state. 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.10.2 Quix and PTR cases reporting this problem: 5.2.10.2.1 Quix Cases QXCM1001188471 5.2.10.2.2 PTR(S) None Page 11 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 $GETTIM_PREC() returns time lower than that returned by a preceding call 5.2.11.1 Problem Description: In certain scenarios, the time returned by $GETTIM_PREC() is less than that returned by a preceding call. This can be seen when the system service was called successively in a tight loop. This problem has been fixed. Images Affected: - [SYS$LDR]MESSAGE_ROUTINES.STB - [SYS$LDR]MESSAGE_ROUTINES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE 5.2.11.2 Quix and PTR cases reporting this problem: 5.2.11.2.1 Quix Cases QXCM1001194533 5.2.11.2.2 PTR(S) 75-126-289 Page 12 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 In rare conditions, the process might crash while handling multiple signals from within itself or from other processes 5.2.12.1 Problem Description: The process might crash if a signal is raised from within or sent from another process, when it is currently processing another signal or exception. 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 - [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 QXCM1001155018, QXCM1000994840, QXCM1001166426 5.2.12.2.2 PTR(S) None Page 13 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 Intermittent INVEXCEPTN and INCONMMGST bugchecks 5.2.13.1 Problem Description: Systems mapping global sections to reserved memory could experience memory management related bugchecks when deleting a region or RMS global buffers after the installation of the following kits: - VMS83I_SYS-V1900 or VMS83I_UPDATE-V1600 or VMS83I_UPDATE-V1700 - VMS831H1I_SYS-V1600 or VMS831H1I_UPDATE-V1200 or VMS831H1I_UPDATE-V1300 - VMS84I_SYS-V0200 or VMS84I_UPDATE-V0700 or VMS84I_UPDATE-V0800 The problem can manifest itself as an INVEXCEPTN or an INCONMMGST bugcheck at different locations in the code. The possible failing PCs for different versions of OpenVMS are as given below. - INVEXCEPTN bugcheck at SYS$VM+63E20 (V8.3-1H1) - INVEXCEPTN bugcheck at SYS$VM+62E30 (V8.4) - INCONMMGST bugcheck at PROCESS_MANAGEMENT+9EC00 (V8.3-1H1) - INCONMMGST bugcheck at PROCESS_MANAGEMENT+92270 (V8.4 + side built SYS$VM image dated 25-SEP-2012) - INCONMMGST bugcheck at SYS$VM+64BB0 (V8.4) This issue is fixed now. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.13.2 Quix and PTR cases reporting this problem: Page 14 5.2.13.2.1 Quix Cases QXCM1001229469, QXCM1001233544, QXCM1001236248, QXCM1001240650, QXCM1001241634, QXCM1001246146, QXCM1001246762, QXCM1001247907 5.2.13.2.2 PTR(S) 75-72-65 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: Setting bit 4 in SYSGEN parameter MMG_CTLFLAGS will set OpenVMS IA64 to use smaller granularity hint regions, and avoids the code triggering the issue. 5.2.14 AUDIT_SERVER SSRVEXCEPT crash in IO_ROUTINES+E0300 5.2.14.1 Problem Description: A timing window existed in which the AUDIT_SERVER could end up trying to access a Volume Control Block (VCB) that is no longer valid. 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.14.2 Quix and PTR cases reporting this problem: Page 15 5.2.14.2.1 Quix Cases QXCM1001180606 5.2.14.2.2 PTR(S) 75-126-196 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 5.2.15 Adding a boot option fails while executing I64VMS$PCSI_INSTALL_MIN.COM 5.2.15.1 Problem Description: Adding a boot options by executing I64VMS$PCSI_INSTALL_MIN.COM on OpenVMS Itanium systems, fails with the following message: efi$bcfg: Device dkc500: is not found or not local. Status = 3 efi$bcfg: Unable to execute the Add Option. Status = 3 This issue has been fixed. Images Affected: - [SYSEXE]I64VMS$PCSI_INSTALL_MIN.COM 5.2.15.2 Quix and PTR cases reporting this problem: 5.2.15.2.1 Quix Cases QXCM1001173893 5.2.15.2.2 PTR(S) None Page 16 5.2.15.3 Release Version of OpenVMS that will contain this change: Next Release of OpenVMS Integrity after V8.4 5.2.15.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 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=V3.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_SYS /VERSION=V3.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=V3.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: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:46:30.82 Overall Image Checksum: E233484A Page 17 o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information Image name: "EXCEPTION_MON" Image file identification: "X-5" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:46:32.38 Overall Image Checksum: E233484A 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: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:47:04.10 Overall Image Checksum: 12315F35 Page 18 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: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:47:09.00 Overall Image Checksum: 88D788FD o [SYS$LDR]SECURITY.EXE (new image) Image Identification Information Image name: "SECURITY" Image file identification: "X-5" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:46:30.90 Overall Image Checksum: D02A81BE o [SYS$LDR]SECURITY_MON.EXE (new image) Image Identification Information Image name: "SECURITY_MON" Image file identification: "X-5" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:46:36.07 Overall Image Checksum: 30488399 o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information Image name: "SYS$VM" Image file identification: "X-5" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:46:59.41 Overall Image Checksum: 5D9D6EB0 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information Image name: "SYSTEM_PRIMITIVES" Image file identification: "X-5" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:47:09.29 Overall Image Checksum: F1723F48 Page 19 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: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:47:12.36 Overall Image Checksum: 941CFB4B 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]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) o [SYSEXE]I64VMS$PCSI_INSTALL_MIN.COM (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 20 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-V0300.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 21 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=V3.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_SYS-V0300 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=V3.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 22 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.