I use the following in MPEX with a command file called SHOWERRS:

RUN MPEX.PUB.VESOFT;PARM=1;INFO="SHOWOUT @[log in to unmask]@(SPOOL.JOBABORTED)"

It seems to catch most typical job abort situations.
            Tom Hula

"Girard, Frank" wrote:

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

--

        Tom Hula
        Victor S. Barnes Company
        616.361.7351  x173