Re: STRWCH, WRKWCH, ENDWCH, WATCH-ing for conditions

Paul,

If the watch session is showing up as active on WRKWCH *STRWCH then it's
active. One item about your note worries me though. You indicate that the
watch ended with a code of 0. Is this from the CPI3999 message in QSYSOPR? A
code of 0 (x'00') is related to a wait timer expiring and that doesn't
happen with STRWCH. Time is specified with STRTRC, which is another animal
all together. Anytime a watch is ended you should find a message in QSYSOPR
related to the event.

As for finding the job, use WRKACTJOB JOB(ABC) where ABC is the session ID
you see on WRKWCH *STRWCH. To verify the watch is running simply send
whatever message it's watching for to the appropriate destination. To
monitor it's behavior I generally use STRSRVJOB on the watch job, STRDBG on
the watch exit program, fire off the message, and then step through the
code.

I too have experienced the problem of watches getting stuck in ENDING
(though not as frequently as I did a few years back), and can't suggest
anything to get rid of it.

Bruce

On Thu, Feb 4, 2010 at 11:13 AM, Musselman, Paul <
pmusselman@xxxxxxxxxxxxxxxx> wrote:

I've been trying to use the WATCH feature on our iSeries machine. It
seems simple enough-- use STRWCH to tell what to monitor and what
program to nudge when the condition is met.
.
When I STRWCH then go into WRKWCH the watches seem to be active-- Is
there any way to verify they really are? Someone mentioned that there
should be a job running on the system named the same as the Session ID.
When I look for those jobs they all seem to have ended with code 0, even
though WRKWCH thinks they're active.
.
As a result, my exit programs are (probably) not being called.
.
The exit program receives 3 and returns 1 parameter. When I call the
exit program myself from the command line it seems to do what I
expected.
.
If I try to end the watches from the WRKWCH screen they go to Status
ENDING. I've forced the joblogs to complete on some of these and
they're still showing ENDING. Any way to get rid of them??
.
We're at v5r4m5 with cume TL59104 applied.

Any hints?

<<Picture (Metafile)>>

Paul E Musselman
IT Technical Support
General Cable Corporation
(859) 572-8030
(859) 572-8477 (fax)
PMusselman@xxxxxxxxxxxxxxxx


--
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.