Hi
We are experiencing difficulties using a zPDT token to start up RD&T. Steps taken:
- Install RD&T from scratch to a server using RHEL 6.3 as the base Linux os.
- Activated the zPDT token using SecureUpdateUtility and Resourcelink activation process. It seemed to succeed ok.
- The USB stick was then unplugged and plugged back in after few seconds.
Here are the outputs from SecureUpdateUtility, uimcheck and zPDT start:
[root@RDTEST01 bin]# ./SecureUpdateUtility -u HPserv.upw
-------------------------------------------------------------------------------
Secure Update Utility
Sentinel Keys 1.3.1
Copyright (C) 2009 SafeNet Inc. All rights reserved.
-------------------------------------------------------------------------------
Success!
Running uimcheck ...
The UIM client is configured in local mode.
UIMCHECK: serial number entry not yet added to local data base.
UIMCHECK: No local errors
CMD : 061313 16:41:00: awsstart devmapA0 --clean
LOG : 061313 16:41:00: AWSSTART:
z1091, version 1-4.45.26.01, build date - 05/24/13 for Linux on RedHat 64bit
LOG : 061313 16:41:00: AWSSTART: Intel-64 architecture
LOG : 061313 16:41:00: AWSSTART: Configuration File-devmapA0
INFO: 061313 16:41:00: STA: AWSSTA204I zPDT started in directory '/home/ibmsys1/z1090/z'.
INFO: 061313 16:41:00: STA: AWSSTA146I Starting independent 1090 instance 'ibmsys1'
CMD : 061313 16:41:00: awsap -p 4224
LOG : 061313 16:41:01: CPU: DEVMAP loaded for EMILY process, RC=159
LOG : 061313 16:41:01: CPU: Creating 3 CPUs
LOG : 061313 16:41:01: CPU: Starting CPUs.
LOG : 061313 16:41:01: CPU: Starting RAS setup
CMD : 061313 16:41:01: sclp_process 0 0 valid
ERR : 061313 16:41:01: EMI: AWSEMI315E zPDTA License Unavailable for CPU 0
ERR : 061313 16:41:01: EMI: AWSEMI315E zPDTA License Unavailable for CPU 1
ERR : 061313 16:41:01: EMI: AWSEMI315E zPDTA License Unavailable for CPU 2
INFO: 061313 16:41:03: EMI: AWSEMI005I Waiting for 1090 license
The token used is a zPDT token. The actual RD&T token is in production use, where we are experiencing issues with network traffic and that is being worked on via a PMR. To aid the problem resolution process, this test environment was built and a loaner token from IBM representative is being tried.
Any suggestions what could be done to get AWSSTART to obtain the license?
Toni
_tony