Thank you for answers, I agree with the suggestions , increase the SPOOL
size, and/or use
some external writer, or short term SYSOUT classes.
Unfortunately currently I'm not in the position to make this changes,or
persuade the user to change his jobs, but in the
SUBMIT job I can change the called program from IEBGENER to some
REXX or other call.
On 05.09.2013 17:10, Joel C. Ewing wrote:
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.
--
Kind regards, / Mit freundlichen Grüßen
Miklos Szigetvari
Research& Development
ISIS Papyrus Europe AG
Alter Wienerweg 12, A-2344 Maria Enzersdorf, Austria
T: +43(2236) 27551 333, F: +43(2236)21081
E-mail: [email protected]
Info: [email protected] Hotline: +43-2236-27551-111
Visit our brand new extended Website at www.isis-papyrus.com
---------------------------------------------------------------
This e-mail is only intended for the recipient and not legally
binding. Unauthorised use, publication, reproduction or
disclosure of the content of this e-mail is not permitted.
This email has been checked for known viruses, but ISIS Papyrus accepts
no responsibility for malicious or inappropriate content.
---------------------------------------------------------------
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
