@Walt, I would call the exact, full answer to that question proprietary, but a hopefully-adequate answer is "report it as-is to humans in human-readable form." In other words, I don't intend to base additional machine processing on it -- such as attempting to find it in the load library chain. So I'm pretty flexible -- I would not have a problem with a solution that was "arguable" for some scenarios. I am prepared to say "this is the answer we give to this question -- if you don't like it, well, sorry."
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Walt Farrell Sent: Monday, September 12, 2016 8:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Two running job program name discovery questions On Mon, 12 Sep 2016 07:24:13 -0700, Charles Mills <charl...@mcn.org> wrote: >1. Sorry -- I seem to have the feeling this has been covered before but >I was not able to find the discussion. How -- through control block >chasing or macros -- can a running program discover the name of the >jobstep program, the name specified in EXEC PGM= or a USS shell equivalent? > I'm curious what you intend to do with the name once you know it. I suspect there are a number of "solutions" to your question that won't be satisfactory for some usage scenarios. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
