Data set name ===> 'ABCDE.FGHIJK.LMNOP'
Member to use ===> QRSTUV
Disposition ===> NEW (OLD, NEW, SHR, MOD)
Management class ===> (Blank for default management class)
Storage class ===> (Blank for default storage class)
Volume serial ===> (Blank for authorized default volume)
Device type ===> (Generic unit or device address)
Data class ===> (Blank for default data class)
Space units ===> CYLS (BLKS, TRKS, CYLS, BY, KB, or MB)
Primary quantity ===> 25 (In above units)
Secondary quantity ===> 5 (In above units)
Directory blocks ===> 45 (Zero for sequential data set) <=====
Did you specify directory blanks???
Record format ===> FBA
Record length ===> 133
Block size ===>
Data set name type ===> <======= Do you have this value specified???
Extended attributes ===> (NO, OPT, or blank)
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of willie bunter
Sent: Friday, April 29, 2016 7:45 AM
To: [email protected]
Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
Lizette,
I tried your suggestion using NEW but it doesn't work. I get the message
MEMBER NAME NOT ALLOWED
I hit the PF1 option but it wasn't much help.
--------------------------------------------
On Thu, 4/28/16, Lizette Koehler <[email protected]> wrote:
Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
To: [email protected]
Received: Thursday, April 28, 2016, 7:08 PM
When you use XDC and NEW
it will indicate if the member already exists.
You should try this and see if
it works.
I find trying
SHR, OLD and NEW on a PDS that will not matter if it is over written a good
thing to try to understand how things work.
Also, you could press
PF1 (HELP) and see what the HELP panel states.
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List
[mailto:[email protected]]
On
> Behalf Of willie bunter
> Sent: Thursday, April 28, 2016 4:00 PM > To: [email protected] >
> Subject: SAVING JOB OUTPUT IN A PDSE FROM SDSF > > Hallo All, > > I
> need your suggestions. I am savings job output in a PDSE using SDSF. The
> > member name I use is the job number e.g.
> Member to use ===>
JOB067XX
>
> I am
afraid that some where down the line I could overwrite a member because >
the job number could be the same. Is there something I could do to prevent >
this from happening?
>
> Below is an example of the screen when I type XDC beside the job:
>
> Data set name ===>
'SYS2.BATCH.JOBS.OUTPUT
> Member to
use ===> JOB06703
> Disposition
===> SHR (OLD, NEW, SHR, MOD)
>
> Thanks in
advance.
>
----------------------------------------------------------------------
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
