Programming with VisualAge for Java/IBMVJAVA.ISO/icswinnt/iforls/arkdoc.z/i4bu1mst.INF

OS/2 Help File | 1996-07-24 | 214.0 KB | 3,625 lines

ΓòÉΓòÉΓòÉ 1. Version Notice ΓòÉΓòÉΓòÉ

This edition applies to the licensed program License Use Runtime Version 1.0,
Program Number ????-???, and to all subsequent releases and modifications until
otherwise indicated in new editions. Make sure you are using the correct
edition for the level of the product.

Order publications through your IBM representative or the IBM branch office
serving your locality. Publications are not stocked at the address given below.

A form for reader's comments is provided at the back of this publication. If
the form has been removed, address your comments to:

      Distribution Products End-User Technologies
      Rome Networking Software Laboratory
      IBM SEMEA S.p.A.
      Piazzale G. Pastore, 6
      00144 Rome
      Italy
      Fax Number : ([phone]
      Internet ID: ROMERCF at VNET.IBM.COM

 When you send information to IBM, you grant IBM a non-exclusive right to use
 or distribute the information in any way it believes appropriate without
 incurring any obligation to you.

  (C) Copyright 1994, 1995 Gradient Technologies Inc.


ΓòÉΓòÉΓòÉ 2. Notices ΓòÉΓòÉΓòÉ

References in this publication to IBM products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not intended
to state or imply that only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any
of IBM's intellectual property rights may be used instead of the IBM product,
program, or service. Evaluation and verification of operation in conjunction
with other products, except those expressly designated by IBM, is the user's
responsibility.

IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to the IBM Director
of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood NY 10594, United
States of America.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
P.O. Box 12195
3039 Cornwallis
Research Triangle Park, NC 27709-2195
USA

Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.


ΓòÉΓòÉΓòÉ 2.1. Readme.txt ΓòÉΓòÉΓòÉ

A readme.txt file is included in the License Use Runtime diskettes. The file is
installed in the product's target directory. It contains information about
enhancements or changes made to License Use Runtime after publications went to
press. It is recommended that you print it and store it with this book.


ΓòÉΓòÉΓòÉ 2.2. Trademarks and Service Marks ΓòÉΓòÉΓòÉ

The following terms are trademarks of the IBM Corporation in the United States
or other countries or both:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé AIX                  Γöé IBM        Γöé PS/2       Γöé
Γöé BookManager              Γöé Library Reader   Γöé RISC System/6000 Γöé
Γöé Current                Γöé NetView      Γöé TME 10 NetFinity Γöéerver
Γöé Extended Services           Γöé OS/2        Γöé VTAM       Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

Windows is a trademark of Microsoft Corporation.

PC Direct is a trademark of Ziff Communications Company and is used by IBM
Corporation under license.

UNIX is a registered trademark in the United States and other countries
licensed exclusively through X/Open Company Limited.

C-bus is a trademark of Corollary, Inc.

Other company, product, and service names, which may be denoted by a double
asterisk (**), may be trademarks or service marks of others.


ΓòÉΓòÉΓòÉ 3. About This Book ΓòÉΓòÉΓòÉ

This manual provides a guide to setting up the environment required to support
a licensed software product. Refer to Understanding License Use Runtime for
details on licensed products. In this book the SystemView License Use
Management Runtime for OS/2 (referred to as License Use Runtime) is described.
License Use Runtime is the product that manages the licenses of the licensed
products. This book contains information about how to install and configure the
servers that will have the licenses installed, and the clients that will use
the products. It also explains how end users can set up their machines to use
licensed products that do not need a server.

After the environment is set up and configured for the first licensed product,
the same environment supports all other licensed products.

Before reading this guide, follow the procedures described in the documentation
accompanying the software product you purchased.

License Use Runtime is a distributed application that uses communications
technology based on the Network Computing System** (NCS).

License Use Runtime is made up of the following components:

     Server Runtime Kit (SRK)
     Client Runtime Kit (CRK)
     Network Computing System (NCS)

 After you install and configure them, the CRK and SRK are completely
 transparent to the end users of the software products you purchased.

 Read this book to decide which License Use Runtime components you have to
 install and configure, and to install the licensed product licenses.


ΓòÉΓòÉΓòÉ 3.1. Who Should Read This Book ΓòÉΓòÉΓòÉ

This guide is intended for:

     The system administrator who is responsible for setting up and
      administering the product license management using License Use Runtime
      SRK.

      The skills required for a License Use Runtime system administrator are:

        -  General knowledge of OS/2
        -  General knowledge of the NetBIOS transport protocol, or of the
           TCP/IP transport protocol, or of the IPX transport protocol
        -  General knowledge of the network environment
        -  General knowledge of the NCS configuration

     The end users who run the software products on their client machines and
      install and configure the License Use Runtime CRK.

      Only a generic knowledge of the OS/2 operating environment is required by
      the end users, provided that they are supported by the system
      administrator in configuring the CRK.


ΓòÉΓòÉΓòÉ 3.2. How This Book is Organized ΓòÉΓòÉΓòÉ

This guide is divided into the following sections:

 Understanding License Use Runtime, provides an overview of License Use Runtime
           features and benefits, describes supported licensing models and
           license types, and outlines the operational components of License
           Use Runtime runtime environment.

 Setting Up Your Network Environment, provides the basic NCS concepts you need
           to set up your network and manage licenses with License Use Runtime,
           and gives you tips about how to organize your network.

 Installing License Use Runtime, gives you instructions on how to install and
           uninstall License Use Runtime components.

 -- Reference lumr not found --,, provides scenarios on configuring both client
           and server, and administering product licenses using the License Use
           Runtime tools.

 Hints and Tips, provides hints and tips to better take advantage of License
           Use Runtime, and information on how to implement a back up and
           recovery procedure.

 Troubleshooting, helps you to improve performance and to eliminate problems
           that can arise when you use products licensed with License Use
           Runtime.


ΓòÉΓòÉΓòÉ 3.3. Where to Find More Information ΓòÉΓòÉΓòÉ

This section lists other sources of information relating to License Use
Runtime.


ΓòÉΓòÉΓòÉ 3.3.1. Online Information ΓòÉΓòÉΓòÉ

The following online information is available for License Use Runtime.


ΓòÉΓòÉΓòÉ 3.3.1.1. Command-Line Syntax Help ΓòÉΓòÉΓòÉ

To obtain help with the syntax of the command-line interface, type the
following command on the OS/2 command line:

   HELP LUMCMD <command_name>

This will display the syntax for the License Use Runtime command line. For
example, to get help on the command i4nat you type:

   HELP LUMCMD i4nat


ΓòÉΓòÉΓòÉ 3.3.1.2. Message Help ΓòÉΓòÉΓòÉ

To obtain help for the Basic License Tool, the Configuration Tool, and the
Nodelock Administration Tool messages, type the following command on the OS/2
command line:

   HELP LUMMSG <message number>

where <message number> is only the message number. For example, if the message
that pops up when you are using the License Use Runtime has number ADM-10024,
you type:

   HELP LUMMSG 10024
An explanation of the message and instructions on to how to proceed are
displayed.


ΓòÉΓòÉΓòÉ 3.3.1.3. Message Reference ΓòÉΓòÉΓòÉ

It is an online book, and can be viewed online by double-clicking on its icon
in the License Use Runtime folder.


ΓòÉΓòÉΓòÉ 3.3.1.4. Command Reference ΓòÉΓòÉΓòÉ

It is an online book, and can be viewed online by double-clicking on its icon
in the License Use Runtime folder.


ΓòÉΓòÉΓòÉ 3.3.1.5. Using SystemView License Use Management Runtime for OS/2 ΓòÉΓòÉΓòÉ

This book is also available as an installable component of the License Use
Runtime, and can be viewed online by double-clicking on its icon in the License
Use Runtime folder.


ΓòÉΓòÉΓòÉ 4. Understanding License Use Runtime ΓòÉΓòÉΓòÉ

The objective of License Use Runtime is to control the use of licensed products
running in a networked environment.

Note:  License password, password, product password, license key, product key
       and key are used interchangeably in this book.

 The control is based on the following concepts:

     Product developers have to enable their products to protect them from
      improper use, by adding appropriate code. The product becomes
      license-enabled.

     License Use Runtime controls that customers have a license authorizing
      them to use the product at execution time, and not during installation.

     Product vendors must provide the users a protection key. The key (or
      password) contains an encryption of the terms of the contractual
      agreement (how many licenses or concurrent product copies the customer
      can use, the expiration date of the licenses, the type of license).

     Vendors can enforce various levels of security, using License Use
      Runtime. The levels are described in this manual. License Use Runtime can
      simply monitor the use of the license-enabled products without limiting
      their execution. This helps customers to manage directly their compliance
      to the contractual terms. License Use Runtime can instead be used to
      prevent customers from using more licenses than they purchased. This
      obliges customers to purchase a new password to extend the terms and
      conditions of the contract.

     This protection is provided using a client/server model. The model
      assumes that the license-enabled product runs on client workstations.

      The license use management functions are installed on the server system.
      The server must be connected to all the client workstations. The license
      information is stored on the server. The role of the server is to monitor
      the authorization to execute all the products that are license-enabled.

     The license can also be stored on the workstation where the
      license-enabled product is installed. In this case there is no need for a
      license server. These licenses are called nodelocked licenses.

 The license use management is accomplished with four components:

 License Use Toolkit           Used only by the software developer to enable
                               the product for license use management. It is
                               not part of License Use Runtime. It is a
                               separate product called License Use Management
                               Application Developer's Toolkit for OS/2.

 Server Runtime Kit            Must be installed on one or more workstations in
                               the network. These workstations contain the
                               license information and control the execution of
                               the license-enabled products. This component is
                               part of the License Use Runtime product. It is
                               also referred to as License Use Runtime Server.

 Client Runtime Kit            Installed on every workstation where a
                               license-enabled product is installed. This
                               component is part of the License Use Runtime
                               product. It is also referred to as License Use
                               Runtime Client.

 Network Computing System (NCS) Must be installed on all workstations where the
                               SRK is installed. This component is part of the
                               License Use Runtime product.


ΓòÉΓòÉΓòÉ 4.1. Understanding License Use Management Technology ΓòÉΓòÉΓòÉ

The strategic license management tools provided with License Use Management are
based on a client-server scheme technology. The client is a license enabled
product, and the server the license server which maintains a license database,
provides information to the license enabled product about the availability of
licenses, and maintains a count of the usage of the product. The combination of
a license server, the runtime client code, and the associated license database,
is collectively known as License Management System.

A license-enabled product is a product that has imbedded calls to the license
server, which can be located remotely in a node in the network, or locally in
the same node where the product is running. A meter-enabled product as well
calls the license server through a License Use Runtime process (metering
process). The purpose of the calls is to check if a license is available, and
to decide the behavior of the product based on the information provided by the
License Management System. A product makes calls to notify the License
Management System that a new use of the product is starting or ending,
providing up to date information about the actual usage of the product. The
overall process is depicted in details in Understanding Licensing Models.


ΓòÉΓòÉΓòÉ 4.2. Understanding License Types ΓòÉΓòÉΓòÉ

Licensed products that can be managed by IBM License Use Management for OS/2
are enabled by the software vendors. In the future most IBM products will be
enabled, and you will also be able to manage the use of other software
'companies' products.

A license generally gives you the right to run a single instance of a product.

This section describes the types of licenses you can get from the vendor with a
product enabled with License Use Toolkit.

     Nodelocked licenses
     Concurrent-access licenses
     Use-once licenses
 (See Understanding Licensing Models for a detailed description of licensing
 models.)


ΓòÉΓòÉΓòÉ 4.2.1. Using Products with Nodelocked Licenses ΓòÉΓòÉΓòÉ

A nodelocked license allows the use of a product at the particular node for
which the license was created and for as long as the license remains valid. A
good example for a nodelocked licensed product is a word processor. When you
purchase a nodelocked license for a product, the vendor associates the license
with the unique identifier (target ID) of the system where the license (and the
product itself) will reside.

A license server is not required to install or manage nodelocked licenses. The
Nodelock Administration Tool (NAT) on the client permits you to install and
manage nodelocked licenses.

An interactive interface and a command line interface of the Nodelock
Administration Tool are available on OS/2, Windows NT and Windows 95 clients.
The Nodelock Administration Tool command line interface only is available on
clients running:

     Windows 3.1
     Windows 3.11
     Windows for Workgroup

 The vendor could also develop a product with nodelocked licenses that you must
 handle differently. These licenses are called dynamic nodelocked.

 A dynamic nodelocked license has the same use as the nodelocked license.
 However, it is not directly installed on the client machine where the product
 will be used.

 Dynamic nodelocked licenses are installed on the license server using the
 Basic License Tool. The first time the end user uses the licensed product on
 the client, the client workstation requests the dynamic nodelocked license
 from the server, and, if available, it is granted to the client, where it gets
 installed. For later uses of the licensed product, the client has its own
 nodelocked license, and there is no need to request the license from the
 server.

 The vendor can develop a product with another type of nodelocked license
 called the concurrent nodelocked license.

 As a nodelocked license, the concurrent nodelock is bound to a particular
 node, it can be installed and managed by the Nodelock Administration Tool
 (NAT) on the client. Furthermore, it allows a limited number of users to run
 the licensed application simultaneously. A number must be specified with the
 NAT, indicating how many concurrent nodelocked licenses have been acquired for
 the product. The end user can modify this number at any time.

 The concurrent nodelocked licenses are not available on:

     Windows 3.1
     Windows 3.11
     Windows for Workgroup


ΓòÉΓòÉΓòÉ 4.2.2. Using Products with Concurrent Access Licenses ΓòÉΓòÉΓòÉ

A concurrent-access license is a server-based license which, under the
direction of the license server on which it is installed, can be temporarily
granted to run the product for which the license was created, on a client.

When the product is running, that license remains unavailable to other
instances of the product. When the product stops running the license is
returned to the server, where it again becomes available.

Concurrent-access licenses allow as many users to run a licensed software
application simultaneously as there are valid licenses for the product
available from the license servers in your licensing environment.


ΓòÉΓòÉΓòÉ 4.2.3. Using Products with Use-Once Licenses ΓòÉΓòÉΓòÉ

A use-once license is a server-based license that permits the single use of a
particular licensed product within the period for which the license is valid.
Use of a use-once license typically begins when the licensed product is
started. The use of a use-once license typically ends when the licensed product
stops running.

The precise conditions that constitute the beginning and completion of the use
of a use-once license are determined by the product's vendor.

Some vendors provide use-once licenses for their products to supplement
concurrent-access licenses during times when user demand for those products
exceeds the number of available concurrent-access licenses. The vendor designs
the product so that when all concurrent-access licenses for the product are in
use, a user can request an available use-once license. Many vendors also use
use-once licenses to safely distribute promotional or demonstration versions of
their software.


ΓòÉΓòÉΓòÉ 4.2.4. Enrolling Licenses ΓòÉΓòÉΓòÉ

License enabled products require a formal enrollment to place enrollment
certificate information in the license server database, or in the nodelock
file.

The enrollment certificate contains information about the product and the
access information to be used by the product. It is typically shipped with a
product on a diskette from which the enrollment information can be imported
(rather than entered from the system keyboard) using graphical tools: the Basic
License Tool and the Nodelock Administration Tool.

Also products you decide to meter-enable are enrolled through the Basic License
Tool.

As a result of the enrollment, an entry in a tamper resistant audit trail is
created.


ΓòÉΓòÉΓòÉ 4.3. Understanding Passwords ΓòÉΓòÉΓòÉ

Vendors of license-enabled software deliver licenses to use their products in
the form of a license password.

A license password (or license key) is an encrypted character string that
specifies the actual functional characteristics of the license that it
contains. This information, determined by the manufacturer, includes the
specific number and type of licenses contained in the password, the date when
the licenses become active, and the date when the licenses expire.

The vendor includes the password, along with other important information about
their application, in the enrollment certificate.

You use the Basic License Tool to add the password for the server based
licensed products, and the other information to the license database on a
particular license server.

You use the Nodelock Administration Tool (NAT) to add the password and the
other information about the nodelocked licenses on a License Use Runtime
client.

After you add the licenses, instances of the server-based licensed application
can locate license servers on which the appropriate licenses are installed and
request a license to execute. If the license request is granted, the requesting
application can run. Nodelock licensed applications as well can run on the
License Use Runtime client after the license is added to the client machine
itself.

Software vendors can create two distinct types of passwords: simple and
compound.


ΓòÉΓòÉΓòÉ 4.3.1. Simple Passwords ΓòÉΓòÉΓòÉ

Vendors of license-enabled software use simple passwords to provide multiple
concurrent-use and use-once licenses for vendor-managed use products (see
Vendor-Managed Use Products) and to provide nodelocked licenses for
nodelock-licensed products.

Simple passwords contain a specific number of licenses with a finite life span
determined at or before the product sale.


ΓòÉΓòÉΓòÉ 4.3.2. Compound Passwords ΓòÉΓòÉΓòÉ

Compound passwords allow the subsequent creation of concurrent-access licenses,
use-once licenses, and nodelocked (dynamic nodelocked) licenses.


ΓòÉΓòÉΓòÉ 4.4. Understanding Licensing Models ΓòÉΓòÉΓòÉ

License Use Runtime uses two types of licensing models: nodelocked licensing
and server-based licensing. A product can be license-enabled using one or both
licensing models.

Nodelocked licensing locks the use of a software product to the particular
system (node) for which the nodelocked license is created by the product's
vendor. To run the product on another system, you need to purchase another
nodelocked license specifically created for that system.

With server-based licenses, product licenses are managed by license servers,
rather than locally on the machine where the software product is actually
running. When a product starts, it obtains a license from a license server.
When the product stops, the license is returned to the server.


ΓòÉΓòÉΓòÉ 4.4.1. Working with Nodelock Licensed Products ΓòÉΓòÉΓòÉ

When a user starts a product licensed for use with only a nodelocked license,
the client looks in a local file for a nodelocked license password to run. If a
valid nodelocked license exists, the product starts running. If the nodelock
file does not exist, or does not contain a valid nodelocked license for the
product, the next step depends on the licensing policy of the vendor. The
vendor can decide to stop the execution of the product, or make the product run
even with no license available.


Using a Nodelocked License

A nodelocked license comes in the form of an electronic password contained in
an enrollment certificate, which the vendor gives you with the license-enabled
product. The nodelocked license is linked, at time of license creation, to the
unique identifier (target ID) of the system where you intend to run the
licensed product. You use the Nodelock Administration Tool to add nodelocked
licenses and subsequently manage and monitor all of the nodelock licenses that
you install on a License Use Runtime client.

A nodelocked license password is stored locally in a special file (called
nodelock file) on the same machine where the licensed product is running.
Because a nodelocked license and the application that it licenses always reside
on the same system, a nodelocked product does not require the presence of a
license server on the network. The dynamic nodelocked are an exception, see
Using Products with Nodelocked Licenses for details.


ΓòÉΓòÉΓòÉ 4.4.2. Working with Server-Based Licensed Products ΓòÉΓòÉΓòÉ

You can install a product with server-based licenses on any client system in
your network that can communicate with a license server.

All server-based licenses are shared among all potential users of a software
product running on any node that can contact the license server holding its
licenses.

The server-based licensing model provides the following license types:

     Concurrent-access
     Use-once

      This model may also include nodelocked licenses. It is the case of the
      dynamic nodelocked, described in Using Products with Nodelocked Licenses.

 When a user invokes a product with server-based licenses, the product contacts
 the server, and requests a license. If a valid license is available, the
 server grants the license and the product executes. As long as the product is
 running, that license remains unavailable. When the product stops, the license
 is returned to the server where again it becomes available. The dynamic
 nodelocked are an exception, see Using Products with Nodelocked Licenses for
 details.

 The communication between client and server is based on the underlying network
 computing system (NCS) library and tools. See Setting Up Your Network
 Environment for more detailed information about NCS and its entities.


  Using a Server Based License

 Server-based licenses come to you from the software vendor in the form of a
 password. You use the Basic License Tool. to add server-based license
 passwords to the server license database.

 Subsequently, you use the Basic License Tool to manage and monitor all
 server-based licenses in your License Use Runtime environment.

 See -- Reference servbsd not found -- for complete information on how to
 install and manage server-based licenses.


ΓòÉΓòÉΓòÉ 4.5. Understanding Security Levels ΓòÉΓòÉΓòÉ

Software vendors can license their products accordingly to any of the following
IBM predefined security levels:

     Vendor-Managed Use Control
     Customer-Managed Use Control


ΓòÉΓòÉΓòÉ 4.5.1. Vendor-Managed Use Products ΓòÉΓòÉΓòÉ

The Vendor-Managed Use products have the highest level of protection provided
by the SystemView License Use Management Runtime for OS/2.

With vendor-managed use products you are technically  bound to stay within the
limits of the purchase agreement.

When you purchase licenses for a vendor-managed use product, the product vendor
will ask you to supply the unique identifier (target ID) of each machine where
you intend to install the product licenses. For nodelocked licenses this is the
identification of the workstation where the enabled product is to be installed;
for the other types of licenses this is the license server. You must also
supply the license type and the number of licenses you want to make available.
The vendor uses this information to create the password that you use to install
and activate the licenses that you have purchased.

The passwords are contained in an enrollment certificate, which the vendor
gives you with the product. The password, tied to the specified workstation,
cannot be used on another workstation.

Every time you want to change the terms and conditions of the contract, (the
most frequent change being an increase of the number of licences), you have to
provide the vendor with similar information for each of the machines on which
you intend to install the licenses to get a new password.

Vendors can license vendor-managed use products with any license types:

     Concurrent-access licenses
     Use-once licenses
     Nodelock licenses

 You use the BLT to add concurrent-access, use-once, or dynamic nodelock
 licenses for vendor-managed use products to the license server that you
 specify.

 You use the nodelock administration tool to add nodelocked and concurrent
 nodelocked licenses for vendor-managed use products on the machine where the
 product runs.


ΓòÉΓòÉΓòÉ 4.5.2. Customer-Managed Use Products ΓòÉΓòÉΓòÉ

To provide vendors with greater flexibility in the way they deliver licensed
software, License Use Runtime supports customer-managed use product security
level. With this level, licenses are not directly associated by the vendor with
a particular license server (or group of license servers). The vendor does not
set an upper limit on the number of licenses that you are entitled to use.
License Use Runtime provides you with the information on the usage of the
enabled products, so helping you to stay  within the boundaries of the signed
contract.

All license usage events are recorded on the server log.

Vendors license customer-managed use products by means of concurrent-access
licenses or use-once licenses, or both.

Vendors typically ship a customer-managed use product with a compound license
password that you use to install and distribute licenses to use the product.
Each compound password is contained within an enrollment certificate.

You use the BLT to install passwords for customer-managed use products and
distribute the licenses they contain among your license servers. You must
enter, and then you can modify at any time, a number indicating how many
licenses you have acquired for the product in the network.

The compound password contains the total number of licenses you can extract
(which can be virtually unlimited) and has an expiration date. Both the number
of licenses and the expiration date are determined by the vendor when creating
the compound password. The duration of the licenses that you derive and
distribute from a compound password cannot be longer than the length of time
remaining before the compound password expires.

You can extract licenses from a compound password at any time before the
expiration date of the compound password itself.

Vendors of customer-managed use products may reserve the right to examine the
License Use Runtime log files on your servers to determine whether or not the
terms of your existing purchase agreement need to be amended.


ΓòÉΓòÉΓòÉ 4.6. Summarizing License Use Management Concepts ΓòÉΓòÉΓòÉ

The following items contribute to the implementation of license use management:

     License
     License password
     Compound password
     Enrollment certificate file

 Concepts Summary represents a scheme that clarifies the relationship among
 them.


  Concepts Summary

 One or more licenses are always needed to run the enabled product.

 Licenses are contained in a license password. This is an encrypted string that
 gets physically installed either on a license server or in the nodelock file,
 depending on the license type it defines. The license password is the entity
 that the enabled product will check for in order to run. Sometimes, the
 license passwords are contained in compound license passwords, from which they
 are to be extracted. This is the way through which a software vendor
 implements customer-managed use products. In this case, vendors distribute a
 compound password rather than a license password, and let their customer
 extract the number of licenses they need, by creating new license passwords.

 Whether the vendors use compound passwords or not, they always ship their
 passwords through enrollment certificate files. These are simple ASCII files
 distributed along with the product. The enrollment certificate file contains
 all the information needed to enroll the product.

 Enrollment is the formal act, that gives you the needed entitlement to run the
 product. The enrollment process also automatically produces the installation
 of the license password (or the compound password).


ΓòÉΓòÉΓòÉ 4.7. Understanding Product Wait Queues ΓòÉΓòÉΓòÉ

Some of the license-enabled products you purchase with concurrent-access
licenses may use a License Use Runtime mechanism known as a wait queue.

When a user invokes such a product, and there are no concurrent-access licenses
currently available, the product asks if the user wants to wait for a license.
If the user responds affirmatively, that user's name is added to the wait queue
on each of the License Use Runtime servers that provide concurrent-access
licenses to use the product. User names are added to the wait queues in
chronological sequence. When a license becomes available, it is released to the
user. The user is then removed from all of the wait queues and the next user
specified in the queues becomes eligible for the next available license.


ΓòÉΓòÉΓòÉ 4.8. License Use Runtime Packaging ΓòÉΓòÉΓòÉ

The License Use Runtime components you receive are:

     OS/2 Server (SRK)
     OS/2 Client (CRK)
     Windows Client (Windows CRK)

 From now on in this book, the names in each of the following groups, are
 synonyms:

     OS/2 Server
     Server Runtime Kit
     SRK

     OS/2 Client
     OS/2 Client Runtime Kit
     OS/2 CRK
     CRK

     Windows Client
     Windows Client Runtime Kit
     Windows CRK

 Use the Basic License Tool to manage products whose licenses are installed on
 the license server. This tool provides an easy-to-use graphical interface that
 enables you to perform a variety of management and license-monitoring
 operations on the license server that you specify. Tasks include adding
 products to a license server, distributing customer-managed use products,
 creating and distributing licenses for not license-enabled products, and
 generating displays and reports on license usage and server events. By
 default, the tool displays information for all product licenses from all
 vendors installed on the license server that you specify. You can easily
 restrict the view of the tool to gather management information about a subset
 of products. The Basic License Tool is packaged with the Server Runtime Kit
 (SRK).

 Use the Nodelock Administration Tool of the CRK to manage software products
 installed locally (on the same system where the tool is running) and licensed
 under the License Use Runtime nodelock licensing model.


ΓòÉΓòÉΓòÉ 5. Setting Up Your Network Environment ΓòÉΓòÉΓòÉ

License Use Runtime provides several ways to satisfy your needs for a licensing
system. Designing the licensing environment that provides the best solution for
your business requires careful and thoughtful planning.

It is recommended that you include enough time for planning, especially when
using License Use Runtime in large networks or across subnetworks. This chapter
helps you as the system administrator to plan the licensing system and to find
the configuration options you need for your requirements.

To plan the correct licensing configuration in your network, you need to know
the NCS concepts described in this chapter.


ΓòÉΓòÉΓòÉ 5.1. Deciding between Direct Binding and Namespace Binding ΓòÉΓòÉΓòÉ

License Use Runtime provides two main types of network configuration:

     Direct binding
     Namespace binding

 Namespace binding uses location brokerage services and provides a powerful
 method of administering large client-server networks.

 For small environments, with 1 or 2 servers, setting up and managing the
 namespace binding can be expensive.  Direct binding responds directly to the
 market need for simple licensing environment installation configuration, and
 management.

 As the licensing environment increases, the complexity of managing direct
 binding increases, and the namespace binding becomes the best way to manage
 the license use management environment.

 It is not suggested that you set a mixed environment of both namespace and
 direct binding.

 Also, it is not suggested that you switch from a namespace to a direct binding
 environment and viceversa.

 The above restriction does not apply to clients. Clients infact can be
 configured in direct binding to communicate with servers configured for the
 namespace binding. This is on the contrary recommended when a client resides
 on a different subnetwork, connected through a router, that may not support
 NCS broadcast. Direct binding, moreover, is the only way to connect Windows
 clients to a server. The server in turn, can be configured as namespace
 binding enabled (in such a case it works in both namespace and direct
 binding), and namespace binding disabled (in such a case it works only in
 direct binding).


ΓòÉΓòÉΓòÉ 5.2. Using Direct Binding ΓòÉΓòÉΓòÉ

You may have a system that does not support broadcasting. In this case,
configure your license server and clients in direct binding mode. To locate
servers configured for direct binding, client applications read a local
configuration file with the network addresses of these license servers.

All license servers listen for incoming communications on well-known ports
(1515 and 10999). The client code uses these port numbers, together with the
network addresses of the server systems specified in the local configuration
file, to locate and connect to the servers.


ΓòÉΓòÉΓòÉ 5.3. Introducing the Network Computing System (NCS) ΓòÉΓòÉΓòÉ

The network computing system (NCS) is a set of tools for heterogeneous
distributed computing. License Use Runtime runs on top of the network computing
kernel (NCK), which is included in the License Use Runtime components that you
install.

The NCK includes:

 Remote Procedure Call (RPC) Runtime Library
           The backbone of the network computing system. It provides the calls
           that enable local programs to execute procedures on remote hosts.
           These calls transfer requests and responses between clients (the
           programs calling the procedures), and servers (the programs
           executing the procedures). The RPC embedded in all license servers
           and enabled products provides a common mechanism to support the
           request and acquisition of licenses.

 Location Broker
           A mechanism that allows the enabled products to locate license
           servers in the network. Location broker software includes the global
           location broker (GLB), the local location broker (LLB), and
           administrative tools. The location broker software is included in
           the License Use Runtime.

 After they are configured, these mechanisms are transparent to the end user of
 the software product.

 This section covers NCS concepts and how they apply to License Use Runtime.


ΓòÉΓòÉΓòÉ 5.4. Using Namespace Binding ΓòÉΓòÉΓòÉ

Sometimes it is desirable to logically partition a network so that some of the
servers serve only some of the clients. This grouping of clients and servers is
known as a cell. An enabled product, running on a client, that requires a
license, can have its license requests satisfied only by a license server in
the same cell where the client is.

All nodes belonging to a cell are identified by the same name, called a
universal unique identifier (UUID), a 16-byte string identifying the host on
which the UUID is created and the time at which it is created.

A node cannot be in more than one NCS cell.

Because cells cannot overlap, it is important to understand who should have
access to what licenses when the servers are configured. In a production
environment you may want to configure all your license servers to run in the
default NCS cell. This simplifies the task of managing servers and allows a
central administrator to control all the license servers. However, if some
licenses are to be restricted to a certain group of users, those licenses
should be installed on servers running in an alternate cell; the clients as
well should belong to that cell to use those licenses. If clients of this
alternate cell need access to licenses in the default cell, you need to
reconfigure the clients to have them in the default cell. You should establish
alternate NCS cells for test environments, because the unstable nature of the
test environment could negatively affect regular production users.

You can decide to which cell a node (client or server) has to belong when
configuring the SRK and the CRK, after their installation.

All the nodes in the network are configured by default in the default cell. You
can create a different cell to isolate individual departments. Follow the
instructions in -- Reference sccfn not found -- to configure servers and
clients.


ΓòÉΓòÉΓòÉ 5.4.1. Running the Location Brokers ΓòÉΓòÉΓòÉ

The NCS provides a standard way to make the services offered by a server
available to client systems. To locate the services on the servers, the clients
use a locating service called a location broker.

The location broker guides the client to the servers that provide a specific
service. Location broker tasks are split into two components: local and global.

The local location broker handles communication between the global location
broker and the actual servers. A local location broker must run on each node
that provides a service, that is on each license server.

The part of License Use Runtime that implements the local location broker is a
process called i4llbd.

Every node that provides services to the NCS (that is, every license server)
must run the local location broker process, including systems that run the
global location broker service. You can establish several configurations
depending on the number of servers you decide to have. You can also have mixed
systems for interoperability purposes. For example iFOR/LS AIX server (netlsd
process) may already be running in your environment.

The global location broker maintains a database of where all services reside on
the network. There can be a global location broker on one or more license
servers on the network. At least one node in an NCS cell must run the global
location broker.

The global location broker dynamically updates network location information for
each license server. If you configure new license servers, or move existing
license servers to new locations on the network, licensed applications will
always be able to find them.

The global location broker is called i4glbd. This process runs continuously in
the background, waiting for a request for the function it provides. The
function it provides is called infrequently. It is usually in wait state and
has little effect on system performance.

See -- Reference sccfn not found -- to configure your network and start these
processes. The License Use Runtime server provides also an administration tool,
called GLBDs List (i4lbfind), to locate the global location broker processs
running in the network. To use it, see Using NCS Tools.

You can replicate the i4glbd process and have more than one running within a
cell of the network.


ΓòÉΓòÉΓòÉ 5.4.2. Accessing the License Server of a Different Subnetwork ΓòÉΓòÉΓòÉ

Ordinarily, products on clients contact a Global Location Broker (GLB) by
broadcasting on the local network. However, you may have a system that does not
support broadcasting. Or, you may have the GLB running on a license server of a
separate subnetwork. In these cases, you have to perform the following
additional configuration steps on the clients of your network:

   1. Make a file called glb_site.txt in the

            x:\ifor\etc

      directory, where x is the drive where the License Use Runtime client is
      installed.

      In the glb_site.txt file enter the network addresses of the server(s)
      running the GLB you want to reach from the clients.

      The file is not set by default. Clients that have a glb_site.txt file
      look for server running the GLB in order, on the machines whose addresses
      are in the glb_site.txt file. Each address has the following form:

            family:host

      Where:

      family
                     Is the textual name of an address family, and its possible
                     values include ip and ipx.

      host
                     It is the host name, or ip address if the family is ip, or
                     it is the network┬╖MAC_address if the family is IPX. For
                     the ip address you use a leading # to indicate that the
                     host is an address, and is in the standard numeric form
                     (for example, #192.9.8.7 or #515c.111g).

      Blank lines and lines beginning with # are ignored.

      If a machine has a glb_site.txt file, but does not find a Global Location
      Broker at any of the addresses listed in the file, the machine then tries
      to locate a GLB via broadcast. See glb_site.txt File Example for an
      example of glb_site.txt.

   2. Copy the file called glb_obj.txt from the

            x:\ifor\etc

      directory of the server with the GLB, into the:

            y:\ifor\etc

      directory of the clients. Where x is the directory where the License Use
      Runtime server is installed, and y is the directory where the License Use
      Runtime client is installed.


ΓòÉΓòÉΓòÉ 5.4.3. glb_site.txt File Example ΓòÉΓòÉΓòÉ

The following is a sample glb_site.txt file:

ip:pippo
ip:#192.9.8.7
ipx:00000002┬╖10005AAF12FA


ΓòÉΓòÉΓòÉ 5.5. Running License Use Runtime Processes ΓòÉΓòÉΓòÉ

License Use Runtime also has its own processes that manage the storing of
licensing information and the communication between clients and servers, and
that are independent from the type of binding you choose. These processes are:

     Administration Database Server
     NetBIOS Socket Server
     License Server


ΓòÉΓòÉΓòÉ 5.5.1. Administration Database Server ΓòÉΓòÉΓòÉ

The administration database server subsystem provides a mechanism for storing
licensing information in a database common to all the servers. It is used for
the administration of customer-managed use products. It is called i4gdb. There
must be one and only one administration database subsystem running in a cell,
in the case of namespace binding, and one and only one running in all the
license use management environment, in the case of direct binding, or in a
mixed environment. That is, only one server node must have the i4gdb started.
This ensures that the data is accurate and complete.

     Important After you place the administration database on a network node,
     it must always reside on it. This means the administration database server
     must always be started on the same node.

 Note:

   1. The machine running the administration database must always be up and
      running in order to perform administration tasks using the Basic License
      Tool.

   2. In namespace binding the configuration tool automatically places and
      starts the administration database subsystem on the server that starts
      the new global location broker. If more than one administration database
      is found, the newly started i4gdb subsystem automatically shuts down.

   3. In direct binding you need to decide where to start the i4gdb subsystem
      using the configuration tool. Make sure that there is no more than one
      i4gdb in your network licensing environment.


ΓòÉΓòÉΓòÉ 5.5.2. NetBIOS Socket Server ΓòÉΓòÉΓòÉ

If you use NetBIOS as the communication protocol in your network, the NetBIOS
socket server process must run on all license servers and clients of the
network.

The name of the License Use Runtime part that implements this process is
i4nbssvr, and it is provided with both the SRK and the CRK.

To make the NetBIOS socket server work you have to configure the MPTS NetBIOS
sockets. Do it in this way:

   1. Start MPTS

   2. Select the Configure push button

   3. Select the NetBIOS Socket Access radio button

   4. Select the Configure push button

   5. Select the Close push button

   6. Exit the MPTS.


ΓòÉΓòÉΓòÉ 5.5.3. License Server ΓòÉΓòÉΓòÉ

The license server process provides the actual license services, and is called
i4lmd. A node that works as a license server must run this process.

From now on the words server or license server will be used to indicate the
node of your network on which the i4lmd process runs, that is the server on
which the License Use Runtime has been installed.


ΓòÉΓòÉΓòÉ 5.5.4. Global Location Broker Database Cleaner ΓòÉΓòÉΓòÉ

The global location broker database cleaner is a process that automatically
cleans up the global location broker databases.


ΓòÉΓòÉΓòÉ 5.6. Summarizing the Processes Requirements ΓòÉΓòÉΓòÉ

NCS and License Use Runtime processes are started on servers and clients
depending on the type of configuration, as shown in the following table.

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 1. Rules to Have License Use Runtime Running in Your Network      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RULE             Γöé PROCESS   Γöé ON  Γöé ON  Γöé DIRECT   Γöé NAMESPACE Γöé
Γöé               Γöé NAME    Γöé SERVΓöéRCLIEΓöéTBINDING  Γöé BINDING  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé The socket server process  Γöé i4nbssvr  Γöé X  Γöé X  Γöé X     Γöé X     Γöé
Γöé starts on any server and   Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γöé client on which you want to Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γöé use the NetBIOS transport  Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γöé protocol.          Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé The local location broker  Γöé i4llbd   Γöé X  Γöé   Γöé      Γöé X     Γöé
Γöé process starts on any    Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γöé server in the network.    Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé The global location broker  Γöé i4glbd   Γöé X  Γöé   Γöé      Γöé X     Γöé
Γöé process starts at least on  Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γöé one server per cell.     Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé The license server process  Γöé i4lmd    Γöé X  Γöé   Γöé X     Γöé X     Γöé
Γöé starts on all the servers  Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γöé of the network.       Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé The administration database Γöé i4gdb    Γöé X  Γöé   Γöé X     Γöé X     Γöé
Γöé server process starts on   Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γöé one (and only one) license  Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γöé server machine in a cell.  Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé The global location broker  Γöé i4glbcd   Γöé X  Γöé   Γöé      Γöé X     Γöé
Γöé database cleaner starts on  Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
Γöé any server in the network.  Γöé       Γöé   Γöé   Γöé      Γöé      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 5.7. Planning Your Network ΓòÉΓòÉΓòÉ

The license server system is dependent on a stable network. If routing and name
resolution in a network are not running properly, then the servers and the
clients may be unable to communicate properly. Keep license servers for
production environments separated from license servers for test environments.

A license server should be a computer that stays on at all times. Computers
that are frequently unavailable and unreliable, such as those taken down often
for testing or maintenance, are not good candidates.

If a computer has already been designated as a file server, it becomes a good
choice for a license server, because it satisfies many of the previously
mentioned criteria.

If you have an environment that consists of several subnetworks, ideally,
license servers should be on the same subnetwork as the majority of clients
that will run the licensed products. Accessing license servers in another
subnetwork, across a bridge or router, may not be quite as fast. The
subnetworks can be connected by routers that do not support NCS broadcast to
license servers. In such a case you need to configure your machines in direct
binding mode.

If the network spans subnetworks, you need to spread the licenses out among
servers. Also, inside the same network, each client request for a license
generates network traffic. Therefore, it can help to spread the client
applications across more than one server machine, and across multiple
platforms. When a computer is down, the licenses assigned to the license server
on that system are unavailable, but licenses assigned to other license servers
remain available. Having more license servers on the network will help to
loosen the bottleneck associated with many clients communicating with a single
license server.

The number of license servers in the network should be supplied by the product
vendor; in any case this number should be proportional to the frequency of
license requests, not to the number of users. Suppose a compiler and a word
processor are license enabled.  A single user running many short compilations
will place a heavier stress on the license server than would many users each
starting a single invocation of the word processor.

If the license activity on a network is so high that the server is unable to
handle all requests, you can add a server to the network and split the licenses
between the two.

Computers that function as license server nodes can run the licensed products.
The license server software does not have a noticeable effect on the
performance of products. If you have a computer that is not in a network, but
you purchased a concurrent or use-once license, you can install the license
server software on that computer.  It then acts as both the license server and
the client.

If the network is small to medium in size with high-speed connections
throughout, one global location broker is probably sufficient.  Choose one of
the license servers to run the global location broker. If the network is large,
it may be best to set up one global location broker server on each LAN.

If your machine is not on the network and you plan to have a license server
running on this machine, it is best to configure NCS to be in its own alternate
cell.

     Important Before you start to configure your servers, make sure you have
     carefully planned your licensing environment.


ΓòÉΓòÉΓòÉ 5.7.1. Examples ΓòÉΓòÉΓòÉ

This section shows the possible network configurations you can have in your
environment. The examples only show an environment with, at the most, five
clients for one server, but you can configure more clients for one server.


NCS Cell Where All the Processes Run on the Same Server.

NCS Cell Where All the Processes Run on the Same Server. shows a recommended
configuration where all the required NCS processes run on the same server.


NCS Cell with Two License Servers and Four Clients.

NCS Cell with Two License Servers and Four Clients. shows a network with two
license servers. One of them runs only the local location broker, which is
mandatory on all servers; the other also runs the administration database and
the global location broker.


NCS Cell with Three License Servers and Three Clients.

NCS Cell with Three License Servers and Three Clients. shows a network with
three license servers. This example shows that more than one license server in
the network can run the global location broker but with only one administration
database. Server C runs a global location broker that is a replica of the first
that was started, on server B.


A License Server and Two Clients Using Direct Binding.

A License Server and Two Clients Using Direct Binding. shows an example of a
network configuration using direct binding.

Note:  If you run in a NetBIOS network, all the machines, servers and clients
       must also run the socket server process (i4nbssvr).


ΓòÉΓòÉΓòÉ 5.8. Using NCS Tools ΓòÉΓòÉΓòÉ

NCS provides tools that you can optionally use to monitor and change your NCS
network configuration.

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 2. NCS Tools                              Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TOOL      Γöé DESCRIPTION                         Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Local Broker  Γöé Administers the registration of the servers in global    Γöé
Γöé Administration Γöé location broker or local location broker databases. It can  Γöé
Γöé (i4lbadm)    Γöé be used to look up information, add new entries, and delete Γöé
Γöé         Γöé existing entries in a specified database.          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé GLBD Replicas  Γöé Monitors and modifies the list of the replicated versions  Γöé
Γöé Administration Γöé of the global location broker databases. It can be used to  Γöé
Γöé (i4drmadm)   Γöé modify, or merge databases to force convergence among rep-  Γöé
Γöé         Γöé licas, to stop servers, and to delete replicas.       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé GLBDs List   Γöé Lists the servers running the global location broker in the Γöé
Γöé (i4lbfind)   Γöé network.                           Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Universal    Γöé Universal Unique Identifier generator (i4uuid)        Γöé
Γöé Unique Identi- Γöé                               Γöé
Γöé fier generator Γöé                               Γöé
Γöé (uuid_gen)   Γöé                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Generates the  Γöé                               Γöé
Γöé UUID which is  Γöé                               Γöé
Γöé used to create Γöé                               Γöé
Γöé the       Γöé                               Γöé
Γöé glb_obj.txt   Γöé                               Γöé
Γöé file in the   Γöé                               Γöé
Γöé ifor\etc    Γöé                               Γöé
Γöé directory.   Γöé                               Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

The tools can all be started from an OS/2 window command prompt, or double
clicking on their icons on the server.

For a detailed explanation of how to start the tools from an OS/2 command
prompt, and how to use them, see License Use Runtime Command Reference.


ΓòÉΓòÉΓòÉ 6. Installing License Use Runtime ΓòÉΓòÉΓòÉ

License Use Runtime contains the following main components:

     License Use Runtime - Server (also referred to as Server Runtime Kit, or
      SRK)

     License Use Runtime - Client (also referred to as Client Runtime Kit, or
      CRK)

 Install both the Server Runtime Kit and the Client Runtime Kit on the machines
 you want to set as License Use Runtime servers on your network. Use the Server
 Runtime Kit to install, manage, and monitor software products that use
 concurrent or use-once licenses.

 Install the Client Runtime Kit on all the machines you want to set as clients
 on your network to allow them to communicate with the servers to use the
 licensed products, and to install, manage, and monitor nodelocked licenses.

 For information on the number of clients and servers to install in your
 network, see Planning Your Network.

 To manage only nodelocked licenses, install only the CRK.

 The CRK and SRK are transparent for the end users of the applications in a
 properly configured system. However, you must install the two components and
 set up the initial configuration.

 The License Use Runtime Client is automatically installed when you choose to
 install the License Use Runtime Server.

 This chapter includes information about:

     What to do before installing License Use Runtime SRK and CRK
     Installing the SRK and the CRK
     What to do after installing License Use Runtime SRK and CRK


ΓòÉΓòÉΓòÉ 6.1. Before Installing License Use Runtime Components ΓòÉΓòÉΓòÉ

Before installing the License Use Runtime program, be sure you have allocated
sufficient disk space:

      14MB on the server machine

      5MB on the client machine

 The installation of the License Use Runtime - Server requires that the License
 Use Runtime - Client component is also installed on the machine.

 Before you install License Use Runtime components, back up the original
 diskettes to ensure against damage.  Store the originals and always run the
 installation program from the backup copies of the License Use Runtime
 diskettes.


ΓòÉΓòÉΓòÉ 6.1.1. Server Runtime Kit Recommended Hardware ΓòÉΓòÉΓòÉ

To install the SRK, you need the following hardware:

     An IBM PS/2 system with a minimum of 33MHZ 386 CPU or better
     16MB of RAM


ΓòÉΓòÉΓòÉ 6.1.2. Client Runtime Kit Recommended Hardware ΓòÉΓòÉΓòÉ

To install the CRK, you need the following hardware:

     An IBM PS/2 having a 33MHZ 386 CPU or better
     8MB of RAM


ΓòÉΓòÉΓòÉ 6.1.3. Server Runtime Kit Software Requirements ΓòÉΓòÉΓòÉ

     One of the following transport protocols:

        -  IBM OS/2 LAN Adapter and Protocol Support Version 2.13, or IBM OS/2
           Socket/Multi-Protocol Transport Services Version 1.00

           Note:  If you use the LAN Adapter you need to update some of its
                  parameters. Their values, currently set for your NetBIOS
                  environment, must be increased, according to the minium
                  values required by License Use Runtime. Here are the
                  parameters and their values requested by License Use Runtime:

             -- Session=1
             -- Names=2
             -- NCBs=40

           For example, if you had the NCBs parameter set to 30, you have to
           modify it to 70.

        -  TCP/IP Base for OS/2 2.0 and 2.1, Version 2.00 or later

     OS/2 2.11 or later

     Optionally, to check your identity when logging on the SRK, Network
      Security Program Version 1 Release 2

 To find out the latest level of the products on your machine, enter the
 following command from an OS/2 prompt:

      syslevel

 The output of this command for the prerequisites follows:

 For the operating system (except OS/2 Warp):

                          drive:\OS2\INSTALL\SYSLEVEL.OS2
                                           IBM OS/2 Base Operating System
                      System
                          Version 2.11  Component ID 562107701
                          Type 0-2
                          Current CSD Level: XR06200
                          Prior CSD Level: xxxxxxx

 For the OS/2 Warp operating system:

                          drive:\OS2\INSTALL\SYSLEVEL.OS2
                                           IBM OS/2 Base Operating System
                      System
                          Version 3.0  Component ID 562260100
                          Type W
                          Current CSD Level: XRU3000
                          Prior CSD Level: xxxxxxx

 For the TCP/IP:

                          drive:\TCPIP\SYSLEVEL.TCP
                                           TCP/IP Base for OS/2 2.0 and 2.1
                          Version 2.00 Component ID 562208600
                          Current CSD Level: UN64092
                          Prior CSD Level: xxxxxxx

 For the LAN Adapter:

                          drive:\IBMCOM\SYSLEVEL.TRP
                                           IBM OS/2 LAN Adapter and Protocol Support
                      Support
                          Version 2.13 Component ID 562125303
                          Current CSD Level: WR07020
                          Prior CSD Level: xxxxxxx

 For the Socket/Multi-Protocol:

                          drive:\MPTN\SYSLEVEL.MPT
                                           IBM OS/2 Socket/Multi-Protocol Transport Services
                      Support
                          Version 1.0 Component ID 562246103
                          Current CSD Level: WR08000
                          Prior CSD Level: xxxxxxx

 where drive is the letter of the drive where the product is installed, and
 xxxxxxx is the number corresponding to the CSD level on top of which you
 installed the current product.

 If OS/2 Warp is not your operating system, another CSD is required, which is
 not shown with the syslevel command. It is the CSD XR_F018. To find out if you
 have the CSD, issue this command from the drive prompt where the operating
 system is installed:

  dir os2krnl /s

 and verify that the date of the os2krnl file is 6/21/94 or later.

 Contact your IBM representative for the latest CSDs.


ΓòÉΓòÉΓòÉ 6.1.4. Client Runtime Kit Software Requirements ΓòÉΓòÉΓòÉ

The software requirements for the CRK are the same as those for the SRK. They
are listed in Server Runtime Kit Software Requirements,


ΓòÉΓòÉΓòÉ 6.2. Installing  License Use Runtime ΓòÉΓòÉΓòÉ

You can choose between three methods of installing License Use Runtime: from
diskettes, from CD-ROM, or from a code server.

The following steps assume that, if you are installing from diskettes, you are
starting the installation program from drive A. If you are starting the License
Use Runtime from a different drive, substitute the letter of that drive in the
steps that follow.

License Use Runtime is provided either on a CD-ROM, or on six diskettes:

     OS/2 Installation diskette
     Windows installation diskette
     OS/2 diskettes from 1 to 4

 The following steps assume that you are starting the installation program from
 drive A. If you are starting the License Use Runtime from a different drive,
 substitute the letter of that drive in the steps that follow.


ΓòÉΓòÉΓòÉ 6.2.1. Installing from CD-ROM or from Diskettes ΓòÉΓòÉΓòÉ

This method can be either interactive or noninteractive:

     In interactive mode the installation requires you to answer questions as
      prompted.

     In noninteractive mode the installation is driven by a response file,
      which contains the answers to all of the questions that the installation
      needs.


ΓòÉΓòÉΓòÉ 6.2.1.1. Installing Interactively ΓòÉΓòÉΓòÉ

This session explains how to install the License Use Runtime interactively
using the installation program provided on CD-ROM or on diskettes. This chapter
only shows you the windows that appear when you install on an OS/2 machine. To
install on a Windows machine, you can follow the same instructions, even if the
displayed windows appear slightly different.

To install the License Use Runtime interactively, follow these steps:

   1. On the CD-ROM select the License Use Runtime installation directory (os2
      for OS/2  or windows for Windows) and type install

 or

 Insert the Installation diskette in drive A, and at the OS/2 command prompt,
 type install,

 and press the Enter key. The License Use Runtime installation window appears
 (Main License Use Runtime Window and the Instructions Window).


  Main License Use Runtime Window and the Instructions Window

   2. Select the Continue push button in the Instructions window. The
      Instructions window closes, and the Install window appears (Install
      Window).


            Install Window

   3. Verify that the Update CONFIG.SYS check box is selected if you want
      License Use Runtime to modify your CONFIG.SYS file for you. To update
      your CONFIG.SYS file yourself, deselect the Update CONFIG.SYS check box.
      For more information about modifying the CONFIG.SYS file, see Modifying
      Your CONFIG.SYS File.

      Select the Overwrite files check box only if you want the License Use
      Runtime to overwrite any existing files in the directory where you want
      to install the product. This check box applies only if you are replacing
      an existing version of License Use Runtime.

      If you are installing License Use Runtime Version 1.0.1 on License Use
      Runtime Version 1.0, check the Overwrite files check box. This will
      prevent a warning message from appearing for every file that is
      downloaded, but will overwrite also the configuration file, I4LS.INI, in
      the directory IFOR\LS\CONF. So, either save this file before the
      installation renaming it, or configure License Use Runtime again after
      the installation.

   4. Select the OK push button. The install window closes, and the
      Install-directories window appears (Install-directories Window).


            Install-directories Window

   5. Select the License Use Runtime components you want to install from the
      License Use Runtime components list box:

        a. Select License Use Runtime - Client to set the machine as a client.

        b. Select License Use Runtime - Server to set the machine as  a server.
           Note that the installation of the License Use Runtime - Server
           requires that the License Use Runtime - Client component is also
           selected on the machine.

      Specify a destination drive for License Use Runtime files in the Enter
      destination drive field. The default C: is initially displayed in the
      entry field. You can type over it. If you already installed License Use
      Runtime and you specify the same drive, the License Use Runtime
      installation program displays a confirmation message asking you if you
      want to override files with the same names.

      You can specify the drive only. The product is always installed in the
      IFOR directory. If you are installing License Use Runtime Version 1.0.1
      on License Use Runtime Version 1.0, install the product on the same drive
      where it was already installed.

   6. Select the Install push button. The Install-directories window closes,
      and the Install-progress window appears, displaying the component you
      selected (Install-progress Window).


            Install-progress Window

 License Use Runtime begins copying files. You can monitor the progress by
 watching the progress bar.

 Only if you are installing from diskettes, when all the files are copied, the
 Insert disk window (Insert Disk Window) appears and prompts you to insert
 Diskette1.


  Insert Disk Window

 Insert Diskette1 into the A drive and select the Continue push button in the
 Insert disk window. The Insert disk window closes, and the Install-progress
 window is active again (Install-progress Window).

      When all files are copied, the Insert disk window appears and prompts you
      to insert the required diskette.

 When the installation is complete, the Install-progress window closes, and the
 Installation and Maintenance window appears, and displays a completion message
 (Installation and Maintenance Window).


  Installation and Maintenance Window

   7. Select the OK push button. The Installation and Maintenance window
      closes, and the License Use Runtime Installation window appears (Main
      License Use Runtime Window and the Instructions Window).

   8. Select the Exit push button. License Use Runtime is installed on your
      workstation and a folder named License Use Runtime - Server or License
      Use Runtime - Client appears on your desktop, depending on to the
      component you have selected.

      If you selected the Update CONFIG.SYS check box in the Install window,
      restart your workstation before you start License Use Runtime.

      If you deselected the Update CONFIG.SYS check box, modify your CONFIG.SYS
      file as explained in Modifying Your CONFIG.SYS File.

   9. Shut down and restart your machine.


ΓòÉΓòÉΓòÉ 6.2.1.2. Installing Non-Interactively ΓòÉΓòÉΓòÉ

You can also use the INSTALL command to install License Use Runtime without
being prompted, but just changing diskettes when required.

You can create a response file in advance, as explained in Writing a Response
File. With the response file you need to be present only to initiate the
installation, insert diskettes, and restart your workstation when the
installation is complete; no questions are asked while the installation is
running.

   1. Insert the Installation diskette in drive A.

   2. Open an OS/2 window.

   3. At the OS/2 command prompt enter the INSTALL command according to the
      syntax described in Using the Installation Command.

   4. Change the diskettes when requested by the installation procedure. When
      you have successfully installed License Use Runtime, a message indicates
      that the installation is complete.

   5. Shut down and restart your machine, then follow the instructions in --
      Reference sccfg not found --..


ΓòÉΓòÉΓòÉ 6.2.2. Installing from a Code Server ΓòÉΓòÉΓòÉ

Use this method if you have access to a code server that contains the License
Use Runtime diskette images.

A code server is a workstation that contains the files (or diskette images) to
be used during the installation. Diskettes are not required at the target
system to perform the installation.

This method can be either interactive or noninteractive. In both cases it works
just as if you were installing from diskettes, except that it does not ask for
diskettes.

To install License Use Runtime using a code server, first prepare the code
server as explained in Setting Up a Code Server, then:

   1. Open an OS/2 command prompt.

   2. Assign the installation image on the code server to a redirected drive on
      your workstation. The command you use depends on the network protocol the
      code server is using.

      If you are using TCP/IP

      Be sure you have the NFS for TCP/IP installed; then, from an OS/2 command
      prompt, issue the following commands:

            start nfsc

            mount <drive> <hostname>:<mountpoint>

      where:

      <drive>
                     is the local drive name

      <hostname>
                     is the host to attach to

      <mountpoint>
                     is the directory to attach to (the one on which the
                     installation image is placed)

      For example:

            mount x: server1:c:\i4inst

      Enter the requested user ID (UID) and group ID (GID), as they were
      defined on the code server (see Setting Up a Code Server). The following
      message appears:

            NFS Drive 'x:' was attached successfully

      If you are using NetBIOS

      Be sure you have the IBM OS/2 LAN Server/Requester product installed.
      Then from an OS/2 command prompt, issue the following commands:

            logon

            net use x: \\<server name>\<alias name>

      where:

      x
                     is the drive letter of the redirected drive

      <server name>
                     is the name of the server to attach to

      <alias name>
                     is the directory to attach to (the one on which the
                     diskettes images are placed)

   3. Type the command:

            x:\INSTALL
      where x is the drive letter of the redirected drive.

      You can include any other parameters as indicated in the section Using
      the Installation Command.

   4. Proceed with the installation as explained in Installing Interactively.
      When you have successfully installed License Use Runtime, a message
      indicates that the installation is complete.

   5. Shut down and restart your machine.


ΓòÉΓòÉΓòÉ 6.3. Using the Installation Command ΓòÉΓòÉΓòÉ

Both License Use Runtime SRK and CRK installation programs for OS/2
workstations are contained on the Installation Diskette of the respective
packages. The installation programs are both called INSTALL.EXE.

The following syntax diagram shows the parameters accepted by INSTALL:

>>ΓöÇΓöÇINSTALLΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
       ΓööΓöÇ/AΓöÇΓöÿ  ΓööΓöÇ/XΓöÇΓöÿ  ΓööΓöÇ/T:driveΓöÇΓöÿ  ΓööΓöÇ/R:responsefileΓöÇΓöÿ
>ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ><
  ΓööΓöÇ/L1:logfileΓöÇΓöÿ  ΓööΓöÇ/L2:historylogΓöÇΓöÿ  ΓööΓöÇ/L3:configlogΓöÇΓöÿ

where:

 /A
           Specifies the action for INSTALL to execute. Possible values for
           this parameter are:

               D to Delete
               I to Install
               R to Restore
               U to Update

           If you omit this parameter, the installation starts interactively
           with all windows displayed.

           If you specify D, be sure no License Use Runtime processes are
           active, or the deletion will fail.

 /X
           Specifies that the License Use Runtime SRK or CRK installation is
           noninteractive and uses the default values specified in the response
           file you specify with the /R parameter. If you do not specify this
           option, you are prompted for any information the installation
           utility needs to complete the action.

 /T:drive
           The drive path on which the License Use Runtime SRK or CRK files are
           installed. If you do not specify a drive, its value is:

                      C:

           Note:  You can specify the drive only. The product is always
                  installed in the IFOR directory.

 /R:responsefile
           Specifies the drive, path, and file name of the specific response
           file. A response file sample is supplied with the product on the
           INSTALLATION diskette, and is called I4LS_SRK.DAT (or I4LS_CRK.DAT).
           An example of using the /R parameter to specify the RESPONSE.DAT
           response file is:

                      /R:D:\XYZ\RESPONSE.DAT

           See Writing a Response File to write a response file.

 /L1:logfile
           Specifies the drive, path, and file name of the error log file,
           which contains all the installation error messages. If the /X
           parameter is not used, no error log file is created. An example of
           using the L1 parameter to create the ERROR.LOG file in the C:\ABC
           directory follows:

                      /L1:C:\ABC\ERROR.LOG

 /L2:historylog
           Specifies the drive, path, and file name of the history log file,
           which contains all the installation log messages. This file contains
           a record of all that the installation process does and is a source
           for problem determination. If you do not specify the drive and path,
           no history log file is generated.

           An example of using the L2 parameter to create the HISTORY.LOG file
           in the C:\ABC directory follows:

                      /L2:C:\ABC\ERROR.LOG

 /L3:configlog
           Specifies the drive, path, and file name of the error log file,
           which contains all the configuration error messages. If you do not
           specify the drive and path, no history configuration log file is
           generated.

           An example of using the L3 parameter to create the CONFIG.LOG file
           in the C:\ABC directory follows:

                      /L3:C:\ABC\CONFIG.LOG

 After the installation is complete, shut down and restart your machine; then
 configure your machine as explained in -- Reference sccfg not found -- or in
 or in -- Reference sccfn not found --..

 An example of how to install the SRK or the CRK using only a response file
 follows:

  INSTALL /X /R:C:\RESPONSE.DAT

 RESPONSE.DAT is your response file, located in the C directory.


ΓòÉΓòÉΓòÉ 6.4. Writing a Response File ΓòÉΓòÉΓòÉ

A response file is a flat ASCII file that you create using any text editor.

You can use a response file both to install and configure the server and the
client. In this section you can find a description of the parameters available
for the installation and an example of an installation response file.

For a list of the configuration parameters available see Response File
Configuration Keywords.

Each line in a response file has a maximum length of 255 bytes. There are two
types of lines in a response file:

 Comment lines     Contain only blank characters, or have either an asterisk or
                   a semicolon as the first nonblank character on the line.

 Response lines    Determine the options and configurations to install on the
                   target system. Response lines have the following syntax:

                                      keyword=value
                   Keywords are not case sensitive. Keyword-value pairs in a
                   response file can be in any order, but there can be only one
                   pair on a line.

 An example of response file that can be used to customize License Use Runtime
 SRK installation is:

  file=D:
  comp=License Use Runtime - Client
  comp=License Use Runtime - Server
  cfgupdate=auto
  overwrite=yes
  savebackup=no
  deletebackup=no

 Where:

 file (required)
           Target drive for the License Use Runtime SRK.

 comp(required)
           Is the name of the components you want to install. Do not use
           quotation marks around the component name, even when it is more than
           one word with blanks between words. It can assume the following
           values:

               License Use Runtime - Client
               License Use Runtime - Server
               License Use Runtime - Server Security Feature

 cfgupdate (required)
           Indicates whether the CONFIG.SYS file is automatically updated.
           Valid values for this keyword are:

           auto         Automatically updates the CONFIG.SYS file

           manual       Does not update the CONFIG.SYS file

 overwrite (required)
           Specifies whether to automatically override files during the
           installation, if you already have License Use Runtime SRK installed.
           Valid values for this keyword are:

               YES
               NO

 savebackup
           Specifies whether to make a backup copy of the product if you
           already have License Use Runtime SRK installed, and you are going to
           overwrite it. Valid values for this keyword are:

               YES
               NO

 deletebackup (required)
           Specifies whether to delete only the backup version of the product
           or to delete the entire product. Valid values for this keyword are:

               YES
               NO

           If you attempt an unattended deletion and this keyword is not
           present, the deletion fails.


ΓòÉΓòÉΓòÉ 6.5. Setting Up a Code Server ΓòÉΓòÉΓòÉ

A code server provides the installation source files on a resource that can be
accessed remotely. Other systems can install either the License Use Runtime SRK
or CRK from this resource instead of installing from diskettes. The code server
must be able to share resources through network protocols (NetBIOS or TCP/IP).

To create the installation image:

   1. Open an OS/2 command prompt.

   2. Create a subdirectory to hold the installation image. The drive you use
      must have at least 6MB of free space. If, for example, you decide to call
      the directory C:\I4INST, type the command:

            MKDIR C:\I4INST

   3. Insert the first installation diskette into your diskette drive and use
      the XCOPY command to copy it to the directory you just created. Type:

            XCOPY A:\* C:\I4INST\ /S

      Be sure to specify the /S parameter to copy the entire directory
      structure from the diskette.

   4. Repeat step 3 for the remaining installation diskettes.

 To share the directory on the network:

 Using TCP/IP

 Be sure you have the NFS Kit and the NFS for CID Installation component
 installed, then:

   1. Open the TCP/IP configuration

   2. Configure the NFS supplying the client ID and the user ID, and adding the
      directory you want to make shared in the network to the EXPORTS
      directories. Read only access is enough.

   3. From an OS/2 command prompt, issue the following command:

            start nfsd

 Using NetBIOS

 Be sure you have the LAN Server installed, then:

   1. Create an alias for the directory you want to make shared in the network

   2. Define the users that can access the alias

   3. Create an access profile for the alias with Read/Execute/Access
      permissions, and apply the profile.


ΓòÉΓòÉΓòÉ 6.6. Modifying Your CONFIG.SYS File ΓòÉΓòÉΓòÉ

If you deselected the Update CONFIG.SYS check box in the Install window when
you installed License Use Runtime components, you must modify several
statements in your CONFIG.SYS file to include the path for the License Use
Runtime SRK. The path you add to your CONFIG.SYS file must be the same as the
path you specified during installation. The installation procedure uses C:\IFOR
as the default path for executable files and dynamic link libraries.

   1. Open your CONFIG.SYS file with a text editor.

   2. Add the License Use Runtime directory to your LIBPATH statement. If you
      use the default path, your edited LIBPATH statement might look like this:

            LIBPATH=C:\IFOR\LS\DLL;C:\IFOR\NCE\GNE\DLL;

   3. Add the License Use Runtime directory to your SET PATH and SET DPATH
      statements. If you use the default path, your edited SET PATH and SET
      DPATH statements might look like these:

            SET
            PATH=C:\IFOR\LS\BIN;C:\IFOR\NCE\GNE\BIN;
            SET
            DPATH=C:\IFOR\LS\BIN;C:\IFOR\NCE\GNE\BIN;

   4. Update your SET LANG statement like this:

            SET LANG=EN_US

   5. Add the following two statements, where C is the default path:

            DEVICE=C:\IFOR\LS\BIN\I4NODOS2.SYS
            /B:C:
            SET I4_INSTALL_DRIVE=C:

   6. Save your modified CONFIG.SYS file and exit the text editor.

   7. Shut down your workstation.

   8. Start your workstation again, then follow the instructions in --
      Reference sccfg not found --..


ΓòÉΓòÉΓòÉ 7. Hints and Tips ΓòÉΓòÉΓòÉ

Read the following chapter to better manage your licensing environment.


ΓòÉΓòÉΓòÉ 7.1. Enforcing the Soft Stop ΓòÉΓòÉΓòÉ

If you have purchased less licenses than you use, read this section to
determine the number of extra licenses you need.


ΓòÉΓòÉΓòÉ 7.1.1. Enforcing the Soft Stop for Customer-Managed Use Products ΓòÉΓòÉΓòÉ

For customer-managed use product licenses, if you set the threshold to a
certain level, and set the purchased licenses field value to the number of
licenses you purchased, you get a periodic warning message when the threshold
is reached.

When you reach 100% of usage for the product, increase the number of purchased
licenses so that the threshold is reached when all the purchased licenses are
in use. For a period of time see how many more licenses are used over the
acquired limit, but under the new purchased licenses field value.

When you have determined the number of licenses you need over the number you
have, contact the vendor to purchase new licenses.

For example, suppose you have purchased 200 licenses, and you have set the
threshold to 80%. You will get a warning message when at least 160 licenses are
in use.

When all the 200 licenses are in use, update the number of purchased licenses
to 250. In this way the 80% of the threshold is exceeded when more than 200
licenses are in use. After this, check how many concurrent licenses are in use,
and, suppose they are 230, contact the vendor and purchase 30 licenses, then
set the purchased licenses filed value to 230.


ΓòÉΓòÉΓòÉ 7.1.2. Enforcing the Soft Stop for Meter-Enabled Products ΓòÉΓòÉΓòÉ

For meter-enabled product licenses, if you set the threshold to a certain
level, and distribute the purchased licenses, you get a periodic warning
message when the threshold is exceeded.

When you reach 100% of usage for the product, distribute other licenses, so
that the threshold is reached when all the purchased licenses are in use. For a
period of time see how many extra licenses are used over the acquired limit,
but under the number of total distributed licenses.

When you have determined the number of licenses you need over the number you
have, contact the vendor to purchase new licenses.

For example, suppose you have purchased 200 licenses, and you have set the
threshold to 80%. You will get a warning message when at least 160 licenses are
in use.

When all the 200 licenses are in use, distribute 50 extra licenses. In this way
the 80% of the threshold is exceeded when more than 200 licenses are in use.
After this, check how many concurrent licenses are in use, and, suppose they
are 230, contact the vendor and purchase 30 licenses, then delete the 50 extra
distributed licenses, and distribute the 30 new purchased licenses.


ΓòÉΓòÉΓòÉ 7.2. Managing Licenses for Meter-Enabled Products ΓòÉΓòÉΓòÉ

Here are some tips on how to use meter-enabled products.


ΓòÉΓòÉΓòÉ 7.2.1. Distributing Licenses ΓòÉΓòÉΓòÉ

If you have more than one server in your environment, it is suggested that you
distribute at least one license of the meter-enabled product on the machine on
which the administration server runs.

In a namespace binding environment the administration server is on the machine
where the New global location broker is started.


ΓòÉΓòÉΓòÉ 7.2.2. Reducing the Number of Distributed Licenses ΓòÉΓòÉΓòÉ

The way to decrease the number of licenses for a meter-enabled product is to
delete the distributed licenses in groups. If the sum of licenses in the groups
you delete contains more licenses than those you really want to delete, you
then have to distribute again some licenses.

For example, if you want to use 200 licenses of a product, distribute them in 2
groups, one with 150, the other with 50 licenses. In this way, if you want to
reduce the number of licenses by, for instance, 30, delete the group of 50
licenses, and distribute 20 more licenses.

To delete a group of licenses, follow these steps:

   1. Select the product on the Basic License Tool main window

   2. Select Open as details from the Selected pull down menu

   3. Select the Concurrent tab in the Details notebook

   4. Here you will find the list of separate groups of licenses you
      distributed

   5. Select the group you want to remove, then select Delete from the Selected
      pull down menu.


ΓòÉΓòÉΓòÉ 7.2.3. Using Different Versions of a Product ΓòÉΓòÉΓòÉ

If two different versions of the same product have the same executable name,
and you want to meter both of them, you must rename one of the executable files
before meter-enabling them.

The executable names of the running programs must match the ones entered when
meter-enabling them.

For example, if you want to monitor the use of Editor Version 1, and Editor
Version 2, and their executable name is ed, rename one of them to ed2, and then
enter the two different names when meter enabling them.


ΓòÉΓòÉΓòÉ 7.3. Operating in a Mixed Environment: OS/2 and AIX ΓòÉΓòÉΓòÉ

If in your licensing environment you have OS/2 and AIX servers, to allow the
interoperability between them you have to set the same timezone variable.

For example, if the timezone on the AIX server is EST5DST, add the following
line to the CONFIG.SYS of the OS/2 server:

SET TZ=EST5DST


ΓòÉΓòÉΓòÉ 7.4. Implementing a Backup and Recovery Procedure ΓòÉΓòÉΓòÉ

Because the physical breakdown of license servers may have a potentially severe
impact on production, you should set up a backup and recovery procedure when
you start using License Use Runtime. This section describes how to be prepared
in the following cases:

     Definitions and database files are corrupted.
     The operating system has to be recovered or reinstalled from scratch.

 The minimum backup activity expected of the system administrator is to keep
 the enrollment certificate received from the license provider in a secure
 place.


ΓòÉΓòÉΓòÉ 7.4.1. Causes for Corrupted Definition or Database Files ΓòÉΓòÉΓòÉ

There are many situations that can cause the definition or database files to
get corrupted. The most common causes may be split into two groups

     NCS-related issues
     License Use Runtime-related issues

 NCS-related issues

 The NCS definition and database files are static and linked to network
 addresses. For this reason, changing definitions or adapters within the
 network may lead to connection errors. The following files are used by the
 local location broker (i4llbd) and global location broker (i4glbd) processes
 during startup to establish connection with the network and to register
 objects.

     The i4llbd process uses the \ifor\etc\llbdbase.dat file
     The i4glbd process uses the \ifor\etc\glb.e database

 License Use Runtime-related issues

 Since License Use Runtime uses the database files dynamically, any
 disk-related problems like the following may cause the database files to
 become corrupted:

     Hardware failures (media surface errors)
     File-system problems (for example, file system full)
     Synchronization errors during write of data (that is, loss of electrical
      power)

 When a License Use Runtime database is corrupted, problem determination
 procedures should be performed after the database is recovered to find out the
 real cause of the problem.

 The contents of the definition and database files used by NCS and by License
 Use Runtime are changed only by defined administrative commands and tools.

 The contents of the following dynamically updated files are rebuilt, in case
 of corruption and deletion, whenever the i4glbd and the i4lmd processes,
 respectively, are started.

     glb.p
     cur_db


ΓòÉΓòÉΓòÉ 7.4.2. Backup of the NCS and License Use Runtime Configuration Files ΓòÉΓòÉΓòÉ

Save the following files on all your clients and servers:

     \ifor\etc\glb_obj.txt (if it exists)
     \ifor\etc\glb_site.txt (if it exists)
     \ifor\ls\conf\i4ls.ini

 The preceding files must be saved after the first or later configurations. The
 tool used to change these files is the Configuration Tool.


ΓòÉΓòÉΓòÉ 7.4.3. Backup of the License Use Runtime Database Files ΓòÉΓòÉΓòÉ

On Clients:

Save the following database files located in the \ifor\ls\conf directory:

     nodelock
     i4conmgr.log

 The i4conmgr.log is the default name for a file that you might have renamed in
 the Log page of the Nodelock Administration Tool.

 On Servers:

 Stop all running License Use Runtime processes either clicking on the Service
 Manager Tool icon in the License Use Runtime folder, and then selecting Stop
 from the Services pull down menu, or issuing the following command:

  \ifor\ls\bin\i4cfg -stop

 Then save the following database files located in the \ifor\ls\conf directory:

     lic_db
     gdb_db
     log_file
     nodelock
     i4conmgr.log

 The i4conmgr.log is the default name for a file that you might have renamed in
 the Log page of the Nodelock Administration Tool.

 The log_file is the default name for a file that you might have renamed in the
 Log page of the Configuration Tool.

 Save the preceding files periodically. You may want to save them after
 creation and whenever changed. The administrative commands and tools used to
 change these files are:

 i4blt or Basic License Tool
           Administer vendor, product, and license information. This
           administrative tool can be used to change the contents of the
           lic_db, gdb_db, and log_file databases.

 i4nat or Nodelock Administration Tool
           Used to update the nodelock and the i4conmgr.log files.


ΓòÉΓòÉΓòÉ 7.4.4. Recovery of the NCS and License Use Runtime Configuration Files ΓòÉΓòÉΓòÉ

On Clients

   1. Delete the following files:

          \ifor\etc\glb_obj.txt (if it exists)
          \ifor\etc\glb_site.txt (if it exists)
          \ifor\ls\conf\i4ls.ini

   2. Restore the following deleted files from the backup you did:

          \ifor\etc\glb_obj.txt (if it was deleted)
          \ifor\etc\glb_site.txt (if it was deleted)
          \ifor\ls\conf\i4ls.ini

 On Servers

 Stop all running NCS and License Use Runtime processes either clicking on the
 Stop Services icon in the License Use Runtime Configuration - Icon View
 folder, or issuing the following command:

  \ifor\ls\bin\i4cfg -stop

 Then do the following:

   1. Delete the following files:

          \ifor\etc\llbdbase.dat (if it exists)
          \ifor\etc\glb_obj.txt (if it exists)
          \ifor\etc\glb_site.txt (if it exists)
          \ifor\etc\glb_log (if it exists)
          \ifor\etc\glb.e (if it exists)
          \ifor\etc\glb.p (if it exists)
          \ifor\ls\conf\i4ls.ini

   2. Restore the following deleted files from the backup you did:

          \ifor\etc\glb_obj.txt (if it was deleted)
          \ifor\etc\glb_site.txt (if it was deleted)
          \ifor\ls\conf\i4ls.ini

   3. In a namespace binding environment, if your corrupted server is in an NCS
      cell that has more than one server running the global location broker,
      and if in the i4ls.ini you are restoring there is the following line:

            RunGLBD=yes

      issue the following command on the corrupted server:

        a.

                      \ifor\nce\gne\bin\i4drmadm

        b. Set the object to be worked on to global location broker. For
           example:

                      drmadmin.: set -o glb -h ip:HostName

           replace ip with the actual protocol your machine uses, and HostName
           with your actual machine host name):

        c. Synchronize all the GLBs in the cell:

                      drmadmin: merge -from ip:otherhost

           Where otherhost is one of the other servers running the global
           location broker in the cell.

   4. Restart the NCS and License Use Runtime processes either clicking on the
      Start Services icon in the License Use Runtime Configuration - Icon View
      folder, or issuing the following command:

            \ifor\ls\bin\i4cfg -start


ΓòÉΓòÉΓòÉ 7.4.5. Recovery of the License Use Runtime Database Files ΓòÉΓòÉΓòÉ

On Clients

Follow these steps only on the corrupted machines:

   1. Delete the following files from the \ifor\ls\conf\ directory:

          nodelock
          nodelock.bak
          i4conmgr.log

   2. Restore the following deleted files from the backup you did in the
      \ifor\ls\conf\ directory:

          nodelock
          i4conmgr.log

 On Servers

 On all the servers stop the running License Use Runtime processes either
 clicking on the Service Manager Tool icon in the License Use Runtime folder,
 and then selecting Stop from the Services pull down menu, or issuing the
 following command:

  \ifor\ls\bin\i4cfg -stop

 Then do the following:

   1. Delete the following files from the \ifor\ls\conf\ directory:

          nodelock
          nodelock.bak
          i4conmgr.log
          lic_db
          cur_db
          lic_db.bak
          gdb_db
          gdb_db.bak
          log_file
          gdb_cr
          gdb_lf

   2. Restore the following deleted files from the backup you did in the
      \ifor\ls\conf\ directory:

          nodelock
          i4conmgr.log
          lic_db
          gdb_db
          log_file

   3. Restart the License Use Runtime processes either clicking on the Service
      Manager Tool icon in the License Use Runtime folder, and then selecting
      Start from the Services pull down menu, or issuing the following command:

            \ifor\ls\bin\i4cfg -start


ΓòÉΓòÉΓòÉ 7.5. Managing the Reports Log File ΓòÉΓòÉΓòÉ

When you ask for a report, the Basic License Tool reads the file:

ifor\ls\conf\log_file

This file can get very big and take all the space on your disk. To avoid this,
it is suggested that you periodically apply the following procedure:

   1. Generate all the types of reports, that are:

          Standard, with the All events filter selected
          License requests by product
          License requests by user
          License use by product
          License use by user
          License distribution audit

      and save all of them on files. To generate reports see TME 10 NetFinity
      Server Scenarios.

   2. Copy all the report files and the ifor\ls\conf\log_file on an external
      support.

   3. Clean the log file issuing the following License Use Runtime command:

            i4blt -x delete_date -n server_name

      where:

      delete_date
                     Specifies an end date for the delete operation. All log
                     entries recorded before the delete date are removed from
                     the log file. If you do not specify a date all the entries
                     are deleted. Be sure to specify a date included in the
                     date range you specified generating the reports.

      server_name
                     Specifies the license server where you want to delete the
                     entries of the log file.


ΓòÉΓòÉΓòÉ 7.6. Managing the Coexistence between NCS and DCE ΓòÉΓòÉΓòÉ

If in your network environment you have applications, such as Directory
Services and Security (DSS), that use the Distributed Computing Environment
(DCE), and License Use Runtime configured in namespace binding and using TCP/IP
as transport protocol, read this section.

Both the NCS local location broker, and the DCE daemon use the same TCP/IP port
number, 135, that has been assigned them.

Since the NCS local location broker can be replaced by the DCE daemon, do the
following:

   1. Open the ifor\ls\conf\i4ls.ini file with an editor, and add the following
      entry:

            DCED=yes

      in the already existing section [iFOR/LS NCS-Server]

   2. Start the application that includes the DCE daemon before starting
      License Use Runtime services.

 To start the License Use Runtime services issue the following command:

  ifor\ls\bin\i4cfg -start

 or double-click on the Start Services icon in the License Use Runtime
 Configuration - Icon View folder.


ΓòÉΓòÉΓòÉ 8. Troubleshooting ΓòÉΓòÉΓòÉ

This chapter provides a checklist of hints for debugging, problem determination
and performance improving when using products managed with License Use Runtime.

If you are running OS/2 2.1 ensure that you have the XR_F018 OS/2 CSD installed
on your machine before installing either the SRK or the CRK. This will prevent
SYS3170 errors from occurring when you start or run SystemView License Use
Management Runtime for OS/2 tools or interactive interfaces.


ΓòÉΓòÉΓòÉ 8.1. Troubleshooting Nodelocked Licenses ΓòÉΓòÉΓòÉ

If a node with a nodelocked license does not allow an end user to use the
corresponding product, check the following:

     That the name and path of the nodelock file are correct. The name should
      be nodelock and it should be in the IFOR\LS\CONF directory.
     That the date and time on your machine are set correctly. Each nodelocked
      license has a start date and an end date built into it. If your machine
      date is set to the wrong date and time, the license may not be recognized
      as active.
     That the license you received is the correct license for the software you
      are running. The nodelocked license must be for the same version of the
      application that you are running.


ΓòÉΓòÉΓòÉ 8.2. Troubleshooting Concurrent-Use and Use-Once Licenses ΓòÉΓòÉΓòÉ

If a node with a concurrent-use or use-once license does not allow an end user
to use the corresponding product, do the following:

     If you are using TCP/IP, make sure that it is running.
     Check that the license for the application you are running is installed
      on your server machine. If the license is not installed on the server,
      you need to install it.
     Verify the following:
        -  That the product version of the installed license is the same as the
           product version of the application you are attempting to run.
        -  That normal TCP/IP, NetBIOS, or IPX communications can occur between
           the client machine and server machine. (Verify that client and
           server are configured to communicate with the same transport
           protocol).
        -  That the date and time on the server and client are synchronized.

           If client and server are geographically far away from each other and
           they use TCP/IP check the time zone (tz) variable in the config.sys.
     If the server machine where the licenses are installed is configured in a
      namespace binding environment, check that the needed License Use Runtime
      processes are running properly on it, and that the first server in the
      cell is running the i4gdb, To verify which processes must be running see
      the table in Summarizing the Processes Requirements.

      To check the list of running processes double-click on the Service
      Manager Tool icon in the License Use Runtime folder.
     If one or more of the above is not running, select Stop from the Services
      pull-down menu to shut down all the processes normally required for the
      license server to work.

      To restart the processes, select Start from the Services pull-down menu.
      Check to see if your license server is now running.
     If your license server still does not respond, check the error messages
      in the i4ls.log file in the IFOR\LS\BIN directory, or in the glb_log file
      in the IFOR\ETC directory, or reconfigure your license server. (Before
      reconfiguring stop the processes).

      Start the processes after configuration.

      Try to run the application on your client machine. If your license
      requests are still not being granted, then one or both of the following
      is probably true.
        -  The client machine is in a different NCS cell from the license
           server. To join the same cell as the license server, reconfigure
           your client machine. Refer to Using Namespace Binding
        -  The client machine is in a different communications subnetwork from
           the global location broker (GLB), and cannot contact the GLB through
           the normal broadcasts (the GLB is used to help the client talk with
           the license server). Reconfigure the client machine to direct
           communications to the GLB. Or, you may configure the client in
           direct binding mode. See Using Direct Binding.
        -  The client machine is configured in direct binding, but it does not
           point to the right server. Reconfigure the client to bind it to the
           right server.


ΓòÉΓòÉΓòÉ 8.3. Troubleshooting NCS ΓòÉΓòÉΓòÉ

 If the license server uses namespace binding, a failure in NCS can cause
License Use Runtime to degrade in performance or fail altogether. It is often
the case that a License Use Runtime problem is actually a problem in the state
of NCS at that instant. There are several ways to clean up NCS and return the
system to a stable, smooth-running operation. The cleanup method you use
depends on the size and complexity of your network.


ΓòÉΓòÉΓòÉ 8.3.1. NCS Cell Fixup for License Use Runtime ΓòÉΓòÉΓòÉ

Here are some methods to clean up the NCS environment.


ΓòÉΓòÉΓòÉ 8.3.1.1. Quick and Easy NCS Cell Fixup ΓòÉΓòÉΓòÉ

If products with server-based licenses running on the clients do not start, and
the related licenses are installed on the server, check the file
ifor\ls\conf\i4ls.log on the server. If you see NCS communication errors, the
easiest way to bring your server back up is to reconfigure it from the
beginning.

 This method is best for any of the following situations:

     You are running a stand-alone (non-networked) server.
     You have only one server in the cell, and the cell has few client
      machines.
     Your server is a member of a cell that has other servers with global
      location brokers running.


ΓòÉΓòÉΓòÉ 8.3.1.2. Manual NCS Cell Fixup ΓòÉΓòÉΓòÉ

If your license server machine is the only server machine in an alternate cell
with many clients, it may not be practical to rerun the configuration tool.
Doing so would regenerate the glb_obj.txt file on the server, and that would
then need to be copied to each client machine. In such a situation, you can
quickly reconfigure the NCS cell and restart the license server by using the
following instructions. This will preserve your glb_obj.txt file, keeping your
cell identifier the same so that it does not have to be changed on your client
machines.

   1. To stop the license server process and the location broker processes
      double-click on the Stop Services icon in the License Use Runtime
      Configuration - Icon View folder.
   2. Delete any previously configured location broker databases. From
      ifor\etc\ directory in the drive where you have License Use Runtime
      installed, enter the following commands:

            del glb.e
            del glb.p
            del glb_log
            del llbdbase.dat

   3. Start all processes by double clicking on the Start services icon.
   4. Verify that your license server has restarted successfully, checking that
      all server processes are running by clicking on the Active Services List
      icon. To determine which processes must be running on your server see
      Summarizing the Processes Requirements.


ΓòÉΓòÉΓòÉ 8.3.2. Finding Servers in Other Subnets ΓòÉΓòÉΓòÉ

The i4lbfind command uses the NCS Remote Procedure Call (RPC) broadcasting
mechanism to find GLB servers in the network. Because RPC broadcasting is
limited to the local network, GLB servers in different physical subnets and
servers that do not support broadcasting cannot be located. To solve this
problem the glb_site.txt file can be used to directly contact global location
broker (GLB) servers, even across the subnet (gateways and routers). This will
work if the GLB server is a member of the default cell (that is the glb_obj.txt
file does not exist on the machine) or if the local machine joins the GLB
server's cell (that is the server's glb_obj.txt file must be copied to the
local machine).

See Accessing the License Server of a Different Subnetwork for further
information on the glb_site.txt file.


ΓòÉΓòÉΓòÉ 8.3.3. Cleaning Up Location Broker Databases ΓòÉΓòÉΓòÉ

When an NCS cell is running several global location brokers (GLBs), the
database at each GLB node must be kept synchronized with the others. This
allows any GLB in the cell to satisfy a location request by a client.
Occasionally, a GLB will be removed, or a license server will be stopped
without being shut down properly. This usually results in invalid entries being
left in the GLB databases. This can introduce significant delays when
applications attempt to get licenses for execution, or when running the Basic
License Tool.

In such configurations, you cannot clean up the GLB databases by simply
removing and adding back a server.


ΓòÉΓòÉΓòÉ 8.3.3.1. Periodical Cleaning Up ΓòÉΓòÉΓòÉ

An automatic periodical cleaning up of stale entries in the global location
broker database, is set up by default. If you want to change the settings of
the periodical cleaning up, edit the ifor\ls\conf\i4ls.ini configuration file
and set the values of the following tags:

 SelfClean The cleaning enabling flag. Its possible values are:

               yes
               no

           The default value is yes

 Frequency The number of minutes between one cleaning up and the following. Its
           allowed values are between 15 and 43200. The default value is 180

 Timeout   The type of timeout. Its possible values are:

               long
               short

           The default value is long


ΓòÉΓòÉΓòÉ 8.3.3.2. Manual Cleaning Up ΓòÉΓòÉΓòÉ

You must remove the invalid entries by using Local Broker Administration
(i4lbadm) and resynchronize the GLB database by using GLBDs Replicas
Administration (i4drmadm). These tools are located in the License Use Runtime
tools folder. Both tools are interactive. For more information on how to use
these tools refer to the online Command Reference.

To clean up GLB databases, follow these steps:

   1. Start the Local broker administration tool at one of the GLB servers
      double-clicking on its icon, or entering the following command from an
      OS/2 command prompt:

            i4lbadm

   2. Set the object to be worked on to be the local location broker:

            lb-admin: use local

   3. Enter the clean subcommand to remove any invalid entries:

            lb-admin: clean

   4. If prompted to remove entries, type y.
   5. Set the object to be worked on to be the global location broker:

            lb-admin: use global

   6. Use the clean subcommand to remove any invalid entries:

            lb-admin: clean

   7. If prompted to remove entries, type y.
   8. Exit lb_admin by using the quit subcommand:

            i4lbadm: quit

   9. Start the GLBD Replicas Administration tool by double-clicking on its
      icon in the License Use Runtime Tools folder, or by entering the
      following command from an OS/2 command prompt:

            i4drmadm

  10. Set the object to be worked on to global location broker on your machine
      (replace HostName with your actual machine host name):

            drmadmin.: set -o glb -h ip:HostName

  11. Synchronize all the GLBs in the cell:

            drmadmin: merge_all

  12. If messages appear that declare that a host is unreachable, you should
      remove it from the global replica list:

            drmadmin: purgerep ip:HostName
      where Host Name is the host name of this machine that is no longer acting
      as a server.

      If a host machine is purged from the replica list, it should no longer be
      running the global location broker process (i4glbd). If the global
      location broker needs to be run on this machine at a later date,
      configure it and join it to the cell.
  13. Synchronize all the GLBs in the cell:

            drmadmin: merge_all

  14. To exit drm_admin, type the quit subcommand:

            drmadmin: quit


ΓòÉΓòÉΓòÉ 8.4. Handling Communication Failures ΓòÉΓòÉΓòÉ

If the server machine goes down, the current license transaction is stored on
disk. The server will return to the same state when it is restarted.

If the client machine goes down, the server reclaims the licenses after the
check period expires.

If the network fails, the server reclaims the licenses after the check period
expires. The client behavior depends on the single software product that is in
use.


ΓòÉΓòÉΓòÉ 8.5. Collecting Error Log Data ΓòÉΓòÉΓòÉ

In order to help us helping you in problem determination you should gather
additional information to send to your IBM representative. License Use Runtime
processes and tools can be run in traced mode as explained in the following
sections.


ΓòÉΓòÉΓòÉ 8.5.1. Running Processes in Traced Mode ΓòÉΓòÉΓòÉ

To run License Use Runtime processes in traced mode follow these instructions:

   1. Stop all active processes either clicking on the Stop Services icon in
      the License Use Runtime Configuration - Icon View folder, or issuing the
      following command:

            \ifor\ls\bin\i4cfg -stop

   2. Edit the file:

            \ifor\ls\conf\i4ls.ini

      and set to yes the following tags:

          DebugProc=yes
          DebugNCS=yes

   3. Re-start the processes either clicking on the Start Services icon in the
      License Use Runtime Configuration - Icon View folder, or issuing the
      following command:

            \ifor\ls\bin\i4cfg -start

   4. Produce the error condition again.

 The trace information is contained in the OS/2 windows titled with the names
 of the processes in the OS/2 Window List. You can also redirect the processes
 output to files issuing the following commands in the same order as they are
 written:

  start i4nbssvr your_machine_name NB_BCAST 0

  start i4llbd -dl > i4llbd.out

  start i4glbd -create -first -family netbios -debug -rpc_debug
               -log_stdout > i4glbd.out

  start i4lmd -v > i4lmd.out

  start i4gdb -a -v > i4gdb.out

 The output is collected in the files with extension out. You may be requested
 to send them to the IBM support in case you detect errors.


ΓòÉΓòÉΓòÉ 8.5.2. Collecting Other Data ΓòÉΓòÉΓòÉ

Other information data concerning License Use Runtime servers is automatically
collected by the global location broker (i4glbd) and by the license server
(i4lmd) processes. These data are stored in the following files:

\ifor\etc\glb_log
\ifor\ls\bin\i4ls.log

Most of the messages you find in these files and the related return codes are
not documented.

Provide us also the configuration file:

\ifor\ls\conf\i4ls.ini

If you are in a namespace binding environment, another file you have to provide
us is the \ifor\etc\glb_obj.txt which must be always present when the machine
is part of a non-default NCS Cell. Its content must be the same of NCSCell
keyword in i4ls.ini file.


ΓòÉΓòÉΓòÉ 9. Response File Configuration Keywords ΓòÉΓòÉΓòÉ

License Use Runtime configuration keywords are available on the servers, and on
OS/2 clients only.

Keywords for configuring License Use Runtime are of two types:

     General keywords used for both License Use Runtime OS/2 clients and
      servers
     Server-only keywords that are added to configure License Use Runtime
      servers


ΓòÉΓòÉΓòÉ 9.1. General Keywords ΓòÉΓòÉΓòÉ

 LIC.ConfigureAs
      Specifies the client or server configuration. Possible values are client
      and server.

      Type: Mandatory if License Use Runtime is to be installed. No
      configuration is performed if this keyword is omitted.

 LIC.Username
      Any name you choose, up to 32 alphanumeric characters.

      Type: Optional (if not specified, the default is the SystemName value)

 LIC.Usergroup
      A name of your choice, up to 32 alphanumeric characters.

      Type: Optional (if not specified, the default is DefaultGroupName)

 LIC.Transport
      Type of transport used. The value can be tcpip, netbios, or ipx. You can
      also specify two or all three values; for example,

            LIC.Transport=netbios,tcpip,ipx

      Type: Optional

 LIC.Machname
      NetBIOS machine name; a name of your choice, up to 11 alphanumeric
      characters with no embedded blanks.

      Type: Optional; can be specified only if LIC.Transport includes netbios.
      The default is a randomly generated number.

 LIC.LogFile
      Concurrent nodelock log file name. The default is:

            <drive>\IFOR\LS\CONF\I4CONMGR.LOG

      where <drive> is the drive where the product is installed.

      Type: Optional

 LIC.LogLevel
      Concurrent nodelock logging level. The value can be a digit from 0 to 4.

             0 means: no logging
             1 means: log all delete/add/update licenses
             2 means: log only not granted licenses
             3 means: 1 + 2
             4 means: log all events

      The default is 0.

      Type: Optional

 LIC.LogMsgsMaxNum
      Concurrent nodelock maximum number of messages in log. The default is
      10000.

      Type: Optional

 LIC.LanAdaptor
      LAN adapter number. The value can be 0 or 1.  The default is 0.

      Type: Optional

 LIC.NCBS
      Number of NetBIOS NCBs; the recommended, and default, value is 20.

      Type: Optional

 LIC.RunMeteringAgent
      This keyword allows you to start the metering process. The value can be
      yes or no. The default is no.

      Type: Optional

 LIC.GDBRefreshFreq
      The frequency, in minutes, at which the metering process checks the list
      of meter-enabled products in the administration database.

      The metering process compares this list with the list of products running
      on the machine, to determine for which of them it should request a
      license.

      Valid values are 1 to 1440. The default is 5.

      Type: Optional

 LIC.LicCheckFreq
      The frequency, in minutes, at which the metering process calls the server
      to specify that a license for the product is being used.

      Valid values are 1 to 1440. The default is 15.

      Type: Optional

 LIC.ProcPollFreq
      The frequency, in seconds, at which the metering process checks the list
      of products running on the machine.

      The metering process compares this list with the list of meter-enabled
      products in the administration database, so as to determine for which of
      them it should request a license.

      Valid values are 1 to 1440.  The default is 10.

      Type: Optional

 LIC.UseDirectBindingOnly
      This keyword allows you to configure your machine in direct binding only
      mode. The value can be yes or no. The default is no.

      Type: Optional

 LIC.GDBServer
      The address of the administration server.

      If the transport is TCP/IP, it is the IP address. For example:

            ip:alex.rnsl.ibm.com

      If the transport is NetBIOS, it is the machine name. For example:

            netbios:alex

      If the transport is IPX, it is the MAC address. For example:

            ipx:00000002.10005AAF12FA

      Type: Mandatory if LIC.UseDirectBindingOnly is set to yes.

 LIC.NumDirectBindServers
      The number of license servers (excluding the one that is also the
      administration server, specified with the LIC.GDBServer keyword) to
      connect to. Valid values are 0, 1, 2, 3...

      Type: Mandatory if LIC.UseDirectBindingOnly is set to yes.

 LIC.NumDirectBindServern
      The address of an additional license server (excluding the administration
      server, specified with the LIC.GDBServer keyword) to connect to. Code
      this keyword once for each additional license server, starting with n=1
      and increasing n by 1.

      If the transport is TCP/IP, it is the IP address. If the transport is
      NetBIOS, it is the machine name. If the transport is IPX, it is the MAC
      address. For example:

            LIC.NumDirectBindServer2=ip:alex.rnsl.ibm.com
            LIC.NumDirectBindServer3=netbios:alex
            LIC.NumDirectBindServer1=ipx:00000002.10005AAF12FA
            .
            .
            .

      Type: Optional


ΓòÉΓòÉΓòÉ 9.2. Server-Only Keywords ΓòÉΓòÉΓòÉ

 LIC.Create
      Configure the server as a new Global Location Broker in a new cell or as
      a replicate of another Global Location Broker in the same cell. The value
      can be replicate or new. The default is new.

      Type: Mandatory

 LIC.Family
      Transport used by Global Location Broker. The value can be ip, netbios,
      or ipx. If LIC.Transport=tcpip, LIC.Family must be ip. If
      LIC.Transport=netbios, LIC.Family must be netbios. If LIC.Transport=ipx,
      LIC.Family must be ipx.

      Type: Mandatory if LIC.Create=new

 LIC.RunGLBD
      Run Global Location Broker flag. The value can be yes or no (always yes
      if LIC.Create=new; if LIC.Create=replicate, the keyword is optional and
      the default is yes.)

      Type: Optional

 LIC.DisableRemoteAdmin
      Disable remote administration flag. The value can be yes or no; the
      default is no.

      Type: Optional

 LIC.ServLogFile
      Server log file full path and name. The default is:

            <drive>\IFOR\LS\CONF\LOG_FILE

      where <drive> is the drive where the product is installed.

      Type: Optional

 LIC.LogAllEvents
      Log all the events. The value can be yes or no; the default is no.

      Type: Optional

 LIC.LogGrant
      Log the license granting. The value can be yes or no; the default is yes.

      Type: Optional

 LIC.LogCheckin
      Log license checkin. The value can be yes or no; the default is no.

      Type: Optional

 LIC.LogWait
      Log the license wait. The value can be yes or no; the default is yes.

      Type: Optional

 LIC.LogVendor
      Log vendor added/deleted. The value can be yes or no; the default is yes.

      Type: Optional

 LIC.LogProduct
      Log product added/deleted. The value can be yes or no; the default is
      yes.

      Type: Optional

 LIC.LogTimeout
      Log license timeout. The value can be yes or no; the default is yes.

      Type: Optional

 LIC.LogErrors
      Log errors. The value can be yes or no; the default is yes.

      Type: Optional

 LIC.LogVendorMsg
      Log vendor messages. The value can be yes or no; the default is yes.

      Type: Optional

 LIC.LogSvrStartStop
      Log server start/stop. The value can be yes or no; the default is yes.

      Type: Optional


ΓòÉΓòÉΓòÉ 10. Glossary ΓòÉΓòÉΓòÉ

This glossary defines License Use Runtime abbreviations and terms. It includes
terms and definitions from the IBM Dictionary of Computing, New York:
McGraw-Hill, 1994, which defines many additional data processing terms.


ΓòÉΓòÉΓòÉ 10.1. administrator ΓòÉΓòÉΓòÉ

The person who is responsible for setting up the License Use Runtime for OS/2
environment. The tasks of the administrator are:

     Configuring the network.
     Installing and configuring the License Use Runtime SRK on the server
      nodes of the network.
     Supporting end users in the installation and configuration of the License
      Use Runtime CRK on the client nodes of the network.
     Installing the software product licenses on the servers.
     Monitoring the software products use through the Basic License Tool.


ΓòÉΓòÉΓòÉ 10.2. administration database ΓòÉΓòÉΓòÉ

A database containing information about the enrollment and distribution of
Customer-Managed Use Control products, and of meter-enabled products.

See also Administration Database Server to have more information.


ΓòÉΓòÉΓòÉ 10.3. annotation ΓòÉΓòÉΓòÉ

See license annotation. See -- Reference scserbs not found -- for details on
how to use the Basic License Tool.


ΓòÉΓòÉΓòÉ 10.4. binding ΓòÉΓòÉΓòÉ

There are two types of binding mechanisms in which you can configure your
machine:

 Direct binding
           With this mechanism, the client applications locate license servers
           configured for direct binding, reading a local text file with the
           network addresses of these license servers.

           License Use Runtime servers configured only for direct binding
           listen for incoming communications on two well-known ports (1515 and
           10999). The client code uses these port numbers, together with the
           network addresses of the server systems specified in the text file,
           to locate and connect to the servers.

 Namespace binding
           With this mechanism, the license servers register themselves with an
           entity called global location broker; the client applications locate
           them using standard NCS location broker services. Namespace binding
           also allows the license server to support direct binding client
           applications.

 See also Using Namespace Binding and Using Direct Binding for more details.


ΓòÉΓòÉΓòÉ 10.5. cell ΓòÉΓòÉΓòÉ

See NCS cell.


ΓòÉΓòÉΓòÉ 10.6. client ΓòÉΓòÉΓòÉ

The end user machine on which the License Use Runtime CRK is installed.


ΓòÉΓòÉΓòÉ 10.7. compound password ΓòÉΓòÉΓòÉ

A key that specifies multiple nodelocked, concurrent access, or use-once
licenses. After installing it, you can extract a key containing a specified
number of licenses from the compound password.

The compound password cannot be used by enabled applications until the license
keys are extracted from it.

Note:  Extracting a license key means distributing from a compound password.


ΓòÉΓòÉΓòÉ 10.8. concurrent access license ΓòÉΓòÉΓòÉ

A type of license administered by the license server that can be used by
different users from any node that is connected to a license server node.
Concurrent access licenses enable as many users to use a particular software
product concurrently as there are licenses. See -- Reference scserbs not found
-- for details on how to install concurrent access licenses.


ΓòÉΓòÉΓòÉ 10.9. customer-managed use control ΓòÉΓòÉΓòÉ

A form of licensing method that enables the administrator to distribute a
virtually unlimited number of licenses from compound passwords shipped as part
of the enrollment certificate.

See Customer-Managed Use Products for further details.


ΓòÉΓòÉΓòÉ 10.10. default NCS cell ΓòÉΓòÉΓòÉ

A cell that is identified by the default GLB object UUID. You can recognize
machines that are in the default cell because they do not have the glb_obj.txt
file in the ifor\etc directory.


ΓòÉΓòÉΓòÉ 10.11. direct binding ΓòÉΓòÉΓòÉ

See binding.


ΓòÉΓòÉΓòÉ 10.12. end user ΓòÉΓòÉΓòÉ

The user of the software products enabled with License Use Toolkit for OS/2.
The tasks of the end users are:

     Installing the License Use Runtime CRK with the help of the
      administrator.
     Configuring the License Use Runtime CRK only if they are going to use
      other than nodelocked licenses.
     Installing nodelocked licenses on the License Use Runtime clients.


ΓòÉΓòÉΓòÉ 10.13. enrollment certificate ΓòÉΓòÉΓòÉ

A mechanism for the distribution of licenses to end users. It is usually in the
form of an electronic file, and contains all the information related to the
enabled product licenses you purchased.


ΓòÉΓòÉΓòÉ 10.14. Basic License Tool ΓòÉΓòÉΓòÉ

The interactive tool included in the License Use Runtime for OS/2, that enables
the administrator to add or delete licenses from the server database, display
the licenses installed, distribute the licenses among the servers available on
the network, and generate reports on license usage and server events.


ΓòÉΓòÉΓòÉ 10.15. folder ΓòÉΓòÉΓòÉ

An icon on the OS/2 workstation desktop that is used to store and organize
objects and information.


ΓòÉΓòÉΓòÉ 10.16. gdb server ΓòÉΓòÉΓòÉ

See administration database.


ΓòÉΓòÉΓòÉ 10.17. generic database ΓòÉΓòÉΓòÉ

See administration database.


ΓòÉΓòÉΓòÉ 10.18. GLB ΓòÉΓòÉΓòÉ

See global location broker.


ΓòÉΓòÉΓòÉ 10.19. glbd replica ΓòÉΓòÉΓòÉ

A copy, on a new server, of a global location broker database already existing
on another  server.

You can make a replica when configuring a server in namespace binding. In this
way the new server will join the same NCS cell as the one that is replicated.


ΓòÉΓòÉΓòÉ 10.20. glb_obj.txt ΓòÉΓòÉΓòÉ

A file specifying the object UUID of the global location broker. The
glb_obj.txt file allows you to  override the default value by specifying a
different GLB object UUID for a particular machine. The glb_obj.txt file is
used only in special configurations that require several disjoint GLB databases
(each of which is possibly replicated). In  most networks and internets, there
is only one GLB database (possibly  replicated), and machines do not need to
have a glb_obj.txt file. If a machine has a glb_obj.txt file, the UUID in the
file identifies the GLB object to which that machine directs lookups and
updates. You would only have a glb_obj.txt file if you have created an
alternate cell or if you choose an existing alternate cell for the system cell
name.


ΓòÉΓòÉΓòÉ 10.21. global location broker ΓòÉΓòÉΓòÉ

Part of the Network Computing System (NCS), that helps clients to locate
servers on a network or internet. It is a process that manages a database that
stores the locations (network addresses and port numbers) where server
processes are running.  The global location broker process maintains this
database and provides access to it. The GLB actually maintains information
about objects and interfaces throughout the network or internet.

See Running the Location Brokers for more details.


ΓòÉΓòÉΓòÉ 10.22. internet ΓòÉΓòÉΓòÉ

A set of two or more connected networks. The networks in an internet do not
necessarily use the same communications protocol. SystemView License Use
Management Runtime for OS/2 supports the following protocols on OS/2:

     NetBIOS
     TCP/IP
     IPX


ΓòÉΓòÉΓòÉ 10.23. IPX ΓòÉΓòÉΓòÉ

A communication protocol that creates, maintains, and terminates connections
among network devices (workstations, file servers, or routers, for example).


ΓòÉΓòÉΓòÉ 10.24. i4blt ΓòÉΓòÉΓòÉ

The command to do administrative tasks on the License Use Runtime servers. See
the online Command Reference.


ΓòÉΓòÉΓòÉ 10.25. i4lmd ΓòÉΓòÉΓòÉ

A string used to launch the license server. See also license server.


ΓòÉΓòÉΓòÉ 10.26. key ΓòÉΓòÉΓòÉ

See license key.


ΓòÉΓòÉΓòÉ 10.27. license ΓòÉΓòÉΓòÉ

Permission to use an instance of a licensed software product or service.
Sometimes, a user needs more than one license to make full use of a particular
product features.

See also Understanding License Types for further details.


ΓòÉΓòÉΓòÉ 10.28. license annotation ΓòÉΓòÉΓòÉ

A string that can be used to modify the use of a license as defined by the
vendor of the software product.


ΓòÉΓòÉΓòÉ 10.29. license database ΓòÉΓòÉΓòÉ

The database of the licenses maintained by a license server.


ΓòÉΓòÉΓòÉ 10.30. license enabled product ΓòÉΓòÉΓòÉ

A product that is enabled for license use management.

The vendors provide you with the license enabled products together with a
protection key, or password, that authorizes you to use the product. The
password contains an encryption of the terms of the contractual agreement (how
many licenses the customer can use, the expiration date of the licenses, and
the type of license).


ΓòÉΓòÉΓòÉ 10.31. license information ΓòÉΓòÉΓòÉ

The information that describes licenses. This information consists of the
product name, the product version, the number of licenses, the license type,
the start and end dates for the licenses, and a time stamp.


ΓòÉΓòÉΓòÉ 10.32. license key ΓòÉΓòÉΓòÉ

A string encoded with the license information for a software product. The two
types of license keys are:

     simple
     compound


ΓòÉΓòÉΓòÉ 10.33. license model ΓòÉΓòÉΓòÉ

A method of licensing a software product with License Use Runtime for OS/2. The
two basic licensing models are:

     Customer-Managed Use Control
     Vendor-Managed Use Control


ΓòÉΓòÉΓòÉ 10.34. license password ΓòÉΓòÉΓòÉ

See license key.


ΓòÉΓòÉΓòÉ 10.35. licensed product ΓòÉΓòÉΓòÉ

A software product that has been licensed under SystemView License Use
Management Runtime for OS/2.


ΓòÉΓòÉΓòÉ 10.36. license server ΓòÉΓòÉΓòÉ

A program that provides the actual license services, administering licenses for
software products. It is part of the License Use Runtime for OS/2 and runs on
every machine configured as a server. This name is used to indicate an License
Use Runtime server.


ΓòÉΓòÉΓòÉ 10.37. local location broker ΓòÉΓòÉΓòÉ

Part of the network computing system (NCS).  It manages the local location
broker (LLB) database, which stores information about NCS-based server programs
running on the local host. A host must run the local location broker process
(i4llbd) if it is to support the location broker forwarding function, or allow
remote access to the LLB database. In general, any machine that runs NCS-based
servers must run the i4llbd before starting.

See also Running the Location Brokers for further details.


ΓòÉΓòÉΓòÉ 10.38. location broker ΓòÉΓòÉΓòÉ

See global location broker and local location broker.


ΓòÉΓòÉΓòÉ 10.39. log file ΓòÉΓòÉΓòÉ

A text file that records messages and errors from the license server, and
sometimes licensed products as well.

The default log file is called log_file and is located in the ifor\ls\conf. You
can change its name and location when configuring the machine.

To display its contents use the Report facility of the Basic License Tool.


ΓòÉΓòÉΓòÉ 10.40. namespace binding ΓòÉΓòÉΓòÉ

See binding.


ΓòÉΓòÉΓòÉ 10.41. NCS ΓòÉΓòÉΓòÉ

A set of software components, developed by Apollo Computer Inc., that conform
to the Network Computing Architecture.  These components include the Remote
Procedure Call (RPC) runtime library, and the Location Brokers.

See also Introducing the Network Computing System (NCS) for further details.


ΓòÉΓòÉΓòÉ 10.42. NCS cell ΓòÉΓòÉΓòÉ

A logical grouping of clients and servers; a subset of a network. Machines in
one cell cannot communicate with machines in other cells. Machines cannot be in
more than one cell at a time. Machines in the same cell are identified by the
same global location broker (GLB) object Universal Unique Identifier (UUID).
For machines that are not in the default cell, the file glb_obj.txt in the
ifor\etc directory specifies an alternate UUID.

See also Using Namespace Binding for further details.


ΓòÉΓòÉΓòÉ 10.43. NetBIOS ΓòÉΓòÉΓòÉ

A commonly used transport protocol for PC local area networks introduced with
the IBM PC Network and implemented in Microsoft MS-Net and LAN Manager.
Application programs use NetBIOS for client/server or peer-to-peer
communications.


ΓòÉΓòÉΓòÉ 10.44. network ΓòÉΓòÉΓòÉ

A group of nodes and the links interconnecting them.


ΓòÉΓòÉΓòÉ 10.45. node ΓòÉΓòÉΓòÉ

The machines that constitute the network. They can be either SystemView License
Use Management Runtime for OS/2 clients or servers.


ΓòÉΓòÉΓòÉ 10.46. nodelocked license ΓòÉΓòÉΓòÉ

A type of license locked to a specific node, so that the product can be only
used at that node. The nodelock license is installed on the machine for which
it was created. The license server does not administer nodelocked licenses;
they are stand-alone. A license server does not have to be installed on the
network for an application that runs with a nodelock license. However, the
administrator can install a dynamic nodelock compound password on a server.
When the product running on a client asks for a nodelocked license, the
nodelocked license is extracted from the compound, and installed on the client
node. See -- Reference scnodl not found -- for information on how to enroll a
nodelocked license.


ΓòÉΓòÉΓòÉ 10.47. object ΓòÉΓòÉΓòÉ

In the Network Computing System, an entity that is manipulated by well-defined
operations. Databases, files, directories, devices, processes, and processors
are all objects. Objects are accessed through interfaces. Every object has a
type.


ΓòÉΓòÉΓòÉ 10.48. password ΓòÉΓòÉΓòÉ

A string encoded with information about a software vendor (vendor password), or
about a software product (product password).

See see page Understanding Passwords for further details.


ΓòÉΓòÉΓòÉ 10.49. process ΓòÉΓòÉΓòÉ

A program that runs unattended to perform a standard service.


ΓòÉΓòÉΓòÉ 10.50. product ID ΓòÉΓòÉΓòÉ

A number that identifies a vendor licensed software product. By means of
product IDs, the license server can distinguish between products from the same
vendor.


ΓòÉΓòÉΓòÉ 10.51. replica ΓòÉΓòÉΓòÉ

See glbd replica.


ΓòÉΓòÉΓòÉ 10.52. report ΓòÉΓòÉΓòÉ

A summary of the events related to the licenses installed on the current
server. You can choose filters for the events you want to be displayed.
Examples of events are:

     The number of licenses requested for a product in a given interval of
      time.

     The server startup.


ΓòÉΓòÉΓòÉ 10.53. server ΓòÉΓòÉΓòÉ

The node of the network on which the SystemView License Use Management Runtime
for OS/2 SRK has been installed and configured.


ΓòÉΓòÉΓòÉ 10.54. socket server ΓòÉΓòÉΓòÉ

The process that allows SystemView License Use Management Runtime for OS/2
clients and servers to communicate among them through the NetBIOS protocol.


ΓòÉΓòÉΓòÉ 10.55. target ΓòÉΓòÉΓòÉ

The node at which a password is to be installed. If the password specifies a
single nodelocked license, the target is the node licensed to run the product.


ΓòÉΓòÉΓòÉ 10.56. target ID ΓòÉΓòÉΓòÉ

A unique identifier of a node (either client or server).


ΓòÉΓòÉΓòÉ 10.57. TCP/IP ΓòÉΓòÉΓòÉ

Transmission Control Protocol/Internet Protocol. A set of communication
protocols that support peer-to-peer connectivity functions for both local and
wide area networks.


ΓòÉΓòÉΓòÉ 10.58. time stamp ΓòÉΓòÉΓòÉ

A number that identifies the date and time at which a set of licenses was
created.


ΓòÉΓòÉΓòÉ 10.59. Universal Unique Identifier ΓòÉΓòÉΓòÉ

An identifier that is used by NCS to identify interfaces, objects, and types.


ΓòÉΓòÉΓòÉ 10.60. use-once license ΓòÉΓòÉΓòÉ

A type of license administered by the license server that is effective for only
a single instance of starting a product or using a service. The license server
decrements the number of available use-once licenses each time the product or
service is used.

See Using Products with Use-Once Licenses for further details.


ΓòÉΓòÉΓòÉ 10.61. UUID ΓòÉΓòÉΓòÉ

See Universal Unique Identifier.


ΓòÉΓòÉΓòÉ 10.62. vendor ID ΓòÉΓòÉΓòÉ

The identifier of a vendor of licensed products. Vendor IDs are a License Use
Runtime specific usage of NCS Universal Unique Identifiers (UUIDs).


ΓòÉΓòÉΓòÉ 10.63. Vendor-Managed Use Control ΓòÉΓòÉΓòÉ

See Vendor-Managed Use Products.