S0C4 in IEBCOPY on z/OS 1.8
Wonder if anyone else has experienced this. We just rolled out z/OS 1.8 to our 1st two Test/Dev LPARs and we have encountered a problem. Our DB2 folks were copying a PDSE loadlib and got an IGW message in the IEBCOPY followed by recursive S0C4 and S0C1 abends. Essentially, until this is resolved, we are stopped dead in our tracks from rolling out z/OS 1.8 any further. -- 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: S0C4 in IEBCOPY on z/OS 1.8
For the archives Someone just wrote me about this post from June 2007 and I realized I never followed up in IBM-MAIN. On Fri, 29 Jun 2007 09:54:00 -0500, Mark Zelden <[EMAIL PROTECTED]> wrote: >On Fri, 29 Jun 2007 09:47:20 -0400, Petersen, Jim ><[EMAIL PROTECTED]> wrote: > >>Wonder if anyone else has experienced this. We just rolled out z/OS >>1.8 to our 1st two Test/Dev LPARs and we have encountered a problem. >>Our DB2 folks were copying a PDSE loadlib and got an IGW message in the >>IEBCOPY followed by recursive S0C4 and S0C1 abends. Essentially, until >>this is resolved, we are stopped dead in our tracks from rolling out >>z/OS 1.8 any further. >> > >Nope. But we rolled out to our biggest development environment this >past weekend. Even though we have several production LPARs running >1.8, this was the one I was most concerned about. Turns out I was right. >We have 2 open LE issues. One is an abend in a PL/I 2.3 program running >in CICS TS 2.3 (also failed in 3.1). Since it was holding up testing of a >regulatory change due to go in this weekend, I almost had to back out >on Tuesday. We were able to STEPLIB to the z/OS 1.6 version of >SCEERUN and use that in DFHRPL to get around the problem. IBM has >since provided a test fix that will get tested today. No APAR number yet, >but there will be one. > This first problem dragged on for a while between IBM LE and CICS support and eventually we found the problem to be caused by an ISV software product (eXpeditor). The vendor had a fix for the problem already but we didn't have it applied. >The other is a LE U4094 reason 18 in a DB2 program in batch. Still haven't >proved it's not an application issue, but the app folks say that pointing >to the production version of the program gets the same failure and this >worked last week. Unfortunately, there is no DB2 data sharing involved >here, so we can't run this on another LPAR in the sysplex that is still 1.6. > >We are still working on getting more diagnostic information for IBM (running >tests with changes to LE options) for the U4094 reason 18. > This was an application problem - actually a JCL problem. One of those cases where a hole was probably closed in LE. The abending program had defined an output file as VB LRECL=6110, BLKSIZE=6144. The output records were actually 458 bytes but the JCL had the DCB coded as DCB=(RECFM=F,LRECL=456,BLKSIZE=456). The programmer fixed the JCL to resolve the problem. -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS 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: S0C4 in IEBCOPY on z/OS 1.8
On Fri, 29 Jun 2007 09:47:20 -0400, Petersen, Jim <[EMAIL PROTECTED]> wrote: >Wonder if anyone else has experienced this. We just rolled out z/OS >1.8 to our 1st two Test/Dev LPARs and we have encountered a problem. >Our DB2 folks were copying a PDSE loadlib and got an IGW message in the >IEBCOPY followed by recursive S0C4 and S0C1 abends. Essentially, until >this is resolved, we are stopped dead in our tracks from rolling out >z/OS 1.8 any further. > Nope. But we rolled out to our biggest development environment this past weekend. Even though we have several production LPARs running 1.8, this was the one I was most concerned about. Turns out I was right. We have 2 open LE issues. One is an abend in a PL/I 2.3 program running in CICS TS 2.3 (also failed in 3.1). Since it was holding up testing of a regulatory change due to go in this weekend, I almost had to back out on Tuesday. We were able to STEPLIB to the z/OS 1.6 version of SCEERUN and use that in DFHRPL to get around the problem. IBM has since provided a test fix that will get tested today. No APAR number yet, but there will be one. The other is a LE U4094 reason 18 in a DB2 program in batch. Still haven't proved it's not an application issue, but the app folks say that pointing to the production version of the program gets the same failure and this worked last week. Unfortunately, there is no DB2 data sharing involved here, so we can't run this on another LPAR in the sysplex that is still 1.6. We are still working on getting more diagnostic information for IBM (running tests with changes to LE options) for the U4094 reason 18. My next set of roll outs (one more devl LPAR and another production LPAR) is not for a month, so as long as we can get a work around or fix to the 2nd LE issue by early next week, I won't have to back out 1.8 in this environment and we can continue our roll out schedule as planned. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group: G-ITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ 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: S0C4 in IEBCOPY on z/OS 1.8
Do you have PDSFAST, FDRREORG, or other product which replaces IEBCOPY ? You may need to re-install, or at least look into, the usermod or other "hook" that does provides the IEBCOPY entry point. Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 IBM Mainframe Discussion List wrote on 06/29/2007 09:47:20 AM: > Wonder if anyone else has experienced this. We just rolled out z/OS > 1.8 to our 1st two Test/Dev LPARs and we have encountered a problem. > Our DB2 folks were copying a PDSE loadlib and got an IGW message in the > IEBCOPY followed by recursive S0C4 and S0C1 abends. Essentially, until > this is resolved, we are stopped dead in our tracks from rolling out > z/OS 1.8 any further. > > -- > 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: S0C4 in IEBCOPY on z/OS 1.8
"Petersen, Jim" <[EMAIL PROTECTED]> wrote:Wonder if anyone else has experienced this. We just rolled out z/OS 1.8 to our 1st two Test/Dev LPARs and we have encountered a problem. Our DB2 folks were copying a PDSE loadlib and got an IGW message in the IEBCOPY followed by recursive S0C4 and S0C1 abends. Essentially, until this is resolved, we are stopped dead in our tracks from rolling out z/OS 1.8 any further. We had a broken PDSE after converting to Z/OS 1.8. The PDSE was broken by HSM partial space release. Symptoms were S0F4, S0C4 and S0C1 abends. We have opened an ETR with IBM and sent doc, but have not received a resolution. - Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. -- 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: S0C4 in IEBCOPY on z/OS 1.8
Turned out the person doing the upgrade had only applied HIPERs out of all the maintenance available in SMPPTS. We found a PTF from March which wasn't HIPER that fixed the problem. The person went back and applied all maint without error holds and that is what is going forward from here. ___ Jim Petersen MVS - Lead Systems Engineer Home Depot Technology Center 1300 Park Center Drive, Austin, TX 78753 www.homedepot.com email: [EMAIL PROTECTED] 512-977-2615 direct 512-977-2930 fax 210-859-9887 cell This message may contain confidential information. The information contained in this message and any attachments are intended solely for the use of the addressee(s) named above. If you are not the intended recipient, any disclosure, copying, distribution or other use of the contents of this message is strictly prohibited. If you have received this email in error, please notify the sender immediately by email and delete all copies of this message -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Craig Bakken Sent: Monday, July 02, 2007 9:48 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: S0C4 in IEBCOPY on z/OS 1.8 "Petersen, Jim" <[EMAIL PROTECTED]> wrote:Wonder if anyone else has experienced this. We just rolled out z/OS 1.8 to our 1st two Test/Dev LPARs and we have encountered a problem. Our DB2 folks were copying a PDSE loadlib and got an IGW message in the IEBCOPY followed by recursive S0C4 and S0C1 abends. Essentially, until this is resolved, we are stopped dead in our tracks from rolling out z/OS 1.8 any further. We had a broken PDSE after converting to Z/OS 1.8. The PDSE was broken by HSM partial space release. Symptoms were S0F4, S0C4 and S0C1 abends. We have opened an ETR with IBM and sent doc, but have not received a resolution. - Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. -- 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
