z/VM: CP Commands and Utilities Reference - z/VM - IBM

INDICATE QUEUES
INDICATE QUEUES
►►
INDicate
Authorization
Purpose
Operands
Usage Notes
Responses
Queues
EXP
Privilege Class: E
480 z/VM: CP Commands and Utilities Reference
Use INDICATE QUEUES to display, in order of their priority, current members of the
dispatch and eligible lists.
Note: Each member is a virtual processor with a transaction in progress. Status
critical to the system scheduler and dispatcher is also displayed.
EXP
displays expanded information about users with a transaction in progress.
1. When INDICATE QUEUES consistently shows En users, an eligible list is
forming because one or more system resources appears to be constrained.
Under such conditions, forcing users with a transaction in progress to wait in the
eligible list increases virtual machine throughput as a whole, and also reduces
system overhead. The appearance of a constrained resource is affected by:
a. The amount of resources available on the system.
b. The total demand for the resources.
c. The fraction of resource that is available to certain user classes. For
example, a preferred virtual machine does not contend for storage, but all
other virtual machines must vie for the leftover storage. Also, the SET SRM
STORBUF and SET SRM DSPBUF commands can affect the amount of
resources available to certain user classes.
The system resources tracked are: storage, paging capacity, and CPU.
2. When you enter INDICATE QUEUES EXP and the bbb field is TI (user in
test-idle state), the associated priority field shows 99999. This should not be
read literally as a 99,999 second deadline priority; the 99999 value is used by
the scheduler to temporarily place the user at the bottom of the dispatch list.
3. The format of Response 2 is extremely sensitive to the product release and
service level.
4. All users on the limit list are also part of the dispatch list. However, they have
exceeded the limit of the CPU resource that they are allowed to use and will not
run until they leave the limit list.
Note: The response you receive lists users in the following order:
1. All dispatch list users (Qn) in dispatch priority order
2. All eligible list users (En) in eligible list priority order.
►◄