Re: Monitoring issue - batch vs interactive

We have 5 STRWCHs monitoring about 20 key MSGs
Sending SMSs when such MSG occurs (using a mail to SMS service provider)
Works fine (rarely there are SNDSMTPEMM problems)

HTH
Gad

date: Mon, 16 Sep 2019 18:28:08 +0000
from: "Steinmetz, Paul via MIDRANGE-L" <midrange-l@xxxxxxxxxxxxxxxxxx>
subject: Monitoring issue - batch vs interactive

I created a few new Halcyon Level 2 QSYSOPR monitors for various issues.
What I discovered is that if the issue is run by an interactive job as
opposed to batch, the MSG goes to the interactive msgq, not QSYSOPR.
Thus, the monitor does not pick these up.

Halcyon support suggest monitoring all interactive joblogs to resolve this.
Not a good option, since this creates a huge performance issue (due to how
Halcyon coverts the interactive joblog to a temp disk file to do the
monitoring)
I have an open issue with their support on this from way back, asked if the
their joblog monitors could be implemented using WRKWCHs.
Temporary I created a WRKWCH for the joblog monitors.

Questions to the group
How are others monitoring various messages that would be caused by an
interactive job, not a batch job?
WRKWCH is one option, are there others?
If using a WRKWCH, should one WRKWCH handle multiple messages, or should
each message have its own WRKWCH?
What performance impact, if any, do WRKWCHs have on the system?


Thank You
_____
Paul Steinmetz
IBM i Systems Administrator