It's a bit more complicated if you have more keywords than just SYSOUT, e.g., FCB. Also, don't forget the characteristcs JOEs.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Lizette Koehler <[email protected]> Sent: Tuesday, January 30, 2018 6:20 PM To: [email protected] Subject: Re: JES2 JOE curiosity So JOES are output elements. If you have a job and all the SYSOUT is defined as SYSOUT=X then one joe for the whole job If you have JCL Coded with SYSOUT=X,SPIN=CLOSE,FREE=UNALLOC then one joe for each of these and that frees up nicely in JES2. There are also other things that affect jobs. So if you have a COBOL Program with DISPLAY that will produce a JOE We had an IMS Tran a long time ago where a programmer left in a DISPLAY going into production, It cause a bit of panic as we only had 120,000 JOES and it chewed those up. Next depending on the level of JES2, you can have a maximum of 1,000,000 JOEs So two thoughts. What is the current number of JOEs defined? May be time to raise the limit Two - go through SDSF and look at each output class can see where the abuse is coming from. Note: If a job is purged, but there is something still dangling on jes2 spool - the whole job is held until that last little bit is purged. For example, a 10 step job has output going to a printer and is printed, however there is an IEBGENER step with SYSOUT=H for the JES2 hold class. Unless The SPIN and FREE coding is coded for IEBGENER, this last little bit holds all the output from all the job. Only way to see those is from ST panel in SDSF. I would code an ISFEXEC process to run through the various SYSOUT queues and see what is there. Also use the ST panel and sort on QUE. See if there is anything around $MASCOM that is in HELD status. That probably has not passed through OUTPUT Processing. This occurs when a job is running and someone enters H next to the running job. Hope this helps Lizette A theory can never be proven, but it can be falsified. Karl Raimund Popper > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Jesse 1 Robinson > Sent: Tuesday, January 30, 2018 3:17 PM > To: [email protected] > Subject: JES2 JOE curiosity > > A few JOE shortages here recently has a colleague asking this question: we > can pretty easily tell which jobs are using the most TGs, even specifically > how many. Is there a comparable way to query JOE usage? I've worked with JES2 > for decades but don't know of any simple answer. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office <===== NEW > [email protected]<mailto:[email protected]> > ---------------------------------------------------------------------- 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
