We have our own "IEFBR14" that does exactly that, it just reads input from SYSIN and performs the required SCRATCH or not depending on the status and then reports on what it did.
Craig -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Scott Ford Sent: Wednesday, May 06, 2015 08:18 To: [email protected] Subject: Re: IEFBR14 question Paul, I like that, why not or at the least provide a mechanism that works. Regards, Scott On Wednesday, May 6, 2015, Scheuer, Paul <[email protected]> wrote: > Sure! Can you drop them by Marcello 4406 around 8am? > > Sent from my Android phone using TouchDown (www.nitrodesk.com) > > -----Original Message----- > From: Dave Barry [[email protected] > <javascript:;>] > Received: Tuesday, 05 May 2015, 3:54PM > To: [email protected] <javascript:;> [[email protected] > <javascript:;>] > Subject: Re: IEFBR14 question > > Some third-party software in use here at UPS has used this technique > for years. The assumption is perfectly valid. > > Think about it: If an initiator allocates a migrated dataset > specifically on behalf of IEFBR14 -- which cannot even open it, much > less use it -- just to process a normal disposition of DELETE, why > waste HSM resources and tie up the initiator while waiting for the > recall to complete? The O/S might just as well schedule an HDELETE and be > done with it. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected] > <javascript:;>] On Behalf Of Paul Gilmartin > Sent: Tuesday, May 05, 2015 12:25 PM > To: [email protected] <javascript:;> > Subject: Re: IEFBR14 question > > On 2015-05-05, at 10:16, Greg Shirey wrote: > > > The O/S may never "use" the data set after the step runs, but > > perhaps > "using" the data set wasn't the point of running the step. I'd prefer the > O/S not make that assumption for me. > > > And yet, lately, the O/S makes such an assumption when the data set is > migrated. Yes, as R.S. says, you can turn it off. > It should be possible to override it within a particular job, not > system-wide. OS/360 was not designed as a multi-user system. Its > descendants inherit that original sin. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] <javascript:;> with the message: > INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] <javascript:;> with the message: > INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] <javascript:;> 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 ________________________________ This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
