Modify category assignment of a task
Component: | BS2000 |
Functional area: | Job processing |
Domain: | JOB |
Privileges: | TSOS |
Function
The MOVE-TASK-TO-CATEGORY command enables systems support to modify the application of a task to a category if it is necessary to handle this task better or relieve the load on a category.
In addition to the four categories with the standard names TP, DIALOG, BATCH and SYS, the task management supports 12 other categories whose names are defined with the JMU utility routine. The job management system (JMS) notifies the task management of these JMS categories.
PCS (Performance Control System) enables further categories which are not known to JMS to be set up. However, these additional categories can only be successor categories of JMS categories. A JMS category can also be defined as a successor category of another JMS category.
The change in the chain of successor categories is initiated by PCS when a predefined quantity of added SERVICE-UNITS is exceeded (also referred to as DURATION RUNOUT).
The successor categories specified when PCS is used are displayed using the PCS command SHOW-PCS-OPTION.
The MOVE-TASK-TO-CATEGORY command assigns a task only to target categories which are JMS categories and not successor categories.
Task attributes assigned to the user (DIALOG, BATCH, TP) are defined by systems support in the user catalog and in the job classes. They can be modified via program interfaces (TINF macro).
A task can only be assigned to a target category if the task type which is assigned to the target category is the same as the current task type of the task (if required using a setting made with TINF).
The command is rejected in the event of a task with the task type “SYSTEM” and if the category SYS is specified.
Format
MOVE-TASK-TO-CATEGORY | Alias: MTTC | ||||||||||||||||||||||||
| |||||||||||||||||||||||||
Operands
JOB-IDENTIFICATION =
Type of job identification.
Jobs can be identified by their task sequence number (TSN) or monitoring JV (MONJV). Jobs with the task type “SYSTEM” are not accepted.
JOB-IDENTIFICATION = *TSN(...)
The job is identified by its task sequence number (TSN).
TSN = <alphanum-name 1..4>
TSN of the job whose category assignment is to be modified.
JOB-IDENTIFICATION = *MONJV(...)
The job is identified by the JV which monitors it.
MONJV = <filename 1..54 without-gen-vers>
Name of the JV monitoring the job whose category assignment is to be modified.
TO-CATEGORY = <name 1..7> / *DIALOG / *BATCH / *TP
Name of the target category to which the task is to be assigned. The category SYS is not accepted.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | Without errors | |
1 | 0 | CMD0001 | Task is already assigned to the specified target category |
1 | CMD0202 | Syntactical error | |
32 | CMD0221 | System-internal error | |
64 | CMD0216 | Authorization missing | |
64 | EXC0200 | Parameter error: TSN or MONJV unknown or MONJV belongs to another system in the MSCF network | |
64 | EXC0201 | Parameter error: Target category unknown | |
64 | EXC0202 | Parameter error: Task with system type SYSTEM is not allowed | |
64 | EXC0203 | Parameter error: SYS is not allowed as the target category | |
64 | EXC0204 | Target category is not a JMS category (but a category set up by PCS) | |
64 | EXC0205 | Target category is a (PCS) successor category and not an “autonomous” JMS category or a (JMS) start category in a chain of PCS successor categories | |
64 | EXC0206 | Task type of task and target category do not match |
Example
The task with TSN=0BMU is assigned to the category BATCHF and is now to be assigned to the category TP2:
/show-job-status job-id=*tsn(0bmu)
TSN: 0BMU TYPE: 2 BATCHF NOW: 2012-03-08.154540 ...
/move-task-to-category tsn=0bmu, to-category=tp2
The command is rejected with the following message:
% EXC0205 TARGET-CATEGORY IS A CONSECUTION CATEGORY. COMMAND NOT PROCESSED.
When PCS is used the PCS command /SHOW-PCS-OPTION supplies the following information:
Category TP |
| Category TP1 |
| Category TP2 |
The task is therefore to be assigned to the ( ́JMS) start category, namely TP, in this sequence:
/move-task-to-category tsn=0bmu, to-category=tp
% EXC0208 TASK WITH TSN = '0BMU' ASSIGNED TO TARGET-CATEGORY 'TP'. COMMAND COMPLETED.
The SHOW-JOB-STATUS command now shows that the task is now assigned to the category TP:
/show-job-status job-id=*tsn(0bmu)
TSN: 0BMU TYPE: 2 TP NOW: 2012-03-08.154820 ...
As the task is already assigned to the target category TP, only message EXC0207 is output when the MOVE-TASK-TO-CATEGORY command is issued again for the target category TP:
/move-task-to-category tsn=0bmu, to-category=tp
% EXC0207 TASK WITH TSN = '0BMU' ALREADY ASSIGNED TO TARGET-CATEGORY 'TP'. COMMAND COMPLETED.