>  > >   Each  user can be a  memeber  of only one Q at any point of
time.  Users
>  > >   without any specified Q membership will belong to the general
SYSJOBQ by
>  > >   default. If any Q is deleted,  all the  members of that queue
lose their
>  > >   membership and will belong to the general job queue.
>  >
>  > Buzzz. Sorry, this is completely useless.  Nobody that I know would
want to
>  > run their system this way.  What I want is the ability to have
different jobs
>
>  > from the same user submitted to different queues.  We will happily
go change
>  > the !JOB records to have a ;QUEUE=LONGJOB (or ;INQUEUE= or
whatever) option
>  > on them.  Having a single user only able to submit jobs to a single
queue
>  > does not solve any problems.
>
> We need to know if all the customers feel the same way about being
> able to change job files. But we thought it may not be the case. Will
> need input there.
 
From our point of view - the one-queue-per-user is going to be fine for
the majority of our users. After all, most of our users are really just
*users*; all they want to do is stream a job that's going to produce
a report, and they usually do that by pressing a function key from a
VPLUS screen in some program. They don't know and really don't care
about JOB cards and STREAM commands.
 
BUT - The vast marjority of our jobs are not streamed by those users,
they're streamed by a few users down here in DP, and those few users
are going to NEED to be able to access multiple queues. I like the idea
of being able to assign users different default queues (or assigning
default queues to users), but still allowing the defaults to be
overridden by specifying a different queue in the JOB card or the
STREAM command. I don't see us specifying queues on the STREAM command
so much; I think once we know how the job behaves, the queue will get
specified on the job card, but it's nice to have the option.
 
I also like the idea of a system-default queue to be used when no
queue is specified and the user has no default queue. I like the
idea of it having a name like the user-default queues, but maybe it
could start with HP (e.g. HPQUEUE).
 
of course that's just my opinion.. I could be wrong  :)
 
Ray. (not accustomed to making smiley faces out of special characters).