>Is there a way to assign a higher/lower
>interactive job priority by user id?

The manual you're interested in is the Work Management guide.  I generally
advise trying to get a grip on the major concepts before tinkering.  Also,
run PEX and get a baseline of your performance before making changes.

Basics: Run priority comes from the class, which comes from the routing
entry in the SBSD which comes from the job description which comes from the
user profile.  The point being that the default run priority is intended to
be a direct attribute of the "type" of work being done (batch, interactive,
compiles, communications, etc.), not "who" is doing it.  So driving the run
priority by user is probably best done with an initial program or a
home-grown job monitor.

User Profile to routing entry:
DSPUSRPRF JOBD()
DSPJOBD RTGDTA()

Routing entry to run priority:
DSPSBSD, 7 - routing entries
  display routing entry
DSPCLS

If you're trying to do some performance tuning, you may be better served by
setting up different memory pools.

If you're trying to dynamically turn down interactive query users or
programmers doing compiles interactively, you may be better off writing a
job monitor.

If you're trying to elevate a small group higher than the rest of the box,
then a change to the initial program may serve.

If you have a complex scheme that requires multiple tiers of RUNPTY with
each user potentially in a different slot depending on day, night, end of
month then you might actually need a larger machine rather than attempt to
programmatically assign people into RUNPTY bins.
  --buck


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.