HP3000-L Archives

January 2001, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Patrick Santucci <[log in to unmask]>
Reply To:
Patrick Santucci <[log in to unmask]>
Date:
Mon, 15 Jan 2001 15:39:46 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
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.

ATOM RSS1 RSS2