On Mon, 13 Feb 2017 20:57:56 +0000, Pommier, Rex <[email protected]> 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 [email protected] with the message: INFO IBM-MAIN
