Paul

I provided my example because your subject title pulled me it,
DISP=(MOD,DELETE) being the heart - or so I thought until this thread
unravelled - of the "trick" to starting with a new data set in a following
job step. Thus the objectives of this technique and what you are after
differ.

Regarding SYST: I did provide a reference in an earlier post to an earlier
thread where I solicited comments on the matter of removing SYST. However if
you Google on "SYST SCHEDxx Mason", you'll get one hit, the URL of the
thread in an archive of IBM-MAIN.

Regarding VOL=REF (or VOL=SER): My example is very close to what I used to
use - only the names have been changed to make them more general. Very
probably - almost certainly - you can replace VOL=REF with to whatever it is
normally equivalent.

Regarding SYS1.PARMLIB: From time to time when posting I explain that my
background is *not* production but education/test. I used to run up to 8 MVS
systems where I had one volume per system, the "read/write" volume, and one
common "read-only" volume. I suspect that the SYS1.PARMLIB data set was one
the "read/write" volume for some reason I have now forgotten.

Chris Mason

----- Original Message ----- From: "Paul Gilmartin" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Thursday, May 24, 2007 5:05 AM
Subject: Re: DISP=(MOD,DELETE)


On Wed, 23 May 2007 08:54:01 +0200, Chris Mason <[EMAIL PROTECTED]> wrote:

If you've only just discovered this "trick" - pointed out to me many years
ago by a guru from the Washington Systems Center - perhaps this example can
show you how it may be used:

//NET PROC
//*
//IEFBR14 EXEC PGM=IEFBR14
//NCPDUMP DD DSN=USER.NCPDUMP,DISP=(MOD,DELETE),
// VOL=REF=SYS1.PARMLIB,SPACE=(TRK,1)
//*
//NET EXEC PGM=ISTINM01,TIME=1440,REGION=2048K
//STEPLIB DD DSN=SYS1.SSPLIB,DISP=SHR
//VTAMLST DD DSN=USER.VTAMLST,DISP=SHR
//VTAMLIB DD DSN=USER.VTAMLIB,DISP=SHR
//        DD DSN=SYS1.VTAMLIB,DISP=SHR
//NCPLOAD DD DSN=USER.NCPLOAD,DISP=SHR
//NCPDUMP DD DSN=USER.NCPDUMP,DISP=(NEW,KEEP),
// VOL=REF=SYS1.PARMLIB,SPACE=(TRK,(1,50),RLSE),
// DCB=(RECFM=F,LRECL=512,BLKSIZE=512)

Would it work equally well with VOL=SER as VOL=REF?  (I suspect that
was for portability.  But I'd expect my admins to be pretty fussy
about who creates what on the PARMLIB volume.)

Well, my objectives were (arising from the ISV SMP/E "gripes" thread):

o Create the data set if it does not exist.

o Append to (not replace) the data set if it does exist.

o Allow the user optionally to specify VOLSER.

On experimenting, reading, and receiving input from this list,
I've lowered my sights and retreated to DISP=(NEW,{KEEP|CATLG})

Note that I was obliged to include TIME=1440 on the EXEC statement since I
was obliged to remove SYST from the SCHEDxx entry for ISTINM01.

I don't understand that part at all.

Thanks for the input,
gil

----------------------------------------------------------------------
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

Reply via email to