Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-05-03 Thread willie bunter
* /* On Fri, 4/29/16, R.S. wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, April 29, 2016, 5:06 PM W dniu 2016-04-29 o 22:30, Paul Gilmartin pisze: > On 2016-04-29, at 09:58, R.S. wrote: >>>> That deserve

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-05-02 Thread willie bunter
r more) Extended attributes ===> (NO, OPT, or blank) ---- On Mon, 5/2/16, Richards, Robert B. wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Monday, May 2, 2016, 5:31 AM Willie, According to

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-05-02 Thread Mike Schwab
Maybe put Year in DSN, member name would include Month 1-9,A,B,C, Day 01-31, Time -2359, or Day of Year 001-366, Time -2359. On Mon, May 2, 2016 at 11:21 AM, Pedro Vera wrote: >>> Is there something I could do to prevent this from happening? > > I think JES2 can be customized to use seven

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-05-02 Thread Pedro Vera
>> Is there something I could do to prevent this from happening? I think JES2 can be customized to use seven digit numbers for the job number. On my site, the jobs numbers look like J1234567. That is, you cannot prevent the collision in job numbers, but you can lessen the frequency. If I we

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-05-02 Thread Richards, Robert B.
-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, April 29, 2016 1:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF This is what I have. In the Data set name type

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-29 Thread Paul Gilmartin
On 2016-04-29, at 15:06, R.S. wrote: >> >> Works for me. > You are right. Please rerun the job. I bet you'll get SB214 abend. > I know that well. I assumed that since the OP's requirement was to avoid overwriting an existing member, SB214 would meet his need. I had considered the alternative

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-29 Thread R.S.
W dniu 2016-04-29 o 22:30, Paul Gilmartin pisze: On 2016-04-29, at 09:58, R.S. wrote: That deserves an SR. Works in JCL; works everywhere else. The statement is patently false. No, it isn't. MOD is not allowed for *member* od PDS or PDSE. MOD is allowed for PO dataset, i.e. for IEFBR14 MOD,DE

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-29 Thread Paul Gilmartin
On 2016-04-29, at 09:58, R.S. wrote: >>> >>> That deserves an SR. Works in JCL; works everywhere else. The statement is >>> patently false. >> No, it isn't. MOD is not allowed for *member* od PDS or PDSE. >> MOD is allowed for PO dataset, i.e. for IEFBR14 MOD,DELETE >> >> Try IEBGENER //SYSUT2

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-29 Thread willie bunter
or more)    Extended attributes  ===>           (NO, OPT, or blank)                        ---- On Fri, 4/29/16, Richards, Robert B. wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-29 Thread R.S.
(resend, please be patient if got two copies) W dniu 2016-04-29 o 17:37, R.S. pisze: W dniu 2016-04-29 o 17:31, Paul Gilmartin pisze: On Fri, 29 Apr 2016 11:49:57 +, willie bunter wrote: Paul. I tried out your suggestion using disp=mod however it doesn't work : MOD NOT ALLOWED FOR PDS

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-29 Thread Paul Gilmartin
On Fri, 29 Apr 2016 11:49:57 +, willie bunter wrote: >Paul. > >I tried out your suggestion using disp=mod however it doesn't work : MOD NOT >ALLOWED FOR PDS > ??? That deserves an SR. Works in JCL; works everywhere else. The statement is patently false. -- gil --

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-29 Thread willie bunter
Paul. I tried out your suggestion using disp=mod however it doesn't work : MOD NOT ALLOWED FOR PDS On Thu, 4/28/16, Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SD

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-29 Thread Richards, Robert B.
-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, April 29, 2016 7:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF Lizette, I tried your suggestion using NEW but

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-29 Thread willie bunter
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 wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-29 Thread R.S.
No, you cannot prevent it. Been there... -- Radoslaw Skorupka Lodz, Poland W dniu 2016-04-29 o 00:59, willie bunter pisze: 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 a

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-28 Thread Paul Gilmartin
On Thu, 28 Apr 2016 22:59:45 +, willie bunter wrote: > >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

Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-28 Thread Lizette Koehler
the HELP panel states. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of willie bunter > Sent: Thursday, April 28, 2016 4:00 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: SAVING JOB OUTPUT IN A PDSE FROM S

SAVING JOB OUTPUT IN A PDSE FROM SDSF

2016-04-28 Thread willie bunter
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 coul