Specifications
150 IBM System z Personal Development Tool: Volume 3 Additional Topics
The uimcheck command should be used if there is any question about the state of the serial
number on a zPDT machine. Any user may issue this command.
Do not run SecureUpdateUtility from a client zPDT machine when using a remote license
server. This utility cannot affect the tokens in the remote license server, but will attempt to
access a token in the local PC. You may run SecureUpdateUtility in the license server, to
update the tokens in the server.
The administrator of a SafeNet license server is responsible for ensuring the license keys do
not expire while in use. The situation in which multiple tokens are installed (in a license
server) and the licenses in one token expire can be complex. Clients see license expiration
warning messages starting a month before the license expires. However, if multiple tokens
are present it is not predictable which token will furnish the license(s) for a zPDT startup.
The license expiration date displayed by the token command (in a client machine) may not
reflect the effective expiration date of all the active token(s) in a license server. The token
command (when zPDT is running) produces additional information, for example:
$ token
CPU 0, zPDTA (1090) available and working. Serial 6186(0x182A)
Lic=88570(0x159FA) EXP=4/15/2012
In this example, the zPDT license was obtained from token 0x159FA (decimal 88570) and the
CP serial number used by zPDT is 0x182A. There is no indication of whether a license server
and UIM server are being used. Since the serial number and license number are different, we
know that at some point the serial number was obtained from a license server. However, it is
possible that the token is in the local client but that the serial number previously obtained from
a UIM server is still being used. This fulfills the goal of using a consistent serial number once
it is assigned.
When zPDT is installed, a new Linux group is created named zpdth. This is used to isolate
execution of certain zPDT modules and should not be used for other purposes.
Disk changes
Changing the Linux disk (HDD) changes the identifier that is part of the identification used by
UIM. You may need to reset the local serial number (uimreset -l) or the remote serial
number (uimreset -r) after changing the hard disk.
Cloning zPDT
If you clone a zPDT system, you must delete the files in /usr/z1090/uim on the new system.
This is because the UUID of the new system differs from that of the old system. zPDT will
build new uim files when the new system is started.
14.4 Scenarios
Local to remote server
Consider systems A and B (each using a different PC for zPDT). System A has a zPDT token
with serial number 12345.
The system A owner installs token 12345 in his PC and starts zPDT. When this is done,
serial 12345 is recorded in the local system A UIM database. (This assumes there was no
prior conflicting information in the local UIM database.) System A may be used in this
configuration indefinitely (until the token license expires), with no reference to license or
UIM servers.










