Hello forum,

I'm trying to set up RD&T v9 on RHEL 6.4, and am stuck on obtaining license to RD&T instance.

AWSEMI315E zPDTA License Unavailable for CPU 0

I checked http://localhost:7002 and see the license was issued to the instance, "Licenses-In-Use" count gets 1 from 0 when "awsstart myDev" runs , so the sentinel usb hardware side seems to working. I'm using Green labeled (high capacity) USB key.

I also worked with previous suggestions in the following discussion, and used the same simple device file (myDev).

https://www.ibm.com/developerworks/community/forums/html/topic?id=b6bfd717-cae9-4dcb-b685-63276de35494&ps=25

Here is all logs in  /home/ibmsys1/z1090/logs. Any suggestions here?

[ibmsys1@maint logs]$ ls -l
合計 20
-rw-r-----. 1 ibmsys1 ibmsys1   89 12月  9 15:47 2013 awsstart_p24093_000001.log
-rw-r-----. 1 ibmsys1 ibmsys1  268 12月  9 15:47 2013 emily_uim_p24234_000001.log
-rw-r-----. 1 ibmsys1 ibmsys1 1475 12月  9 15:53 2013 log_console_p24093_t2013-12-09_15-47-41.txt
-rw-rw-r--. 1 ibmsys1 ibmsys1  623 12月  9 15:47 2013 log_cpu0_p24234_t1386571661.txt
-rw-rw-r--. 1 ibmsys1 ibmsys1  530 12月  9 15:47 2013 log_cpu_main_p24234_t1386571661.txt
[ibmsys1@maint logs]$ cat *
06:47:41.652758 24093 - LOG Intel-64 architecture started on Monday, 2013-12-09-06:47:41
06:47:41.821615 24234 - LOG Intel-64 architecture started on Monday, 2013-12-09-06:47:41
06:47:41.821649 24234 - INFO This log is to capture UIM information

06:47:41.821658 24234 - LOG EMILY::open_r_log: The Unix Domain File Name /home/ibmsys1/z1090/pipes/uim_uds
CMD : 120913 15:47:41: awsstart --clean myDev
LOG : 120913 15:47:41: AWSSTART:
z1091, version 1-4.45.26.01, build date - 05/24/13 for Linux on RedHat 64bit

LOG : 120913 15:47:41: AWSSTART: Intel-64 architecture
LOG : 120913 15:47:41: AWSSTART: Configuration File-myDev
INFO: 120913 15:47:41: STA: AWSSTA204I zPDT started in directory '/home/ibmsys1/z'.
INFO: 120913 15:47:41: STA: AWSSTA146I Starting independent 1090 instance 'ibmsys1'
CMD : 120913 15:47:41: awsap -p 24093
LOG : 120913 15:47:41: CPU: DEVMAP loaded for EMILY process, RC=5
LOG : 120913 15:47:41: CPU: Starting CPUs.
LOG : 120913 15:47:41: CPU: Starting RAS setup
CMD : 120913 15:47:41: sclp_process 0 0 valid
LOG : 120913 15:47:43: CPU: 9602 227
LOG : 120913 15:47:43: CPU: 9602 227
INFO: 120913 15:47:43: EMI: AWSEMI005I Waiting for 1090 license
ERR : 120913 15:47:43: EMI: AWSEMI315E zPDTA License Unavailable for CPU 0
INFO: 120913 15:47:49: STA: AWSSTA059I System initialization complete
INFO: 120913 15:47:49: STA: AWSSTA012I All configured subsystems started
CMD : 120913 15:47:52: token
INFO: 120913 15:47:52: zPDTA: CPU 0, No Sentinel License Available 304
INFO: 120913 15:47:52: zPDTA: No License Available
INFO: 120913 15:47:52: zPDTA:

 End of zPDTA Status display
CMD : 120913 15:53:27: token
INFO: 120913 15:53:27: zPDTA: CPU 0, No Sentinel License Available 304
INFO: 120913 15:53:27: zPDTA: No License Available
INFO: 120913 15:53:27: zPDTA:

 End of zPDTA Status display
+----------------------------------------------+
*                                              *
* Begin New Log                                *
*                                              *
+----------------------------------------------+
Mon Dec  9 15:47:41 2013
Linux2.6.32-358.el6.x86_64#1 SMP Tue Jan 29 11:47:41 EST 2013x86_64CPU 0 thread created, sys_key = 0
IPR started for CPU 0
CPU reset
IPR complete for CPU 0
+----------------------------------------------+
*                                              *
* Begin New Log                                *
*                                              *
+----------------------------------------------+
Mon Dec  9 15:47:41 2013
Linux2.6.32-358.el6.x86_64#1 SMP Tue Jan 29 11:47:41 EST 2013x86_64[ibmsys1@maint logs]$

I do not have an answer for you but maybe a few more ideas might help.

Here are a few things to check.  The logs shown above validate some of these but I mention them for future users.

1. Validate that the SecureUpdateUtility -u command returned an indication of "Success".  If it did not, check that the serial number on the key matches the 5 digit serial number in the update file name.  If this is a sysplex enabled license, validate that the RDP_SP.NLF file was applied before the update file usng SecureUpdateUtility -n.
2. Validate that you are running the RD&T program (as opposed to zPDT)...  When you type awsstart without parameters it should show z1091, version 1-4.45.26.01  (your logs show this is OK)
3. Check that the system clock is current.   If it is backdated then you may see  (your logs show this is OK)
4. Run z1090instcheck to validate that the licenses being retrieved are being retrieved locally or remotely as expected.
5. Check if your update file is consistent with your dev map regarding sysplex usage.  If you are using a sysplex enabled update file you must have the cpuopt lvm_couplingfacility line in the [system] stanza.  If not, then the coupling facility lime must not be in the [system] stanza.
6. Using the http://localhost:7002 web page, check that the host name of the license owner matches your machine. This simply excludes the possibility that your machine is acting as a license server and that someone else obtained the license before you did.

The appearance of a license in use within the web page may indicate an uninitialized key. 

I see also that there is a line in the log file that has a line that says CPU: 9602 227.  I'm not sure exactly what that line is saying but I suspect that it may indicate a problem with either the USB hardware key or the update file being used to add licenses to the key or that the SecureUpdateUtility did not successfully apply the update file.   [The 227, if it is what I think, indicates that a demo USB key has been used too many times, but IBM has never created or supplied demo keys or licenses so that is why I think it might be a key or update file problem]. 

Has this USB key worked before or is this the first time it was used?

Thank you for the precious info,

At last we identified the license file imported was very old (issued for 2010), which resulted the key was not authenticated to RD&T instance. The license is always valid for one year.