Tom,
In that case, you may have missed this enhancement in (E)JES Release
Information when V4R1 came out:
|x.7.1 New Meaning for DISP=NEW for PDS(E) Extract
|
|In prior releases, two different mechanisms were needed to protect
|existing DASD data from overlay by an extract operation.
|
|Specifying DISP=NEW prevented overlay of an existing data set. The only
|way to protect an individual member within an existing partitioned data
|set was to specify DISP=MOD, which would result in a B14-04 abend if the
|member previously existed.
|
|This meant that DISP=NEW was the most appropriate way to protect a
|sequential data set from overlay while DISP=MOD was the most appropriate
|way to protect a member of a PDS(E) from overlay.
|
|Beginning in this release, DISP=NEW is treated like DISP=MOD for an
|existing partitioned data set. Now DISP=NEW can be used to protect both
|sequential data sets and PDS(E) members from overlay.
Ed Jaffe
Tom Marchant wrote:
On Thu, 6 Jul 2006 13:39:51 -0500, Paul Gilmartin <[EMAIL PROTECTED]>
wrote:
o DISP=MOD,DSN=HLQ.LLQ(&MEMBER) to prevent overwriting an existing member.
I've distributed some JCL using this, and about once a year I get a phone
call about a Sx14 ABEND. Generally, the caller is grateful when I remind
him he was about to overwrite, and renames the existing member for
backup.
I hadn't noticed this before. Thanks, Gil!
Tom Marchant
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
