Re: COBOL/LE question
On Mon, 13 Feb 2017 17:50:22 -0600, Dale R. Smith wrote: > >http://www.computerworld.com/article/3163192/data-center/just-because-it-fails-doesnt-mean-its-a-failure.html > I had one of those, many years ago. We were trying to convert our programmers from HLASM to an ISV cross-assembler. One of our programmers resisted. He had a program that assembled with RC=0 on HLASM; RC=4 on the cross-assembler. I reviewed the code and spotted an unresolvable expression that HLASM overlooked and the cross-assembler reported properly. Went to SR on HLASM. Got APAR. Now both get RC=4. The programmer, fastidious about RC<>0, grudgingly changed his code. Software, this time. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL/LE question
On Mon, 13 Feb 2017 20:57:56 +, Pommier, Rex wrote: >All, > >Just to circle back and close the issue, I was "barking up the wrong tree" >with the IGZ0268W message. Turns out the driver program that was calling the >OS/VS COBOL program had a logic error in it that was calling the wrong program >with the wrong parameters. I don't know why/how it was working on the 1.13 >system, but a long time ago, the COBOL program that was initiating the abend >was replaced by another OS/VS COBOL program. Unfortunately the developer who >wrote the new COBOL program missed one of the calls in the driving ASM >program. Somehow it has chugged along all these years (obviously the COBOL >program being called at this one point didn't do anything important) until the >OS upgrade. IBM must have closed a hole in LE maintenance between 1.13 and >2.2 and so this logic error that was sliding past now bit us. Modifying the >ASM source to remove the broken call fixed the problem. Since there are other >OS/VS COBOL programs being called by this same ASM driver that are working >fine, it wasn't the warning message after all. > >Thanks again for all your suggestions and help. > >Rex http://www.computerworld.com/article/3163192/data-center/just-because-it-fails-doesnt-mean-its-a-failure.html -- Dale R. Smith -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL/LE question
All, Just to circle back and close the issue, I was "barking up the wrong tree" with the IGZ0268W message. Turns out the driver program that was calling the OS/VS COBOL program had a logic error in it that was calling the wrong program with the wrong parameters. I don't know why/how it was working on the 1.13 system, but a long time ago, the COBOL program that was initiating the abend was replaced by another OS/VS COBOL program. Unfortunately the developer who wrote the new COBOL program missed one of the calls in the driving ASM program. Somehow it has chugged along all these years (obviously the COBOL program being called at this one point didn't do anything important) until the OS upgrade. IBM must have closed a hole in LE maintenance between 1.13 and 2.2 and so this logic error that was sliding past now bit us. Modifying the ASM source to remove the broken call fixed the problem. Since there are other OS/VS COBOL programs being called by this same ASM driver that are working fine, it wasn't the warning message after all. Thanks again for all your suggestions and help. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex Sent: Wednesday, February 01, 2017 4:55 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question We're starting down that path. Management doesn't want to have to recompile things but I'm thinking we may need to do so just to see if that's the problem. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Beaver Sent: Wednesday, February 01, 2017 4:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question I have a simple question do you happen to have a the source modules that if you attempted to reassemble them and recompile them to see if that's the problem Sent from my iPhone Steve Beaver > On Feb 1, 2017, at 16:41, Pommier, Rex wrote: > > Hello all, > > We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into > an issue with our COBOL and LE environment. We are running COBOL 4.2. > Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM > introduced the warning message "IGZ0268W An invocation was made of OS/VS > COBOL program XXX." along with providing a usermod that can be installed > to suppress the message. Normally that is OK but we have an ancient load > module written partially in OS/VS COBOL and partially in assembler that has a > home-grown ESTAE routine attached to it. This program has consistently > failed spectacularly while testing it under 2.2. Here's the sequence of > events. > > 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED > <<<< 4 normal messages issued at start of run > 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING > > 13.04.12 JOB01549 +TRBCYCLE: LIMIT= 900.00 SECONDS EACH 001 > > 13.04.13 JOB01549 +TRBCYCLE: 20 ABENDS ALLOWED > > 13.06.37 JOB01549 +TRBCHDLR: U4038 ABEND TRAPPED FOR POLICY 1512345623 (LE) > <<<< first abend message > > $HASP375 DCD110 ESTIMATED LINES EXCEEDED (a bunch of these) > CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4087 TO DATA SET: > > IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO RRP.D032.T1306504.DCD110 > +CEE3797I LANGUAGE ENVIRONMENT HAS DYNAMICALLY CREATED A DUMP. > +CEE0374C CONDITION=IGZ0268W TOKEN=0001010C 49C9C7E9 0001 406 > WHILE RUNNING PROGRAM IGZCMSG WHICH STARTS AT 1687F3B0 > AT THE TIME OF INTERRUPT > PSW 0008 804340DA > GPR 0-3 0043D9A8 0043D668 0043D668 00433038 > GPR 4-7 0043D38C 0043D698 00433038 0043D658 > GPR 8-B 0042CED0 0042AB40 0045D050 9687F3B0 > GPR C-F 0042AC30 0043D490 804340DA 966F4958 > +CEE0374C CONDITION=IGZ0016W TOKEN=00010010 49C9C7E9 0002 407 > WHILE RUNNING PROGRAM UNKNOWN > AT THE TIME OF INTERRUPT > Hello all, > > We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into > an issue with our COBOL and LE environment. We are running COBOL 4.2. > Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM > introduced the warning message "IGZ0268W An invocation was made of OS/VS > COBOL program XXX." along with providing a usermod that can be instal
Re: COBOL/LE question
Rex, I sure would re-compile the Cobol programs. I have ran into issues but it was going backward. It was in regard to callable LE functions and what was supported... Scott On Thu, Feb 2, 2017 at 12:12 PM, Bill Woodger wrote: > The IGZ0268W is a warning message (no kidding). If your are using up to > Enterprise COBOL V4.2 (which you are), it is just a warning that some time > in the future (going to V5+, or perhaps with some future LE) you *will* > have a problem. If you are using V5+ (which you are not) it is a problem > right now. > > You have a different case from it just being COBOL. Your combined > COBOL/ASM was previously running non-destructively with LE. And now it > doesn't. > > First shot would be to recompile one COBOL program that uses the Asm, and > see if you then get cooperation. If not, someone has to visit with the Asm. > > If you are simply not allowed to recompile (cast-iron policy), then just > pack up and go home early. It is highly unlikely that any simple magic > exists to fix it in such a way that you need cease to wonder "OK, but what > the heck else could be going on while it 'apparently works (RC0)'. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL/LE question
The IGZ0268W is a warning message (no kidding). If your are using up to Enterprise COBOL V4.2 (which you are), it is just a warning that some time in the future (going to V5+, or perhaps with some future LE) you *will* have a problem. If you are using V5+ (which you are not) it is a problem right now. You have a different case from it just being COBOL. Your combined COBOL/ASM was previously running non-destructively with LE. And now it doesn't. First shot would be to recompile one COBOL program that uses the Asm, and see if you then get cooperation. If not, someone has to visit with the Asm. If you are simply not allowed to recompile (cast-iron policy), then just pack up and go home early. It is highly unlikely that any simple magic exists to fix it in such a way that you need cease to wonder "OK, but what the heck else could be going on while it 'apparently works (RC0)'. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL/LE question
No I don't. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Beaver Sent: Thursday, February 02, 2017 9:56 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question You would not happen to have z/XDC to debug this mess? Steve -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex Sent: Thursday, February 2, 2017 9:15 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question Hi Kolusu, Thanks for the idea. Unfortunately it made no difference. The initial driver program being executed here is assembler which is calling COBOL programs. Looks like it is time to dig into an estae routine. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Sri h Kolusu Sent: Wednesday, February 01, 2017 5:30 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question Rex, I forgot to mention that DO NOT SET RTEREUS(ON) as default. Just set it for the particular job you are having problem with. Something like this //STEP0100 EXEC PGM=yourpgm,PARM='RTEREUS(ON)/any le parms if u have' Here are some old topics on migration https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/DFSpeCSKUog https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/_QnqYPU3eIk Thanks, Kolusu From: "Pommier, Rex" To: IBM-MAIN@LISTSERV.UA.EDU Date: 02/01/2017 03:41 PM Subject:COBOL/LE question Sent by:IBM Mainframe Discussion List Hello all, We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into an issue with our COBOL and LE environment. We are running COBOL 4.2. Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM introduced the warning message "IGZ0268W An invocation was made of OS/VS COBOL program XXX." along with providing a usermod that can be installed to suppress the message. Normally that is OK but we have an ancient load module written partially in OS/VS COBOL and partially in assembler that has a home-grown ESTAE routine attached to it. This program has consistently failed spectacularly while testing it under 2.2. Here's the sequence of events. 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED <<<< 4 normal messages issued at start of run 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING 13.04.12 JOB01549 +TRBCYCLE: LIMIT= 900.00 SECONDS EACH 001 13.04.13 JOB01549 +TRBCYCLE: 20 ABENDS ALLOWED 13.06.37 JOB01549 +TRBCHDLR: U4038 ABEND TRAPPED FOR POLICY 1512345623 (LE) <<<< first abend message $HASP375 DCD110 ESTIMATED LINES EXCEEDED (a bunch of these) CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4087 TO DATA SET: IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO RRP.D032.T1306504.DCD110 +CEE3797I LANGUAGE ENVIRONMENT HAS DYNAMICALLY CREATED A DUMP. +CEE0374C CONDITION=IGZ0268W TOKEN=0001010C 49C9C7E9 0001 406 WHILE RUNNING PROGRAM IGZCMSG WHICH STARTS AT 1687F3B0 AT THE TIME OF INTERRUPT PSW 0008 804340DA GPR 0-3 0043D9A8 0043D668 0043D668 00433038 GPR 4-7 0043D38C 0043D698 00433038 0043D658 GPR 8-B 0042CED0 0042AB40 0045D050 9687F3B0 GPR C-F 0042AC30 0043D490 804340DA 966F4958 +CEE0374C CONDITION=IGZ0016W TOKEN=00010010 49C9C7E9 0002 407 WHILE RUNNING PROGRAM UNKNOWN AT THE TIME OF INTERRUPT PSW 0008 804340DA GPR 0-3 00441DE0 00441AA0 00441AA0 00433038 GPR 4-7 0044187C 00441AD0 00433038 00441A90 GPR 8-B 0042CED0 0008 0045D050 9687F3B0 GPR C-F 0042AC30 004418C8 804340DA 966F4958 FLT 0-2 49310F59C000 4E00030869B8 FLT 4-6 4E025368 IEA995I SYMPTOM DUMP OUTPUT 417 USER COMPLETION CODE=4087 REASON CODE= TIME=13.06.50 SEQ=00312 CPU= ASID=0045 PSW AT TIME OF ERROR 078D1000 966A5806 ILC 2 INTC 0D ACTIVE LOAD MODULE ADDRESS=1660D410 OFFSET=000983F6 NAME=CEEPLPKA DATA AT PSW 166A5800 - 00181610 0A0DA7F4 001C1811 GR 0: 8400 1: 84000FF7 2: 3: 00433038 4: 166E8398 5: 166E8A34 6: 00429358 7: 166A57CA 8: 8000 9: 00443EC6 A: 0001 B: 966A5728 C: 0042AC30 D: 00441EC8 E: 8043404E F: END OF SYMPTOM DUMP I'm not asking anybody to chase the dumps for me or anything like that, just wondering if anybody has had issues like this while migrating to 2.2. I added a STEPLIB to the job step to point to the 1.13 SCEERUN and SCEERUN2 libraries and the program runs fine. I've tried it with and without the USERMOD designed to suppress the warning message about OS/VS COBOL to no avail. To make it even more bizarre, I even went
Re: COBOL/LE question
You would not happen to have z/XDC to debug this mess? Steve -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex Sent: Thursday, February 2, 2017 9:15 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question Hi Kolusu, Thanks for the idea. Unfortunately it made no difference. The initial driver program being executed here is assembler which is calling COBOL programs. Looks like it is time to dig into an estae routine. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Sri h Kolusu Sent: Wednesday, February 01, 2017 5:30 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question Rex, I forgot to mention that DO NOT SET RTEREUS(ON) as default. Just set it for the particular job you are having problem with. Something like this //STEP0100 EXEC PGM=yourpgm,PARM='RTEREUS(ON)/any le parms if u have' Here are some old topics on migration https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/DFSpeCSKUog https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/_QnqYPU3eIk Thanks, Kolusu From: "Pommier, Rex" To: IBM-MAIN@LISTSERV.UA.EDU Date: 02/01/2017 03:41 PM Subject:COBOL/LE question Sent by:IBM Mainframe Discussion List Hello all, We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into an issue with our COBOL and LE environment. We are running COBOL 4.2. Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM introduced the warning message "IGZ0268W An invocation was made of OS/VS COBOL program XXX." along with providing a usermod that can be installed to suppress the message. Normally that is OK but we have an ancient load module written partially in OS/VS COBOL and partially in assembler that has a home-grown ESTAE routine attached to it. This program has consistently failed spectacularly while testing it under 2.2. Here's the sequence of events. 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED <<<< 4 normal messages issued at start of run 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING 13.04.12 JOB01549 +TRBCYCLE: LIMIT= 900.00 SECONDS EACH 001 13.04.13 JOB01549 +TRBCYCLE: 20 ABENDS ALLOWED 13.06.37 JOB01549 +TRBCHDLR: U4038 ABEND TRAPPED FOR POLICY 1512345623 (LE) <<<< first abend message $HASP375 DCD110 ESTIMATED LINES EXCEEDED (a bunch of these) CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4087 TO DATA SET: IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO RRP.D032.T1306504.DCD110 +CEE3797I LANGUAGE ENVIRONMENT HAS DYNAMICALLY CREATED A DUMP. +CEE0374C CONDITION=IGZ0268W TOKEN=0001010C 49C9C7E9 0001 406 WHILE RUNNING PROGRAM IGZCMSG WHICH STARTS AT 1687F3B0 AT THE TIME OF INTERRUPT PSW 0008 804340DA GPR 0-3 0043D9A8 0043D668 0043D668 00433038 GPR 4-7 0043D38C 0043D698 00433038 0043D658 GPR 8-B 0042CED0 0042AB40 0045D050 9687F3B0 GPR C-F 0042AC30 0043D490 804340DA 966F4958 +CEE0374C CONDITION=IGZ0016W TOKEN=00010010 49C9C7E9 0002 407 WHILE RUNNING PROGRAM UNKNOWN AT THE TIME OF INTERRUPT PSW 0008 804340DA GPR 0-3 00441DE0 00441AA0 00441AA0 00433038 GPR 4-7 0044187C 00441AD0 00433038 00441A90 GPR 8-B 0042CED0 0008 0045D050 9687F3B0 GPR C-F 0042AC30 004418C8 804340DA 966F4958 FLT 0-2 49310F59C000 4E00030869B8 FLT 4-6 4E025368 IEA995I SYMPTOM DUMP OUTPUT 417 USER COMPLETION CODE=4087 REASON CODE= TIME=13.06.50 SEQ=00312 CPU= ASID=0045 PSW AT TIME OF ERROR 078D1000 966A5806 ILC 2 INTC 0D ACTIVE LOAD MODULE ADDRESS=1660D410 OFFSET=000983F6 NAME=CEEPLPKA DATA AT PSW 166A5800 - 00181610 0A0DA7F4 001C1811 GR 0: 8400 1: 84000FF7 2: 3: 00433038 4: 166E8398 5: 166E8A34 6: 00429358 7: 166A57CA 8: 8000 9: 00443EC6 A: 0001 B: 966A5728 C: 0042AC30 D: 00441EC8 E: 8043404E F: END OF SYMPTOM DUMP I'm not asking anybody to chase the dumps for me or anything like that, just wondering if anybody has had issues like this while migrating to 2.2. I added a STEPLIB to the job step to point to the 1.13 SCEERUN and SCEERUN2 libraries and the program runs fine. I've tried it with and without the USERMOD designed to suppress the warning message about OS/VS COBOL to no avail. To make it even more bizarre, I even went so far as to try it in my 1.13 system with a STEPLIB pointing to the 2.2 SCEERUN and SCEERUN2 libraries to try to get it to fail and it didn't. Am I looking at the wrong place by looking at this IGZ0268W message? Am I missing something obvious? Thanks
Re: COBOL/LE question
Hi Kolusu, Thanks for the idea. Unfortunately it made no difference. The initial driver program being executed here is assembler which is calling COBOL programs. Looks like it is time to dig into an estae routine. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Sri h Kolusu Sent: Wednesday, February 01, 2017 5:30 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question Rex, I forgot to mention that DO NOT SET RTEREUS(ON) as default. Just set it for the particular job you are having problem with. Something like this //STEP0100 EXEC PGM=yourpgm,PARM='RTEREUS(ON)/any le parms if u have' Here are some old topics on migration https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/DFSpeCSKUog https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/_QnqYPU3eIk Thanks, Kolusu From: "Pommier, Rex" To: IBM-MAIN@LISTSERV.UA.EDU Date: 02/01/2017 03:41 PM Subject:COBOL/LE question Sent by:IBM Mainframe Discussion List Hello all, We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into an issue with our COBOL and LE environment. We are running COBOL 4.2. Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM introduced the warning message "IGZ0268W An invocation was made of OS/VS COBOL program XXX." along with providing a usermod that can be installed to suppress the message. Normally that is OK but we have an ancient load module written partially in OS/VS COBOL and partially in assembler that has a home-grown ESTAE routine attached to it. This program has consistently failed spectacularly while testing it under 2.2. Here's the sequence of events. 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED <<<< 4 normal messages issued at start of run 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING 13.04.12 JOB01549 +TRBCYCLE: LIMIT= 900.00 SECONDS EACH 001 13.04.13 JOB01549 +TRBCYCLE: 20 ABENDS ALLOWED 13.06.37 JOB01549 +TRBCHDLR: U4038 ABEND TRAPPED FOR POLICY 1512345623 (LE) <<<< first abend message $HASP375 DCD110 ESTIMATED LINES EXCEEDED (a bunch of these) CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4087 TO DATA SET: IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO RRP.D032.T1306504.DCD110 +CEE3797I LANGUAGE ENVIRONMENT HAS DYNAMICALLY CREATED A DUMP. +CEE0374C CONDITION=IGZ0268W TOKEN=0001010C 49C9C7E9 0001 406 WHILE RUNNING PROGRAM IGZCMSG WHICH STARTS AT 1687F3B0 AT THE TIME OF INTERRUPT PSW 0008 804340DA GPR 0-3 0043D9A8 0043D668 0043D668 00433038 GPR 4-7 0043D38C 0043D698 00433038 0043D658 GPR 8-B 0042CED0 0042AB40 0045D050 9687F3B0 GPR C-F 0042AC30 0043D490 804340DA 966F4958 +CEE0374C CONDITION=IGZ0016W TOKEN=00010010 49C9C7E9 0002 407 WHILE RUNNING PROGRAM UNKNOWN AT THE TIME OF INTERRUPT PSW 0008 804340DA GPR 0-3 00441DE0 00441AA0 00441AA0 00433038 GPR 4-7 0044187C 00441AD0 00433038 00441A90 GPR 8-B 0042CED0 0008 0045D050 9687F3B0 GPR C-F 0042AC30 004418C8 804340DA 966F4958 FLT 0-2 49310F59C000 4E00030869B8 FLT 4-6 4E025368 IEA995I SYMPTOM DUMP OUTPUT 417 USER COMPLETION CODE=4087 REASON CODE= TIME=13.06.50 SEQ=00312 CPU= ASID=0045 PSW AT TIME OF ERROR 078D1000 966A5806 ILC 2 INTC 0D ACTIVE LOAD MODULE ADDRESS=1660D410 OFFSET=000983F6 NAME=CEEPLPKA DATA AT PSW 166A5800 - 00181610 0A0DA7F4 001C1811 GR 0: 8400 1: 84000FF7 2: 3: 00433038 4: 166E8398 5: 166E8A34 6: 00429358 7: 166A57CA 8: 8000 9: 00443EC6 A: 0001 B: 966A5728 C: 0042AC30 D: 00441EC8 E: 8043404E F: END OF SYMPTOM DUMP I'm not asking anybody to chase the dumps for me or anything like that, just wondering if anybody has had issues like this while migrating to 2.2. I added a STEPLIB to the job step to point to the 1.13 SCEERUN and SCEERUN2 libraries and the program runs fine. I've tried it with and without the USERMOD designed to suppress the warning message about OS/VS COBOL to no avail. To make it even more bizarre, I even went so far as to try it in my 1.13 system with a STEPLIB pointing to the 2.2 SCEERUN and SCEERUN2 libraries to try to get it to fail and it didn't. Am I looking at the wrong place by looking at this IGZ0268W message? Am I missing something obvious? Thanks for any advice you may be able to offer. Rex The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delive
Re: COBOL/LE question
Rex, I forgot to mention that DO NOT SET RTEREUS(ON) as default. Just set it for the particular job you are having problem with. Something like this //STEP0100 EXEC PGM=yourpgm,PARM='RTEREUS(ON)/any le parms if u have' Here are some old topics on migration https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/DFSpeCSKUog https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/_QnqYPU3eIk Thanks, Kolusu From: "Pommier, Rex" To: IBM-MAIN@LISTSERV.UA.EDU Date: 02/01/2017 03:41 PM Subject:COBOL/LE question Sent by:IBM Mainframe Discussion List Hello all, We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into an issue with our COBOL and LE environment. We are running COBOL 4.2. Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM introduced the warning message "IGZ0268W An invocation was made of OS/VS COBOL program XXX." along with providing a usermod that can be installed to suppress the message. Normally that is OK but we have an ancient load module written partially in OS/VS COBOL and partially in assembler that has a home-grown ESTAE routine attached to it. This program has consistently failed spectacularly while testing it under 2.2. Here's the sequence of events. 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED 4 normal messages issued at start of run 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING 13.04.12 JOB01549 +TRBCYCLE: LIMIT= 900.00 SECONDS EACH 001 13.04.13 JOB01549 +TRBCYCLE: 20 ABENDS ALLOWED 13.06.37 JOB01549 +TRBCHDLR: U4038 ABEND TRAPPED FOR POLICY 1512345623 (LE) first abend message $HASP375 DCD110 ESTIMATED LINES EXCEEDED (a bunch of these) CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4087 TO DATA SET: IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO RRP.D032.T1306504.DCD110 +CEE3797I LANGUAGE ENVIRONMENT HAS DYNAMICALLY CREATED A DUMP. +CEE0374C CONDITION=IGZ0268W TOKEN=0001010C 49C9C7E9 0001 406 WHILE RUNNING PROGRAM IGZCMSG WHICH STARTS AT 1687F3B0 AT THE TIME OF INTERRUPT PSW 0008 804340DA GPR 0-3 0043D9A8 0043D668 0043D668 00433038 GPR 4-7 0043D38C 0043D698 00433038 0043D658 GPR 8-B 0042CED0 0042AB40 0045D050 9687F3B0 GPR C-F 0042AC30 0043D490 804340DA 966F4958 +CEE0374C CONDITION=IGZ0016W TOKEN=00010010 49C9C7E9 0002 407 WHILE RUNNING PROGRAM UNKNOWN AT THE TIME OF INTERRUPT PSW 0008 804340DA GPR 0-3 00441DE0 00441AA0 00441AA0 00433038 GPR 4-7 0044187C 00441AD0 00433038 00441A90 GPR 8-B 0042CED0 0008 0045D050 9687F3B0 GPR C-F 0042AC30 004418C8 804340DA 966F4958 FLT 0-2 49310F59C000 4E00030869B8 FLT 4-6 4E025368 IEA995I SYMPTOM DUMP OUTPUT 417 USER COMPLETION CODE=4087 REASON CODE= TIME=13.06.50 SEQ=00312 CPU= ASID=0045 PSW AT TIME OF ERROR 078D1000 966A5806 ILC 2 INTC 0D ACTIVE LOAD MODULE ADDRESS=1660D410 OFFSET=000983F6 NAME=CEEPLPKA DATA AT PSW 166A5800 - 00181610 0A0DA7F4 001C1811 GR 0: 8400 1: 84000FF7 2: 3: 00433038 4: 166E8398 5: 166E8A34 6: 00429358 7: 166A57CA 8: 8000 9: 00443EC6 A: 0001 B: 966A5728 C: 0042AC30 D: 00441EC8 E: 8043404E F: END OF SYMPTOM DUMP I'm not asking anybody to chase the dumps for me or anything like that, just wondering if anybody has had issues like this while migrating to 2.2. I added a STEPLIB to the job step to point to the 1.13 SCEERUN and SCEERUN2 libraries and the program runs fine. I've tried it with and without the USERMOD designed to suppress the warning message about OS/VS COBOL to no avail. To make it even more bizarre, I even went so far as to try it in my 1.13 system with a STEPLIB pointing to the 2.2 SCEERUN and SCEERUN2 libraries to try to get it to fail and it didn't. Am I looking at the wrong place by looking at this IGZ0268W message? Am I missing something obvious? Thanks for any advice you may be able to offer. Rex The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscri
Re: COBOL/LE question
IGZ0268W means that OS/VS COBOL is trying to interface with COBOL 5. Which is a no-no. Thanks, Tom Savor Software Developer, Sr FRMS-SCM Fiserv -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL/LE question
The most common problem in a recovery routine is failure to restore registers properly. The older the code, the more likely you are to hit such a glitch. I once debugged a bizarre COBOL program error that was completely inexplicable. I set a SLIP trap for the 'first' error, which turned out to be a run of the mill S0C7 data problem. The program had an ancient assembler recovery routine that messed up the registers and took a wild branch into PLPA. My solution was to BR14 out the recovery routine rather than try to fix it. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Beaver Sent: Wednesday, February 01, 2017 3:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: COBOL/LE question i am guess the c/vs was nores nodynam and the asm90 is your real trouble maker Sent from my iPhone Steve Beaver > On Feb 1, 2017, at 16:58, Steve Beaver wrote: > > Rex OS VS call Wold to call Bob five is a big jump > > Sent from my iPhone > Steve Beaver > > >> On Feb 1, 2017, at 16:55, Pommier, Rex wrote: >> >> We're starting down that path. Management doesn't want to have to recompile >> things but I'm thinking we may need to do so just to see if that's the >> problem. >> >> Rex >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Steve Beaver >> Sent: Wednesday, February 01, 2017 4:54 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: COBOL/LE question >> >> I have a simple question do you happen to have a the source modules >> that if you attempted to reassemble them and recompile them to see if >> that's the problem >> >> Sent from my iPhone >> Steve Beaver >> >> >>> On Feb 1, 2017, at 16:41, Pommier, Rex wrote: >>> >>> Hello all, >>> >>> We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into >>> an issue with our COBOL and LE environment. We are running COBOL 4.2. >>> Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, >>> IBM introduced the warning message "IGZ0268W An invocation was made of >>> OS/VS COBOL program XXX." along with providing a usermod that can be >>> installed to suppress the message. Normally that is OK but we have an >>> ancient load module written partially in OS/VS COBOL and partially in >>> assembler that has a home-grown ESTAE routine attached to it. This program >>> has consistently failed spectacularly while testing it under 2.2. Here's >>> the sequence of events. >>> >>> 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED >>> <<<< 4 normal messages issued at start of run >>> 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING >>> >> We're starting down that path. Management doesn't want to have to recompile >> things but I'm thinking we may need to do so just to see if that's the >> problem. >> >> Rex >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Steve Beaver >> Sent: Wednesday, February 01, 2017 4:54 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: COBOL/LE question >> >> I have a simple question do you happen to have a the source modules >> that if you attempted to reassemble them and recompile them to see if >> that's the problem >> >> Sent from my iPhone >> Steve Beaver >> >> >>> On Feb 1, 2017, at 16:41, Pommier, Rex wrote: >>> >>> Hello all, >>> >>> We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into >>> an issue with our COBOL and LE environment. We are running COBOL 4.2. >>> Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, >>> IBM introduced the warning message "IGZ0268W An invocation was made of >>> OS/VS COBOL program XXX." along with providing a usermod that can be >>> installed to suppress the message. Normally that is OK but we have an >>> ancient load module written partially in OS/VS COBOL and partially in >>> assembler that has a home-grown ESTAE routine attached to it. This progr
Re: COBOL/LE question
i am guess the c/vs was nores nodynam and the asm90 is your real trouble maker Sent from my iPhone Steve Beaver > On Feb 1, 2017, at 16:58, Steve Beaver wrote: > > Rex OS VS call Wold to call Bob five is a big jump > > Sent from my iPhone > Steve Beaver > > >> On Feb 1, 2017, at 16:55, Pommier, Rex wrote: >> >> We're starting down that path. Management doesn't want to have to recompile >> things but I'm thinking we may need to do so just to see if that's the >> problem. >> >> Rex >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Steve Beaver >> Sent: Wednesday, February 01, 2017 4:54 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: COBOL/LE question >> >> I have a simple question do you happen to have a the source modules that if >> you attempted to reassemble them and recompile them to see if that's the >> problem >> >> Sent from my iPhone >> Steve Beaver >> >> >>> On Feb 1, 2017, at 16:41, Pommier, Rex wrote: >>> >>> Hello all, >>> >>> We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into >>> an issue with our COBOL and LE environment. We are running COBOL 4.2. >>> Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, >>> IBM introduced the warning message "IGZ0268W An invocation was made of >>> OS/VS COBOL program XXX." along with providing a usermod that can be >>> installed to suppress the message. Normally that is OK but we have an >>> ancient load module written partially in OS/VS COBOL and partially in >>> assembler that has a home-grown ESTAE routine attached to it. This program >>> has consistently failed spectacularly while testing it under 2.2. Here's >>> the sequence of events. >>> >>> 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED >>> <<<< 4 normal messages issued at start of run >>> 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING >>> >> We're starting down that path. Management doesn't want to have to recompile >> things but I'm thinking we may need to do so just to see if that's the >> problem. >> >> Rex >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Steve Beaver >> Sent: Wednesday, February 01, 2017 4:54 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: COBOL/LE question >> >> I have a simple question do you happen to have a the source modules that if >> you attempted to reassemble them and recompile them to see if that's the >> problem >> >> Sent from my iPhone >> Steve Beaver >> >> >>> On Feb 1, 2017, at 16:41, Pommier, Rex wrote: >>> >>> Hello all, >>> >>> We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into >>> an issue with our COBOL and LE environment. We are running COBOL 4.2. >>> Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, >>> IBM introduced the warning message "IGZ0268W An invocation was made of >>> OS/VS COBOL program XXX." along with providing a usermod that can be >>> installed to suppress the message. Normally that is OK but we have an >>> ancient load module written partially in OS/VS COBOL and partially in >>> assembler that has a home-grown ESTAE routine attached to it. This program >>> has consistently failed spectacularly while testing it under 2.2. Here's >>> the sequence of events. >>> >>> 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED >>> <<<< 4 normal messages issued at start of run >>> 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING >>> >>> 13.04.12 JOB01549 +TRBCYCLE: LIMIT= 900.00 SECONDS EACH 001 >>> >>> 13.04.13 JOB01549 +TRBCYCLE: 20 ABENDS ALLOWED >>> >>> 13.06.37 JOB01549 +TRBCHDLR: U4038 ABEND TRAPPED FOR POLICY 1512345623 >>> (LE) <<<< first abend message >>> >>> $HASP375 DCD110 ESTIMATED LINES EXCEEDED (a bunch of these) >>> CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4087 TO DATA SE
Re: COBOL/LE question
Rex OS VS call Wold to call Bob five is a big jump Sent from my iPhone Steve Beaver > On Feb 1, 2017, at 16:55, Pommier, Rex wrote: > > We're starting down that path. Management doesn't want to have to recompile > things but I'm thinking we may need to do so just to see if that's the > problem. > > Rex > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Steve Beaver > Sent: Wednesday, February 01, 2017 4:54 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: COBOL/LE question > > I have a simple question do you happen to have a the source modules that if > you attempted to reassemble them and recompile them to see if that's the > problem > > Sent from my iPhone > Steve Beaver > > >> On Feb 1, 2017, at 16:41, Pommier, Rex wrote: >> >> Hello all, >> >> We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into >> an issue with our COBOL and LE environment. We are running COBOL 4.2. >> Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM >> introduced the warning message "IGZ0268W An invocation was made of OS/VS >> COBOL program XXX." along with providing a usermod that can be installed >> to suppress the message. Normally that is OK but we have an ancient load >> module written partially in OS/VS COBOL and partially in assembler that has >> a home-grown ESTAE routine attached to it. This program has consistently >> failed spectacularly while testing it under 2.2. Here's the sequence of >> events. >> >> 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED >> <<<< 4 normal messages issued at start of run >> 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING >> > We're starting down that path. Management doesn't want to have to recompile > things but I'm thinking we may need to do so just to see if that's the > problem. > > Rex > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Steve Beaver > Sent: Wednesday, February 01, 2017 4:54 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: COBOL/LE question > > I have a simple question do you happen to have a the source modules that if > you attempted to reassemble them and recompile them to see if that's the > problem > > Sent from my iPhone > Steve Beaver > > >> On Feb 1, 2017, at 16:41, Pommier, Rex wrote: >> >> Hello all, >> >> We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into >> an issue with our COBOL and LE environment. We are running COBOL 4.2. >> Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM >> introduced the warning message "IGZ0268W An invocation was made of OS/VS >> COBOL program XXX." along with providing a usermod that can be installed >> to suppress the message. Normally that is OK but we have an ancient load >> module written partially in OS/VS COBOL and partially in assembler that has >> a home-grown ESTAE routine attached to it. This program has consistently >> failed spectacularly while testing it under 2.2. Here's the sequence of >> events. >> >> 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED >> <<<< 4 normal messages issued at start of run >> 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING >> >> 13.04.12 JOB01549 +TRBCYCLE: LIMIT= 900.00 SECONDS EACH 001 >> >> 13.04.13 JOB01549 +TRBCYCLE: 20 ABENDS ALLOWED >> >> 13.06.37 JOB01549 +TRBCHDLR: U4038 ABEND TRAPPED FOR POLICY 1512345623 (LE) >> <<<< first abend message >> >> $HASP375 DCD110 ESTIMATED LINES EXCEEDED (a bunch of these) >> CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4087 TO DATA SET: >> >> IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO RRP.D032.T1306504.DCD110 >> +CEE3797I LANGUAGE ENVIRONMENT HAS DYNAMICALLY CREATED A DUMP. >> +CEE0374C CONDITION=IGZ0268W TOKEN=0001010C 49C9C7E9 0001 406 >> WHILE RUNNING PROGRAM IGZCMSG WHICH STARTS AT 1687F3B0 >> AT THE TIME OF INTERRUPT >> PSW 0008 804340DA >> GPR 0-3 0043D9A8 0043D668 0043D668 00433038
Re: COBOL/LE question
when all else fails you may have to do them one at a time as the problems crop up Sent from my iPhone Steve Beaver > On Feb 1, 2017, at 16:55, Pommier, Rex wrote: > > We're starting down that path. Management doesn't want to have to recompile > things but I'm thinking we may need to do so just to see if that's the > problem. > > Rex > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Steve Beaver > Sent: Wednesday, February 01, 2017 4:54 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: COBOL/LE question > > I have a simple question do you happen to have a the source modules that if > you attempted to reassemble them and recompile them to see if that's the > problem > > Sent from my iPhone > Steve Beaver > > >> On Feb 1, 2017, at 16:41, Pommier, Rex wrote: >> >> Hello all, >> >> We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into >> an issue with our COBOL and LE environment. We are running COBOL 4.2. >> Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM >> introduced the warning message "IGZ0268W An invocation was made of OS/VS >> COBOL program XXX." along with providing a usermod that can be installed >> to suppress the message. Normally that is OK but we have an ancient load >> module written partially in OS/VS COBOL and partially in assembler that has >> a home-grown ESTAE routine attached to it. This program has consistently >> failed spectacularly while testing it under 2.2. Here's the sequence of >> events. >> >> 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED >> <<<< 4 normal messages issued at start of run >> 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING >> -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL/LE question
We're starting down that path. Management doesn't want to have to recompile things but I'm thinking we may need to do so just to see if that's the problem. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Beaver Sent: Wednesday, February 01, 2017 4:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question I have a simple question do you happen to have a the source modules that if you attempted to reassemble them and recompile them to see if that's the problem Sent from my iPhone Steve Beaver > On Feb 1, 2017, at 16:41, Pommier, Rex wrote: > > Hello all, > > We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into > an issue with our COBOL and LE environment. We are running COBOL 4.2. > Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM > introduced the warning message "IGZ0268W An invocation was made of OS/VS > COBOL program XXX." along with providing a usermod that can be installed > to suppress the message. Normally that is OK but we have an ancient load > module written partially in OS/VS COBOL and partially in assembler that has a > home-grown ESTAE routine attached to it. This program has consistently > failed spectacularly while testing it under 2.2. Here's the sequence of > events. > > 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED > <<<< 4 normal messages issued at start of run > 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING > > 13.04.12 JOB01549 +TRBCYCLE: LIMIT= 900.00 SECONDS EACH 001 > > 13.04.13 JOB01549 +TRBCYCLE: 20 ABENDS ALLOWED > > 13.06.37 JOB01549 +TRBCHDLR: U4038 ABEND TRAPPED FOR POLICY 1512345623 (LE) > <<<< first abend message > > $HASP375 DCD110 ESTIMATED LINES EXCEEDED (a bunch of these) > CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4087 TO DATA SET: > > IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO RRP.D032.T1306504.DCD110 > +CEE3797I LANGUAGE ENVIRONMENT HAS DYNAMICALLY CREATED A DUMP. > +CEE0374C CONDITION=IGZ0268W TOKEN=0001010C 49C9C7E9 0001 406 > WHILE RUNNING PROGRAM IGZCMSG WHICH STARTS AT 1687F3B0 > AT THE TIME OF INTERRUPT > PSW 0008 804340DA > GPR 0-3 0043D9A8 0043D668 0043D668 00433038 > GPR 4-7 0043D38C 0043D698 00433038 0043D658 > GPR 8-B 0042CED0 0042AB40 0045D050 9687F3B0 > GPR C-F 0042AC30 0043D490 804340DA 966F4958 > +CEE0374C CONDITION=IGZ0016W TOKEN=00010010 49C9C7E9 0002 407 > WHILE RUNNING PROGRAM UNKNOWN > AT THE TIME OF INTERRUPT > Hello all, > > We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into > an issue with our COBOL and LE environment. We are running COBOL 4.2. > Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM > introduced the warning message "IGZ0268W An invocation was made of OS/VS > COBOL program XXX." along with providing a usermod that can be installed > to suppress the message. Normally that is OK but we have an ancient load > module written partially in OS/VS COBOL and partially in assembler that has a > home-grown ESTAE routine attached to it. This program has consistently > failed spectacularly while testing it under 2.2. Here's the sequence of > events. > > 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED > <<<< 4 normal messages issued at start of run > 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING > > 13.04.12 JOB01549 +TRBCYCLE: LIMIT= 900.00 SECONDS EACH 001 > > 13.04.13 JOB01549 +TRBCYCLE: 20 ABENDS ALLOWED > > 13.06.37 JOB01549 +TRBCHDLR: U4038 ABEND TRAPPED FOR POLICY 1512345623 (LE) > <<<< first abend message > > $HASP375 DCD110 ESTIMATED LINES EXCEEDED (a bunch of these) > CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4087 TO DATA SET: > > IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO RRP.D032.T1306504.DCD110 > +CEE3797I LANGUAGE ENVIRONMENT HAS DYNAMICALLY CREATED A DUMP. > +CEE0374C CONDITION=IGZ0268W TOKEN=0001010C 49C9C7E9 0001 406 > WHILE RUNNING PRO
Re: COBOL/LE question
I have a simple question do you happen to have a the source modules that if you attempted to reassemble them and recompile them to see if that's the problem Sent from my iPhone Steve Beaver > On Feb 1, 2017, at 16:41, Pommier, Rex wrote: > > Hello all, > > We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into > an issue with our COBOL and LE environment. We are running COBOL 4.2. > Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM > introduced the warning message "IGZ0268W An invocation was made of OS/VS > COBOL program XXX." along with providing a usermod that can be installed > to suppress the message. Normally that is OK but we have an ancient load > module written partially in OS/VS COBOL and partially in assembler that has a > home-grown ESTAE routine attached to it. This program has consistently > failed spectacularly while testing it under 2.2. Here's the sequence of > events. > > 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED > 4 normal messages issued at start of run > 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING > > 13.04.12 JOB01549 +TRBCYCLE: LIMIT= 900.00 SECONDS EACH 001 > > 13.04.13 JOB01549 +TRBCYCLE: 20 ABENDS ALLOWED > > 13.06.37 JOB01549 +TRBCHDLR: U4038 ABEND TRAPPED FOR POLICY 1512345623 (LE) > first abend message > > $HASP375 DCD110 ESTIMATED LINES EXCEEDED (a bunch of these) > CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4087 TO DATA SET: > > IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO RRP.D032.T1306504.DCD110 > +CEE3797I LANGUAGE ENVIRONMENT HAS DYNAMICALLY CREATED A DUMP. > +CEE0374C CONDITION=IGZ0268W TOKEN=0001010C 49C9C7E9 0001 406 > WHILE RUNNING PROGRAM IGZCMSG WHICH STARTS AT 1687F3B0 > AT THE TIME OF INTERRUPT > PSW 0008 804340DA > GPR 0-3 0043D9A8 0043D668 0043D668 00433038 > GPR 4-7 0043D38C 0043D698 00433038 0043D658 > GPR 8-B 0042CED0 0042AB40 0045D050 9687F3B0 > GPR C-F 0042AC30 0043D490 804340DA 966F4958 > +CEE0374C CONDITION=IGZ0016W TOKEN=00010010 49C9C7E9 0002 407 > WHILE RUNNING PROGRAM UNKNOWN > AT THE TIME OF INTERRUPT > Hello all, > > We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into > an issue with our COBOL and LE environment. We are running COBOL 4.2. > Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM > introduced the warning message "IGZ0268W An invocation was made of OS/VS > COBOL program XXX." along with providing a usermod that can be installed > to suppress the message. Normally that is OK but we have an ancient load > module written partially in OS/VS COBOL and partially in assembler that has a > home-grown ESTAE routine attached to it. This program has consistently > failed spectacularly while testing it under 2.2. Here's the sequence of > events. > > 13.04.12 JOB01549 +TRBCYCLE: ESTAE ISSUED/LE COND HDLR REGISTERED > 4 normal messages issued at start of run > 13.04.12 JOB01549 +TRBCYCLE: BEGIN PROCESSING > > 13.04.12 JOB01549 +TRBCYCLE: LIMIT= 900.00 SECONDS EACH 001 > > 13.04.13 JOB01549 +TRBCYCLE: 20 ABENDS ALLOWED > > 13.06.37 JOB01549 +TRBCHDLR: U4038 ABEND TRAPPED FOR POLICY 1512345623 (LE) > first abend message > > $HASP375 DCD110 ESTIMATED LINES EXCEEDED (a bunch of these) > CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4087 TO DATA SET: > > IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO RRP.D032.T1306504.DCD110 > +CEE3797I LANGUAGE ENVIRONMENT HAS DYNAMICALLY CREATED A DUMP. > +CEE0374C CONDITION=IGZ0268W TOKEN=0001010C 49C9C7E9 0001 406 > WHILE RUNNING PROGRAM IGZCMSG WHICH STARTS AT 1687F3B0 > AT THE TIME OF INTERRUPT > PSW 0008 804340DA > GPR 0-3 0043D9A8 0043D668 0043D668 00433038 > GPR 4-7 0043D38C 0043D698 00433038 0043D658 > GPR 8-B 0042CED0 0042AB40 0045D050 9687F3B0 > GPR C-F 0042AC30 0043D490 804340DA 966F4958 > +CEE0374C CONDITION=IGZ0016W TOKEN=00010010 49C9C7E9 0002 407 > WHILE RUNNING PROGRAM UNKNOWN > AT THE TIME OF INTERRUPT > PSW 0008
