Hi. We thought it was a space issue initially so we made the &&work large. For
a while it seemed to get the job to run by upping the && allocation. Looks like
a coincidence. We have run it with the same input and with different inputs and
it fails sporadically. Today we used different input files each time. If it was
a bad record it would be there each run until it was downloaded to us it should
fail everytime but it doesn't. The user said he ran it all day yesterday and it
0C4ed. Came in this AM and it ran. No rhyme or reason to this.
Think Spring !!!
Bob Pelletier
Connecticut Student Loan Foundation
Rocky Hill, Connecticut
-----Original Message-----
From: Charles Mills [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 23, 2006 12:41 PM
To: [email protected]
Subject: Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When &&Dataset
Used
If the job works with a space allocation of CYL,(5,5) then why do you
specify much larger quantities in the && situation?
Are you using a smaller input file or otherwise a smaller test case in the
"good" situation? Is it possible that the S0C4 is related not to DSN=&& but
rather to data volumes, or to some problem with the n'th input record?
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Robert Pelletier
Sent: Thursday, February 23, 2006 11:27 AM
To: [email protected]
Subject: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When &&Dataset Used
Hi All. Once again I look to the group for help. I am at a total loss and
have test extensively. This is the issue:
If I use the following && JCL the job fails consistently with an 0C4:
//WORK01 DD DISP=NEW,UNIT=SYSDA,SPACE=(CYL,(4300,5)),
// LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=&&WORK01
//WORK02 DD DISP=NEW,UNIT=SYSDA,SPACE=(CYL,(4300,5)),
// LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=&&WORK02
//WORK03 DD DISP=NEW,UNIT=SYSDA,SPACE=(CYL,(900,5)),
// LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=&&WORK03
//WORK04 DD DISP=NEW,UNIT=SYSDA,SPACE=(CYL,(900,5)),
// LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=&&WORK04
I have 4 PUBLIC volumes.
If I use this JCL which uses permanent datasets the job works everytime:
//WORK01 DD DISP=(NEW,CATLG),UNIT=SYSDA,SPACE=(CYL,(5,5)),
// LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=TRAM1.WORK1,
// VOL=SER=BACK09
//WORK02 DD DISP=(NEW,CATLG),UNIT=SYSDA,SPACE=(CYL,(5,5)),
// LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=TRAM1.WORK2,
// VOL=SER=BACK09
//WORK03 DD DISP=(NEW,CATLG),UNIT=SYSDA,SPACE=(CYL,(5,5)),
// LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=TRAM1.WORK3,
// VOL=SER=BACK09
//WORK04 DD DISP=(NEW,CATLG),UNIT=SYSDA,SPACE=(CYL,(5,5)),
// LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=TRAM1.WORK4,
// VOL=SER=BACK09
----------------------------------------------------------------------
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
