RE: Changing job submitted priority

["Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxx>]

Ron,

The place to look would be in the routing data of the SBMJOB command
which put the job in the job queue.  This routing data is then compared
with the compare values in the subsystem routing entries.  When a match
is found, the class associated with that routing entry determines the
priority.

If all else is the same, then I assume that the different job queues
mentioned below are associated with different subsystems.  The job queue
will have no effect on the priority of the job beyond associating the
job with a particular subsystem.  Either that, or the job is not being
submitted identically.

HTH,
Regards,
Andy Nolen-Parkhouse

> Subject: Changing job submitted priority
>
> Hi All
> We have one job queue here that submits everything at a run level of
30.
> I
> don't believe it is a jobd changing the priority because I can submit
it
> to
> a different job queue and then move the job and it will run at 30 when
in
> the other job queue it would run at 50.
>
> Can anyone steer me in the right direction to slow this thing down.  I
> tried
> looking at CHGJOBQE but nothing there seemed to make any sense as far
as
> this problem.
>
> TIA
> Ron