Re: receiving message from QSYSOPR msgq

Chuck

I've found the technique of looping through message keys to be very effective. This has long been recommended by IBM. I've used it to bracket a process where messages can come from diverse sources. Article is entitled "Receiving Messages from the Joblog after the Program Is off the Callstack", number 28942837. Would that be useful in this scenario?

Vern

CRPence wrote:

Arco Simonse wrote:

I was not aware of the QWCRSSTS API and I'll take that further
for my program.

However, I see my assumption of the working of RCVMSG is bad. I thought that giving the MSGID as parameter to the RCVMSG would be
sufficient to receive the last message with that id.

I'll study that part again...

The MSGID() parameter of RCVMSG is a /return value/ only; i.e. the value of the variable &MSGID when a request is made to RCVMSG MSGQ(QSYSOPR) MSGTYPE(*INFO) RMV(*NO) MSGID(&MSGID) does not effect any /selection/ across the available informational messages.

Supposing the parameter could effect selection, then there would be little reason to follow that request with the condition logic of IF COND(&MSGID *NE 'CPF0968') THEN(DO), but if the effect of RCVMSG with selection could change the value, then the code should have done CHGVAR &MSGID 'CPF0968' before retry anyhow.

Regards, Chuck