Chapter 1
ptx/LICENSE V1.1.1 Release Notes


Introduction

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


Product Compatibility and Prerequisites

ptx/LICENSE V1.1.1 supports the runtime licensing of Micro Focus® COBOL V4.0 on your system.

The following products are prerequisites for ptx/LICENSE V1.1.1:


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 either nodelock-licensed or installation-licensed, you do not need to install ptx/LICENSE.


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:

                        license_instl

    ptx/LICENSE Installation

    ptx/LICENSEconsists of two components: 1
    NCS runtime and
    Administrator Runtime Kit (ARK)
    Not all components need to be installed.
    Enter the type of installationyou want:
    1) NCS and ARK (complete product)
    2)Server administration tools only
    (part of the ARK)

    Selecting 1 (the default) will install the complete product (NCS and ARK). This allows the system on which you are installing ptx/LICENSE to act as a license server, as well as perform administrative functions on license servers on any node. Additional questions will be asked.

    Selecting 2 will install only the server administration tools (part of the ARK). This allows the node to perform only administrative functions on license servers on other nodes. No further ptx/LICENSE-specific questions will be asked; the installation process will complete and then terminate.


    ATTENTION

    Choose option 1 if you intend to use any runtime-concurrent licensed1 product on this node.


  2. If you selected to install the complete product (option 1 above), the following question is displayed:

                        license_instl

    ptx/LICENSE Installation

    Do you wantto configure ptx/LICENSE? y

    ATTENTION

    Answer y if you have already installed and configured ptx/TCP/IP for networking and intend to use runtime-concurrent licensed products on this node. Answer n if ptx/TCP/IP is not installed or configured on this node. If you answer n, you will be required to manually configure this node as a license server (see the ptx/LICENSE Administration Guide for instructions on how to do this). No further questions will be asked; the installation process will complete and then terminate.


    If you answer y (the default), the installation will configure the cell2 to which the server is added, and the following information will be displayed:

    NCS must be properlyconfigured and initialized
    for ptx/LICENSE to function properly.
  3. Next, the following choices are displayed:

                       license_instl

    ptx/LICENSE Installation

    Enter your choice for system Cell Name: 2
    1) Continue with installation without
    choosing a Cell Name.
    2) Use the default for system Cell Name.
    3) Create a new alternatecell for
    system Cell Name.
    4) Choose an existingalternate cell
    for system Cell Name.

    ATTENTION

    Option 4 appears only if there are existing alternate cells configured in the network.


    If you select 1 to continue installation without choosing a Cell Name, ptx/LICENSE will not function. Selecting 2 (the default) will add this license server to the default cell. (The system nodename will be used as the default cell name.) Selecting 3 will set up this server in a new alternate cell. Selecting 4 will present you with a selection box from which you choose an alternate cell.

    After making your selection, the following question is displayed:

                      license_instl

    ptx/LICENSE Installation

    Do you wantto setup the netlsd license y
    server andthe location broker daemons,
    llbd and glbd, to start automatically
    when the machine reboots?

    Answering y will update the files in /etc/rc[02].d and automatically start the server when the machine reboots.

    If you answer n, the netlsd, llbd, and glbd servers will need to be started manually each time the system is rebooted.


ATTENTION

If you are installing an alternate disk, answering y will cause ptx/LICENSE to be configured and started when you boot from the alternate disk.

If you answer n, ptx/LICENSE will need to be manually configured and started when you boot from the alternate disk.



ATTENTION

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


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.


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.


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


Related Documentation

The following document accompanies the ptx/LICENSE product:

ptx/LICENSE Administration Guide 1003-72402-00


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 offree 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


Fixed Problems

The following problem was fixed in this release:


Open Problems


Stale Entries in the GLB database (220693)

If it takes a long time to acquire a license, the problem may be related to stale entries in the global location broker (GLB).

Workaround. Run lb_admin on the offending server:

# /etc/ncs/lb_admin
lb_admin: clean
lb_admin: use global
lb_admin: clean

lb_find Hangs During ptx/LICENSE Configuration Process (230893)

If the system ptx/LICENSE is being installed on has an FDDI network interface configured, in the "not running" state, the lb_find utility will hang causing the software installation process to hang.

Similarly, if an attempt is made to manually configure ptx/LICENSE using the netls_config script, lb_find will hang if the FDDI network interface is configured but in the "not running" state.

Workaround. Either deconfigure the FDDI network interface or put it in the "running" state.


Footnotes

1. A concurrent license allows as many user to use a software product at the same time as there are licenses for the product, until the licenses expire. Refer to the ptx/LICENSE Administration Guide for more information.

2. A cell is a subset of a network or internet in which all hosts use the same Global Location Brocker object UUID. Refer to the ptx/LICENSE Administration Guide for more information.

3. The Global Location Broker daemon (glbd) database stores the locations of objects and interfaces throughout a network or internet. Refer to the ptx/LICENSE Administration Guide for more information.