>>> Mohan Das <[log in to unmask]>  1/10/96, 12:00pm >>>
 
>[snip]
 
> One of the underlying assumptions behind this proposal was that
> users/system administrators would not want to change all (or
> most) of the job scripts on their system to take advantage of the
> new feature. We wanted to provide a way of controlling the jobs
> on the system in a better way than is possible today, without
> having to change all the job scripts and UDC's. We need
> feedback from the customers whether this assumption is correct
> in the first place.
 
>[snip]
 
>>> John Schick <[log in to unmask]>  1/10/96, 03:34pm >>>
 
> Count me in as a customer who *strongly* disagrees with this
> assumption.  I will *gladly* edit my jobs and STREAM commands to
> achieve maximum flexibility in assigning jobs to queues.
> Automatically assigning job queues (whether by logon account or
> just about any other straight-forward criteria) doesn't cut it for
> me.
 
>John Schick
>Manager/Technical Support
>Times Mirror Higher Education Group
 
 
>>> Paul H. Christidis <[log in to unmask]>  1/10/96,
04:41pm >>>
 
> While I too would not hesitate to edit all my 'job cards' and
> 'stream' commands I do *not* discount the value of having default
> queues.  Many sites have third party software running their
> business with *no access* to the source code for making changes to
> the, application generated, 'job cards' and 'stream' commands.
>
> If multiple job queues were implemented along Gavin's ideas I would
> like the job queue evaluation hierarchy (when no queue name is
> specified in the JOB or STREAM commands) be:
>        1.  Place job in the queue with the same name as the account
name on the 'job card' of the stream file. (if one has been defined).
>        2.  Place job in the system default queue
($sysq|$hpqueue|...)
 
> Paul H. Christidis
 
 
Sorry, I came across a bit too strong in my first post.  I too see
that there would be plenty of value in a mechanism for assigning
default job queues.  I should have said "If the only mechanism for
assigning job queues was one automatically determined by the
operating system (based on logon account, for example) that won't cut
it for me".  There have been a number of suggestions in this thread
concerning mechanisms to give us the "best of both worlds"--default
queues with the option to override via JOB or STREAM parameters.  I
am fully supportive of that concept.  And I'm really enjoying this
thread!
 
John Schick