======================================================================= VMS Software, Inc. OpenVMS ECO Kit Release Notes ======================================================================= 1 KIT NAME: VMS842L1I_RTL-V0200 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1: To be installed by all customers. 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 to use the images provided by this kit on all nodes of a VMSCluster using a common system disk. Refer to Section 8.3, "Special Installation Instructions", for required post-installation actions. 2.3 Version(s) of OpenVMS to which this kit may be applied: VSI OpenVMS for Integrity Servers V8.4-2L1 3 KITS SUPERSEDED BY THIS KIT: This kit is a superset of all previously released kits for RTL defect repair and the new functionality of the C99 kits, plus some additional bugfixes as described in Section 5. These specific kits are superseded: VMS842L1I_RTL-V0100 VMS842L1I_BASRTL-V0100 VMS842L1I_C99-V0200 VMS842L1I_C99-V0100 4 KIT DEPENDENCIES: VMS842L1I_DPML-V0100 This provides new math library functions needed by the C99 functionality included in this kit. NOTE: The DPML kit *must* be installed with a separate PRODUCT INSTALL command prior to installing this kit. Do not use the same PRODUCT INSTALL command to install both kits simultaneously. VMS842L1I_UPDATE-V0100 All new patch kits for VSI OpenVMS for Integrity Servers V8.4-2L1 require the VMS842L1I_UPDATE-V0100 kit. 5 PROBLEMS ADDRESSED IN THIS KIT 5.1 C RTL functions l64a and l64a_r fail if called with invalid arguments 5.1.1 Problem Description The C RTL functions l64a and l64a_r are used to convert between a long integer and a base-64 ASCII string. These functions will fail when invalid parameters are passed: l64a has a virtual memory leak when called with a negative number as the parameter. l64a_r provokes an access violation when called with a null buffer pointer. These issues are corrected with this patch kit. 5.1.2 Images and/or Files Affected: [SYSLIB]DECC$SHR.EXE 5.1.3 Quix and/or Bugzilla cases reporting this problem: VSI Internal Jira RTLS-45 5.1.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 5.2 Pascal Run-Time Library condition handling may produce ACCVIO 5.2.1 Problem Description The Pascal Run-Time Library will sometimes produce an access violation (ACCVIO) when attempting to handle a condition. A prior update to the Pascal Run-Time Library enabled user-written condition handlers when using the LINKER /SEGMENT=CODE=P2 qualifier. This introduced a regression that caused the RTL itself to sometimes ACCVIO when handling user-written condition handlers. The exact Pascal syntax required to trigger this error is difficult to describe. This patch kit corrects the issue. 5.2.2 Images and/or Files Affected: [SYSLIB]PAS$RTL.EXE 5.2.3 Quix and/or Bugzilla cases reporting this problem: VSI Bugzilla 3040 5.2.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 5.3 The C RTL header may generate a compiler error 5.3.1 Problem Description The C99 kit version of the DECC$RTLDEF.TLB standard definitions library contained some spurious definitions which are for a future VSI OpenVMS release. Most of these are harmlessly ignored under normal conditions but could cause a compiler error if the value of the __CRTL_VER macro is explicitly set to a value used by an earlier version of the CRTL. This kit corrects the problem. 5.3.2 Images and/or Files Affected: [SYSLIB]DECC$RTLDEF.TLB 5.3.3 Quix and/or Bugzilla cases reporting this problem: VSI Bugzilla 3393 5.3.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 6 PROBLEMS ADDRESSED FROM PREVIOUS KITS 6.1 FILATTNOT (ERR=160) error when a BASIC program opens a file 6.1.1 Problem Description When a BASIC program opened a file with a quadword key, the BASIC RTL file open routine used the wrong key type to check the key. This resulted in a FILATTNOT (ERR=160) error: File attributes not matched. This patch kit corrects the problem. 6.1.2 Images and/or Files Affected: [SYSLIB]DEC$BASRTL.EXE 6.1.3 Quix and/or Bugzilla cases reporting this problem: QXCM1001370616 6.1.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 6.2 COBOL application crash when reading RMS file sequentially backwards 6.2.1 Problem Description If reading a file in reverse sequence order, the COBOL RTL could encounter an RMS status indicating a record was already locked. This status was incorrectly handled under this circumstance, which lead to a recursive attempt to handle the error and an eventual access violation which would terminate the image. This patch kit corrects the problem. 6.2.2 Images and/or Files Affected: [SYSLIB]DEC$COBRTL.EXE 6.2.3 Quix and/or Bugzilla cases reporting this problem: QXCM1001464116 6.2.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 6.3 Reading a file with multiple keys using COBOL may access violate 6.3.1 Problem Description The COBOL RTL was incorrectly comparing keys of different sizes when multiple keys were defined for a file. This could lead to an access violation which would terminate the image. This patch kit corrects the problem. 6.3.2 Images and/or Files Affected: [SYSLIB]DEC$COBRTL.EXE 6.3.3 Quix and/or Bugzilla cases reporting this problem: QXCM1001526800 6.3.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 6.4 Pascal RTL access violation using condition handler in P2 space 6.4.1 Problem Description The Pascal RTL will access violate when attempting to dispatch to a user-written condition handler when the image is running in P2 space. This could occur when using the LINK/SEGMENT=CODE=P2 qualifier when the image was linked. The Pascal RTL incorrectly used only the low 32 bits of the address to the handler data area encoded in the unwind descriptors. For code that is loaded into P2 space, the corresponding unwind information is also loaded into P2 space, and therefore only accessible using 64 bit pointers. This patch kit corrects the problem. 6.4.2 Images and/or Files Affected: [SYSLIB]PAS$RTL.EXE 6.4.3 Quix and/or Bugzilla cases reporting this problem: None, found during internal testing 6.4.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 6.5 The C RTL stat() function may return an invalid st_ino value 6.5.1 Problem Description When using _USE_STD_STAT, the stat() function returns an invalid value for st_ino if the NAM$W_FID_SEQ or FIB$W_FID_SEQ value is larger then 32767. This patch kit corrects the problem. 6.5.2 Images and/or Files Affected: [SYSLIB]DECC$SHR.EXE 6.5.3 Quix and/or Bugzilla cases reporting this problem: QXCM1001543598 6.5.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 6.6 The C RTL lstat() function may leak I/O channels 6.6.1 Problem Description The lstat() function may not release I/O channels when the filename includes a logical name that is search list. This patch kit corrects the problem. 6.6.2 Images and/or Files Affected: [SYSLIB]DECC$SHR.EXE [SYSLIB]DECC$SHRP.EXE 6.6.3 Quix and/or Bugzilla cases reporting this problem: PTR 75-126-461 6.6.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 6.7 The C RTL header may generate syntax errors 6.7.1 Problem Description The header will generate a syntax error if _XOPEN_SOURCE_EXTENDED is defined on the C or C++ command line using the /DEFINE qualifier. This patch kit corrects the problem. 6.7.2 Images and/or Files Affected: [SYSLIB]DECC$SHR.EXE [SYSLIB]DECC$RTLDEF.TLB 6.7.3 Quix and/or Bugzilla cases reporting this problem: PTR 75-126-462 6.7.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 6.8 Various LIBRTL routines may cause alignment faults 6.8.1 Problem Description The initial problem report was for the STR$ELEMENT routine, which will generate an alignment fault if the 'delimiter' character is not on a quadword boundary. This was because the compiler was unaware of the intended size and alignment of the delimiter. Upon review of other LIBRTL routines for similar potential issues, all of these routines were found to be at risk of alignment faults: LIB$INIT_DATE_TIME_CONTEXT LIB$DELETE_FILE LIB$FIND_FILE LIB$CVT_DX_DX for numeric strings with overpunched signs LIB$GETQUI STR$DUPL_CHAR STR$ELEMENT STR$LEFT STR$LEN_EXTR STR$REPLACE STR$RIGHT With this patch kit, all of these routines have been corrected to avoid alignment faults. 6.8.2 Images and/or Files Affected: [SYSLIB]LIBRTL.EXE [SYSLIB]LIBRTL.STB [SYSLIB]LIBRTL.DSF 6.8.3 Quix and/or Bugzilla cases reporting this problem: VSI Bugzilla 1279 6.8.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 6.9 Exception handling issues when using routine DBASIC$IO_NO_SIGNAL 6.9.1 Problem Description The routine DBASIC$IO_NO_SIGNAL() was added in prior versions of OpenVMS to avoid the cost of an expected I/O exception. This can provide a performance benefit for applications written in BASIC which encounter exceptions during normal processing. Exception handling has a very high CPU overhead on Integrity servers. This patch kit corrects two problems in that routine: - When an IO operation fails and the flag(s) set by DBASIC$IO_NO_SIGNAL prevent throwing an exception, the buffer pointer was sometimes updated to an incorrect value. This is now corrected. - When an IO operation completes successfully, the flags left DBASIC$IO_NO_SIGNAL should be cleared. This is now done. 6.9.2 Images and/or Files Affected: [SYSLIB]DEC$BASRTL.EXE 6.9.3 Quix and/or Bugzilla cases reporting this problem: External Bugzillas 353, 389 6.9.4 Release Version of OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 6.10 Add C99 Standard support to the C Runtime Library 6.10.1 Problem Description This patch kit provides support for new C99 routines to the C Run Time Library, as well as support for new C99 math routines to the C and Math Run Time Libraries. Various header files have been updated to meet the C99 standard requirements. New format support is supplied for fprint(), fscan(), sprintf(), strptime(), and strftime(). For a complete description of the changes, refer to the additional release notes in: SYS$HELP:VSI_OPENVMS_CRTL_NOTES.TXT SYS$HELP:VSI_OPENVMS_CRTL_NOTES.PDF 6.10.2 Images and/or Files Affected: [SYSLIB]DECC$SHR.EXE [SYSLIB]DECC$SHRP.EXE [SYSLIB]DECC$RTLDEF.TLB [SYSMSG]DECC$MSG.EXE 6.10.3 Quix and/or Bugzilla cases reporting this problem: VSI Bugzilla 2643 6.10.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 6.11 Corrected behavior from the C99 V1.0 kit 6.11.1 Problem Description The following issues from the C99 V1.0 kit have been corrected: o va_copy() is now only defined when using the latest compiler. o C99 routines are now correctly defined when a module is compiled /STANDARD=RELAXED. o fp_classify() has been corrected. o fstat() no longer returns a bad st_ino when compiled with _USE_STD_STAT and the FID rvn contains a value larger than 32767. o isnan() is defined for C99, _XOPEN_SOURCE, and C extensions. o isnanf() and isnanl() are defined only for _XOPEN_SOURCE and C extensions. 6.11.2 Images and/or Files Affected: [SYSLIB]DECC$SHR.EXE [SYSLIB]DECC$SHRP.EXE [SYSLIB]DECC$RTLDEF.TLB [SYSMSG]DECC$MSG.EXE 6.11.3 Quix and/or Bugzilla cases reporting this problem: VSI Bugzilla 2950 6.11.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L1 7 IMAGES OR FILES REPLACED: [SYSLIB]DEC$BASRTL.EXE Image name: "DEC$BASRTL" Image file identification: "V01-038" Image build identification: "XE4H-H4N-000059" Link identification: "Linker I02-37" Link Date/Time: 21-MAR-2020 16:01:02.39 Image Checksum (MD5): 61BC0B842CA8C547E20B80853E30B6D7 [SYSLIB]DEC$COBRTL.EXE Image name: "LIBCOB" Image file identification: "V2.9-785" Image build identification: "XE4H-H4N-000059" Link identification: "Linker I02-37" Link Date/Time: 21-MAR-2020 16:00:57.60 Image Checksum (MD5): 250841B060513CE0508AB23B31AC5767 [SYSLIB]PAS$RTL.EXE Image name: "PAS$RTL" Image file identification: "PAS$RTL V5.0-31" Image build identification: "XE4H-H4N-000059" Link identification: "Linker I02-37" Link Date/Time: 21-MAR-2020 16:00:50.70 Image Checksum (MD5): 761AC7FEE327DE8B083EA7DDA1F3DDAC [SYSLIB]DECC$SHR.EXE Image name: "DECC$SHR" Image file identification: "V8.4-00" Image build identification: "XE4H-H4N-000059" Link identification: "Linker I02-37" Link Date/Time: 21-MAR-2020 15:59:47.85 Image Checksum (MD5): B7F124DDE6EA644465ED740DF2410E15 [SYSLIB]DECC$SHRP.EXE Image name: "DECC$SHRP" Image file identification: "V8.4-00" Image build identification: "XE4H-H4N-000059" Link identification: "Linker I02-37" Link Date/Time: 21-MAR-2020 15:59:46.75 Image Checksum (MD5): 2484EA877CB2B70BDBC51EC4AB625EEF [SYSLIB]DECC$RTLDEF.TLB Checksum (MD5): 296EE565BE8ABB354F771A6892D43BBD [SYSLIB]LIBRTL.EXE Image name: "LIBRTL" Image file identification: "X01-001" Image build identification: "XE4H-H4N-000059" Link identification: "Linker I02-37" Link Date/Time: 21-MAR-2020 15:59:41.03 Image Checksum (MD5): A2F3C27705F0FBE71EB7D9BB806BFD6B [SYSLIB]LIBRTL.STB Checksum (MD5): 79A5CEE622C52A97A83DB73B61EF1A62 [SYSLIB]LIBRTL.DSF Checksum (MD5): 8EAC763E0252F5AF5D73E81D2E688F33 [SYSMSG]DECC$MSG.EXE Image name: "DECC$MSG" Image file identification: "V8.4-00" Image build identification: "XE4H-H4N-000059" Link identification: "Linker I02-37" Link Date/Time: 21-MAR-2020 16:01:16.96 Image Checksum (MD5): C1BDBBCF2E99BE8FFF1F4F5C98DD705C 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 insure 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 as a self-extracting ZIPEXE file. To expand this file to the installable PCSI kit, execute the file image with the following command: $ RUN VMS842L1I_RTL-V0200.ZIPEXE 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 VMS842L1I_RTL [/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 If this kit is being installed in a non-clustered environment, this section may be ignored. In a VMScluster with a shared system disk, additional steps must be taken so that the other nodes which share the system disk will use the new images. Execute the following command on each node that is sharing the system disk that has been updated: $ INSTALL REPLACE SYS$LIBRARY:DEC$BASRTL.EXE $ INSTALL REPLACE SYS$LIBRARY:DEC$COBRTL.EXE $ INSTALL REPLACE SYS$LIBRARY:PAS$RTL.EXE $ INSTALL REPLACE SYS$LIBRARY:DECC$SHR.EXE $ INSTALL REPLACE SYS$LIBRARY:DECC$SHRP.EXE $ INSTALL REPLACE SYS$MESSAGE:DECC$MSG.EXE $ INSTALL REPLACE SYS$LIBRARY:LIBRTL.EXE These same commands should be repeated for other systems sharing the system disk if this patch kit is removed via a PRODUCT UNDO PATCH operation. 8.4 Documentation for C99 functionality Additional documentation for the C99 Standard functions is copied to the system disk during kit installation. This documentation is provided both in text format (.TXT) for immediate reference and convenience of using the OpenVMS SEARCH command, and in PDF format for more legible output and convenience for formatted printing from a browser: SYS$HELP:VSI_OPENVMS_CRTL_NOTES.TXT SYS$HELP:VSI_OPENVMS_CRTL_NOTES.PDF The release notes for this kit and the above files containing additional documentation may be extracted from the PCSI kit before kit installation for reference and planning purposes. The PCSI kit files are present after running the self-extracting ZIPEXE file as described above in Section 8.1. To extract the release notes and the VSI_OPENVMS_CRTL_NOTES.TXT file, use the command: $ PRODUCT EXTRACT RELEASE_NOTES VMS842L*_RTL To extract the PDF format additional documentation, use the command: $ PRODUCT EXTRACT FILE VMS842L*_RTL /SELECT=*.PDF Either of these commands will create a local copy of the desired file(s) in the current default directory. 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 2020 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-VMS842L1I_RTL-V0200--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 VMS842L1I_RTL/VERSION=V2.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