On Jan 23, 2008, at 10:20 AM, Dennis Trojak wrote:
Check the ST display on SDSF for TGNum and TGpct for JES2 track groups being used by the tasks/jobs. On the DA display you can use the DL on each task/job to get SPOOL information for the job.
Suggestion (and I don't know the answer) that there are other JES2 resources other than spool space that a long running jobs takes. One that comes to mind is internal readers. Some STC's I have seen hard coded dd's for internal readers and thus reserve a internal reader for the length of the STC's life (assuming free=close is not coded) if so you will probably need to up the number. I have seen (rarely) when the system runs out and its time to run around and figure out why and to find out how to release any that are currently in use. My memory says IBM (a little while ago) did a good job in cleaning this area of JES2 up. So it may be time to freshen up your expertise in the INTERNAL Reader and read up on the the improvements. Also IIRC if the job has a lot of messages and/or mounts or wto's it might be needed to spin those sysouts say once a week or so or every (suggestion) 20,000 lines.
Ed ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
