James H. H. Lampert wrote:
I can't pass the value going from submitting program to submitted program as a command line parameter (it would show up in the joblog, and that would be "don't cross the streams" bad), and passing it through the same user queue I'd listen to for a response would short circuit the communication.
But environment variables can be passed to a submitted job, don't show up in the joblog, and are invisible from outside the job that created them, and any jobs it passed them to.
I obviously still need the *USRQ for the response, but I can use an environment variable to send the outbound message.
(And now I need some lunch and a nap. Yo-Yo Ma at the Bowl last night, and it was a very long concert. Didn't get to bed until 2.)
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.