Re: Monitoring for MSGW

[Paul Bailey <PabloMotte+Midrange@xxxxxxxxx>]

That sounds interesting. I'm not sure how RCVMSG would lock the QSYSOPR
queue, though. Do you mean use WAIT(*MAX) for the next message and process
every one that arrives?

(I'm on v6r1 and "Soon(TM)" to be on v7r1, if that makes a difference.)


On 22 September 2016 at 15:53, Rob Berendt <rob@xxxxxxxxx> wrote:

> Well, one could put a lock on QSYSOPR by doing a RCVMSG on it.  No CPU
> utilization until the message hits.
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.