On 09/05/2013 03:01 AM, R.S. wrote: > W dniu 2013-09-05 08:57, Miklos Szigetvari pisze: >> Hi >> >> 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. >> > > IMHO the cheapest solution is to add resources to JES and maybe redirect > large outputs to dasd (permanent datasets). > And maybe enforce limit of lines per job (after the limit job is abended > with S722 AFAIR). > Oh last but not least: talk to the people. It's likely they will > understand clear rules and justification and they will follow the rules. >
I would also recommend providing distinct SYSOUT "short-term" HOLD classes that will be eligible for auto-delete after a few days, one day, and perhaps even periods shorter than one day; and set up system automation for the periodic purging of output that exceeds the retention documented for those classes. In many cases the output from test jobs are known to be of short usefulness. Having installation standards for which HOLD classes to use for job MSGCLASS and for test SYSOUT for various test job categories will provide a better means to clean up after users who fail to purge their own garbage. Enforcement of those standards will encourage users to either direct output really needing longer retention to DASD or use some tool like SDSF to save selected held SYSOUT to data sets after job completion before held SYSOUT is auto-purged. Increasing JOBNUM limits and spool space may still be required, but you don't want to just throw JES resources at what is even known by the users to be trash. -- Joel C. Ewing, Bentonville, AR [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
