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:
Tue, 16 Jan 2001 13:29:40 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (65 lines)
Sorry, TELL to a job doesn't work (gives you CIWARN 1627 and nothing shows
up in the $STDLIST). And having the info TELLOPed to the console is really
redundant, since console (input) commands, even if they are ALLOWed and
performed elsewhere, already get into the system logs.

No, I want what I want: replace the generic "JOB aborted by system
management. (CIERR 6027)" with "Job aborted by XXXXX,YYYYY.ZZZZZ (#Sxxxx) ON
LDEV# xxx.  (CIERR xxxx)" in the $STDLIST.

I know it takes a long time to get enhancements implemented, especially
minor ones like this that may not have a great cost-benefit ratio (in terms
of time invested vs. number of customers who would benefit). But then, could
this be shared-sourced or whatever that program is called? How would I go
about requesting that? Seems to me like a fairly simple thing to do. After
all, HP's already done something similar with STREAMED BY, all I want to do
is recycle the concept for ABORTJOB.

Patrick
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Patrick Santucci
HP e3000 Systems Administrator
Cornerstone Consolidated Services Group, Inc.

> -----Original Message-----
> From: Donna Garverick [SMTP:[log in to unmask]]
> Sent: Tuesday, January 16, 2001 12:30 pm
> To:   [log in to unmask]
> Subject:      Re: [HP3000-L] ABORTJOB Enhancement Idea
>
> Patrick Santucci wrote:
>
> > 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, my brain was operating on a stage-2 power level yesterday :-)
>
> i got to thinking about this.  while it would be greatly desireable for
> abortjob's native behavior to echo who's aborting what to the console and
> the
> $stdlist -- this could be fairly easily handled right now if jeff vance's
> abortjob udc were modified to do do a tellop and a tell.  granted the tell
> (to
> the job or session) may fail...but a tellop should always work.  if some
> bored
> soul wants to modify jeff's code and post it back, we could all take
> advantage
> of patrick's nifty idea.            - d
>
> --
> Donna Garverick     Sr. System Programmer
> 925-210-6631        [log in to unmask]
>
> "Unix _is_ user friendly.
> It's just very selective about who its friends are.
> And sometimes even best friends have fights."
>
> >>>MY opinions, not Longs Drug Stores'<<<

ATOM RSS1 RSS2