Controlling Job Execution [ Controlling System Activity ] MPE/iX 5.0 Documentation
Controlling System Activity
Controlling Job Execution
The execution of jobs can be controlled with the JOBSECURITY and JOBPRI
commands. JOBSECURITY designates the level of user who can request
resources and control the execution of jobs. The command can be issued
only at the system console unless previously allowed to another user.
The JOBPRI command sets or changes the default execution, priority for
batch jobs and sets a maximum execution priority for batch jobs. The
command can be issued from a session, job, program, or in BREAK. Users
must have OP capability (operator's capability) to execute this command.
Give Users Job Execution Control With JOBSECURITY
In the following example, the system operator issues JOBSECURITY LOW.
This allows all users on the system to issue the commands ABORTJOB,
ALTJOB, BREAKJOB, and RESUMEJOB, although only for their own jobs.
JOBSECURITY LOW
If the system operator now issues the JOBSECURITY command using the
parameter HIGH, the capabilities allowed by the LOW parameter will be
canceled.
JOBSECURITY Syntax
{HIGH}
JOBSECURITY { }
{LOW }
If no parameter is entered, the current setting of JOBSECURITY is
displayed.
Table 3-10. JOBSECURITY Parameters
--------------------------------------------------------------------------------------------
| | |
| Parameter | Description |
| | |
--------------------------------------------------------------------------------------------
| | |
| HIGH | Specifies control by the logged-on system operator only. |
| | |
| | |
--------------------------------------------------------------------------------------------
| | |
| LOW | Allows users to exercise control over their own jobs. |
| | |
| | |
--------------------------------------------------------------------------------------------
Changing Batch Job Priority
In the following example, the system operator issues JOBPRI 0, CS. This
command with its accompanying parameters raises the maximum execution
priority so that batch jobs can run at any subqueue requested. If no
priority is specified in the batch job, the priority defaults to CS.
JOBPRI 0,CS
JOBPRI Syntax
JOBPRI [maxsubqueue][,defaultsubqueue]
If no parameters are entered, the current setting of JOBPRI is displayed.
Table 3-11. JOBPRI Parameters
--------------------------------------------------------------------------------------------
| | |
| Parameter | Description |
| | |
--------------------------------------------------------------------------------------------
| | |
| maxsubqueue | The maximum priority at which batch jobs will be allowed to run. |
| | This overrides any job priority requested by a user issuing the JOB |
| | command. This parameter may be ES, DS, CS, or 0. If 0 is specified, |
| | no limit is imposed on batch jobs. Default is no change in maximum |
| | priority. |
| | |
| | |
--------------------------------------------------------------------------------------------
| | |
| defaultsubqueue | The default execution priority for batch jobs which may be ES, DS, |
| | CS. This takes effect if a user does not specify an execution |
| | priority in the JOB command. (Default is no change in execution |
| | priority.) |
| | |
| | |
--------------------------------------------------------------------------------------------
MPE/iX 5.0 Documentation