RE: Receiving *DIAG messages

midrange-l-request@xxxxxxxxxxxx wrote:

>   3. Re: Receiving *DIAG messages (Reeve)
>
>G, this code works fine for *EXCP messages when you use MSGQ(*PGMQ)
>MSGTYPE(*EXCP) (and *COMP messages too).  But those pesky *DIAG's are just
>out of my reach.

Reeve:

Since the code explicitly requests *DIAG, it doesn't seem likely that it could 
work for either *EXCP or *COMP. <g>

Even so, you might be right that a *DIAG is out of your reach. If it was sent 
to a particular *PGMQ, then the message can be out of reach if the program is 
out of the stack when you try RCVMSG. The message needs to be in a place that 
is accessible.

Perhaps you're trying to receive messages sent to a previously called program 
that's ended? Make sure the message is where you think it is. Maybe it was sent 
up the stack, maybe it's in *EXT. And maybe it's gone.

Tom Liotta

>On 5/5/06, Grizzly Malchow wrote:
>>
>> I haven't tested the code, but it might be a start.
>>
>> DCL        VAR(&KEYVAR) TYPE(*CHAR) LEN(4)
>> DCL        VAR(&MSGID) TYPE(*CHAR) LEN(7)
>> DCL        VAR(&SEV)    TYPE(*DEC) LEN(2 0)
>> DCL        VAR(&RTNTYP) TYPE(*CHAR) LEN(2)
>>
>> MSG:        RCVMSG     MSGQ(SOMEMSGQ) MSGTYPE(*DIAG) RMV(*NO) +
>>                       KEYVAR(&KEYVAR) MSGID(&MSGID) SEV(&SEV) +
>>                       RTNTYPE(&RTNTYP)
>>            IF         COND(&MSGID *EQ 'CPD32E7') THEN(DO SOMETHING)