Re: WRKACTJOB still a resource pig?

[Dan <dan27649@xxxxxxxxx>]

On Dec 28, 2007 12:33 PM, <rob@xxxxxxxxx> wrote:

> What are you using WRKACTJOB job for?  To see if a job, or jobs, are stuck
> in MSGW in QBATCH?  If so, then will WRKSBSJOB QBATCH work for you and get
> Mordac off of your back?


This production job is submitted by a special production profile, so I won't
get notified of any MSGW's or other messages that might tell me that
something is wrong.  But this particular job uses a third-party application
that does not have a lot of error handling built into it, so we have to
monitor for certain events in the job, and respond to them quickly.  If I
had my druthers, I'd write a special monitoring app just for this, but I
don't have my druthers anytime in the near future.

You might even be able to create a monitor in iNav to email you if a job
> is stuck in MSGW.


This is what I love about this list.  Someone offers a possible solution
that I never knew enough to consider!  Is this functionality built in to the
OS, "out of the box"?

- Dan