HP3000-L Archives

March 1995, Week 4

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:
Richard Gambrell <[log in to unmask]>
Reply To:
Richard Gambrell <[log in to unmask]>
Date:
Sun, 26 Mar 1995 12:52:36 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
According to Guy Smith:
>
> First, let me say that I would like to see each Workload Manager group
> obtain JLIMITs.  Having the two functions (management of resource use and
> threading of concurent jobs) based on the same abstraction (queue) is
> highly desirable from an administration standpoint.
>
I agree.
My prior comments about the Workload Manager were intended toward the
use and administration of the functions, not the implementation.
 
As an aside, I don't know if this has been done, but the Performance
Collection software's definition of a workgroup should also be derived from
the Workload Manager.
 
Controlling the numbers of related jobs that could run simultaneously
and the resources they could consume is a very attractive idea. Along
with the existing scheduling controls, this is very very useful.
 
My own view is that the Workload Manager and the multiple stream queue
functionality should be part of FOS. This would enhance the "value-added"
character of MPE vs Unix and it would better complete with OS/400 and VMS.
 
 
--
-- - - - Speaking for myself and not necessarily anybody else - - - - - -
Richard Gambrell        | Internet: [log in to unmask]
Mgr. Tech. Services     | POT:      504-483-7454     FAX: 504-482-1561
Xavier University of LA | Smail:    7325 Palmetto, New Orleans, LA 70125

ATOM RSS1 RSS2