CRJE On 2019-11-05 08:13, Mike Schwab wrote: > OS/VS1 introduced the 3270 device. > > On Tue, Nov 5, 2019 at 6:41 AM scott Ford <idfli...@gmail.com> wrote: >> Actually, this in the way back machine we were doing this in the OS /VS2 >> days. >> >> On Tue, Nov 5, 2019 at 7:38 AM scott Ford <idfli...@gmail.com> wrote: >> >>> Many concepts re-surface Steve. >>> >>> On Mon, Nov 4, 2019 at 10:02 PM Steve Smith <sasd...@gmail.com> wrote: >>> >>>> This sure sounds like a discussion from the 1980s. Operators? Consoles? >>>> Those are still a thing? >>>> >>>> Try out the new // NOTIFY statement, and send an email to whoever needs to >>>> wake up. >>>> >>>> sas >>>> >>>> >>>> On Mon, Nov 4, 2019 at 8:37 PM CM Poncelet <ponce...@bcs.org.uk> wrote: >>>> >>>>> 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 >>>>> >>>> >>>> -- >>>> sas >>>> >>>> ---------------------------------------------------------------------- >>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>>> >>> -- >>> Scott Ford >>> IDMWORKS >>> z/OS Development >>> >> -- >> Scott Ford >> IDMWORKS >> z/OS Development >> >> ---------------------------------------------------------------------- >> 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
