As other have written, writing something to walk the JCT/SCT chain will do as you ask. Run the program as the last step in the job and you can do with the information as you wish.
I did something like this at a client location a few years ago. The program was called RCWALKER and could execute anywhere in the job stream. In most instances, it was the last step in a job. It produced a couple of different "reports" based on what DD statements were present in the JCL. One of the reports was nothing more than a flat-file, which contained a one-line detail entry for each step. The information in the detail line was jobname, stepname, pgmname, return code or ABEND code and a couple of other pieces of information. In my case, the file produced was emailed to interested parties. In your case, you could read this file with another utility, which would make decisions based on the RC from each step in the job. On Tue Apr 8 16:59 , Michael Knigge <[EMAIL PROTECTED]> sent: >David, > >> file, so how does this help? What would you do with it that I am not >> understanding? > >Hmmm. yes... confusing... :) > > >What I don't want is an "additional STEP after every STEP" in my Job. > >So for example: > >STEP01: IEBCOPY >STEP02: MYTOOL --> writes STEP01 returned CC=0 >STEP03: IEBCOPY >STEP04: MYTOOL --> writes STEP03 returned CC=4 >STEP05: IEBCOPY >STEP06: MYTOOL --> writes STEP05 returned CC=4 > > >I didn't knew that is is quite simple to use JCT and SCT to get the CC >of every STEP in the job. So putting "only one" STEP at the end of the >Job is somehow "ok" for me. > > >And I like this more than the "FTP-Idea", because the FTP-Server may be >down, the JCT/SCT will never ;-) > > >Bye, >Michael > ---------------------------------------------------------------------- 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
