Re: SNDPGMMSG and CPD2409

On 21-Dec-2011 14:13 , CRPence wrote:

On 21-Dec-2011 13:55 , rob@xxxxxxxxx wrote:

SNDPGMMSG MSGID(CPF9898) MSGF(QCPFMSG) MSGTYPE(*INQ) +
MSGDTA('Must select either *START or *STOP') +
TOPGMQ(*EXT) KEYVAR(&KEYVAR)
RCVMSG MSGTYPE(*RPY) MSGKEY(&KEYVAR) WAIT(*MAX) MSG(&MSGRPY)

When I compile this I am getting a CPD2409
Message . . . . : Specified message type not valid with specified
program message queue.
Cause . . . . . : ESCAPE and CMD messages cannot be sent to the
external program message queue (*EXT). INQUIRY messages cannot be
sent to program message queues other than (*EXT).
Recovery . . . : Change the message type or change the program
queue name.

SWAG: Use SNDUSRMSG instead, to define\enable some reply handling
capabilities [e.g. MSGRPY()], or choose a message identifier that has
reply handling capabilities [TYPE(), DFT() and VALUES() on ADDMSGD].

Hmmm, should have said WAG. Thinking more about that...

Even if the definition of the message identifier mattered, the noted condition being detected at compile-time versus run-time would seem amiss, except via prompt override processing. And actually tested [at v5r3], the result suggests no concern expressed by the compiler nor run-time, even though no reply setup exists in the CPF9898 message identifier; I originally responded having inferred "when I run after I compile" was implied.

However if the *CMD object being used [the *LIBL/SNDPGMMSG] were corrupted such that either MSGTYPE(*INQ) or TOPGMQ(*EXT) were not properly effecting the appropriate "To replacement value" as defined by the second element of the SPCVAL() or SNGVAL() [respectively], then the compile-time error might make sense; i.e. the DEP command effect as defined in the Command source could be fooled by corruption. For example if MSGTYPE(*INQ) were somehow being mapped to the equivalent of MSGTYPE(*ESCAPE), that diagnostic would make sense; though if that same command string were being edited in SEU, I would expect that same error would be manifest when syntax checking was enabled.

BTW, any idea what a "CMD" message is?

Regards, Chuck