Comments on: Answer a monmsg from within CL?

By: tomliotta

tomliotta — Tue, 26 Apr 2011 00:06:12 +0000

…could i use something like this…

Probably not.

The message will be displayed as part of processing the CALL command. A reply will be required before the program moves on to the RCVMSG command. That is, by the time RCVMSG is executed, it will all be over. The reply will already be done.

If you can copy/paste a portion of a joblog that demonstrates the messaging, there is probably a good solution available. (And the most useful solution just might be the System Reply List.)

Tom

By: lotofbad

lotofbad — Sat, 23 Apr 2011 11:25:22 +0000

I looked at the message queue the message is coming from (I think) it says that it is *ext. With that said could i use something like this…

pgm

dcl VAR(&MSGKY) TYPE(*CHAR) LEN(6)

call mylib/pgm

RCVMSG MSGQ(*ext) MSGTYPE(*LAST) KEYVAR(&MSGKY)
SNDRPY MSGKEY(&MSGKY) MSGQ(*ext) RPY(‘I’) CCSID(65535)

endpgm

Thanks for are the support guys.

By: tomliotta

tomliotta — Fri, 22 Apr 2011 01:53:34 +0000

Note that an *INQ message can’t be monitored at all. MONMSG only reacts to *ESCAPE, *NOTIFY or *STATUS messages.

If it is an *INQ message, then it will depend on where it is sent among other possible things. But if it is an *INQ message that is generated because of an unhandled *ESCAPE message, then the answer will go to how to handle the *ESCAPE message in order to avoid the *INQ message from ever showing up.

Tom

By: tomliotta

tomliotta — Wed, 20 Apr 2011 22:32:33 +0000

Note that the System Reply List can affect any job that runs with the INQMSGRPY(*SYSRPYL) attribute set on and that you need to set it on for jobs that you want to use the System Reply List.

That is, it can affect an unintended job. And it won’t affect your intended job unless it is configured for it.

Tom

By: jc400it

jc400it — Wed, 20 Apr 2011 21:15:27 +0000

Hello Lotofbad, Try using the i’s Sytem Reply List to automatically reply the (i)gnore. The command is WRKRPYLE He is a sample Change Reply List Entry (CHGRPYLE) Type choices, press Enter. Sequence number . . . . . . . . > 99 1-9999 Message identifier . . . . . . . CPA7025 Character value, *SAME, *ANY Compare data: Comparison data . . . . . . . 'JRNL' Message data start position . 5 1-999, *SAME, *NONE Message reply . . . . . . . . . 'I' Additional Parameters By using this you don’t evening need to make any programming changes. I hope this will help. JC400IT

By: hmssl2k

hmssl2k — Wed, 20 Apr 2011 20:50:46 +0000

Why not just setup a System Reply List Entries, WRKRPYLE

By: tomliotta

tomliotta — Wed, 20 Apr 2011 19:17:35 +0000

It depends on what kind of message it is, though it sounds like either an *ESCAPE or an *INQ (inquiry) message. We should see the message details in order to know if and how the message might be handled automatically.

When the message displays and before you respond to it, move the cursor to the message text and press . When the message display is shown, press to see the message details. Copy/paste the message details back here. We should see at least the message ID, the message type, the from-program and the to-program from the details.

It’s likely that there will be a question or two about those details before an answer is reasonable.

Tom

By: gfprogrammer

gfprogrammer — Wed, 20 Apr 2011 16:57:02 +0000

Is the error message issued on the call to the program or in the program after it is called?