Re: Update: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
On Thu, 23 Feb 2006 12:40:26 -0500, Robert Pelletier [EMAIL PROTECTED] wrote: The job just worked using work files. It failed all morning with work. Any ideas? Does an LE program require a lot of storage? It looks like our PUBLIC volumes have plenty of space. Thanks all. Think Spring !!! Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut Have you found an acceptable answer to this one ??? I recall having a very similar issue a few years ago, but I haven't been able to find my notes on it. We experienced very inconsistent behavior. But I seem to recall our issue relating to passing a temporary dataset between steps. Someone also had an answer, which is why I was trying to find my notes. Are you looking for an answer or a way around it ??? If you just code something in the DSN= and make sure you don't specify DISP=, the end result is a dataset that goes away after the JOB completes much like a tempporary dataset. -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Robert, This looks like a SORT application. Are you using SyncSort and have you applied mandatory maintenance SY62470? We did, even though it fixes hardware we do not have and then started getting 0C4's on jobs restarted by CA-11 (i.e. having funny delete/define processing - don't quote me). I would be interested in the follow-up. Dave On Thu, 23 Feb 2006 12:26:39 -0500, Robert Pelletier [EMAIL PROTECTED] wrote: 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 Can anyone offer suggestions as to why work is not working. We are OS390 V2R10 and the program is written LE. I do not have the source because it was given to us by the agency we feed the data too. In advance thanks all. Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
In [EMAIL PROTECTED], on 02/23/2006 at 03:52 PM, Rugen, Len [EMAIL PROTECTED] said: - But when allocated as a -dataset, it is somehow (?) allocated in virtual memory. Unless there's an enhancement to VIO that I don't know about, SAM doesn't directly use the VIO pages; it runs a simulated channel program into normal buffers just as though it were accessing a normal DASD file. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Here is my theory: Use DISP=(NEW,PASS) Also this looks very much like a program which may write data to a file, close the file, and then read the data back in. On a temporary dataset, it my be getting deleted after the close. Are the temporary datasets being directed to disk or VIO? On Thu, 23 Feb 2006 16:37:07 -0500, Shmuel Metz (Seymour J.) [EMAIL PROTECTED] wrote: In [EMAIL PROTECTED], on 02/23/2006 at 12:26 PM, Robert Pelletier [EMAIL PROTECTED] said: Hi All. Once again I look to the group for help. I am at a total loss and have test extensively. 1. Are there any IEC... messages? 2. What is the Interrupt code? 3. In what module is it taking the S0C4? 4. Where does R14 point? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
I think you're close to the cause. The temp data set does not get deleted until step end, but if the appl closes the file and reopens it, then all bets are off. Matthew Stitt [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/24/2006 10:58 AM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used Here is my theory: Use DISP=(NEW,PASS) Also this looks very much like a program which may write data to a file, close the file, and then read the data back in. On a temporary dataset, it my be getting deleted after the close. Are the temporary datasets being directed to disk or VIO? On Thu, 23 Feb 2006 16:37:07 -0500, Shmuel Metz (Seymour J.) [EMAIL PROTECTED] wrote: In [EMAIL PROTECTED], on 02/23/2006 at 12:26 PM, Robert Pelletier [EMAIL PROTECTED] said: Hi All. Once again I look to the group for help. I am at a total loss and have test extensively. 1. Are there any IEC... messages? 2. What is the Interrupt code? 3. In what module is it taking the S0C4? 4. Where does R14 point? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
If it's going to VIO, then that could change the assigned BLKSIZE since this can be different geometry, which might uncover some kind of bug in the program. Bill On Thu, 23 Feb 2006 20:43:28 -0800, Skip Robinson [EMAIL PROTECTED] wrote: Wow, I love this kind of problem. I ran the following JCL with IEFBR14: //NEWGUY1 DD DISP=(NEW,DELETE),SPACE=(TRK,1),DSN=TED066.TEST //NEWGUY2 DD DISP=(NEW,DELETE),SPACE=(TRK,1),DSN=TEST //NEWGUY3 DD DISP=(NEW,DELETE),SPACE=(TRK,1) The resulting allocations shown below differ in two ways: real DASD vs. VIO, and short vs. long (near max) data set name. I've seen cases where a program would not work with VIO data sets; usually an ISV product that was (or should have been!) documented as such. The length of the data set name may be significant if the application for some reason obtains the data set and stores it somewhere: the longer *generated* name may overlay some buffer or work area. IGD101I SMS ALLOCATED TO DDNAME (NEWGUY1 ) DSN (TED066.TEST ) STORCLAS (STANDARD) MGMTCLAS (STANDARD) DATACLAS (STAND1) VOL SER NOS= ARN030 IGD101I SMS ALLOCATED TO DDNAME (NEWGUY2 ) DSN (SYS06054.T203308.RA000.TESTALLO.TEST.H01) STORCLAS (STANDARD) MGMTCLAS () DATACLAS (STAND1) VOL SER NOS= VIO IGD101I SMS ALLOCATED TO DDNAME (NEWGUY3 ) DSN (SYS06054.T203308.RA000.TESTALLO.R0170562) STORCLAS (STANDARD) MGMTCLAS () DATACLAS (STAND1) VOL SER NOS= VIO . . JO.Skip Robinson Southern California Edison Company SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 02/23/2006 09:26:39 AM: 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 Can anyone offer suggestions as to why work is not working. We are OS390 V2R10 and the program is written LE. I do not have the source because it was given to us by the agency we feed the data too. In advance thanks all. -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Robert, I suppose you have a dump when S0C4 occurs. Can you force a dump during the OK run, for example by adding TIME=(,3) on the EXEC stmt? If you have both dumps, you can compare them and see what's different, such as module placement, memory allocation, etc. This may give you a clue as to why this only happens with temp data sets. -- Gilbert Saint-Flour GSF Software http://gsf-soft.com/ mailto:[EMAIL PROTECTED] On Thursday 23 February 2006 12:32, Robert Pelletier wrote: 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 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 -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Robert, Why 4300 Cylinders for WORK01 and only 5 Cylinders for TRAM1.WORK1?? Stupid Question: Can a TEMP Dataset span a volume? Or is this a Mod-9 or Mod-23?? Thanks...Guy M. Gates Jr. TTI Z/OS Systems Programmer Phone: (817) 740-9000 x-4627 Email: [EMAIL PROTECTED] Z/OS - World-Class Software, Supporting World-Class Business -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Gilbert Saint-Flour Sent: Friday, February 24, 2006 2:45 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used Robert, I suppose you have a dump when S0C4 occurs. Can you force a dump during the OK run, for example by adding TIME=(,3) on the EXEC stmt? If you have both dumps, you can compare them and see what's different, such as module placement, memory allocation, etc. This may give you a clue as to why this only happens with temp data sets. -- Gilbert Saint-Flour GSF Software http://gsf-soft.com/ mailto:[EMAIL PROTECTED] On Thursday 23 February 2006 12:32, Robert Pelletier wrote: 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 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 -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Stupid Question: Can a TEMP Dataset span a volume? Or is this a Mod-9 or Mod-23?? You bet. Just tried it, and my SRS product kicked in and added volumes to the temp file I had allocated, just like it should. Jeffrey Deaver, Senior Analyst, Systems Engineering 651-665-4231 -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Are the tempy files being switched to VIO at your place? -- 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
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 Can anyone offer suggestions as to why work is not working. We are OS390 V2R10 and the program is written LE. I do not have the source because it was given to us by the agency we feed the data too. In advance thanks all. Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
By any chance do you create WORKxx in prior steps in the same job? Robert Pelletier [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/23/2006 12:26 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc 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 Can anyone offer suggestions as to why work is not working. We are OS390 V2R10 and the program is written LE. I do not have the source because it was given to us by the agency we feed the data too. In advance thanks all. Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut -- 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
Update: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
The job just worked using work files. It failed all morning with work. Any ideas? Does an LE program require a lot of storage? It looks like our PUBLIC volumes have plenty of space. Thanks all. Think Spring !!! Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut 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 Can anyone offer suggestions as to why work is not working. We are OS390 V2R10 and the program is written LE. I do not have the source because it was given to us by the agency we feed the data too. In advance thanks all. -- 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
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: IBM-MAIN@BAMA.UA.EDU 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
No first step is a IEFBR14 to delete some files. Think Spring !!! Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut - -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Most application programs are not aware of any file details. About the only thing that springs to mind is some sort of allocation failure/denial that caused OPEN to fail, and the program failed to test the OPEN completion code. Supporting that SWAG is that many shops direct allocation differently for temporary datasets than cataloged datasets. Are there any other messages on the SYSLOG or JOBLOG that may be helpful? -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Robert Pelletier Sent: Thursday, February 23, 2006 11:27 AM To: IBM-MAIN@BAMA.UA.EDU 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 Can anyone offer suggestions as to why work is not working. We are OS390 V2R10 and the program is written LE. I do not have the source because it was given to us by the agency we feed the data too. In advance thanks all. Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
This is all I found: IEF450I TRAM1SFA STEP02 - ABEND=S0C4 U REASON=0004 CEE3204S The system detected a protection exception (System Completion Code=0C4) From entry point EAFile::readNextLine() at compile unit offset +008 CEE3DMP V2 R10.0: Condition processing resulted in the unhandled condition. CEE3204S The system detected a protection exception (System Completion Code=0C4) From entry point EAFile::readNextLine() at compile unit offset +008 CEE3DMP V2 R10.0: Condition processing resulted in the unhandled condition. Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut 860-257-4001 X382 Most application programs are not aware of any file details. About the only thing that springs to mind is some sort of allocation failure/denial that caused OPEN to fail, and the program failed to test the OPEN completion code. Supporting that SWAG is that many shops direct allocation differently for temporary datasets than cataloged datasets. Are there any other messages on the SYSLOG or JOBLOG that may be helpful? -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Robert Pelletier Sent: Thursday, February 23, 2006 11:27 AM To: IBM-MAIN@BAMA.UA.EDU 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 Can anyone offer suggestions as to why work is not working. We are OS390 V2R10 and the program is written LE. I do not have the source because it was given to us by the agency we feed the data too. In advance thanks all. Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
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: IBM-MAIN@BAMA.UA.EDU 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: IBM-MAIN@BAMA.UA.EDU 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Maybe you need to see if you can identify the module containing the failing instruction, then look at the logic in that area if it is your app code. I'll bet on table overflow OR reading from a file after it's closed. Some of my apps people provide good examples of abends from time to time -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
From this and the other postings, I would have to say the failure is data related, not JCL. That is, you are going to have to approach this as a program bug. When the results are unpredictable, that includes test that appear to be successful. Not knowing anything about the program, the messages look to point to an input routine. Perhaps a read past end of file, a read of a file that did not open correctly, a too large/small record, a bogus record, or some such. But nothing to point to problems with the JCL. Sorry. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Robert Pelletier Sent: Thursday, February 23, 2006 12:41 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used This is all I found: IEF450I TRAM1SFA STEP02 - ABEND=S0C4 U REASON=0004 CEE3204S The system detected a protection exception (System Completion Code=0C4) From entry point EAFile::readNextLine() at compile unit offset +008 CEE3DMP V2 R10.0: Condition processing resulted in the unhandled condition. CEE3204S The system detected a protection exception (System Completion Code=0C4) From entry point EAFile::readNextLine() at compile unit offset +008 CEE3DMP V2 R10.0: Condition processing resulted in the unhandled condition. Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut 860-257-4001 X382 -- 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
PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Could the problem be related to the dsns being the same as the ddnames? Debbie Mitchell Utica National Insurance Group /snip 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 /snip -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Do your public/storage volumes have different geometries? (That is, does the system select different blocksizes?) I notice that the files in question are RECFM=VB. A *very* long time ago, with a COBOL compiler that Zeus used in grade school, you had to be careful writing variable-length records (with embedded ODOs). Before performing a WRITE FROM you had to initialize the receiver's DEPENDING ON field, else the implied group move would incorrectly calculate the length of the receiving record. The reason I bring this up is that a program that overruns the logical end-of-record may or not S0C4, depending on blksize / blocking factor. Just something to think about. You said you didn't have access to source code, so all this is mere speculation. -- David Andrews A. Duda and Sons, Inc. [EMAIL PROTECTED] -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Robert, One thing you may want to ask, do you run any file buffering software (Performance Essential and others) 'under the covers'? I have seen '(un)predictable' S0C4's with them and the particular one we work with will handle temporary files different than permanent ones. If you do you may want to see if turn it off for that step helps your problem. Thanks, Fletch -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Robert Pelletier Sent: Thursday, February 23, 2006 12:27 PM To: IBM-MAIN@BAMA.UA.EDU 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 Can anyone offer suggestions as to why work is not working. We are OS390 V2R10 and the program is written LE. I do not have the source because it was given to us by the agency we feed the data too. In advance thanks all. Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
On Thu, 23 Feb 2006 13:53:42 -0500, Robert Pelletier [EMAIL PROTECTED] wrote: 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. Here's a unique idea. Add a SYSABEND DD card or better yet, set a SLIP for the abend and try and debug what is causing the abend (because it could be something else other than the application program). If you have no IPCS experience / skills, then send the dump to the code owner and see what they have to say about it. As a last resort, you could send it to IBM LE support. There have been IBM LE bugs that I have seen (lol). :-) Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America and Farmers Insurance Group mailto: [EMAIL PROTECTED] Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Thanks all. Going to try to get the source code. Not sure they will give it up. Thanks again. Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
As David Andrews mentioned it could be that the program tries to read after EOF. And I think You mentioned that with larger allocation it took a longer time to abend ? So maybe it is like this: - The program always reads one more time after EOF. - Sometimes the position after EOF is on the end of the block, sometimes not. - When allocated on physical disk, this doesn't matter. - But when allocated as a -dataset, it is somehow (?) allocated in virtual memory. - And when the extra read is done when positioned at the end of the block, it translates to a read at an invalid memory address. I'm not sure if this theory is applicable, but I have some experiences with reading outside of the last record and it's varying result depending on whence it was in- or outside of the (last) block. Thomas Berg == Robert Pelletier == wrote2006-02-23 21:40: Thanks all. Going to try to get the source code. Not sure they will give it up. Thanks again. Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Connecticut -- 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 -- __ Mundus Vult Decipi __ They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. - Benjamin Franklin -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Could the problem be related to the dsns being the same as the ddnames? That shouldn't matter. The programme knows the DDNAME (file name), not the DSNAME (file name). - -teD I’m an enthusiastic proselytiser of the universal panacea I believe in! -- 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
Re: PROTECTION EXCEPTION 0C4 - Job Doesn't Work When Dataset Used
Wow, I love this kind of problem. I ran the following JCL with IEFBR14: //NEWGUY1 DD DISP=(NEW,DELETE),SPACE=(TRK,1),DSN=TED066.TEST //NEWGUY2 DD DISP=(NEW,DELETE),SPACE=(TRK,1),DSN=TEST //NEWGUY3 DD DISP=(NEW,DELETE),SPACE=(TRK,1) The resulting allocations shown below differ in two ways: real DASD vs. VIO, and short vs. long (near max) data set name. I've seen cases where a program would not work with VIO data sets; usually an ISV product that was (or should have been!) documented as such. The length of the data set name may be significant if the application for some reason obtains the data set and stores it somewhere: the longer *generated* name may overlay some buffer or work area. IGD101I SMS ALLOCATED TO DDNAME (NEWGUY1 ) DSN (TED066.TEST ) STORCLAS (STANDARD) MGMTCLAS (STANDARD) DATACLAS (STAND1) VOL SER NOS= ARN030 IGD101I SMS ALLOCATED TO DDNAME (NEWGUY2 ) DSN (SYS06054.T203308.RA000.TESTALLO.TEST.H01) STORCLAS (STANDARD) MGMTCLAS () DATACLAS (STAND1) VOL SER NOS= VIO IGD101I SMS ALLOCATED TO DDNAME (NEWGUY3 ) DSN (SYS06054.T203308.RA000.TESTALLO.R0170562) STORCLAS (STANDARD) MGMTCLAS () DATACLAS (STAND1) VOL SER NOS= VIO . . JO.Skip Robinson Southern California Edison Company SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 02/23/2006 09:26:39 AM: 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 Can anyone offer suggestions as to why work is not working. We are OS390 V2R10 and the program is written LE. I do not have the source because it was given to us by the agency we feed the data too. In advance thanks all. -- 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
