Re: S0C4 in IEBCOPY on z/OS 1.8

2008-03-26 Thread Mark Zelden
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 a

Re: S0C4 in IEBCOPY on z/OS 1.8

2007-07-18 Thread Petersen, Jim
t: 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

Re: S0C4 in IEBCOPY on z/OS 1.8

2007-07-02 Thread Craig Bakken
"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

Re: S0C4 in IEBCOPY on z/OS 1.8

2007-06-29 Thread Tim Hare
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 Mainfr

Re: S0C4 in IEBCOPY on z/OS 1.8

2007-06-29 Thread Mark Zelden
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 >IEBCOP

S0C4 in IEBCOPY on z/OS 1.8

2007-06-29 Thread Petersen, Jim
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