Specifications

Chapter 14. License and serial number

servers

A zPDT system must have a license supplied by a 1090 or 1091 token.

In a simple

configuration, a local token is installed in a USB port on the base machine running zPDT. In

this case (one token installed in a local USB port) the token supplies both the zPDT license

and the serial number used for the System z CPs.

For a number of reasons, this simple local

token usage is not always appropriate:

򐂰 Due to security concerns, some PCs no longer have usable USB ports.

򐂰 The physical distribution of tokens may present a problem.

򐂰 Rack-mounted “blade” PCs may not have normal, dedicated USB ports.

򐂰 A token in a work location can easily “walk away.”

򐂰 In virtual environments the dedicated use of a USB port may be a problem.

򐂰 If multiple tokens are used, or are changed, the CP serial numbers become unpredictable.

򐂰 The consistency of the System z serial numbers may be important for some software

licenses (for System z software) and may be important for some System z operating

systems.

Recognizing these concerns, an alternative token and serial number environment that

provides enterprise-wide management is available for zPDT systems.

Briefly, this alternative environment has a license server (which has physical tokens

connected to USB ports) and a unique identifier manager (UIM) server. The license server

can be accessed (TCP/IP) by each client PC running zPDT and the zPDT license is supplied

Important: If you have a simple zPDT system, with a single token connected to a USB port

on your base Linux system, you can ignore this chapter. For more complex environments

(including the use of multiple tokens) you should read this chapter carefully.

Functions described in this chapter apply to zPDT release 41.46 and later.

The tokens identified as 1091 tokens are for RDzUT customers. The material in this chapter applies to both 1090

and 1091 tokens.

This statement assumes that the local zPDT system has never been connected to a remote license server, and has

never used multiple local tokens.