Re: WRKWCH suggestions to replace HALCYON joblog monitor -- MIDRANGE-L

Pro/Con - Once a watch is active (STRWCH), a copy of the corresponding
watch program is "placed on deck", for lack of a better term - even if you
specify *WCHEVT . If you make a change to said program, you must end and
restart the watch to get your changes in place. Consider how much
"concurrent change" you might be doing in your watch designs....

On Tue, Sep 4, 2018 at 1:52 PM Dawn May <DawnMayiCan@xxxxxxxxxxx> wrote:

Paul,
The watch exit program receives the message file name and library, as well
as the message ID, so you could retrieve the message text with that
information (or any of the additional information provided via RTVMSG).

Regarding your other questions:
1) Separate watches or a single watch? 2) pros/cons
It doesn't matter from a technical perspective - it's more about how you
want to manage your watch programs. Do you want one exit program to handle
multiple messages? Or would you rather have things separate? Also, the
WRKWCH command can show you all the active watches on your system. If you
give the watch session a good ID, you can easily find your active watches.
This might also be a factor in how you want to structure your watches.
Assuming the watches are for very separate issues, I personally would set
up separate watches.

3) The performance impact of watches is minimal when the watch is
started. It does not matter if you are watching for messages in a message
queue, job log, or the history log - the overhead is almost zero until the
watched condition is matched. The overhead occurs when your exit program
is called; that overhead is the logic in your program, so you can control
what is done.

Dawn

Dawn May Consulting, LLC

________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of
Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Sent: Tuesday, September 4, 2018 1:32 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: WRKWCH suggestions to replace HALCYON joblog monitor

Is the message text for the Message ID that triggered the WRKWCH included
in the WRKWCH data?
I'm not finding it in of the WRKWCH variables.

https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fssw_ibm_i_61%2Fapis%2Fxwchevnt.htm&data=02%7C01%7C%7Cf3d70ba874fb416c8fbb08d6128c5ce1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636716791387532004&sdata=uW%2FaVs2Qdicw48wxCY9vF3HdCj1PNoeZTfoKLZwE%2B28%3D&reserved=0

If not, can it retrieved, with the variables?

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Friday, August 31, 2018 10:52 AM
To: 'Midrange Systems Technical Discussion'
Subject: WRKWCH suggestions to replace HALCYON joblog monitor

I need to improve the performance of my current Halcyon joblog monitors.
Currently, HALCYON dumps the joblog to a temp file, then scans the file
for desired message id.
From a functionality standpoint, works well, offers many select options.
From a performance standpoint, not acceptable, causing TB disk written/day.

Reviewed and tested various SQL using IBM system catalogs.
Unsuccessful.

It's been suggested from several in the group to use IBM WRKCH.
I've done a few over the years, works well.

I currently have 3 joblog monitors.
1) Info print writer - Incorrect Data was returned by mapping program -
PQT3073 PQT4154
2) Netserver Users Connection - job QZLSFILE - CPIAD12
3) SSL RXS_Transmit() encountered unexpected transmission error - KTA0203

Will be adding more.

Here's the main question.

1) Should a separate WRKWCH be created for each monitor or should they be
combined into a single WRKWCH.
2) Pros/cons.
3) Performance impact of the WRKWCH

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx

https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pencor.com%2F&data=02%7C01%7C%7Cf3d70ba874fb416c8fbb08d6128c5ce1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636716791387532004&sdata=sGjMxz7ZCsRQkND6xzbBk8CkA37k2gwj7HhieLE9dYo%3D&reserved=0

--
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:
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=02%7C01%7C%7Cf3d70ba874fb416c8fbb08d6128c5ce1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636716791387532004&sdata=ulTxerD7uAYDqpTKI2LyGyadqRqEivg%2BU4bZEvmJlUg%3D&reserved=0
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchive.midrange.com%2Fmidrange-l&data=02%7C01%7C%7Cf3d70ba874fb416c8fbb08d6128c5ce1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636716791387532004&sdata=o26lgZXA7uw5WkMBodNOfEtFWOlgN7A0%2FR55J05xlpY%3D&reserved=0
.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Famzn.to%2F2dEadiD&data=02%7C01%7C%7Cf3d70ba874fb416c8fbb08d6128c5ce1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636716791387532004&sdata=qZGFEouRpeYBxMHT1ZO8p%2FPFGaB8fQHrqF5udvIaugk%3D&reserved=0
--
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:
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=02%7C01%7C%7Cf3d70ba874fb416c8fbb08d6128c5ce1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636716791387532004&sdata=ulTxerD7uAYDqpTKI2LyGyadqRqEivg%2BU4bZEvmJlUg%3D&reserved=0
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchive.midrange.com%2Fmidrange-l&data=02%7C01%7C%7Cf3d70ba874fb416c8fbb08d6128c5ce1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636716791387532004&sdata=o26lgZXA7uw5WkMBodNOfEtFWOlgN7A0%2FR55J05xlpY%3D&reserved=0
.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Famzn.to%2F2dEadiD&data=02%7C01%7C%7Cf3d70ba874fb416c8fbb08d6128c5ce1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636716791387532004&sdata=qZGFEouRpeYBxMHT1ZO8p%2FPFGaB8fQHrqF5udvIaugk%3D&reserved=0
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD