In that case I would contact the application group manager who owns that program and require them to schedule a change to the code to issue such a message only once (on first encountering the failure to locate that subroutine for execution) instead of blindly issuing the message every time.
IMHO that is just sloppy application coding that would not pass a peer review by me. It is trivially easy to set and test a flag to remember you already issued a given message already and bypass issuing it repeatedly, or a if little more sophistication is needed then maintain a count of times the message is issued and stop after some reasonable number of times (like 5 or 10). It might also require a table of "modules not found so far" with a separate flag and/or count for each unique program for which the message can be issued. In any case, absolutely trivial code to implement. BTDTGTTS. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Pommier, Rex Sent: Tuesday, April 25, 2017 1:26 PM To: [email protected] Subject: Re: program-name is unresolved/uncallable Unfortunately that is the complete message text. 10.54.31 JOB00450 +CKDCISLC IS UNRESOLVED/UNCALLABLE 10.54.31 JOB00450 +CKDCISLC IS UNRESOLVED/UNCALLABLE After I posted the question, I did some more digging and found the message text embedded in the program being executed. It appears now that it is something being generated by the application code, and not coming out of LE or from the binder as I initially suspected. Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Tuesday, April 25, 2017 11:42 AM To: [email protected] Subject: Re: program-name is unresolved/uncallable Could you provide the complete message and text? Easier to analyze that way. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Pommier, Rex > Sent: Tuesday, April 25, 2017 9:25 AM > To: [email protected] > Subject: program-name is unresolved/uncallable > > Hello, > > I have what I am suspecting will be an easy question but I haven't > found the answer yet. We have jobs that, while running, they will > display message "program-name IS UNRESOLVED/UNCALLABLE" multiple times > on the console as well as in the programmer's job log. Is the > elimination of these messages something that can be accomplished by a > binder parameter change or something else fairly uncomplicated? The > problem I'm dealing with is some of these programs generate this > message repeatedly for the same program name, and it occurs hundreds of > thousands of times in a single execution of a program. > > TIA, > > Rex > -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
