zPDT® licenses in a token or in a software license server are usually valid for a year and must be renewed after that time. The procedure for renewing token licenses varies with different categories of zPDT users.
Users with 1090 tokens (typically ISVs or IBM® internal users) normally create a request file by using the Z1090_token_update -r command and send this file to their zPDT provider. The provider, in turn, returns an update file that is installed with the Z1090_token_update -u command. This example shows one sequence of commands for requesting and installing the update file.
$ awsstop $ su # cd /usr/z1090/bin # Z1090_token_update -r mytoken.req
In this sequence of commands, the file name mytoken.req is an arbitrary name that you provide for the request. The mytoken.req file is sent to the zPDT provider. The provider returns the file mytoken.zip.
# Z1090_token_update -u mytoken.zip # exit
Older versions of zPDT use the SecureUpdateUtility command instead of Z1090_ token_update and work with .upwreturned files instead of .zip files.
The returned .zip file also installs the token licenses needed to decrypt z/OS® IPL volumes. After installing the new file, the token must be removed from the computer for about 15 seconds. Removing the token forces the token drivers to reread the token when it is reinstalled.
For IBM internal users, the provider is Resource Link®.
$ awsstop $ su # cd /usr/z1090/bin # Z1091_token_update -u xxxxx.zip # exit
After you install the .zip file, the token must be removed for about 15 seconds. Software licenses (for LDK-SL servers) are installed by installing a new v2c file as described in LDK-SL server.
Licenses must be renewed on the computer that runs the server. You cannot renew or update the token licenses remotely. The Z1090_token_update command or the older SecureUpdateUtility command work only with a single token installed in a local USB port.