Hah! We had a similar problem a few months ago at my current client; after upgrading to z/OS 2.2, a REXX/ISPF app started bombing. Many moons before I'd written an external exec and called it LOG; its only purpose is to send to the guy responsible for supporting that app (me, I mean) messages under certain circumstances so I could be apprised of problems. Turns out that a new library in 2.2 has a load module named LOG, which was intercepting the old invocation. Easy fix: I just renamed the REXX module and updated the code to use the new name. But it gave me a turn for a few days.
--- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* Jonny snorted. "You mean out among the decadence of the big worlds? Come on, Jame, you don't really believe that sophistication implies depravity, do you?" / "Of course not. But someone's bound to try and convince you that depravity implies sophistication." From _Cobra_ by Timothy Zahn */ -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Lars Höglund Sent: Tuesday, May 7, 2024 14:27 We had a program called JOBINFO (in allocated STEPLIB) Didn't realize that jobinfo = jobinfo() in a Rexx will trying to start, and maybe executing the cobolmodule We also have a Rexx called jobinfo, and that the one I want to execute. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
