Steps for examining why a job is not running

Enter the IPCS SYSTRACE ALL command.
Enter FIND WAIT in the SYSTRACE report and identify WAIT type trace entries.
1. If you find WAIT entries, there are intervals when the dispatcher did not find any dispatchable work to dispatch. Review the previous sections of Diagnosing a job or subsystem hang to ensure nothing overlooked.
2. If you do not find any WAIT entries, examine which ASIDs are running by scrolling through the IPCS SYSTRACE ALL report.

In a IPCS VERBX SRMDATA report, compare the service classes and periods of the jobs executing in SYSTRACE to those that are hung.

For example:

JOB   ZFS                                           
ASID  01F5                                          
OUCB  02700780 IN      QUEUE                        
                +11 (NSW)  NONSWAPPABLE             
                +11 (PVL)  PRIVILEGED PROGRAM       
                (ASCBRSME) RAX ADDRESS IS 020848C8  
                           SERVICE CLASS = SYSSTC   
                           WORKLOAD = SYSTEM        
                           INTERNAL CLASS= $SRMGOOD 
                           PERIOD = 01

If these are of higher priority, examine where they are running by using the IPCS WHERE on several of the PSW addresses from the SYSTRACE report.

Search for a known problem using the module, CSECT, or both.