The COND=EVEN/ONLY will not work if the job hits a *JCL error*. <g>
On 04/11/2019 23:56, Charles Mills wrote: > It would be nice if there were a way to get the condition codes into the WTO > program, something like (don't try this at home): > > //WTO1 EXEC PGM=WTO,COND=EVEN, > // PARM='Job FOOBAR terminating. Highest CC was &MAXCC' > > I seem to recall a discussion here about retrieving the last and maximum job > CC's from within a program running as a jobstep and the answer was that there > was no good way. > > Charles > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Jesse 1 Robinson > Sent: Monday, November 4, 2019 1:01 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WTO message at the end of JCL > > 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'. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > . > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
