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 ?
(*) DISPLAY statements can be coded as debug lines ('D' at column 7), and these
can be
"turned on" by inclusion of the "with Debugging Mode" clause in the
"SOURCE-COMPUTER"
paragraph, but this is only a compile-time switch
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
----------------------------------------------------------------------
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
