MPE/iX Commands Reference Manual (32650-90877)
58 Chapter3
Command List I
Commands ABORT to BYE
@S - all sessions,
@J - all jobs,
@ - all sessions and jobs
The USER and ANYUSER options apply only to
jobspec
and only if
jobspec
is wildcarded. The USER option, which is the default, alters only processes
matching the user's name, while the ANYUSER option alters all processes
matching the wildcarded
jobspec
. For example, if the user's name is
STEVE.UI and you enter the command shown below, then only job
processes logged on as STEVE.UI are altered.
:ALTPROC job=@j;pri=cs
However, if you add anyuser to the same command as shown below, then
all job processes are altered.
:ALTPROC job=@j;pri=cs;anyuser
TREE is the default for all
jobspec
target processes, and can be overridden
with the NOTREE option.
The SYSTEM option is ignored for all
jobspec
target processes.
The
jobspec
is optional as long as a
pinspec
is supplied. If both are
omitted, an error is reported.
pri
The queue or absolute priority for the process. If omitted, the priority is
unchanged.
CAUTION
Exercise extreme caution when altering a process's priority, scheduling queue
attribute, or workgroup membership. Such a change can significantly impact
system performance.
NOTE
For Workload Manager Users
Avoid using the ;PRI= option to explicitly change a process. If you have created
user-defined workgroups that have ;MEMB_QUEUE as membership criteria, use of the ;PRI=
option may change the workgroup. Instead, use either the ;WG=
workgrp
or
;WG=NATURAL_WG option, explained below, to move target processes into existing
workgroups.
Using ;WG= to explicitly change a workgroup should be a temporary measure, and used
rarely. Instead, adjust workgroup membership criteria to ensure that desired processes
become natural members of the workgroup.
If you specify both the ;WG= and ;PRI= in the ALTPROC command line, you will
get an error.
The
pri
value may be one of the following:
• A scheduling queue value {BS,CS,DS,ES} sets the queue attribute of the
target process(es). If a user-defined workgroup does not capture the
process, then the process will fall into to the corresponding