TSSXTEND Abend CODE 3006 ERROR 075 PROCESSING ACID=TSSCSA

Document ID : KB000095339
Last Modified Date : 24/05/2018
Show Technical Document Details
Introduction:
TSSXTEND to create a BCP copy of the security file and there have been cases that the job would abend with CODE 3006 ERROR 075 PROCESSING ACID=TSSCSA.
The solution is to rerun the job with no changes and it will execute normally
Question:
We are executing TSSXTEND to create a BCP copy of the security file and there have been 2 cases recently that the job would abend with CODE 3006 ERROR 075 PROCESSING ACID=TSSCSA which causes the on-call person to come in, research, and the solution is to rerun the job with no changes and it will execute normally. Searching the CA site, the following Document ID : KB000014769 is found which has the following Answer: The live security file should not be used as input when running TSSXTEND. Run TSSXTEND against the backup security file. Our job IS using the backup security file. Is there another reason that would cause an abend with CODE 3006 ERROR 075 PROCESSING ACID=TSSCSA? Below is the symptom which was identical both times: IEA995I SYMPTOM DUMP OUTPUT 158 USER COMPLETION CODE=3006 TIME=04.07.15 SEQ=00536 CPU=0000 ASID=0110 PSW AT TIME OF ERROR 478C1000 80007884 ILC 2 INTC 0D ACTIVE LOAD MODULE ADDRESS=00007000 OFFSET=00000884 NAME=TSSXTEND DATA AT PSW 0000787E - 00181610 0A0D4110 0BBF0A0D AR/GR 0: 00000001/00010000_80000000 1: 00000000/00000000_80000BBE 2: 00000000/00000000_0000C5C7 3: 00000000/00000000_009D3D6C 4: 00000000/00000000_00049111 5: 00000000/00000000_2EAE9000 6: 00000000/00000000_009B9FC8 7: 00000000/00000000_00FC4A00 8: 00000000/00000000_009D0950 9: 00000000/00000000_00057011 A: 00000000/00000000_009B50A8 B: 00000000/00000000_0000C2CC C: 00000000/00000000_80007000 D: 00000000/00000000_009B5150 E: 00000000/00000000_800079E0 F: 00000000/7F78C400_8001049A END OF SYMPTOM DUMP
Environment:
Z/OS
Answer:
The U3006 could indicate this is either an 'Invalid Encryption Key' or 'Damaged Acid'.
It could also be a timing issue.
Since it is copying from a backup file there is the potential that the data changes due to a concurrent TSS BACKUP request.
Check on the console log it is worth checking when a TSS backup occurs.
Ensure scheduling of the TSSXTEND so it never runs when a BACKUP is running.