NOMAD 7.50 License File

NOMAD 7.50 - License File

NOMAD License File to ease upgrade and disaster recovery

When customers are upgrading their CPUs or performing disaster recovery, the new NOMAD "license file" capability will allow sites to apply a new CPUID (CPU password) without a re-installation of NOMAD.

VM

With version 7.50 under VM, you can place CPUID product passwords, expiration dates, and extensions into a product license file rather than installing them through the $NOMOPTS ASSEMBLE file. Using a product license file makes it easier to change passwords if you upgrade your processor, or subsequently purchase add-on products for which new extensions are provided, since there’s no need to re-assemble $NOMOPTS and re-install NOMAD. You simply change or add the new passwords or extensions to the license file. Using a license file will also enable you to easily get the products up and running on a different processor for disaster recovery, where you may not have the installation files needed to install CPUID passwords and extensions through the $NOMOPTS ASSEMBLE file.

If you plan to use an external license file for disaster recovery/upgrades, install NOMAD version 7.50 with $NOMOPTS parameters enabling this feature.

OS/390

As of version 7.50 under OS/390, access to NOMAD products can be dynamically activated by running the NLICENSE program. A started procedure is implemented to run at IPL time to activate product access. NLICENSE activates product access based on license information contained in the NOMAD license file which provides CPUID product passwords, expiration dates, and extensions. The NLICENSE program can also be run at any time by an authorized user as a started task, batch job, or from a TSO/E foreground session to update license information from new CPUID product passwords and extensions.

Using NLICENSE to activate product access makes installing CPUID passwords, expiration dates, or extensions in the $NOMOPTS options module optional, and allows you to install new CPUID product passwords and extensions without re-APPLYing the MNOMOPT SMP/E USERMOD or changing the contents of the product LINKLIB.

The external license file can be implemented via parameters in $MVSOPTS during the NOMAD version 7.50 installation, or dynamically by running LICENABL.

VM and OS/390 License File


	--------------------------------------------------------------------- * CPUID: CPUID product password --------------------------------------------------------------------- 1) CPUID=(AAAAAAAAAAAAAAAAAAAA,BBBB) Temporary Password 2) CPUID=CCCCCCCCCCCCCCCCCCCC Permanent Password --------------------------------------------------------------------- * CPUX: CPUID extension passwords * --------------------------------------------------------------------- 1) CPUX=DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD Extension for CPUID pswd #1 2) CPUX=EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE Extension for CPUID pswd #2

Above is an example of a license file for a site that has one temporary and one permanent password.

Learn More

To find out more about how Select Business Solutions can help you either Contact Us, or visit our Product Resources area for all the latest related downloads.