Re: receiving message from QSYSOPR msgq

[Peter Dow <petercdow@xxxxxxxxx>]

Hi Arco,

You might want to try RCVMSG ... MSGTYPE(*LAST).  Right now you're 
receiving an *INFO message, and the message you're sending is an *INFO 
message, but probably not a CPF0968, so it loops, and receives the same 
*INFO message again.

hth,
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

On 5/10/2010 7:48 AM, Arco Simonse wrote:
> Hi list,
>
> First I have to say that I am not well experienced with the way the i's
> messaging system works. But digging around did not shine the light to me.
>
> I have arranged some CL code for a batch job to bring the system to
> restricted state and do a SAVSYS.
> All working well, I can intercept the message which tells that the system
> has reached restricted state, and continue to the save procedure.
>
> This code works:
>
>       ENDSBS     SBS(*ALL) +
>                    OPTION(*IMMED) +
>                    BCHTIMLMT(120)
>   WAIT:
>       RCVMSG     MSGQ(QSYSOPR) +
>                    MSGTYPE(*INFO) +
>                    RMV(*NO) +
>                    MSGID(&MSGID)
>       IF         COND(&MSGID *NE 'CPF0968') +
>                    THEN(DO)
>          DLYJOB     DLY(20)
>          GOTO       CMDLBL(WAIT)
>       ENDDO
>       /* And the SAVSYS goes on*/
>
> But before the ENDSBS I need to send an other message to the MSGQ of
> QSYSOPR. When I thus invoke for example:
>       SNDUSRMSG  MSG(&MYMSG) +
>                    MSGTYPE(*INFO) +
>                    TOMSGQ(*SYSOPR)
>
> And then the routine is no longer functioning. The WAIT loop then keeps
> running until the BCHTIMLMT has expired.
> So it seems to be caused by my sending of that before message to the msgq of
> QSYSOPR. But I don't understand why, and also cannot find a good solution
> for it.
> This is driving me nuts. I must be doing something wrong, but what?
>
> Thanks in advance,
> Arco Simonse
>
> --
>