Re: MONMSG/RCVMSG with QSH

I'm not sure what you're trying to accomplish. Personally, I tend to use QIBM_QSH_CMD_ESCAPE_MSG set to Y, and then just MONMSG QSH0005. That way, I only have to run my RCVMSG when I receive the QSH0005 and am not worried about getting other messages.

Your original question wasn't "Should I use QIBM_QSH_CMD_ESCAPE_MSG", but rather "how can this sample program from IBM possibly work?". I explained how it worked. Now that you know that, you can write yours differently, and use QIBM_QSH_CMD_ESCAPE_MSG to make it more robust :)


Michael Ryan wrote:

Hi Scott -

Right as always. :) I had environment variable QIBM_QSH_CMD_ESCAPE_MSG
set to 'Y' at a job level from some earlier testing. The QSH0005 was
issued as a *COMP message once that environment variable wasn't in
effect. I could then RCVMSG the QSH0005 message and query the return
code in the MSGID - works fine.

But an interesting (to me) issue now. I'm using environment variable
QIBM_QSH_CMD_OUTPUT and setting it to *NONE to suppress the command
output. But when I do that, the RCVMSG picks up the CPCA980
(Environment variable added) *COMP message. I currently have a RCVMSG
coded right after the ADDENVVAR to pick up the CPCA980 message, and
another RCVMSG right after the QSH command to pick up the QSH0005
message. Is there a better practice? Perhaps I should have one RCVMSG
and loop until I find the QSH0005?