On Dec 25, 2007, at 6:40 AM, Giliad Wilf wrote:
We are trying to target cases where a COBOL program "goes
production" but is still
riddled with lots of active DISPLAY(*) statements left from its
debugging period
Examining the output of such a program, one can see millions of
records written to a DD
named SYSOUT (COBOL's default)
We want to selectively abort COBOL programs that "went production"
with such forgotten
DISPLAY statements left behind from debugging period
We intend to force users to code a reasonable OUTLIM on DDs named
SYSOUT in COBOL
jobsteps. The problem is, while we can get control when OUTLIM is
exceeded (IEFUSO), we
do not know what is the DDNAME for which this event occurred
Any suggestion ?
Well this has holes in it but if you really did want to for it it
would let the exit know and it could issue the abend. Just enforce
outlim= on all sysout cards. you could put it in automatically in a
JES2 exit (as an example).
Personally I wouldn't do it but it is possible, hold on to your seat
for repercussions though.
Ed
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
