As I recall, the system uses lots of watches. I don't have access to a
recent-enough system, so I wonder if there is an option to display
something - option 5, perhaps?
The documentation says these can be started from all kinds of traces.
I'm sure you can find info by pressing F1 on that screen.
Watches are very lightweight as to performance impact. The code stream
for sending messages has to check in any case whether there are watches
defined for that particular message - not knowing how it's implemented,
I can imagine an index or keyed file - doesn't matter, it'll be fast. So
adding watches has almost no effect on things, until there is a match,
of course, and you WANT that to happen.
The program specified is called as part of the job stream, so you will
have to wait for the called program to finish.
HTH
Vern
On 1/29/2013 9:10 AM, Gqcy wrote:
WOW (I didn't know we had such a thing as this...)
I did a WRKWCH, and I find a whole bunch of watches for
Major and minor codes...
How do I know 1) what they are for and 2) how/why they were created...
On 1/28/2013 8:14 PM, Glenn Gundermann wrote:
Kirk,
How about using "Message Watching"?
See the IBM commands for STRWCH, ENDWCH, and WKRWCH.
Also QSCSWCH and QSCEWCH APIs.
Bruce Vining presented at the TUG Meeting of Members and showed us a nice message watch exit program.
Yours truly,
Glenn Gundermann
-----Original Message-----
From: Kirk Goins<kirkgoins@xxxxxxxxx>
Sender: midrange-l-bounces@xxxxxxxxxxxx
Date: Mon, 28 Jan 2013 15:05:46
To: Midrange-L<midrange-l@xxxxxxxxxxxx>
Reply-To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>
Subject: Tracking Job Start and End Times with out coding each job
What are folks using these days to
#1 Track Job Start and End Times
#2 Job Completion Status
#3 Email when jobs hang or end abnormally?
