z/OS JES2 Diagnosis
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Waits

z/OS JES2 Diagnosis
GA32-0993-00

JES2 waits have the same symptoms as MVS™ waits.

Use SYSLOG to determine the cause of the wait. If you determine that JES2 is the cause of a wait state, ensure that you dump JES2 by entering the following command from a console with master authority:


DUMP COMM=(JES2 HANG DURING INITIALIZATION)

The system will respond with the message:


* id IEE094D SPECIFY OPERAND(S) FOR DUMP COMMAND

Reply:


R id,JOBNAME=JES2,SDATA=(SERVERS,PSA,SQA,LSQA,RGN,TRT,LPA,CSA,GRSQ,SUM,XESDATA,COUPLE)
 

Waits can be caused by resource shortages. See Resource shortages for additional information.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014