Gil, When I said choked, I really meant crashed (as in choked and died).
The reference to DFSMSdss is my bad, and in fact it may have been changing DFSMShsm to use the dss datamover that solved many of the "dataset left behind problems" we were having at this particular site. It's been 15 years since I worked as a Storage Admin so the memory is a bit dodgy, but I'm certain there was a time when DFSMShsm would not migrate an empty dataset. Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Paul Gilmartin > Sent: Sunday, March 18, 2012 10:30 AM > To: [email protected] > Subject: Re: [IBM-MAIN] IEFBR14 > > On Sun, 18 Mar 2012 10:02:28 -0400, Gerhard Postpischil wrote: > > >On 3/18/2012 9:03 AM, Ron Hawkins wrote: > >> And finally, my memory may be a bit dodgy nowadays, but it's my > >> recollection that the EOF for empty datasets was introduced so that > >> DFSMShsm and DFSMSdss could migrate, move and copy empty datasets. > >> When there is no EOF for a zero empty dataset these utilities choke > >> and spit it back. I don't think security was an objective. > > > IIRC, there was a time in prehistory or thereabouts when HSM choked > attempting to migrate a properly formatted PDS with no members. > There might have been a mismotivated performance concern here: > If it's empty, it's more efficient to delete and later reallocate than to migrate > and recall. > > >When you use the ALLDATA option, DSS copies whatever exists past the > >last valid EOF. ... > > > Presumably also past DS1LSTAR? > > -- 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
