Mike,

If I recall correctly, the interactive job priority is based upon the
routing data contained in the job description associated with the user
profile.  As the job enters the subsystem, this comparison data is
matched against the routing data in the subsystem.  The first match in
the sequenced routing data will determine the priority of the job by
referencing an object called a class, which will have a run priority
associated with it.

The work management manual will contain specifics, but in summary you
would perform the following steps.

- Create a unique job description for this privileged group of users.
This job description would contain a unique value in the RTGDTA
parameter (something like 'SUPERUSER').  I believe the default is
'QCMDI'.

- Create a new class (make a copy of the IBM-supplied 'QINTER') with a
priority of '19'.  You should be able to do this from the WRKCLS screen.

- Add a routing entry to your interactive subsystem (ADDRTGE) which
references the RTGDTA in the CMPVAL parameter and your new class in the
CLS parameter.  Give it a sequence number lower than the default within
the subsystem.

- Change the users' profile to refer to the new job description.

Please note that you can hurt your system (and perhaps yourself), by
messing with this stuff.  I don't know your background, but be careful.
:)

Regards,
Andy Nolen-Parkhouse

>
> Yes, I'm aware of that, but what I'm looking at (since I'm lazy) is to
> make
> this
> a permanent change by user, taking effect when they log in.
> On thought I had is to perhaps create a new subsystem for groups of
users
> &
> sign them in there.
>



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.