We have an 8.0.3 environment utilising a high density USB license key. The license key had 2 licenses applied. Initially we were running one instance of the client with 3 CPU's installed. After running up a second instance with 1 CPU it wouldn't start as it said there was not a license available. We IPL'ed the original instance with 2 CPU's then we could start the second instance with 1 CPU. I subsequently added an extra two licenses to the USB key but we are still experiencing the same issue. The log shows
AWSEMI314I CPU 0 zPDTA License Obtained
AWSEMI314I CPU 1 zPDTA License Obtained
AWSEMI315E zPDTA License Unavailable for CPU 2
Any thoughts/suggestions? Thanks.
This topic has been locked.
6 replies Latest Post - 2012-05-22T02:29:52Z by keithvb
Pinned topic CPU License issue starting RDzUT
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-05-22T02:29:52Z at 2012-05-22T02:29:52Z by keithvb
Re: CPU License issue starting RDzUT2012-05-18T04:10:24Z in response to SystemAdminHello,
To begin to assist you, I need some information.
What is the z1091 version as found by command z1090ver or rpm -qa | grep z109 .
I do not know the license size of your high density token, If you know please let me know. Is this token plugged locally or in a remote token server. If in a remote license server, are other z1091 clients connected to it ? From the information you provided in post, it appears to be acting as if you only have a L03 token (has only 3 licenses available). If the fourth cp tries to come on line, it would fail to get a license as all licenses are taken.
I am not familiar how RDzUT sets the available number of licenses on the high density token . I will go investigate how this occurs. (I am confused in your post when you mentioned "The license key had 2 licenses applied" and then "subsequently added an extra two licenses to the USB key")
There is a token monitor function that can identify the token hard license limit and number of licenses in use. On the machine with token plugged, using a web browser pointed to localhost:7002 or 127.0.0.1:7002. Then click on the right "Key Information". Please provide that information.
I look forward to reading your reply,
Re: CPU License issue starting RDzUT2012-05-18T05:59:04Z in response to SystemAdminHi Keith,
Thanks for your response.
Both the License Server and the Clients show the same version of z1091.
IBM System z Personal Development Tool (zPDT)
Licensed Materials - Property of IBM
(C) Copyright IBM Corp. 2007 All Rights Reserved.
z1091, version 1-2.41.47, build date - 01/29/12 for Linux on RedHat 64bit
The key is installed in a dedicated License server with the two clients configured to use the remote license server.
Regarding my comment around the 2 licenses. Initially I only registered 2 licenses on the key. As part of my troubleshooting I requested another 2 licenses from IBM. These were provided and applied using the SecureUpdateUtility -u command. The license file from IBM came with a comment "This update file will enable 4 3-CP instances for the key with serial number 03-00E29".
Browsing to port 9451 on the License server returns the two clients connecting to the server.
CPU serial numbers on zPDT UIM server email@example.com
Machine UUID 4225EAC1-0877-BBA3-5033-5F984DE408C3
Serial Host UUID Year Day
7955 bmfrd1.int.corp.sun 4225DF5D-F933-2E25-967A-169FEE432835 2012 123
7669 rdzrd2.int.corp.sun 4225B76C-B51F-F5B4-5024-87D04CDABC7A 2012 079
Unfortunately there is nothing showing under Key Information. I get the Info, Add, Add server, Edit, Delete, Clear, Save and Close across the bottom but there is nothing else showing.
Re: CPU License issue starting RDzUT2012-05-21T02:43:20Z in response to SystemAdminAndrew,
From your last post, "Unfortunately there is nothing showing under Key Information....", Was that on your local machine or the remote key server ? I would expect that on the local machine with no token, but I would expect there to key information on the remote license server. Is it possible to open a browser on the remote license server ?
I will still need to talk with the Ration System z Development and Test team to understand their token update process. I hope to get back to you tomorrow.
Re: CPU License issue starting RDzUT2012-05-21T02:53:36Z in response to keithvbHi Keith,
I was looking at the Key Information on the license server. I don't expect it makes any difference but I was using Links as a html viewer as I don't have any xwindows software installed to provide a GUI.
Re: CPU License issue starting RDzUT2012-05-22T02:29:52Z in response to SystemAdminAndrew,
We can change the remote license server's token config file to capture some token information and to allow another machine besides the localhost, to administer the token function. We would want this other machine's web browser (Windows or Linux) to have java plug-in installed which is required to operate token monitor.
I am going to provide a copy of the token server config file. (Please send your email address to firstname.lastname@example.org to allow me to send you the config file.) When activated, it will add a token "Response" file to record some token activity and will let you assign another machine to perform some token administration. Please use the following procedure on the remote license server.
--using root id on the remote license server
--cp sntlconfigsrvr.xml sntlconfigsrvr.xml.orig
--cp in new sntlconfigsrvr.xml file
--edit sntlconfigsrvr.xml , change xx.yy.zz.ww to the ip or the fullly qualified hostname with domain name of another system which will perform the token administration
--dos2unix sntlconfigsrvr.xml to clear any DOS CRLFs
--restart the key server via command: ./loadserv restart
--please provide the contents of response_log.log file . (if you do not want to attach to the forum, please send file to email@example.com)
--using a web browser on the machine who's address you added to the sntlconfigsrvr.xml , please go to your remote license server ip:7002. Then on the right, click on "Keys Information" and please provide the "hard limit" value.
Let me know how you make out,