How do I debug ENQ (ENQUEUE) lockout problems with the TMC / Audit?
Release: R14.0
Component: CA/1 TAPE MANAGEMENT
If you have a task that is waiting on the TMC or Audit file and is not able to continue processing you may have an ENQ (Enqueue) lockout. To diagnose the problem it needs to be determined what task is holding the resource and why it is not being released (for example, the holding task is waiting for another resource, or the holding task is swapped out). This document is to help you determine what task holds the resource.
The most common causes however, are that the job that OWNS the TMS-TMC is either HSM or CATALOG. If it is HSM, you will probably have to shutdown and restart HSM. First however, look at the TCB address of HSM that OWNS the TMC or Audit file and see if you can find that same TCB waiting for a different resource. In particular, look for it under SYSZTIOT. If it is there, then you will need to have HSM shutdown and restarted. In this case, gather the SYSLOG from this system from about 30 minutes before the problem started until HSM is cancelled and everything clears out.
If the job that OWNS the TMC or AUDIT file is CATALOG, there are a few more options.
Examples:
D U,VOL=TMCVOL
IEE457I 08.06.54 UNIT STATUS 595
UNIT TYPE STATUS VOLSER VOLSTATE
8720 3390 A-R TMSVOL PRIV/RSDNT
D U,,ALLOC,8720,1
IEE106I 08.07.00 UNITS ALLOCATED
UNIT JOBNAME ASID JOBNAME ASID JOBNAME ASID
8720 *MASTER* 0000 BATCHJOB 0006 LLA 0016
8720 HSM 006F CTS 0079
D GRS,C
S=SYSTEM TMSQNAME TMS-AUD
SYSNAME JOBNAME ASID TCBADDR EXC/SHR STATUS CPUA
BATCHJOB 0175 008E36B0 EXCLUSIVE OWN
CPUA TMSXTEND 0153 008E36C8 EXCLUSIVE WAIT
CPUA TMSRINIT 027E 008E36C8 EXCLUSIVE WAIT