We use <plug> some $STDLIST checking software from Gainsborough 
Software Limited.   Based in the UK - 'phone Adrian Partridge on 
+44 121 321 2555. </plug> 

>>> "Girard, Frank" <[log in to unmask]> 22/05/00 22:20:49 >>>
Is there any way to catch fatal errors in jobs that abort other than looking
at the standard list -- sometimes hours later?  Does MPEX have this
capability?  I'm looking to catch things like Missing Colon before command,
Program ended in an error state: remainder of job flushed, and any others
that happen because of an abnormal condition.  The job stream itself is not
being edited, the program is aborting on some data exception, or data base
problem, like a user that did not get aborted by abortjob, and had a
database that was being autoresized by Bradmark software.  I want to send an
E-mail through Kick Mail from the HP to our Operations center to notify them
of the problem.  The jobs don't get checked till 7:00 - 8:00 AM when the job
is usually done by.

Thanks

Frank Girard
J. Baker Inc.
[log in to unmask]