I don't think so. I still want some of my sequential output to be on z/OS UNIX 
(where I also now keep 99% of my JCL and source). The new "status" would not 
help me use UNIX tools on sequential files. Yes, I do have ways to do it. But, 
IMO, they have more overhead because those tools cannot read sequential 
datasets.

--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets®

9151 Boulevard 26 . N. Richland Hills . TX 76010
(817) 255-3225 phone . 
[email protected] . 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:[email protected]] On Behalf Of Frank Swarbrick
> Sent: Thursday, February 23, 2012 4:07 PM
> To: [email protected]
> Subject: Re: Thought: new DISP "status" function
> 
> Do you think that this new feature would be able to fulfill 
> both needs?
> Frank
> 
> 
> 
> 
> >________________________________
> > From: "McKown, John" <[email protected]>
> >To: [email protected] 
> >Sent: Thursday, February 23, 2012 2:52 PM
> >Subject: Re: Thought: new DISP "status" function
> > 
> >I don't have a need. We use CA-11, which takes care of the 
> problem of recreating existing datasets. Why I thought of it 
> is due to my new tendency to use z/OS UNIX files instead of 
> sequential datasets, when I intend to edit them. I use 
> PATHOPTS=(OTRUNC,OCREAT) and it just occurred to me that it 
> might be nice for standard sequential datasets too. I use 
> z/OS UNIX files because I like to use programs like sed, awk, 
> and perl for data manipulation. 
> >
> >--
> >John McKown 
> >Systems Engineer IV
> >IT
> >
> >Administrative Services Group
> >
> >HealthMarkets®
> >
> >9151 Boulevard 26 . N. Richland Hills . TX 76010
> >(817) 255-3225 phone . 
> >[email protected] . 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:[email protected]] On Behalf Of Frank Swarbrick
> >> Sent: Thursday, February 23, 2012 3:44 PM
> >> To: [email protected]
> >> Subject: Re: Thought: new DISP "status" function
> >> 
> >> 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" <[email protected]>
> >> >To: [email protected] 
> >> >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 . 
> >> >[email protected] . 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:[email protected]] On Behalf Of Frank Swarbrick
> >> >> Sent: Thursday, February 23, 2012 3:30 PM
> >> >> To: [email protected]
> >> >> 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 <[email protected]>
> >> >> >To: [email protected] 
> >> >> >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
> >> >> ><[email protected]> 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 [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
> >> >
> >> >
> >> >
> >> 
> >> 
> ----------------------------------------------------------------------
> >> 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
> 
> 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to