The lack of a message number would tend to indicate a "homegrown" message. I think nearly all IBM, and hopefully most 3rd-pary vendor, messages have a more-or-less standard sort of message id. "Local" programmers have a tendency I think to "just say something on the console/SYSPRINT."
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex Sent: Tuesday, April 25, 2017 10:26 AM To: IBM-MAIN@LISTSERV.UA.EDU 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. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
