Chapter 1
ptx/LICENSE V2.0.0 Release Notes


Introduction

These release notes support Version 2.0.0 of the ptx® /LICENSE software. We recommend that you read these release notes before installing this software on your system.

ptx/LICENSE provides a variety of licensing models that enable software providers to enforce the license agreements established with their customers.


Product Compatibility and Prerequisites

The following products are prerequisites for ptx/LICENSE V2.0.0:


ATTENTION

In order to properly configure ptx/LICENSE, ptx/TCP/IP should be installed and configured for networking prior to configuring ptx/LICENSE.



Software Installation

This section contains instructions for installing ptx/LICENSE. You should be familiar with the ptx/INSTALL procedures and with the ptx/ADMIN® menu system. The DYNIX/ptx and Layered Products Software Installation Release Notes describes the installation procedure used for all products. The ptx/LICENSE release notes contain installation information that is specific to the ptx/LICENSE product. For supplementary information about ptx/INSTALL, refer to the ptx/INSTALL Software Installation Guide.


ATTENTION

If you are using software products that are installation-licensed, you do not need to install ptx/LICENSE.



ATTENTION

If you are running a previous version of ptx/LICENSE, use ptx/INSTALL to deinstall that version of ptx/LICENSE. Removing a previous version of ptx/LICENSE does not remove the old license database; you can use this database again if you choose.

Either of the following messages indicate that a previous version is still installed, and needs to be deinstalled:

Checking for running daemons...
The following daemons are running:
netlsd glbd llbd

You need to shut down these Daemons
before you can install.

or,

Checking for License V1 installation
ptx/License V1 is still installed.
You must use menu to remove it before 
proceeding.


ATTENTION

If you see the following message:

The following daemons are running:
 I4lmd I4glbcd glbd llbd 

 You need to shut down these Daemons 
 before you can install.

issue the command /opt/ifor/ls/bin/I4stop to shut down the Daemons.


Follow the procedure as described in the DYNIX/ptx and Layered Products Software Installation Release Notes to install the ptx/LICENSE software.

  1. Once you have selected ptx/LICENSE as a software package to install, the following screen is displayed:

    If you have license keys for License
    Vers. 1 that have not been enrolled,
    you should enroll them before upgrading
    to License Vers. 2.
        To Continue installing License Vers 2 ..
          Y) To install the ptx/License product
          N) To quit.
    

    If you are not running ptx/LICENSE V1.x.x, or have enrolled all of the ptx/LICENSE V1.x.x license keys which have been provided, answer Y, otherwise answer N.

    If you answer Y, you will then see the following:

    Checking for running daemons...
    No daemons running.
    Checking for License V1 installation
    No ptx/License Ver. V1 database detected.
    Press RETURN to continue
    

  2. The actions which occur next will depend upon whether or not you were previously running ptx/LICENSE V1.x.x, and the type of installation you have chosen.


ROOT Installation

During installation the ptx/LICENSE V1.x.x database and nodelock files are automatically migrated to ptx/LICENSE V2.0.0. No other actions are required by the user. During the migration process, the user will see the following:

Copying and Converting V1.x.x license database...
db file /var/ifor/lic_db has been successfully migrated **

After the migration completes, a reminder will be displayed to configure the license server:

NOTE: Run /opt/ifor/ls/bin/i4config_init.ksh        
      Refer to the release notes or the 'ptx/License
      Administration Guide'.          


ALT DISK DELTA Installation

During installation, if you are booted from the original root disk, the ptx/LICENSE V1.x.x database and nodelock files are automatically copied to the new partition, and the following message is displayed:

NOTE: Run /opt/ifor/ls/bin/i4dbmigrate
      after rebooting from new partition.

In addition, a reminder will be displayed to configure the license server:

NOTE: After rebooting from new partition    
      run /opt/ifor/ls/bin/i4config_init.ksh         
      Refer to the Release Notes, or the 'ptx/License
      Administration Guide'.


SCRATCH and INIT ALT DISK DELTA Installations

ptx/LICENSE V1.x.x database and nodelock files are neither copied nor migrated to the new partition; however, a reminder will be displayed to configure the license server:

NOTE: After rebooting from new partition    
      run /opt/ifor/ls/bin/i4config_init.ksh     
      Refer to the Release Notes, or the 'ptx/License
      Administration Guide'.

From this point on, the installation continues as described in the DYNIX/ptx and Layered Products Software Installation Release Notes with creating a preview log for each product, resolving file conflicts, and recompiling the kernel, if necessary. After installation completes, the License Server must be configured as described in the "License Server Configuration" section that follows.


License Server Configuration

See the ptx/LICENSE Administration Guide, "Setting Up Your Servers and Clients," for an explanation of configuring the License Server and a description of the i4config command.


ATTENTION

Do not mix different versions of ptx/LICENSE license servers in the same cell. Also, do not put license servers from any other license management product in the same cell as ptx/LICENSE. License management functionality can vary between products at different release levels.


After the ptx/INSTALL installation completes, you need to run the following script to complete the license configuration:

/opt/ifor/ls/bin/i4config_init.ksh

Next, run this command to list the servers:

/opt/ifor/ls/bin/i4config -list

And lastly, run this command to check that ptx/LICENSE has been successfully installed:

/opt/ifor/ls/bin/i4tv

The output of this command should report that the license transaction is complete.


ATTENTION

Runtime-concurrent licensed products will not run unless the license server is running.



ATTENTION

If you configured the license server to be part of an Alternate Cell, copy the /var/ncs/glb_obj.txt file from the license server to the /var/ncs directory of all client nodes where the application will run.



Software Deinstallation

If you are no longer using ptx/LICENSE, you can delete the files making up the product.


ATTENTION

Deinstalling ptx/LICENSE will not delete the license database, the nodelock license file, or the user file.



ATTENTION

During Deinstallation the following messages are expected, and should be ignored:

/etc/ncs does not match BOM, not removed
/etc/rc0.d/K98ifor does not match BOM, not removed
/etc/rc2.d/S98ifor does not match BOM, not removed
/opt/ifor/ls/bin/i4gdb does not match BOM, not removed
/opt/ifor/ls/bin/i4llmd does not match BOM, not removed


For additional information on the deinstallation procedure, refer to the ptx/INSTALL Software Installation Guide.


Product Documentation

The following documentation is available on the online documentation CD or at http://webdocs.numaq.ibm.com/:

ptx/LICENSE Administration Guide

Kernel Parameters

Licensed software products that employ concurrent licensing use the User Datagram Protocol (UDP) to communicate with the license server. For each license transaction, the licensed product uses one UDP connection and the license server initially uses two UDP connections. Thus, with a large number of concurrent user license transactions, it may be possible to exceed the number of UDP Process Control Blocks configured within the kernel. If this occurs, the following message will be displayed on the system console:

WARNING: udp: Out of free PCB structures

If this occurs, users may not be granted a license to run licensed software products. To prevent this from occurring, increase the value of the N_UDP_PCB_FREE kernel parameter.


Problem Report Summary


Open Problem Reports

There are no open problems with this release.


Fixed Problem Reports

There are no fixed problems with this release.