Re: backups on AS/400, objects

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

<snip>
Evan Harris
I find WRKACTJOB gives me a reasonable fix on this (on those days I feel
like playing nice). If you WRKACTJOB and look in the interactive susbystem,

take a command 11, column INT will indicate whether any activity is taking
place. You can watch the numbers change - 0 indicates no activity. I think
this indicates Interactions but I'm open to correction.
<endsnip>
Rob Berendt

==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.


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