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:
Mohan Das <[log in to unmask]>
Reply To:
Mohan Das <[log in to unmask]>
Date:
Thu, 11 Jan 1996 22:37:04 +0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (50 lines)
Chris Bartram writes:
 > Mohan (and group!);
 >
 >   I'd first like to add my appreciation for the opportunity to provide
 > feedback on this potential feature. I've been one of the backers of this
 > enhancement for quite a while, and would like to throw in my $.02 in hopes
 > that it might provide another viewpoint and perhaps something to think
 > about.
 
It sure does. Thanks Chris.
 
 >   Currently input spoolfiles are kept in IN.HPSPOOL (aka /HPSPOOL/IN). How
 > about simply(?) using HFS and allowing the creation of a hierarchy of
 > directories under /HPSPOOL/IN denoting additional input queues, perhaps
 > something like:
 >
 >   /HPSPOOL/IN           {contains default input spoolfiles as today}
 >   /HPSPOOL/IN/01MAINTQ  {contains input spoolfiles in MAINTQ queue}
 >   /HPSPOOL/IN/01PAYROLLQ{ditto PAYROLLQ queue}
 >   /HPSPOOL/IN/06DEV     {ditto DEV queue}
 >   /HPSPOOL/IN/08LOWPRI  {ditto LOWPRI queue}
 
I don't know if there will be any issues with the input spooler if we
change it this way. Will have to consider. Good suggestion,
nevertheless. But I didn't understand how those two digits came in ?
Do they signify some relative priority among the queues or something ?
 
 >   I like the idea of replacing the IN-dev in the showjob display with the
 > queue name, though it would have to be a non-default format since I'm sure
 > there are a lot of programs/command files depending on the showjob format
 > now. I also like the idea of a default queue for a user.account, but the
 > order of precedance should be:
 >  <default queue based on user.account in !job card>
 >  <jobq= parm on !job card>
 >  <jobq= parm on :STREAM command>
 >  <:ALTJOB ;jobq= specified by OP/SM>
 
Ok, another vote for "best-of-both-worlds" approach.
 
Thanks for responding.
 
mohan
--
 ============================================================================
Mohan Das K S                                   email: [log in to unmask]
HP India Software Centre                        Phone: 91-80-225-1554 x218
29, Cunningham Road                             Telnet:     408-847-1026
Bangalore - 560 001 INDIA                       Voice Mail: 408-447-4329
 ============================================================================

ATOM RSS1 RSS2