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
