You may also wish to look at the $JD commands (HISTORY, STATUS, DETAIL). History of various JES2 elements might help to know when it is CNVT is having a problem.
You could also use the SDSF panel (RES???) to do something similar. How many jobs are being handled by JES2 at the time of the issue? How many auto-sched jobs are there? Does this happen at the same time or different times? Is the workload to JES2 the same or different with this issue? Is your checkpoint on DASD or CF? If on DASD are there any other files on the volume with the JES2 checkpoint dataset? How many systems are involved in this environment? 1 , 2 more??? Also, check out the $D PERFDATA command http://www-03.ibm.com/support/techdocs/atsmastr.nsf/585741c64201a45286256ccf 00653ad4/59ebc9c955fc619e85256d8c000d6156/$FILE/perfdataFlashzOSR2.pdf Or tinyurl: http://tinyurl.com/kjkvc6k This command will do: C 1997-2004, IBM Advanced Technical Support Techdocs - Washington Systems Center Version 1/20/2004 http://www.ibm.com/support/Techdocs W9744B - JES2 for OS/390 and z/OS Performance Data Title: JES2 Performance Data Command ($DPERFDATA) JES2 for OS/390 and z/OS Performance Data - Updated January 20, 2004 JES2 provides internal performance statistics which can be displayed with the $D PERFDATA operator command. Disclaimer: This is intended to be used under direction of personnel knowledgeable in interpreting JES2 PERFDATA displays. Development may add/change/delete any part thereof as required to improve its usefulness as necessary, so there is no intent to document the externals in the JES2 product publications at this time. Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of baby eklavya Sent: Tuesday, June 04, 2013 4:34 AM To: [email protected] Subject: JES2 conversion delay Hello , We are running Z/OS 1.11 in our environment and recently had a problem with Auto-sched jobs in Jobtrac . There were a set of auto-sched jobs which comes to JES2 and jobtrac puts a HOLD on it by design (for Auto-sched processing) . Later ,Jobtrac issues a release command to free them for execution . It was found that JES2 conversion took longer and couldn't complete the conversion processing when Jobtrac issued the release command.As a result , the release command had no effect on the job and the job stayed in the JES2 queue waiting for execution . We are not sure why the conversion took longer . Any idea on why this could happen ? Regards, Baby ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
