|
midrange.com
WRKACTJOB is a joke!
I have an experienced user who would use WRKACTJOB to ensure that everyone
was out. Then they would use WRKOBJLCK and find that there were still jobs
running in QINTER which held locks, yet didn't show up on WRKACTJOB.
Why do you think they call it wrkACTjob? There must be some level of
activity for it to show on WRKACTJOB.
A better choice is WRKSBSJOB. This command showed the jobs that WRKACTJOB
didn't show. And I am not talking about system tasks, like you see in
WRKSYSACT.
This is even documented by IBM in the help for WRKSYSACT:
It is possible for a job to not appear on the WRKACTJOB display even
though an active status is shown for the job on one of the following
displays:
o Work with Job (WRKJOB)
o Work with Subsystem Jobs (WRKSBSJOB)
o Work with Submitted Jobs (WRKSBMJOB)
o Work with User Jobs (WRKUSRJOB)
This is because a status indicator that is used to determine whether
a job is active in the job's internal structure indicates an active
status just before and just after the actual processing of the job.
Normally, the amount of time that a job is in this state is very
short, but the following conditions can make it longer:
...
Rob Berendt
==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.
Schmuel
<schmuel@bigfoot.co To: MIDRANGE-L@midrange.com
m> cc:
Sent by: Subject: IFACTIVE OCL glitch
?
owner-midrange-l@mi
drange.com
05/31/01 07:31 AM
Please respond to
MIDRANGE-L
Hi Midrange,
Running OCL (of course :-) we use the IFACTIVE command in some
procedures,
in the S36E environment type of situation..
Last night, in a program that runs every day and has never been a
problem..
the IFACTIVE-'ARINQB' (A/R Inquiry Program) answered yes to a user,
despite
our operations people making triply sure that WRKACTJOB did not show any
thing even remotely close to that running, as well as checking all the
users in
the shop visually, and I checked the jobs also when I came in to take the
running procedure out of its loop/wait state by cancelling it and jumping
over..
somewhere in the midst of all of this, the system stopped thinking the job
was running, tho clearly no such job was ended..... (I was testing)
Is there any possible known glitch that could hold that information in
the system
area even tho the job is de facto ended.. (perhaps related to running
through
Client Access and an NT server to the workstations) ...
It was quite strange, a tad disconcerting, not a big problem but
something I
could use a little idea on .. Thanks most excellent AS/400 list...
Steven in newyawk
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
