I'd much prefer the latter, but of course have no idea how much work it would be.
What is your 'driver' for wanting this feature? Mine is to eliminate the requirement of the separate IEFBR14 to do a MOD,DELETE prior to doing a NEW. Honestly have a hard time understanding how MVS has gone this long with that kludgey (IMHO) behavior, but... Frank >________________________________ > From: "McKown, John" <john.mck...@healthmarkets.com> >To: IBM-MAIN@bama.ua.edu >Sent: Thursday, February 23, 2012 2:34 PM >Subject: Re: Thought: new DISP "status" function > >A good question. The simpliest thing was to have the INITIATOR write an EOF to >the dataset and then make the access method use MOD. This should be a minimal >change. IMO, the best thing to do would be to have the initiator do a catalog >lookup and scratch the dataset if it exists, then do NEW processing to redrive >SMS and allocation. > >-- >John McKown >Systems Engineer IV >IT > >Administrative Services Group > >HealthMarkets® > >9151 Boulevard 26 . N. Richland Hills . TX 76010 >(817) 255-3225 phone . >john.mck...@healthmarkets.com . www.HealthMarkets.com > >Confidentiality Notice: This e-mail message may contain confidential or >proprietary information. If you are not the intended recipient, please contact >the sender by reply e-mail and destroy all copies of the original message. >HealthMarkets® is the brand name for products underwritten and issued by the >insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance >Company®, Mid-West National Life Insurance Company of TennesseeSM and The MEGA >Life and Health Insurance Company.SM > > > >> -----Original Message----- >> From: IBM Mainframe Discussion List >> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Frank Swarbrick >> Sent: Thursday, February 23, 2012 3:30 PM >> To: IBM-MAIN@bama.ua.edu >> Subject: Re: Thought: new DISP "status" function >> >> I like it. >> >> John: What would your expectation be if the characteristics >> of the existing dataset were different than those specified >> on the DD. SPACE and the like. Would this new parm alter >> the characteristics as specified on the DD, or would they say >> the same? >> >> Frank >> >> >> >> >> >________________________________ >> > From: Mike Schwab <mike.a.sch...@gmail.com> >> >To: IBM-MAIN@bama.ua.edu >> >Sent: Thursday, February 23, 2012 1:39 PM >> >Subject: Re: Thought: new DISP "status" function >> > >> >DISP=REUSE or DISP=(REUSE,CATLG) in case of additional volumes. >> > >> >On Thu, Feb 23, 2012 at 2:28 PM, McKown, John >> ><john.mck...@healthmarkets.com> wrote: >> >> We all know that you can specify DISP=OLD|SHR|NEW|MOD for >> a dataset. I just had another wacky thought of a new one that >> I would like. I can't really think of a good, three >> character, value for it. But what it would do is what UNIX >> does with a PATHOPTS=(OTRUNC,OCREAT). It would, like MOD, >> either reuse an existing allocation, or create a new one. >> But, unlike MOD, it would not add to the end, but put an EOF >> at the beginning of the dataset and start writing over the >> old data. What do others think? >> >> >> >> John McKown >> > >> >-- >> >Mike A Schwab, Springfield IL USA >> >Where do Forest Rangers go to get away from it all? >> > >> >------------------------------------------------------------- >> --------- >> >For IBM-MAIN subscribe / signoff / archive access instructions, >> >send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN >> > >> > >> > >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN >> >> > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN