HP3000-L Archives

February 1996, 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:
"Paul H. Christidis" <[log in to unmask]>
Reply To:
Date:
Wed, 14 Feb 1996 14:25:02 PST
Content-Type:
text/plain
Parts/Attachments:
text/plain (42 lines)
Well I knew the flood gates would open up again when this topic resurfaced.
 
I'm a little disappointed, though, that the default mapping was dropped for now.
In our shop there are two major applications running on our 3K: A Human
Resources system (home grown) and our financial (Third party + home grown
enhancements). In terms of batch jobs volume the financial system submits 3
times the number of jobs.
  What I was hoping to get out of this enhancement was the ability to create two
separate queues with different limits and cause any jobs submitted out of our HR
application (Production or Development) to go to one queue and anything
submitted out of our financial application (Production or Development) to go to
the other *without* having to make any source code changes.
 
  Mohan is indicating that default user mapping would involve much more work,
perhaps because he feels that the NEW/ALT/PURGE[ACCT|GROUP|USER] commands would
need to be involved.  Granted that he has not shut the door completely by saying
that the mapping is dropped for the time being, but I *really* would like to
have default queues at the account level at the first cut of the enhancement.
 
  I feel that such mapping could be achieved with out involving changes to any
other commands.  It could be handled in the same code that would address the
case where a queue is *not* specified in the *stream* command or the *Job* card.
 
For example:
 
        1.  The contents of a variable (HPACCOUNTQUE) could be used to determine
which job queue to use.  Said variable would contain 'SYSTEMQ' by default (or
whatever the system default will be) or it could be set by each site using
account level UDCs.
 
        2.  The existence of a file *or symbolic link* 'acctname.JOBQ.HPSPOOL'
would indicate which queue to be used as the default.   (Using this scheme in
combination with the latest proposal I would build a queue for our HR production
account 'HR.JOBQ.HPSPOOL' and a *link* 'HRDEV.JOBQ.HPSPOOL' that points to
'hr.jobq.hpspool' and *all* the jobs submitted from our HR and HRDEV accounts
would go into the same jobqueue)
 
 
Thanks again for the opportunity.
 
Paul Christidis

ATOM RSS1 RSS2