Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

CHANGE-TASK-PRIORITY

&pagelevel(3)&pagelevel

Change run priority of active job

Component:

BS2000

Functional area:

Job processing

Domain:

JOB                                                                                                                   

Privileges:

STD-PROCESSING
OPERATING
SAT-FILE-EVALUATION
SAT-FILE-MANAGEMENT
SECURITY-ADMINISTRATION

Routing code:

P

Function

The CHANGE-JOB-PRIORITY command changes the run priority of a job running under the user’s own ID. The command can also be used to process jobs generated by the user’s own ID and running under a different user ID (extended access).

The maximum permissible priority is the numeric minimum of the maximum values (i.e. the more favorable of the values) in the user catalog and the job class definition. If no maximum value is defined for the job class, then the standard run priority is used.

Information on the entry in the user catalog can be requested using the SHOW-USER-ATTRIBUTES command (output field MAX-RUN-PRIORITY), using the job class definition with the SHOW-JOB-CLASS (output field RUN PRIORITY) command.

The priority of jobs that have not yet been started can be changed using the MODIFY-JOB command.

Privileged function

If the CHANGE-TASK-PRIORITY command is issued at the operator terminal or under the TSOS user ID, it can be used to change the run priority of a job issued under any user ID. In this case the maximum permissible priority as defined for that user ID in the user catalog is irrelevant. 

Format

CHANGE-TASK-PRIORITY                                                                                                                            

JOB-IDENTIFICATION = *TSN(...) / *MONJV(...)


*TSN(...)



|

TSN = <alphanum-name 1..4>



|

,HOST = *STD / <c-string 1..8>


*MONJV(...)



|

MONJV = <filename 1..54 without-gen-vers>

,RUN-PRIORITY = <integer 30..255>

Operands

JOB-IDENTIFICATION =
Type of job identification.
Jobs may be identified by task sequence number (TSN) or by monitoring JV (MONJV).

JOB-IDENTIFICATION = *TSN(...)
The job is identified by its task sequence number (TSN) and where appropriate by the host on which it is running.

TSN = <alphanum-name 1..4>
TSN of the job whose priority is to be changed.

HOST = *STD / <c-string 1..8>
Host system on which the job is running.
The default is *STD, which means that the job is running on the local host.
The host name of a remote system can only be specified for systems which are on a computer network (see the “HIPLEX MSCF” manual [25]).

JOB-IDENTIFICATION = *MONJV(...)
The job is identified by its monitoring JV.

MONJV = <filename 1..54 without-gen-vers>
Name of the JV monitoring the job whose priority is to be changed.

RUN-PRIORITY = <integer 30..255>
Specifies the run priority to be assigned to the job. A low value indicates a high priority. The maximum permissible priority is the numeric minimum of the maximum values (i.e. the more favorable of the values) in the user catalog and the job class definition. If no maximum value is defined for the job class, the standard run priority is used. The values can be queried using the SHOW-USER-ATTRIBUTES and SHOW-JOB-CLASS commands. 

Return codes

(SC2)

SC1

Maincode

Meaning


0

CMD0001

No error


1

CMD0202

Syntax error


32

CMD0221

System error


32

JMS0024

System error


64

JMS0630

Semantic error (see SYSOUT message)


64

JMS0640

MONJV error, illegal access or invalid time of call


64

JMS0670

Error in a remote job


130

JMS0620

Memory saturation


130

JMS0650

MSCF or destination processor not available