Are we overlooking OUTLIM= here? Or is it a case of the OP needing a
way to deal with spool flooding regardless of totally irresponsible job owners?
I've seen JES exits and submit exits which enforce the presence of
OUTLIM on SYSOUT DD statements, with different limits mandated by
class. If
A relatively simple MPF exit can satisfy your second issue.
-Original Message-
From: Sridhar K Veena [mailto:snip]
Sent: Monday, October 15, 2007 4:41 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: To set cancel of job based on SYSOUT
G'day,
Is there a way I can set a job to be
Sridhar ,
Look in the manual items *ESTBYTE* And *ESTLNCT *of parm JES of these
items control the number of lines and automatically purged the job.
G'day,
Is there a way I can set a job to be auto purged if it crosses certain
number of lines of SYSOUT. We have JES2.
Ours is a pu
Sridhar Veena asks:
>Is there a way I can set a job to be auto purged if it crosses certain
number of lines of SYSOUT. We have JES2.
>Also, is there a way I can set up auto delete response to some dump
messages which keep popping up in logs?
If you have automation, these tasks can easily be ha
Sridhar K Veena wrote:
G'day,
Is there a way I can set a job to be auto purged if it crosses certain
number of lines of SYSOUT. We have JES2.
Ours is a pure training mainframe with limited resources, we often see
some looping jobs filling up the SPOOL volumes (though we have automat
G'day,
Is there a way I can set a job to be auto purged if it crosses certain
number of lines of SYSOUT. We have JES2.
Ours is a pure training mainframe with limited resources, we often see
some looping jobs filling up the SPOOL volumes (though we have automated
the purge of SPOOL volu
6 matches
Mail list logo
