https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieab600/iea3b6_Example_3.htm
I would check each step after the backup with //NOTIFYB IF (ABEND OR TSOBATCH.RC > 0000 OR BKDSN.RC > 0004) THEN //ALERTB EXEC PGM=CICCRE01 //SYSPRINT DD SYSOUT=* //NOTIFYXB ENDIF and within the Proc. //NOTIFYP IF (ABEND // OR CLEARIT.RC > 0000 // OR COPYS.RC > 0000 // OR COPYQ.RC > 0000 // OR CLEARIT.RC > 0000 // OR COPYB.RC > 0000 // OR CHKQMGR.RC > 0000) THEN //ALERTP EXEC PGM=CICCRE01 //SYSPRINT DD SYSOUT=* //NOTIFYXP ENDIF If you wait until after the proc then you would need to add the PROC INVOKATION name, IE // OR STEP010.CLEARIT.RC > 0000 If 4 was acceptable on all steps or you submit a separate job after the ADDRSU BACKUP then it would be much simpler. On Thu, Jan 17, 2019 at 3:51 AM Ward Able, Grant <gwarda...@dtcc.com> wrote: > > This seems simple and I may be having a senior moment, but I don’t seem to be > able to get this to work. > I have a number of batch jobs that do ADRDSSU backups, then execute a > variable number of PROC statements to copy files. > TSOBATCH PGM=IKJEFT01 CC= 0000 > BKDSN PGM=ADRDSSU CC= 0004 > > Each PROC causes a series of steps to execute: > CLEARIT PGM=IEBCOPY CC= 0000 > COPYS PGM=IEBCOPY CC= 0000 > COPYQ PGM=IEBCOPY CC= 0000 > CLEARIT PGM=IEBCOPY CC= 0000 > COPYB PGM=IEBCOPY CC= 0000 > CHKQMGR PGM=IKJEFT01 CC= 0000 > > Then the final step is to check the return codes and issue an alert for RC > 0 > //NOTIFY IF (ABEND | RC > 0) THEN > //ALERT EXEC PGM=CICCRE01 > //SYSPRINT DD SYSOUT=* > //NOTIFYX ENDIF > > My question is this: how do I code the IF/THEN(/ELSE) to allow for RC=4 from > step BKDSN? I do not want an alert if this is the case, but any other step > > 0 should give me an alert. > > Regards – Grant > > > DTCC Internal (Green) > DTCC DISCLAIMER: This email and any files transmitted with it are > confidential and intended solely for the use of the individual or entity to > whom they are addressed. If you have received this email in error, please > notify us immediately and delete the email and any attachments from your > system. The recipient should check this email and any attachments for the > presence of viruses. The company accepts no liability for any damage caused > by any virus transmitted by this email. > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
