Jack Schudel has made the crucial point. With the availability of the JOBRC= parameter on the JOB statement, any job, however troubled, can have RC=0. One simply begins it with a step, call it MISLEAD. that executed an innocuous program, a certain wrell known do-nothing IBM utility will do, and specifies the stepname MISLEAD in the JOBRC= parameter value.
All this is a little too easy, in my view anyway. The use of an on-line table of jobnames and RC-value thresholds would be a better approach. John Gilmore, Ashland, MA 01721 - USA ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
