It took me a while to remember the parameter, but VESOFT's "Streamx" product
has what you need:

T:[TOM]/EMERSON/WORK>help jobparm

Not found in MPEX help, using SECURITY HELP...


  1. $JOBPARMS-ALWAYS, STREAMX configuration keyword
  2. $JOBPARMS-DEFAULT, STREAMX configuration keyword
Which of the above would you like help on (or CR to exit)? 1

     Note: to use this feature, you will have to patch the third-party
software
     to use STREAMX instead of STREAM.  As documented earlier (see "What If
     Your Program Does A :STREAM Programmatically (With The COMMAND
     INTRINSIC)"), this is very easy to do.

   * Require jobs launched by certain users to run with, say, a lower
run-time
     priority or input priority.  For instance, if you want to make sure
that
     all jobs streamed by people in the TEST account run with PRI=DS and
     INPRI=3, you can say

       $JOBPARMS-ALWAYS @.TEST @[log in to unmask]@ @.@ "PRI=DS;INPRI=3"

     Note that this uses the $JOBPARMS-ALWAYS keyword, which adds the
     parameters to the job card regardless of whether the job card already
     contains these parameters -- the $JOBPARMS-DEFAULT keyword parameters
can
     be overridden by parameters specified on the job card.

If both a $JOBPARMS-DEFAULT and a $JOBPARMS-ALWAYS apply, the
$JOBPARMS-ALWAYS
takes effect, whether it comes first in the STREAMX.DATA file or not.

[I no longer work for them, you decide if <plug>'s are needed or not :) ]

Although this predates the JOBQ parameter, since what you supply is a quoted
string that gets "tacked on" to the job card, it should not have any problem
with this "new" keyword [but if it does, complain to VESOFT to get it
fixed!]

> -----Original Message-----
> From: Michael Anderson [mailto:[log in to unmask]]
> I would like thoughts from others on the list about JOBQ's and
> how to implement them in an environment of programmatically
> streamed jobs. When job stream files are created and streamed
> programmatically I have no way to define different JOBQ's for
> each user or account. I do not have access to the source code.
[...]
> Now with
> the introduction of JOBQ's I am feeling the need to resurrect
> my old stream program. By analyzing the stream file I could
> programmatically decide what JOBQ it belongs in, and stream
> it into that Que. Has anyone been here and done this?