======================================================================= VMS Software, Inc. OpenVMS ECO Kit Release Notes ======================================================================= 1 KIT NAME: VMS842L3I_UTILITY-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: A reboot is required after installing this kit. VMS Software, Inc. strongly recommends that a reboot be performed immediately after kit installation to avoid system instability. If you are installing this kit in a VMScluster, any systems that share the same system disk with the installing system must also be rebooted in order to make use of the new images. 2.3 Version(s) of VSI OpenVMS to which this kit may be applied: VSI OpenVMS for Integrity Servers V8.4-2L3 3 KITS SUPERSEDED BY THIS KIT: None Note: There was no UTILITY V1.0 patch kit for VSI OpenVMS for Integrity Servers V8.4-2L3. This kit is named V2.0 to allow a common patch version level across all VSI OpenVMS V8.4-* versions which have equivalent functionality and defect repair. 4 KIT DEPENDENCIES: None 5 PROBLEMS ADDRESSED IN THIS KIT 5.1 OPCOM displays incorrect value on rare error message 5.1.1 Problem Description On rare occasions, the OPCOM utiity may encounter an inconsistency and enter a message in the operator log file similar to this: %%%%%%%%%%% OPCOM 27-MAY-2022 00:24:57.58 %%%%%%%%%%% WRITE_LOG_FILE The OpenVMS host software has requested the preservation of the following OPCOM message data here in the operator log file. No user action is normally required. "OPCOM has noticed a COD inconsistency. Count(7AEEB778) = Alloc(00000000) - (Busy(00038624) + Wait(00000000) + Free(000F40BC) + Dealloc(00000000)." The value for the "Count" field is incorrectly displaying the count field address instead of the actual count itself. This error has been corrected with this patch kit. The conditions to provoke this message are exceedingly rare, and such a message should be reported to VSI Software Support. In some cases the OPCOM process must be restarted after logging this error. 5.1.2 Images and/or Files Affected: [SYSEXE]OPCOM.EXE 5.1.3 VSI case identifier None 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 Spurious error in UTC$TIME_SETUP.COM 5.2.1 Problem Description If the user invoking the UTC$TIME_SETUP.COM procedure has defined DCL symbols for "TY" or "SEAR", a PIPE command embedded in the procedure could fail when the intended commands were "TYPE" or "SEARCH". In most cases, this would cause the procedure to exit with an unrelated error. This has been corrected with this patch kit. 5.2.2 Images and/or Files Affected: [SYSMGR]UTC$TIME_SETUP.COM 5.2.3 VSI case identifier Jira UT-121 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.2.5 Workaround Delete the interfering DCL symbols TY or SEAR before invoking the UTC$TIME_SETUP.COM procedure. 5.3 SPKITBLD procedure could encounter BACKUP verification error 5.3.1 Problem Description The SPKITBLD procedure is used to build an installation kit for an OpenVMS software product using an older installation mechanism, VMSINSTAL. Typically only legacy software developers or ISPs would use this procedure. Use of the SPKITBLD procedure can give a BACKUP verification error if the input device is ODS-5 and the output device is ODS-2. In the reported problem, a directory file failed verification since at least one of the files in the directory had its name changed to be ODS-2 compliant. The BACKUP command in SPKITBLD uses the /CONVERT qualifier implicitly, due to the use of the /INTERCHANGE qualifier, which implies /CONVERT. The fix is to remove the use of the /VERIFY qualifier if the output device is a disk, and to add /NOCONVERT if the output device is ODS-5. 5.3.2 Images and/or Files Affected: [SYSUPD]SPKITBLD.COM 5.3.3 VSI case identifier Jira UT-126 Netsuite 2067 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 SET PROCESS /KERNEL_THREAD_LIMIT=n does not affect a different process 5.4.1 Problem Description The command definition for SET PROCESS /KERNEL_THREAD_LIMIT accepts a PID for /IDENTIFICATION or a process name, but any such provided specification was not used to set the process characteristics and instead the current process was affected. With this change, both a PID and a process name are accepted and used to set the limit in the desired target process. 5.4.2 Images and/or Files Affected: [SYSEXE]SET.EXE 5.4.3 VSI case identifier Jira UT-115 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 SHOW DEVICE does not display NFS-mounted devices 5.5.1 Problem Description The command SHOW DEVICE, when used without specifying a device type, does not show NFS-mounted devices. The devices would be shown if the command was SHOW DEVICE D instead. This has been corrected with this patch kit. 5.5.2 Images and/or Files Affected: [SYSEXE]SHOW.EXE 5.5.3 VSI case identifier Jira UT-149 Netsuite 3268 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 UTC$TIME_SETUP.COM displays erroneous values after input error 5.6.1 Problem Description If a bogus time zone differential factor value is entered when executing UTC$TIME_SETUP.COM, an error message is displayed and the user is re-prompted for the value. The error message displayed shows an incorrect TDF value range and causes confusion about what the correct input values could be. The range must only be -13:00 < TDF =< 13:00, by definition of a time zone differential factor. The error displayed now shows this correct range. 5.6.2 Images and/or Files Affected: [SYSMGR]UTC$TIME_SETUP.COM 5.6.3 VSI case identifier Jira QTV-531 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 MAIL utility triggers ill-formed audits during privilege validation 5.7.1 Problem Description Using the MAIL utility to inspect the VMS Profile database can trigger ill-formed internal (TCB) audits for each record read, similar to this: %%%%%%%%%%% OPCOM 29-MAR-2022 12:25:16.11 %%%%%%%%%%% Message from user AUDIT$SERVER on NODE1 Security alarm (SECURITY) and security audit (SECURITY) on NODE1, system id: 34 Auditable event: Ill-formed internal (TCB) audit Event time: 29-MAR-2022 12:25:16.11 PID: 000004AE Process name: SYSTEM Username: SYSTEM Process owner: [SYSTEM] Terminal name: OPA0: Image name: $1$DGA184:[SYS0.SYSCOMMON.][SYSEXE]MAIL.EXE Posix UID: -2 Posix GID: -2 (%XFFFFFFFE) Status: %SYSTEM-F-BADBUFLEN, specified buffer length is invalid or out-of-range This issue is corrected with this patch kit. 5.7.2 Images and/or Files Affected: [SYSLIB]MAILSHRP.EXE 5.7.3 VSI case identifier Jira UT-160 Netsuite 3859 5.7.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.8 Support procedure VSI$SUPPORT.COM added to SYS$MANAGER for all systems 5.8.1 Problem Description VSI$SUPPORT.COM is a DCL procedure written by VMS Software Support for analyzing supported systems. The tool takes a snapshot of system information important to assist OpenVMS technical support and customers to diagnose reported problems or identify potential problems. Submit VSI$SUPPORT at system startup and store the report in a known location. The reports are useful to compare system parameter settings, installed product versions and other system configuration changes that have occurred since the system boot. Prior to shutting down the system, submit or run VSI$SUPPORT and store the report in the known location. The reports provide an audit trail to compare and identify any differences between shutdown and reboot. For example, a system parameter change might not be written to the permanent database or recorded in the MODPARAMS.DAT file prior to system shutdown causing differences in behavior upon reboot. 5.8.2 Images and/or Files Affected: [SYSMGR]VSI$SUPPORT.COM 5.8.3 VSI case identifier None 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.9 PIPE command may hang in RWMBX state 5.9.1 Problem Description The PIPE command uses internal mailboxes to move data from one pipe stage to another. Due to a small timing window, a write request to a mailbox could get stuck in RWMBX state forever because it finds no available mailbox quota to use. The problem is corrected with this patch kit. 5.9.2 Images and/or Files Affected: [SYS$LDR]SYS$PIPEDRIVER.EXE 5.9.3 VSI case identifier Jira BO-940 Netsuite 3686 5.9.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.10 Bogus behavior attempting to use x86 images on I64 system 5.10.1 Problem Description Running an x86 image on an Itanium Server system results in a run-time error, usually an access violation (ACCVIO), rather than an image activation error message. With this change, the image activator on I64 now detects the image is for a different architecture and prints an activation error message. 5.10.2 Images and/or Files Affected: [SYS$LDR]IMAGE_MANAGEMENT.EXE [SYS$LDR]IMAGE_MANAGEMENT.STB 5.10.3 VSI case identifier Jira BO-293 5.10.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.11 INSTALL utility mistakenly accepts x86 images on I64 systems 5.11.1 Problem Description When using the INSTALL utility, installing an x86 image on an Itanium Server system may succeed, although this image cannot be run. With this change, the INSTALL utility on I64 detects that the image is for a different architecture, rejects the attempted INSTALL action, and prints an activation error message. 5.11.2 Images and/or Files Affected: [SYSEXE]INSTALL.EXE [SYSMSG]SYSMGTMSG.EXE 5.11.3 VSI case identifier Jira BO-293 5.11.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 6 PROBLEMS ADDRESSED FROM PREVIOUS KITS None 7 IMAGES OR FILES REPLACED: [SYS$LDR]IMAGE_MANAGEMENT.EXE Image name: "IMAGE_MANAGEMENT" Image file identification: "X-5" Image build identification: "XFWL-C6E-000114" Link identification: "Linker I02-37" Link Date/Time: 16-JUL-2022 08:06:19.13 Image Checksum (MD5): 8D3357EBADA2E1A9A54235AF978AA471 [SYS$LDR]IMAGE_MANAGEMENT.STB Checksum (MD5): 92314BC47B489ED4901800AFE7A4A51D [SYS$LDR]SYS$PIPEDRIVER.EXE Image name: "SYS$PIPEDRIVER" Image file identification: "X-5" Image build identification: "XFWL-C6E-000114" Link identification: "Linker I02-37" Link Date/Time: 16-JUL-2022 08:06:15.74 Image Checksum (MD5): DA84D4FED831396A2ADFDD9F814D3166 [SYSEXE]INSTALL.EXE Image name: "INSTALL" Image file identification: "X-35" Image build identification: "XFWL-C6E-000114" Link identification: "Linker I02-37" Link Date/Time: 16-JUL-2022 08:06:18.35 Image Checksum (MD5): AD7D90D78F94EAF54D0D4B567466E5E8 [SYSEXE]OPCOM.EXE Image name: "OPCOM" Image file identification: "X-16" Image build identification: "XFWL-C6E-000114" Link identification: "Linker I02-37" Link Date/Time: 16-JUL-2022 08:06:17.67 Image Checksum (MD5): 003B5C3E680E34C84DAF882DE4409FF3 [SYSEXE]SET.EXE Image name: "SET" Image file identification: "X02-00" Image build identification: "XFWL-C6E-000114" Link identification: "Linker I02-37" Link Date/Time: 16-JUL-2022 08:06:59.07 Image Checksum (MD5): 51176D1ECD0852A10599B92449D24DAA [SYSEXE]SHOW.EXE Image name: "SHOW" Image file identification: "X-8" Image build identification: "XFWL-C6E-000114" Link identification: "Linker I02-37" Link Date/Time: 16-JUL-2022 08:06:58.77 Image Checksum (MD5): DC7870346FCEE0DC383F774832ADB75D [SYSLIB]MAILSHRP.EXE Image name: "MAILSHRP" Image file identification: "X-4" Image build identification: "XFWL-C6E-000114" Link identification: "Linker I02-37" Link Date/Time: 16-JUL-2022 08:05:59.99 Image Checksum (MD5): A6C680697032BCDB45EF8ED353B42AE6 [SYSMGR]UTC$TIME_SETUP.COM Checksum (MD5): 20646769211602302ECED0FE0013B090 [SYSMGR]VSI$SUPPORT.COM Checksum (MD5): E99DC2B5212A03BC80965E8AC64D1A2B [SYSMSG]SYSMGTMSG.EXE Image name: "SYSMGTMSG" Image file identification: "X-4" Image build identification: "XFWL-C6E-000114" Link identification: "Linker I02-37" Link Date/Time: 16-JUL-2022 08:06:17.98 Image Checksum (MD5): 76100052B051524C9D2CCB0178CDB5D4 [SYSUPD]SPKITBLD.COM Checksum (MD5): 2354B37F51B419B1F816D01E56BD2F17 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 as a self-extracting ZIPEXE file. To expand this file to the installable PCSI kit, execute the file image with the following command: $ RUN VMS842L3I_UTILITY-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 VMS842L3I_UTILITY [/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. 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 2022 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_UTILITY-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 VMS842L3I_UTILITY/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