If a job is running and you place it on hold it will remain in a limbo state (spool is still used) until it is later RELEASE to allow output processing to complete. Jobs in such a state are not easy to see. I would suggest that periodically you go into SDSF using the ST command (turn off all filters) and SORT QUEUE. Then do a F $MAS name and then scroll back one page. You may be surprised at what you find. We have had jobs over a year old still on spool because they never went through output processing and were tying up spool.
If you have JES2 - the following might be valid 1) You could implement WLM Inits. They may be able to throttle the workload 2) You could use the JES2 OFFLOADER to specific classes that just keeps accepting output in specific classes keeping spool clean? 3) You could put in place an automation process that will purge output based on class or jobname, etc... 4) You could add on a product ($) to archive the spool? Things like $AVERS is a nice tool. But there are others. There was a REXX that John McKown shared with us called JES2DISK that you could run periodically to write the JES2 spool to disk or UNIX file. There are probably many ways to address this issue. Do you room on a VTS or Tape environment? Do you have sufficient dasd to increase the SPOOL to accommodate the extra workload? What automation tools could you use to either purge or using an external writer, move data off of spool. There is also Brian Westerman's suite of tools http://syzygyinc.com/SyzSpool.htm Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jon Perryman Sent: Thursday, September 05, 2013 7:04 AM To: [email protected] Subject: Re: Searching for a SUBMIT and WRITER tool If you have an automation product, then you can use it to take the action needed. You could trigger off of the job submitted rate or the JES number of lines exceeded message. You could place jobs on hold. Jon Perryman. >________________________________ > From: Miklos Szigetvari <[email protected]> > > >I have the problem, some of our users, submits, time to time several hundred tests jobs, for different application tests. >It fills the spool, difficult to handle etc etc . >I would need some simple tool to manage this: >- submit again and again , only a a limited number of jobs. >- if a job is ready, write out the outputs to some dataset. >- maybe check the return codes. > >Before starts to write, maybe someone has a good idea about this. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
