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:
"Simonsen, Larry" <[log in to unmask]>
Reply To:
Simonsen, Larry
Date:
Tue, 16 Jan 2001 13:08:48 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (45 lines)
As with any request like this we must ask ourselves if the solution provided
by our supplier is adequate.  If not we must ask if what is given is
sufficient to build an appropriate system.  and in the end if needed ask our
supplier to improve the system.  there appear so many things which would be
nice to have done that at some point via the enhancement survey we
prioritized and hope that the items on the top of the total pile get done.

How have past items been completed and what priorities do we wish for the
next round?
I do not know as I have not reviewed past surveys and the coming years
results but it is hoped that the requests which get the highest votes are
truly the ones which are completed sooner.  To change these priorities
outside of the normal cycle leads to much project confusion.  It certainly
has in every project I have worked on.


-------------------------------------------------
Larry Simonsen                Phone: 801-489-2450
Flowserve Corporation     Fax: 801-491-1750
PO Box 2200                    http://www.Flowserve.com
Springville, UT 84663      e-mail: [log in to unmask]
-------------------------------------------------
All opinions expressed herein are my own and reflect, in no way, those of my
employer.

 -----Original Message-----
From:   [log in to unmask] [mailto:[log in to unmask]]
Sent:   Tuesday, January 16, 2001 1:01 PM
To:     [log in to unmask]
Subject:        Re: ABORTJOB Enhancement Idea

X-no-Archive:yes
This would break existing behaviors; third-party products like Nobix JobPak
et al, can read STDLists and will treat certain strings as indicating
failure or success. So this behavior needs either needs to append to the
existing message, which I don't think would work, or, after the existing
message for instance, say who aborted the job. Since users can abort their
own jobs, and account managers can abort any job in their accounts, and
system manager can abort anything, I can see where this info could be
useful. But expect your phone to start ringing...

Greg Stigers
http://www.cgiusa.com
But why doesn't a SELEQ=[JOBABORT=TRUE] list these?

ATOM RSS1 RSS2