PERFMGMT V3.1-1 ECO1 Kit for VSI OpenVMS x86-64

INSTALL_2: To be installed by all customers using the following feature(s):

• OpenVMS x86_64 V9.2-4
• VSI Performance Management for OpenVMS v3.1-1

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.

No reboot is necessary after installation of this kit.

However if the IMAGE_SECURITY parameter is set to a value greater than one, or secure boot was enabled during the last boot, you should execute the Performance Management Agent startup procedure:

$ @SYS$STARTUP:PERF$AGENT$STARTUP.COM

VSI OpenVMS x86-64 V9.2-3 or higher

Problem Description

VSI Performance Management V3.1-1 will not function correctly on VSI OpenVMS x86-64 E9.2-4 when Secure Boot is enabled or the IMAGE_SECURITY parameter is set to a value higher than 1.

Images and/or Files Affected

• SYS$LOADABLE_IMAGES:PSDC$LOADABLE_IMAGE.EXE
• SYS$LOADABLE_IMAGES:PSDCTIMER.EXE

VSI Case Identifier

Jira BSS-156

Release Version of VSI OpenVMS That Will Contain This Change

Not applicable

Workaround

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 X86VMS-PERFMGMT-V0301-1-ECO1.ZIP

This will extract the installable VMSINSTAL product kit files and their associated signed manifest (_VNC file), used for kit validation during VMSINSTAL commands.

VSI strongly recommends always using the manifest to validate the kit content during any VMSINSTAL commands. This will occur automatically if the files are both contained in the same directory.

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

$ @SYS$UPDATE:VMSINSTAL VPA031 <name-of-directory-where-the-kit-is-located>

None of the files replaced by this installation are contained in the system memory disk, therefore it does not need to be updated.