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]] On Behalf Of Paul Gilmartin Sent: Tuesday, May 05, 2015 12:25 PM To: [email protected] 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] 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
