Re: WRKACTJOB still a resource pig?

On 29/12/2007, at 4:46 AM, Dan wrote:

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.

If your primary reason for running WRKACTJOB is simply to see if/when MSGW occurs for this job (rather than actually monitoring real-time performance of the job) then you could change the SBMJOB for this job to specify MSGW(your-msg-queue) which will cause all such messages to appear on your nominated queue. Put this queue in break mode (or notify) and you'll know when a problem occurs.

As others have noted there are less intensive monitoring tools than WRKACTJOB however running a single instance will not have a noticeable impact on the system.

I'll refrain from commenting about your admin nazi except to point out there is a sub-culture who, for a fee, can deal with people like that.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------