In 4d43781a.4060...@phoenixsoftware.com, on 01/28/2011
at 06:14 PM, Edward Jaffe edja...@phoenixsoftware.com said:
It fails with:
IEF212I JCLERROR IGMLENU SYSUT2 - DATA SET NOT FOUND
Try using a referback fof SYSUT2.
If it can find the data set for SYSUT1, then why can't it find it
for
: Saturday, January 29, 2011 11:10 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Second Reference to Temporary Data Set Fails
On Fri, 28 Jan 2011 18:14:50 -0800, Edward Jaffe wrote:
It fails with:
IEF212I JCLERROR IGMLENU SYSUT2 - DATA SET NOT FOUND
If it can find the data set for SYSUT1
Reference to Temporary Data Set Fails
Obviously, IANFJE (I ain't no friggin JCL expert). But, it seems to me that this
should work:
//JCLERROR JOB ...
//AGMLENU EXEC PGM=IEFBR14
//GML DD DSN=GML,UNIT=SYSALLDA,
// RECFM=FB,LRECL=80,BLKSIZE=0,
// DISP=(NEW,PASS),SPACE
If you do that - use permanent data sets as pseudo-temporaries - then you
forego the potential for VIO (In Central). But then I do it myself
sometimes.
Cheers, Martin
Martin Packer,
Mainframe Performance Consultant, zChampion
Worldwide Banking Center of Excellence, IBM
+44-7802-245-584
On Fri, 28 Jan 2011 22:46:47 -0600, John McKown wrote:
That's what I do:
//SYSUT1 DD DSN=amp;DSN,DISP=(OLD,PASS)
//SYSUT2 DD DSN=*.SYSUT1,DISP=(OLD,PASS),
// UNIT=AFF=SYSUT1,
// VOL=REF=*.SYSUT1
I frequently do this to create SYSEXEC (DISP=NEW) as a temp DS;
populate it with an EXEC
On Fri, 28 Jan 2011 18:14:50 -0800, Edward Jaffe wrote:
It fails with:
IEF212I JCLERROR IGMLENU SYSUT2 - DATA SET NOT FOUND
If it can find the data set for SYSUT1, then why can't it find it for SYSUT2?
It
works fine when a normal cataloged data set is used. It fails only with a
temporary data
@bama.ua.edu
Subject: Re: Second Reference to Temporary Data Set Fails
On Fri, 28 Jan 2011 18:14:50 -0800, Edward Jaffe wrote:
It fails with:
IEF212I JCLERROR IGMLENU SYSUT2 - DATA SET NOT FOUND
If it can find the data set for SYSUT1, then why can't it find it for SYSUT2?
It
works fine when a normal
At 13:09 -0600 on 01/29/2011, Paul Gilmartin wrote about Re: Second
Reference to Temporary Data Set Fails:
Armed with a priori knowledge of the correct answer, I went looking for
the restriction. I found, to the contrary, that it's supposed to
work:
http://publibz.boulder.ibm.com/cgi-bin
At 14:53 -0500 on 01/29/2011, David Kreiss wrote about Re: Second
Reference to Temporary Data Set Fails:
I think this explains the passed data set restriction seen. I
believe the example found in section 4.1.1.2.1 is incorrect and is a
doc error.
That section shows how to create a member
Obviously, IANFJE (I ain't no friggin JCL expert). But, it seems to me that this
should work:
//JCLERROR JOB ...
//AGMLENU EXEC PGM=IEFBR14
//GML DD DSN=GML,UNIT=SYSALLDA,
// RECFM=FB,LRECL=80,BLKSIZE=0,
// DISP=(NEW,PASS),SPACE=(TRK,(1,1,1))
//IGMLENU EXEC
Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Edward Jaffe
Sent: Friday, January 28, 2011 6:15 PM
To: IBM-MAIN@bama.ua.edu
Subject: Second Reference to Temporary Data Set Fails
Obviously, IANFJE (I ain't no friggin JCL expert). But, it seems to me
The good news is that you don't need the SYSUT1 when PARM=NEW. Just
take it out and it will work. In fact, you don't need a separate step to
allocate
the temporary data set.
Bill
On Fri, 28 Jan 2011 18:14:50 -0800, Edward Jaffe wrote:
Obviously, IANFJE (I ain't no friggin JCL expert). But,
@bama.ua.edu] On Behalf
Of Edward Jaffe
Sent: Friday, January 28, 2011 6:15 PM
To: IBM-MAIN@bama.ua.edu
Subject: Second Reference to Temporary Data Set Fails
Obviously, IANFJE (I ain't no friggin JCL expert). But, it seems to me that
this
should work:
//JCLERROR JOB ...
//AGMLENU EXEC
13 matches
Mail list logo
