RE: Issue with SNDUSRMSG not breaking for response.

[qsrvbas@xxxxxxxxxxxx]

midrange-l-request@xxxxxxxxxxxx wrote:

>   3. Issue with SNDUSRMSG not breaking for response. (Imtiaz Ahmed)
>
>Can any one please let me know what I am missing here? I am using a
>simple CL program to send an inquiry message to QSYSOPR message queue.
>It sends the message but does not wait for a response. I ran the program
>in Debug and the &REPLY value returned is *N. I also tried with a MSGID
>CPF9898 but still the same results. I did check the message queue
>setting for QSYSOPR and the delivery option is set for *BREAK. Any help
>in this regards is most appreciated.
>
>>             PGM        PARM(&MSG)
>>             DCL        VAR(&RPLY) TYPE(*CHAR) LEN(1)
>>             DCL        VAR(&MSG)  TYPE(*CHAR) LEN(99)
>>             SNDUSRMSG  MSG(&MSG) VALUES(Y) MSGTYPE(*INQ) +
>>                          TOUSR(*SYSOPR) MSGRPY(&RPLY)
>>             ENDPGM

Imtiaz:

What's mostly missing is a bunch of info about the environment.

1. Is QSYSOPR signed on?
2. Is QSYSOPR *MSGQ allocated to any job?
3. If (2) is 'yes', then:
3a. What is INQMSGRPY() for the job?
3b. What is BRKMSG() for the job?
3c. What is QSYSOPR *MSGQ PGM()?

After that, do you see the message appear in QSYSOPR *MSGQ? Does it show *N as 
the reply there?

Maybe the problem is simply that you don't supply any  VALUES() parm on the 
SNDUSRMSG command or perhaps a DFT() parm. And since this "message" is coming 
in externally to your routine, your routine has no idea what values or default 
is appropriate.

Tom Liotta