HP3000-L Archives

January 1996, Week 2

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:
Duane Percox <[log in to unmask]>
Reply To:
Duane Percox <[log in to unmask]>
Date:
Wed, 10 Jan 1996 14:06:21 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (56 lines)
My .02 worth:
 
1. In our application system each user may stream many different classes of
jobs based on their security settings. I want to control the queues using
the job card not the user because its the job not the user that defines what
load is being put on the system and what requirements for job execution are
needed.
 
2. In our applications system you don't necessarily need a different mpe
user for each unique application user. This makes tying job queues to mpe
users not workable for our application.
 
3. Tying job queues to mpe users will also make it tough for our
client/server apps which share one logon (batch job) user name/account.
These apps do stream jobs!
 
4. In our application we have very few *real jcl* files. They are really
skeleton files which are read to build real jcl on the fly with selection
criteria and user info plugged into the job card.
 
Given the above I believe the best approach that fits our needs is to have
it this way:
 
1. A default job queue that all jobs will go to if not otherwise instructed.
This will allow someone to install this new job queue stuff and operate as
always without having to do anything.
 
2. Allow mpe users to be associated with job queues as a default queue for
the user.
 
3. Allow the job card to contain something like: ;queue= to specify the queue.
 
4. Allow the stream command to have a ;queue= parm that overides the job card.
 
If the code assumes that 4 overides 3, 3 overides 2, 2 overides 1, then
logical order is maintained and everyone can have it the way they want.
 
 
Final comments:
 
-- Thanks to HP for asking!
 
-- I obviously disagree with their assumption about the changing of job cards.
   The job is the unit of work we are managing here, not the user. It is not
   possible to assume that a user is a good proxy for what a job requires. In my
   daily work I stream jobs that do compiles and I stream jobs that run reports.
   I do this all from the same mpe user. I need the job to define the queue, not
   the user.
 
 
Duane Percox  (QSS)
[log in to unmask] (415-306-1608, fax 415-365-2706)
http://www.aimnet.com/~qssnet/
 ftp://ftp.aimnet.com/pub/users/qssnet/
"The best way to have a good idea is to have a lot of ideas." -- Linus Pauling

ATOM RSS1 RSS2