Jon,

No, my main goal, as stated, is to allow anyone who can read the $STDLIST to
know WHO aborted the job (and from what ldev), the same as they can now tell
WHO streamed it (and from what ldev). The stats are secondary and can
probably be gathered, as you said, in other ways. But it sure would make MPE
more user-friendly to have a meaningful, *informative* JOB ABORTED BY
message than a generic one, yes?

Patrick

> -----Original Message-----
> From: Jon Diercks [SMTP:[log in to unmask]]
> Sent: Tuesday, January 16, 2001 12:17 am
> To:   [log in to unmask]
> Subject:      Re: [HP3000-L] ABORTJOB Enhancement Idea
>
> Patrick--
>
> Interesting idea, but if your main goal is traceability and stats logging,
> I
> suggest that a quicker solution would be to create a system-level ABORTJOB
> UDC that uses TELLOP and/or "ECHO !HPDATE !HPUSER... >>logfile" to capture
> the data you want.
>
> --Jon
>
> On Mon, 15 Jan 2001 15:39:46 -0500, Patrick Santucci
> <[log in to unmask]>
> wrote:
>
> >Hi all,
> >
> >We had an incident over the weekend which prompted the following
> question:
> >
> >What would it take to have ABORTJOB display something similar to the
> STREAM
> >information in the $STDLIST, i.e. instead of the message:
> >
> >  JOB aborted by system management. (CIERR 6027)
> >
> >the $STDLIST would contain the message:
> >
> >  Job aborted by PJS,MGR.CINMAR (#S7625) ON LDEV# 104  (CIERR xxxx)
> >
> >This is basically the same format as the STREAMED BY info at the
> beginning
> >of the $STDLIST. Has anyone ever asked for this before? I know it's
> possible
> >to find console commands (like ABORTJOB) in the system logs (at least up
> >through 6.0, not sure about 6.5), I do it all the time. But this
> >functionality would really make it easy -- especially for an operator or
> a
> >plain old user -- to know who killed a job. It would also enable me, as a
> >system manager, to collect stats on this kind of activity, i.e. how often
> >are jobs being aborted, and by whom? And it seems like it wouldn't take a
> >lot of work on HP's part, though I could be wrong.
> >
> >What do you think?
> >
> >Patrick
> >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >Patrick Santucci
> >HP e3000 Systems Administrator
> >Cornerstone Consolidated Services Group, Inc.