RTL V10.0 ECO Kit for VSI OpenVMS

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 Disclaimer of Warranty and Limitation of Liability Statement.

A reboot is mandated as part of installing this kit, performed automatically following the kit installation.

VSI OpenVMS for the x86-64 architecture uses a memory disk image, stored on the system disk, when booting the system. The content of the memory disk must remain consistent with the system disk content.

This kit updates the memory disk image and invokes a system reboot sequence (shutdown with reboot) directly as part of the kit installation. You must be prepared to allow the system reboot when installing the kit. After all other kit actions are complete, the system will automatically shutdown and reboot.

If you allow the reboot, you will have the choice of whether to invoke the site-specific shutdown procedure, SYS$MANAGER:SYSHUTDWN.COM during the shutdown portion of the reboot.

By default, after installation completes, the minutes until shutdown is zero. If you wish to leave additional time before the shutdown begins, define the system logical name SHUTDOWN$MINIMUM_MINUTES as the integer value of the wait time in minutes. For example:

$ DEFINE/SYSTEM SHUTDOWN$MINIMUM_MINUTES 10

No other options for the shutdown may be specified.

The shutdown will commence directly after the memory disk update as the final portion of the kit installation.

VSI OpenVMS x86-64 V9.2-3

This kit will create a new memory disk image file during PRODUCT INSTALL or PRODUCT UNDO PATCH operations. This file is required for x86-64 systems bootstrap. If this file cannot be correctly created, the target disk will not be bootable and you will need to restore from backup.

During PRODUCT INSTALL, the kit will check for sufficient space on the target disk. The minimum free space is 600,000 blocks to ensure that the memory disk image file and kit files can safely fit on the disk.

Additionally, a check is made to determine if the disk is too fragmented to correctly create the memory disk file. If either check fails, the installation will be aborted before making any changes. After you take any necessary corrective actions to free up disk space or defragment the volume, the PRODUCT INSTALL can be re-attempted.

These same checks are not automatically handled by the kit before a PRODUCT UNDO PATCH operation. This is not a frequent operation for customer systems. Should you need to remove this kit, you should ensure sufficient disk space before you start. The same 600,000 block minimum applies. To check fragmentation requirements, you can use the following commands:

$ ANALYZE/DISK/EXTENTS/REQUIRED=200000/NOOUTPUT disk
$ SHOW SYMBOL ANALYZE$REQUIRED_EXTENTS

If the symbol value is 25 or more, the disk is too fragmented and you should defragment it before using PRODUCT UNDO PATCH. You can accomplish this using a defragmentation tool or by restoring an image backup.

This kit is provided for download within a ZIP archive container file.

Info-ZIP's freeware ZIP and UNZIP tools are provided for use on this VSI OpenVMS version. Your site may have already set up symbols for these tools or other equivalent ZIP tools. If not, use the following command to define a symbol to run the UNZIP image:

$ UNZIP == "$SYS$SYSDEVICE:[VMS$COMMON.SYSHLP.UNSUPPORTED.UNZIP]UNZIP"

Then invoke UNZIP to unpack the kit using the command:

$ UNZIP VMS923X_RTL-V1000

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.

Install this kit with the POLYCENTER Software Installation Utility by logging into the SYSTEM account and typing the following command at the DCL prompt:

$ PRODUCT INSTALL VMS923X_RTL [/SOURCE=location-of-kit]

The kit location may be a 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, "User-Selectable Control Options and Scripting Considerations" for further details.

Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt.

Should you need to remove this kit via PRODUCT UNDO PATCH, the same mandated reboot requirement is in effect as the memory disk image is changed back to the prior system content.

The kit will update the memory disk image automatically as the final part of installation. There is currently no mechanism within the PCSI utility to cleanly invoke a system reboot for PRODUCT UNDO PATCH.

You will be instructed as the kit exits that you must perform this function manually in this case.

%INSTALL-I-NONRESSHRADR, image installed ignoring '/RESIDENT' image_name
                -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint region

%INIT-F-GHREGIONFULL, An allocation was attempted from GH region GH_RES_CODE_S2 but
                there is not enough space in the region for the allocation.

There is not enough space on the memory disk.
                You must take these steps now to complete this installation:
                
                -  Run @SYS$UPDATE:SYS$MD
                -  Reboot the system

Additional documentation for CRTL ECO V10.0 functionality included in this kit 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_ECO10_RELEASE_NOTES.TXT
• SYS$HELP:VSI_OPENVMS_CRTL_ECO10_RELEASE_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 extraction from the ZIP archive as described above in Section 8.1, ''Compressed File''.

To extract the VSI_OPENVMS_CRTL_ECO10_RELEASE_NOTES.TXT file and the standard kit release notes, use the command:

$ PRODUCT EXTRACT RELEASE_NOTES VMS923X_RTL /VERSION=V10.0

To extract the PDF format additional documentation, use the command:

$ PRODUCT EXTRACT FILE VMS923X_RTL /VERSION=V10.0 /SELECT=*.PDF

Either of these commands will create a local copy of the desired file(s) in the current default directory.

An update for the HELP CRTL online help that corresponds to these changes will be contained in a future ECO update kit.

This ECO kit replaces the C RTL shareable image, DECC$SHR.EXE. On VSI OpenVMS x86-64 systems, DECC$SHR.EXE resides within the memory disk used during system boot.

This kit requires extra space on the existing memory disk for correct installation of DECC$SHR.EXE. As such, this may require that an extra invocation of SYS$MD and a subsequent system reboot be performed during the kit installation process. Note that this is in addition to the usual mandatory reboot that the kit will perform automatically after successfully finishing all other kit activity.

The kit will correctly determine whether there is sufficient space on the existing memory disk to allow the complete installation without an additional reboot. The kit will guide the user with what actions to perform if an additional interim reboot is required.

To predict the need for an additional reboot, refer to the summary below based on initial free blocks of space on the existing memory disk. You can determine the current free blocks on the memory disk using the following command:

$ SHOW DEVICE/UNITS=BLOCKS SYS$SYSDEVICE_MD:

Kit Behavior Depending on Initial Memory Disk Free Blocks:

The potential extra reboot and extra memory disk free space are required only for this particular ECO kit. Once this kit is installed, any future updates to the DECC$SHR.EXE image will not have such extreme memory disk free space requirements.