======================================================================= VMS Software, Inc. OpenVMS ECO Kit Release Notes ======================================================================= 1 KIT NAME: VMS842L3I_MISC-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3: To be installed by customers experiencing the problems described in this document. This kit contains fixes for several unrelated issues that could affect your system. None of these are high priority items by themselves and they are all low risk changes to the system. They are grouped together in one patch kit to provide simplified installation. None of these fixes require a system reboot. This installation rating serves as a guide to which customers should apply this remedial kit. Reference the attached Disclaimer of Warranty and Limitation of Liability Statement. 2.2 Reboot Requirement: No reboot is necessary after installation of this kit. However there are additional steps that must be performed after installation. Refer to Section 8.3, "Special Installation Instructions", for required post-installation actions. 2.3 Version(s) of VSI OpenVMS to which this kit may be applied: VSI OpenVMS for Integrity Servers V8.4-1H1 VSI OpenVMS for Integrity Servers V8.4-2 VSI OpenVMS for Integrity Servers V8.4-2L1 VSI OpenVMS for Integrity Servers V8.4-2L3 The images and files in this kit apply to any of these VSI OpenVMS versions. Because patch kits are removed by PCSI during upgrades to newer OpenVMS versions, the kit will need to be reinstalled if an upgrade is done from an older listed version to any newer listed version. 3 KITS SUPERSEDED BY THIS KIT: None 4 KIT DEPENDENCIES: The following patch kits must be installed prior to installing this kit. If installing on V8.4-1H1: VMS841H1I_NOTARY-V0200 VMS841H1I_FILESYS-V0100 VMS841H1I_UTILITY-V0200 If installing on V8.4-2: VMS842I_NOTARY-V0200 VMS842I_FILESYS-V0100 VMS842I_UTILITY-V0200 If installing on V8.4-2L1: VMS842L1I_UPDATE-V0100 VMS842L1I_FILESYS-V0100 VMS842L1I_UTILITY-V0200 If installing on V8.4-2L3: VMS842L3I_FILESYS-V0100 VMS842L3I_UTILITY-V0200 5 PROBLEMS ADDRESSED IN THIS KIT 5.1 DIRECTORY with minimum size selection ignores files larger than 1TB 5.1.1 Problem Description The command DIRECTORY/SELECT=SIZE=MINIMUM=1 does not display files larger than 1TB. This was due to an incorrect signed comparison which interpreted very large file sizes as negative. The issue is corrected with this patch kit. 5.1.2 Images and/or Files Affected: [SYSEXE]DIRECTORY.EXE 5.1.3 VSI case identifier Jira BO-1562 5.1.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.2 UCM Server connect failure or hang after extended use 5.2.1 Problem Description The USB$UCM_SERVER process leaks process I/O channels and locks. These leaks eventually result in command failures or hangs. Applications or command procedures using USB devices will eventually fail with the error: %USB-E-NOSERVER, Unable to connect to the UCM Server Subsequent UCM SHOW commands will likely hang. The command: $ UCM RESTART can be used to restart the server. The leaks have been corrected with this patch kit. 5.2.2 Images and/or Files Affected: [SYSEXE]USB$UCM_SERVER.EXE 5.2.3 VSI case identifier Jira BO-1516 Netsuite NS6161 5.2.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.3.5 Workaround Use the UCM RESTART command at regular intervals of little or no USB activity to release the leaked resources and start a new server incarnation. 5.3 PRODUCT INSTALL may spuriously terminate operation 5.3.1 Problem Description The PRODUCT INSTALL command may spuriously terminate product or patch kit installation. This occurs on rare circumstances, but could be repeatable for a particular kit which encounters the behavior. With no apparent errors or reason, the installation may fail with the message: %PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition Note that this message is the behavior from PCSI when a kit installation is purposely terminated by user command or other errors encountered by the kit. In those cases this message is correct and expected. The failure behavior is from an internal procedural mismatch which gives no warning or other explanation of the failure. The issue is corrected with this patch kit. 5.3.2 Images and/or Files Affected: [SYSEXE]PCSI$MAIN.EXE 5.3.3 VSI case identifier Jira UT-176 Bugzilla BZ4513 5.3.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.4 The XFC extension for SDA may not display all file headers 5.4.1 Problem Description Using the following command from the SDA XFC extension may fail to display a file header as it displays the relevant information: SDA> XFC SHOW FILE /BRIEF /OPEN The routine which displays the file information did not always detect it had switched to a new and different disk volume, and in such circumstances would skip the new file header information. This is corrected with this patch kit. 5.4.2 Images and/or Files Affected: [SYSLIB]XFC$SDA.EXE 5.4.3 VSI case identifier Jira BO-1538 Netsuite NS6238 5.4.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.5 Callable FDL generates misleading "Alpha" reference in IDENT record 5.5.1 Problem Description Callable FDL generates an FDL file (an RMS File Description Language entity for creating specific format files). Prior to this patch kit, a line similar to this was generated in the output FDL file: IDENT FDL_VERSION 02 "25-JAN-2021 12:51:22 Alpha/VMS FDL$GENERATE Routine" The "Alpha" reference is a leftover remnant of older ported code and is misleading since FDL files are architecture neutral. This patch kit merely removes the string "Alpha/" from the generated IDENT record to avoid confusion. 5.5.2 Images and/or Files Affected: [SYSLIB]FDLSHR.EXE 5.5.3 VSI case identifier Jira FS-177 Netsuite NS2152 5.5.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.6 Removed stale qualifiers from example LAVC tools build file 5.6.1 Problem Description The command procedure SYS$EXAMPLES:LAVC$BUILD.COM is used to build some example programs for analyzing or modifying bus state for some VMScluster configurations. Some stale command qualifiers were present in the procedure. The /MIGRATE qualifier was removed from the MACRO command and the /ALPHA qualifier was removed from the LINK command. Some additional changes were made to simplify and clarify the procedure as well. 5.6.2 Images and/or Files Affected: [SYSHLP.EXAMPLES]LAVC$BUILD.COM 5.6.3 VSI case identifier Jira BO-1450 Netsuite NS5920 5.6.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.7 Enhanced SHOW CPU/FULL command to include CPU Type 5.7.1 Problem Description A customer requested that the output from SHOW CPU/FULL display additional information as is done in CLUE CONFIG/CPU. In particular, the CPU Type is now displayed as shown in the example below: Old CPU display: State..........: RC, PA, PP, CV, PV, PMV, PL Type...........: Itanium Major = 33, Minor = 0 Speed..........: 2527 Mhz LID............: 00000000 New CPU display: State..........: RC, PA, PP, CV, PV, PMV, PL Type...........: Itanium Major = 33, Minor = 0 Cpu Type.......: Octa-Core Itanium (Intel Itanium 9500 D0) Speed..........: 2527 Mhz LID............: 00000000 Other fields which were present in CLUE CONFIG/CPU should now display in the same fashion for SHOW CPU/FULL. 5.7.2 Images and/or Files Affected: [SYSEXE]SMPUTIL.EXE 5.7.3 VSI case identifier Jira UT-112 5.7.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 If installing on V8.4-2L3 only -------------------------------- 5.8 Enhanced SYSUAF check to include accounts set /NOPASSWORD 5.8.1 Problem Description SYS$MANAGER:VMS$DEFINE_PASSWORD_POLICY.COM contains a menu entry to scan SYSUAF.DAT for non-compliant accounts. At a customer request, the scanner has been updated to include a check for accounts with no password. 5.8.2 Images and/or Files Affected: [SYSEXE]VMS$CHECK_UAF.EXE 5.8.3 VSI case identifier Jira UT-169 5.8.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.8.5 Workaround For a single account, a simple program calling SYS$GETUAI which tests the returned value for the item code UAI$_PWD against 0 could be written by someone mildly familiar with OpenVMS system services. However, scanning SYSUAF to examine all accounts is a larger problem requiring more extensive knowledge of VMS. It is far simpler to merely install the patch and use the VSI-supplied mechanisms. 6 PROBLEMS ADDRESSED FROM PREVIOUS KITS None 7 IMAGES OR FILES REPLACED: For all target OpenVMS versions supported by this kit ------------------------------------------------------- [SYSLIB]FDLSHR.EXE Image name: "FDLSHR" Image file identification: "X-23" Image build identification: "XFWL-C6E-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 14:05:14.63 Image Checksum (MD5): 2502177138B91C1AD9415DD868BBB566 [SYSHLP.EXAMPLES]LAVC$BUILD.COM File creation date and time: 18-OCT-2023 17:28:36.92 Checksum (MD5): 4DBC22965ED66CB4680D3B6F2E63DF79 If installing on V8.4-1H1 --------------------------- [SYSEXE]DIRECTORY.EXE Image name: "DIRECTORY" Image file identification: "X02-01" Image build identification: "XE30-B4N-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 16:48:38.04 Image Checksum (MD5): F4E255B604474C06856FD4C332CD305B [SYSEXE]PCSI$MAIN.EXE Image name: "PCSI$MAIN" Image file identification: "X34.1" Image build identification: "XE30-B4N-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 16:48:44.37 Image Checksum (MD5): A28BB7F5CBF1CBF254C2727BB87A253C [SYSEXE]SMPUTIL.EXE Image name: "SMPUTIL" Image file identification: "X-30" Image build identification: "XE30-B4N-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 16:48:38.92 Image Checksum (MD5): B6055CE3A4948CF224FAAADE6BF580FD [SYSEXE]USB$UCM_SERVER.EXE Image name: "USB$UCM_SERVER" Image file identification: "X-30" Image build identification: "" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 16:48:51.48 Image Checksum (MD5): F5D91FC9C8B20B8A3CE910289DDAB56F [SYSLIB]XFC$SDA.EXE Image name: "XFC$SDA" Image file identification: "V1.0" Image build identification: "XE30-B4N-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 16:48:44.50 Image Checksum (MD5): A5E9EFC6921CB7E8CCB11B107BAEF830 If installing on V8.4-2 ------------------------- [SYSEXE]DIRECTORY.EXE Image name: "DIRECTORY" Image file identification: "X02-01" Image build identification: "XE3F-M5D-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 17:24:09.22 Image Checksum (MD5): 532584B9F41570B0150C6CA1960FFB23 [SYSEXE]PCSI$MAIN.EXE Image name: "PCSI$MAIN" Image file identification: "X34.1" Image build identification: "XE3F-M5D-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 17:24:14.64 Image Checksum (MD5): 150EB807EF0D2F66AE2B339AF0C02CE4 [SYSEXE]SMPUTIL.EXE Image name: "SMPUTIL" Image file identification: "X-30" Image build identification: "XE3F-M5D-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 17:24:11.84 Image Checksum (MD5): A1A831330A5C21D6C55F95D9CE1F8625 [SYSEXE]USB$UCM_SERVER.EXE Image name: "USB$UCM_SERVER" Image file identification: "X-30" Image build identification: "" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 17:24:21.46 Image Checksum (MD5): BB573C272742EA335172CA5771CCB0DA [SYSLIB]XFC$SDA.EXE Image name: "XFC$SDA" Image file identification: "V1.0" Image build identification: "XE3F-M5D-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 17:24:16.20 Image Checksum (MD5): 0DB0AFD12A63C3747FE8D16D7E689FC4 If installing on V8.4-2L1 --------------------------- [SYSEXE]DIRECTORY.EXE Image name: "DIRECTORY" Image file identification: "X02-01" Image build identification: "XE4H-H4N-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 13:36:49.04 Image Checksum (MD5): E850678ED6CC6ED43052DB933458D4D8 [SYSEXE]PCSI$MAIN.EXE Image name: "PCSI$MAIN" Image file identification: "X34.1" Image build identification: "XE4H-H4N-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 13:36:54.26 Image Checksum (MD5): 6165035D1059C52A0A3B4AEC1FD4F847 [SYSEXE]SMPUTIL.EXE Image name: "SMPUTIL" Image file identification: "X-30" Image build identification: "XE4H-H4N-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 13:36:49.47 Image Checksum (MD5): 4EE4D8443B400D6F809E0341B16F85D6 [SYSEXE]USB$UCM_SERVER.EXE Image name: "USB$UCM_SERVER" Image file identification: "X-30" Image build identification: "" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 13:37:05.52 Image Checksum (MD5): 71409C80922F9BD96CF1983A17654888 [SYSLIB]XFC$SDA.EXE Image name: "XFC$SDA" Image file identification: "V1.0" Image build identification: "XE4H-H4N-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 13:36:57.88 Image Checksum (MD5): C68679784317384EF7E8AAB39278C406 If installing on V8.4-2L3 --------------------------- [SYSEXE]DIRECTORY.EXE Image name: "DIRECTORY" Image file identification: "X02-01" Image build identification: "XFWL-C6E-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 14:06:00.25 Image Checksum (MD5): CE41BBCB5BCE02C8921CF4A85110C6DF [SYSEXE]PCSI$MAIN.EXE Image name: "PCSI$MAIN" Image file identification: "X34.1" Image build identification: "XFWL-C6E-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 14:06:03.44 Image Checksum (MD5): 84279F3A8E3976166A30010DD7642A4D [SYSEXE]SMPUTIL.EXE Image name: "SMPUTIL" Image file identification: "X-30" Image build identification: "XFWL-C6E-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 14:06:03.12 Image Checksum (MD5): 4CDB412D4898AFB663B39918CBA3A86B [SYSEXE]USB$UCM_SERVER.EXE Image name: "USB$UCM_SERVER" Image file identification: "X-30" Image build identification: "" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 14:06:06.77 Image Checksum (MD5): A5669547E61512F89D45B5AF4238BD32 [SYSLIB]XFC$SDA.EXE Image name: "XFC$SDA" Image file identification: "V1.0" Image build identification: "XFWL-C6E-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 14:06:05.98 Image Checksum (MD5): FBFA980616FB35F4A151E801B8F71A44 [SYSEXE]VMS$CHECK_UAF.EXE Image name: "VMS$CHECK_UAF" Image file identification: "X1.2" Image build identification: "XFWL-C6E-000150" Link identification: "Linker I02-37" Link Date/Time: 27-JUL-2024 14:06:01.69 Image Checksum (MD5): 1C9CAAEC226724323973951991CBF4D7 Note: VMS Software, Inc. will only distribute kits in signed form. There is no need for most customers to compare file checksums for security or kit integrity reasons. However, some sites may require such checking even when using signed kits. The image or file checksums are supplied (in MD5 format) to provide comparisons to the extracted final kit files. To find a file checksum, use: $ CHECKSUM/ALGORITHM=MD5 filename $ SHOW SYMBOL CHECKSUM$CHECKSUM Note: Because a file or image may be replaced by multiple patch kits over time, a PCSI generation number is used to ensure that the latest version of the file or image is preserved on your system during PRODUCT INSTALL of a patch kit. Should a particular kit installation discover a newer version of a file or image in place on the system disk, the following message will be displayed: %PCSI-I-RETAIN, file will not be replaced because file from kit has lower generation number This is a normal occurrence depending on the order of kit installation. The correct version of the file or image will remain on the system after the current kit installation. The %PCSI-I-RETAIN message is informational only and does not indicate a problem. 8 INSTALLATION INSTRUCTIONS 8.1 Compressed File This kit is provided for download within a ZIP archive container file. The kit files may be extracted on any system with UNZIP and copied to your OpenVMS system, or extracted on your OpenVMS system directly. Assuming you have created an UNZIP symbol to invoke the UNZIP image, you can invoke UNZIP to unpack the kit on OpenVMS using the command: $ UNZIP VMS842L3I_MISC-V0100 This will extract the installable PCSI product kit file and its associated signed manifest (_VNC file), used for kit validation during PRODUCT commands. VSI strongly recommends always using the manifest to validate the kit content during any PRODUCT commands. This will occur automatically if the files are both contained in the same directory. Note regarding UNZIP tool availability: Most customers likely have already installed a set of ZIP and UNZIP tools on their VSI OpenVMS systems. Should you need these tools, a set of the Info-ZIP freeware ZIP and UNZIP tools for VSI OpenVMS is available for download on the web at this address: https://vmssoftware.com/products/zip-tools/ 8.2 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 VMS842L3I_MISC [/SOURCE=location of kit] The kit location may be a tape drive, CD/DVD, 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. This kit requires the use of /RECOVERY_MODE and /SAVE_RECOVERY_DATA and will automatically set them; they do not need to be present on the command line. The release notes for any kit may be extracted prior to kit installation using the PRODUCT EXTRACT RELEASE_NOTES command. User-selectable options for installation behavior and scripting are available in this kit, refer to Appendix A for further details. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 8.3 Special Installation Instructions While this kit does not require a system reboot, an additional step is required to restart the USB (Universal Serial Bus) Configuration Manager (UCM) with the corrected functionality. If you have configured USB devices on your system, you will need to restart the UCM Server. At a convenient time for you when any USB devices are not in use, issue the following command to restart the configuration manager server: $ UCM RESTART It is safe to wait until the next system reboot should you prefer to do so. If you have never configured USB devices on your system, you do not need to restart the UCM server since it will not be running. It is harmless to attempt the UCM RESTART command anyway, as it will merely display an expected %SYSTEM-F-TIMEOUT message and otherwise ignore the command. In a VMScluster with a shared system disk, the UCM RESTART command should also be performed on each node sharing the system disk with the installation system, for those systems with USB devices configured. In addition, for other systems in a VMScluster which are sharing the system disk which was updated, the following commands must be executed on each node so that the new images are used: $ INSTALL REPLACE SYS$SHARE:FDLSHR.EXE $ INSTALL REPLACE SYS$SYSTEM:DIRECTORY.EXE $ INSTALL REPLACE SYS$SYSTEM:SMPUTIL.EXE All of the relevant steps above should be repeated if this patch kit is removed via a PRODUCT UNDO PATCH operation. 9 COPYRIGHT ******************************************************************** * * * VMS SOFTWARE, INC. CONFIDENTIAL. This software is confidential * * proprietary software licensed by VMS Software, Inc., and is not * * authorized to be used, duplicated or disclosed to anyone without * * the prior written permission of VMS Software, Inc. * * Copyright 2024 VMS Software, Inc. * * * ******************************************************************** 10 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 VMS SOFTWARE, INC. 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. 11 PATCH ID I64VMS-VMS842L3I_MISC-V0100--4 APPENDIX A - User-selectable control options and scripting considerations Controlling kit behavior for introductory questions --------------------------------------------------- This kit provides user-selectable control options for kit dialogue interaction and automated scripting capability as described here in this appendix. The general form of a VSI ECO patch kit, when using PRODUCT INSTALL, consists of three initial questions regarding these topics: 1. System disk backup: A reminder that VSI recommends backing up the system disk before installing patches, followed by a "Do you want to continue?" yes/no question, default = YES. 2. Reboot requirement: A summary of whether the kit being installed requires a system reboot, followed by a "Do you want to continue?" yes/no question, default = YES. 3. Archival of updated files: A description of saving an "_OLD" copy of each image or file updated by the kit, followed by a "Do you want to save "_OLD" copies of replaced files?" yes/no question, default = NO. Other questions may be asked later, depending on the target disk or system environment or other kit-specific requirements. Note: An initial "Do you want to continue?" question may be asked directly by the PCSI utility during any PRODUCT command -- this has nothing to do with the kit being used. To avoid that question, you must supply sufficient detail to uniquely identify the product you wish to use and specify /OPTIONS=NOCONFIRM on the PRODUCT command. Control options are available to customize the dialogue for the initial three kit questions. The controls are logical names, which may be defined in the process logical name table with a value of YES or NO. To modify the behavior of the VSI ECO patch kit regarding the initial questions, define one or more of the following logical names before issuing the PRODUCT INSTALL command. o To skip one or more of the questions, define the corresponding logical name shown here to YES: SKIP$BACKUP - Skip system backup awareness question. SKIP$REBOOT - Skip system reboot awareness question. SKIP$ARCHIVE_OLD - Skip question about saving "_OLD" files. This will take the default, which is NO. SKIP$INTRO - Skip all three of the above questions. o To specifically override the default for saving "_OLD" files, define this logical name to YES or NO: VSIKIT$ARCHIVE_OLD - Sets an answer for saving "_OLD" files behavior. This will skip the archive "_OLD" files question regardless of the above SKIP$* logical names. o Two additional logical names may be defined as YES to modify the amount of explanatory text displayed for each question: VSIKIT$VERBOSE - Shows all explanatory text for questions. VSIKIT$BRIEF - Skips some general details in the explanations. The default if neither name is defined is VERBOSE. If both names are defined to YES, VERBOSE overrides BRIEF. The BRIEF form is displayed for any questions that are skipped. For example, to skip all three questions but save an archive "_OLD" copy of each replaced file: $ DEFINE VSIKIT$ARCHIVE_OLD YES $ DEFINE SKIP$INTRO YES $ PRODUCT INSTALL Standard behavior for YES/NO questions asked during kit installation -------------------------------------------------------------------- Any YES/NO questions asked during kit installation now follow these rules: 1. Ctrl-Y issued while a question is being asked will force the current PRODUCT operation to terminate. This is completely safe to do while the initial three questions are being asked during PRODUCT INSTALL as no changes have yet been made to the target disk. 2. Some questions may ignore Ctrl-Y and ask for a specific answer, if aborting the current operation may have side effects. PCSI may trap Ctrl-Y directly for some PRODUCT operations. Ctrl-Y may be disabled during some sensitive kit processing. 3. The default YES/NO answer is automatically chosen if a kit is installed from a batch job, unless explicitly overridden by a logical name which provides the particular value, such as VSIKIT$ARCHIVE_OLD. Installing a kit from a batch job --------------------------------- To install a kit from a batch job you will need to fully qualify the kit name so PCSI will have enough information to select the kit without asking for confirmation. For example, to install this kit: $ PRODUCT INSTALL VMS842L3I_MISC/VERSION=V1.0/OPTIONS=NOCONFIRM If the kit is located in a directory other than the current default directory, you will also need to add the qualifier: /SOURCE= For a batch job, any YES/NO question will automatically select the default answer. Use the control logical names explained above to modify the behavior if necessary. For the system disk backup and reboot questions, the batch behavior is identical to the default. For the save "_OLD" files question, define the VSIKIT$ARCHIVE_OLD logical name to YES if you want to save copies of the files, since the batch default is NO. Deprecated logical names from HPE patch kits -------------------------------------------- The three names listed below were used by older VSI OpenVMS patch kits for compatibility with HPE patch kit behavior. These old names continue to function, but VSI encourages you to modify any scripts you may have to use the new names shown instead: Old name New name --------------- -------------------- NO_ASK$BACKUP SKIP$BACKUP NO_ASK$REBOOT SKIP$REBOOT ARCHIVE_OLD VSIKIT$ARCHIVE_OLD