VMS Software / Documentation / AUTOGEN V3.0 ECO Kit for VSI OpenVMS IA-64

AUTOGEN V3.0 ECO Kit for VSI OpenVMS IA-64

Release Notes

Publication Date: April 2026

Operating Systems:
VSI OpenVMS IA-64 Version 8.4-1H1
VSI OpenVMS IA-64 Version 8.4-2
VSI OpenVMS IA-64 Version 8.4-2L1
VSI OpenVMS IA-64 Version 8.4-2L3
Kit Name:
VMS842L3I_AUTOGEN-V0300

1. Kit Name

VMS842L3I_AUTOGEN-V0300

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

2.2. Reboot Requirement

No reboot is necessary after installation of this kit.

2.3. Version(s) of VSI OpenVMS to Which This Kit May Be Applied

  • VSI OpenVMS IA-64 Version 8.4-1H1
  • VSI OpenVMS IA-64 Version 8.4-2
  • VSI OpenVMS IA-64 Version 8.4-2L1
  • VSI OpenVMS IA-64 Version 8.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

  • VMS842L1I_AUTOGEN-V0100
  • VMS842L1I_AUTOGEN-V0200

4. Kit Dependencies

VMS841H1I_NOTARY-V0200 (if installing on V8.4-1H1)
VMS842I_NOTARY-V0200 (if installing on V8.4-2)

All VSI OpenVMS ECO kits now require the Notary V2.0 patch kit for their respective version of VSI OpenVMS. This is to ensure correct validation regardless of the manifest version in use.

The Notary V2.0 kit named above which matches the version of VSI OpenVMS being updated is required for this kit to install.

VMS842L1I_UPDATE-V0100 (if installing on V8.4-2L1)

All new ECO kits for VSI OpenVMS IA-64 V8.4-2L1 require the VMS842L1I_UPDATE-V0100 kit.

None (if installing on V8.4-2L3)

5. Problems Addressed in This Kit

5.1. AUTOGEN May Incorrectly Report That a Page or Swap file is Inaccessible

Problem Description

If an existing page or swap file has a size of 100,000,000 blocks or larger, AUTOGEN may issue an error indicating that the file is inaccessible.

This problem is corrected with this patch kit.

Images and/or Files Affected

[SYSUPD]AUTOGEN.COM

VSI Case Identifier

  • Jira UT-156
  • NetSuite NS3725

Release Version of VSI OpenVMS That Will Contain This Change

Next VSI OpenVMS IA-64 release after V8.4-2L3

Workaround

If you have page or swap files that are 100,000,000 blocks or larger, you can avoid the error report by setting PAGEFILE=0 and SWAPFILE=0 in MODPARAMS.DAT. In doing this, AUTOGEN will no longer examine or adjust the sizes of page and swap files.

6. Problems Addressed From Previous Kits

6.1. AUTOGEN May Not Calculate WSMAX Correctly

Problem Description

The calculation of WSMAX by AUTOGEN was modified in OpenVMS V8.4-2 when AUTOGEN_LM.COM (large memory AUTOGEN) and AUTOGEN.COM were merged. The calculation for WSMAX began to produce a value which significantly diverged from older versions of AUTOGEN.

For small memory systems (less than 96 gigabytes), the calculated value is less than it used to be, which could cause performance degradation due to smaller working sets.

For larger memory systems, the calculated value is more than previous versions. This may cause "insufficient virtual memory" errors if the value is not properly sized for the actual amount of physical memory present.

This patch kit corrects the calculation for WSMAX for systems of any memory size. The calculation for WSMAX from AUTOGEN is intended to provide a reasonable value for most environments. If your system has particular working set requirements you can adjust the behavior of AUTOGEN using MODPARAMS.DAT and specifying minimum and maximum values for WSMAX.

An additional problem with the calculation for WSMAX would ignore overrides from MODPARAMS.DAT. This problem has also been corrected.

The SYSGEN help for system parameter WSMAX has been updated to clarify the setting produced by AUTOGEN.

Images and/or Files Affected

  • [SYSUPD]AUTOGEN.COM
  • [SYSHLP]SYSGEN.HLB

Quix and/or Bugzilla cases reporting this problem

VSI Bugzilla 789

Release Version of OpenVMS that will contain this change

VSI OpenVMS IA-64 V8.4-2L3

Workaround

In an emergency, boot interactively and set the value for WSMAX in SYSBOOT, or use SYSGEN to update WSMAX in the CURRENT parameters before a reboot. VMS Software Inc. strongly recommends applying this patch kit and then using AUTOGEN rather than taking either of these extreme steps unless absolutely necessary.

6.2. Calculation of GBLPAGES Too Low on Large Memory Systems

Problem Description

On systems with more than 1TB of memory, GBLPAGES could accidentally be set to a much lower value than expected.

The interaction between GBLPAGFIL and GBLPAGES with very large memory systems could lead to an incorrect calculated value for GBLPAGES.

This issue has been corrected.

Images and/or Files Affected

  • [SYSUPD]AUTOGEN.COM

Quix and/or Bugzilla cases reporting this problem

None

Release Version of VSI OpenVMS that will contain this change

VSI OpenVMS IA-64 V8.4-2L3

6.3. System Dumpfile Could Be Incorrect on Very Full System Disks

Problem Description

Under some circumstances a new SYSDUMP.DMP file of length 0 blocks was created if there was insufficient space on the system disk to extend both the pagefile and dumpfile.

This behavior has been corrected such that if there is not enough room to extend both files, the system dumpfile will not be changed.

Images and/or Files Affected

  • [SYSUPD]AUTOGEN.COM

Quix and/or Bugzilla cases reporting this problem

None

Release Version of VSI OpenVMS that will contain this change

VSI OpenVMS IA-64 V8.4-2L3

6.4. AUTOGEN Failure with %DCL-W-UNDSYM Error

Problem Description

Under some circumstances AUTOGEN could fail with the error:

%DCL-W-UNDSYM, undefined symbol - check validity and spelling
 \USER_DEFINED\

Typically this would occur if there was an error in MODPARAMS.DAT or an included parameter data file that AUTOGEN attempted to automatically correct to a symbol assignment.

This problem has been corrected.

Images and/or Files Affected

  • [SYSUPD]AUTOGEN.COM

Quix and/or Bugzilla cases reporting this problem

VSI Bugzilla 767

Release Version of VSI OpenVMS that will contain this change

VSI OpenVMS IA-64 V8.4-2L3

6.5. Spurious "No Such Device Available" Error During OpenVMS Installation

Problem Description

During the first boot of a newly installed OpenVMS system disk, a spurious "no such device available" was issued during the initial AUTOGEN of the system. The system would then continue normally, calculating parameter values for rebooting the system for customer use.

The initial installation startup procedure has been modified to load the pipe driver so that AUTOGEN may use PIPE commands in that environment, avoiding the "no such device" error.

Images and/or Files Affected

  • [SYSEXE]INS_STARTUP.COM

Quix and/or Bugzilla cases reporting this problem

VSI Bugzilla 2435

Release Version of VSI OpenVMS that will contain this change

VSI OpenVMS IA-64 V8.4-2L3

6.6. Remote Shadow Set Members Might Be Missed During AUTOGEN

Problem Description

Under rare circumstances, remote shadow set members on the current system running AUTOGEN might accidentally be skipped, which could lead to confused shadowing parameter behavior.

This issue has been corrected.

Images and/or Files Affected

  • [SYSUPD]AUTOGEN.COM

Quix and/or Bugzilla cases reporting this problem

VSI Bugzilla 2435

Release Version of VSI OpenVMS that will contain this change

VSI OpenVMS IA-64 V8.4-2L3

7. Images or Files Replaced

[SYSUPD]AUTOGEN.COM
File creation date and time:4-APR-2026 00:42:48.65
Checksum (MD5):63A28DCB4DCD7A0CF748F7B8E51510E8
[SYSEXE]INS_STARTUP.COM
File creation date and time:4-APR-2026 00:44:52.64
Checksum (MD5):617B689ECE6392DC85B58C358FD15ABD
[SYSHLP]SYSGEN.HLB
File creation date and time:4-APR-2026 00:39:50.91
Checksum (MD5):EDDA2D773964FA0303BE4A21C12694B5

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 (in MD5 format) are supplied 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 ECO 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 an ECO 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 filename 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_AUTOGEN-V0300

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.

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/community/freeware/.

8.2. Installation Command

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 VMS842L3I_AUTOGEN [/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, "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.

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 2026 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_AUTOGEN-V0300--4

Note

The terms "ECO kit" and "patch kit" may be used interchangeably in this document. This also applies for other VSI OpenVMS documentation when describing PCSI kits that provide remedial updates to a particular product.

A. User-Selectable Control Options and Scripting Considerations

A.1. 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 OpenVMS ECO 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 updates, followed by a Do you want to continue? YES/NO question, default is 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 is 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 is 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 a VSI OpenVMS ECO kit regarding the initial questions, define one or more of the following logical names before issuing the PRODUCT INSTALL command.

  • To skip one or more of the questions, define the corresponding logical name shown here to YES:

    SKIP$BACKUPSkips system backup awareness question.
    SKIP$REBOOTSkips system reboot awareness question.
    SKIP$ARCHIVE_OLDSkips question about saving "_OLD" files. This will take the default, which is NO.
    SKIP$INTROSkips all three of the above questions.

  • To specifically override the default for saving "_OLD" files, define this logical name to YES or NO:

    VSIKIT$ARCHIVE_OLDSets an answer for saving "_OLD" files behavior. This will skip the archive "_OLD" files question regardless of the above SKIP$* logical names.

  • Two additional logical names may be defined as YES to modify the amount of explanatory text displayed for each question:

    VSIKIT$VERBOSEShows all explanatory text for questions.
    VSIKIT$BRIEFSkips 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 kitname

A.2. 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 (for example, if aborting the current operation may have side effects for the system). Additionally, note the following:

    • 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 that provides the particular value, such as VSIKIT$ARCHIVE_OLD.

A.3. 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_AUTOGEN/VERSION=V3.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=location_of_the_kit

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.

A.4. Deprecated Logical Names From HPE ECO Kits

The three names listed below were used by older VSI OpenVMS ECO kits for compatibility with HPE ECO 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 NameNew Name
NO_ASK$BACKUPSKIP$BACKUP
NO_ASK$REBOOTSKIP$REBOOT
ARCHIVE_OLDVSIKIT$ARCHIVE_OLD