Is there any way we could run a report to find the reason for the security file being locked and what job/resource got held up?
Article ID: 13401
Updated On:
Products
Issue/Introduction
Questions:
1. Is there a batch report that will show who has the outstanding enqueue on the CA Top Secret Security File when a TSS9123A message is received.
2. Is there any job that could be run against the TSS database to find if anyone had run the TSS LIST(ACIDS) DATA(ALL,PROFILE) command or any such related commands to find the possible cause.
Environment
Component:
Resolution
1. Is there a batch report that will show who has the outstanding enqueue on the CA Top Secret Security File when a TSS9123A message is received.
Answer:
There is no report that would give us the reason for the outstanding enqueue on the CA Top Secret Security File. We would need a dump of the TSS address space from the CPU/LPAR that issued enqueued the security file to determine why the enqueue was issued.
2. Is there any job that could be run against the TSS database to find if anyone had run the TSS LIST command or any such related commands to find the possible cause.
Answer:
There isnt a report that will shows if anyone had run the TSS LIST(ACIDS) DATA(ALL,PROFILE). TSS LIST commands are not tracked.
Feedback
