Because what's past is prologue. Until 10-12 years ago, you couldn't do it in a JES2 shop. Now, it's ingrained and too many people/processes depend on it. - Ted MacNEIL [email protected] Twitter: @TedMacNEIL
-----Original Message----- From: Frank Swarbrick <[email protected]> Sender: IBM Mainframe Discussion List <[email protected]> Date: Wed, 1 May 2013 13:49:26 To: <[email protected]> Reply-To: IBM Mainframe Discussion List <[email protected]> Subject: Re: Check whether job still running Which begs the question...why?? >________________________________ > From: retired mainframer <[email protected]> >To: [email protected] >Sent: Wednesday, May 1, 2013 12:56 PM >Subject: Re: Check whether job still running > > >:>: -----Original Message----- >:>: From: IBM Mainframe Discussion List [mailto:[email protected]] On >:>: Behalf Of Frank Swarbrick >:>: Sent: Wednesday, May 01, 2013 10:41 AM >:>: To: [email protected] >:>: Subject: Re: Check whether job still running >:>: >:>: Why are people so insistent that having two same named jobs running at >:>: the same time would cause such havoc? Do people really often have two >:>: jobs with the same name that do different things submitted at the same >:>: time with the intention that they need to run sequentially and not >:>: simultaneously? > >Speaking only for my shop, ABSOTIVELY POSILUTELY AND EMPHATICALLY YES!!! > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
