Before r11.3, the license keys for ESP Workload Automation are dependent on the last 4 digits of CPU serial number, and if they are changed, then the license keys will become invalid and ESP will abend with U0913.
This can happen when:
- Start ESP on DR side where the CPU serial number is different;
- Upgrade CPU and then use a different CPU serial number;
- After applying maintenance and copy over to another prefix.SSCPLINK library, the license key modules are overwritten;
- if the license keys expire, U0913 abend will occur.
ESP911W message will show in JESMSGLG of ESP Workload Automation STC and users who access the system from 5 days before expiration.
Note: If the system is not recycled, it will keep running even the license keys expire; however users can't logon (from ISPF or GUI). Therefore after applying new keys, there is no need to recycle the system.
Release: pre-11.3 including 5.3, 5.4 and 5.5
Component: ESP Workload Automation
Sample JCL to zap the license keys
//ZAPKEY JOB
//STEP1 EXEC PGM=AMASPZAP
//SYSPRINT DD SYSOUT=X
//SYSLIB DD DISP=SHR,DSN=prefix.SSCPLINK
//SYSIN DD *
NAME CYBESDDB CYBESDDB
REP 0200 92E08B1B,F0A3B21D,33180651,40F54631
REP 0210 7ECFC734
NAME CYBRMDDB CYBRMDDB
REP 0200 2BB06205,DE6CDC1E,810A189E,1BF9D369
REP 0210 A7E68E7D
NAME CYBHPDDB CYBHPDDB
REP 0200 42A4FA59,CDAF7846,921B3E5D,90B4A775
REP 0210 28BD4D28
NAME CYBHADDB CYBHADDB
REP 0200 73A4DD69,C8AF625C,B52B3E5D,90B4A775
REP 0210 28BD7002
/*
Common reasons to have U0913 after applied the proper keys:
- LINKLST is not refreshed;
- The keys are zapped to wrong prefix.SSCPLINK;
- Version management utility didn't refresh;
- APF authorization is not done to the prefix.SSCPLINK;
- New license keys are shorter or less than the old ones:
This may occur if the old ones are meant for multiple CPUs while the new ones are for one or fewer CPUs. In this case, the extra lines need to be padded with '0000' to the next word boundary.
"OPER LISTDDB" can be issued from page mode to show current license keys starting from address 200; another way is to use AMASPZAP to dump the key
Sample JCL:
//CZAPDUMP JOB
//SPZAP2 EXEC PGM=AMASPZAP
//SYSPRINT DD SYSOUT=*
//SYSLIB DD DISP=SHR,DSN=prefix.SSCPLINK
//SYSIN DD *
DUMPT CYBESDDB CYBESDDB
//
Then you can add more lines with '0000' to the JCL that's used to zap the new keys.