MVS has provided such a mechanism forever using 1. a program that issues a WTO
2. conditional execution on the WTO step with COND=EVEN or ONLY (depending on the logic required) Most shops already have a more or less sophisticated (security wise) program to issue a WTO. Conditional JCL is free for the coding. Every shop I've worked in uses the mechanism to manage production, including my current one. There is as Brian says no way to handle a JCL error without an external 'product'. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Brian Westerman Sent: Sunday, November 3, 2019 10:38 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: WTO message at the end of JCL Yes, you can use an MPF exit to catch the JCL error. The messages are merely different messages, so you would have your MPF exit process whichever message you want to use as your trigger. Sorry for the marketing: SyzMPF/z has a feature that will capture the condition codes (job failure or not) whenever any job ends and send an email (or text message) with all of that information (the codes from the steps that worked, the JCL error and any part(s) of the job output you might want) dynamically without any JCL changes to any job or any SMF exits being necessary. End of marketing. The point is,if there is a message from a job or because of a job, you can process it with am MPF exit. Sometimes it's not easy, but obviously (since I did it), it's possible. Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
