Parameters for executing batch jobs, TP applications and interactive applications

The following parameters are important when it comes to executing applications in the desired category, taking into account the relevant task attribute TP, DIALOG or BATCH (see also section "Task management") and the desired priority.

TP-ALLOWED     = *NO / *YES(CATEGORY=<name>)
DIALOG-ALLOWED = *NO / *YES(CATEGORY=<name>)
BATCH-ALLOWED  = *NO / *YES(CATEGORY=<name>)

The above parameters define the task attribute for the job class. This serves to assign special internal execution parameters, optimized for the operating mode TP, interactive or batch.

If no category name has been specified, the associated default category name is assumed (e.g. for TP-ALLOWED=*YES the default category name is TP).

A category name must not be assigned to more than one task attribute.

START-ATTRIBUTE = *BATCH / *DIALOG / *TP

This parameter defines the task attribute used to start tasks of this job class. The parameter values for START-ATTRIBUTE and TP-ALLOWED, DIALOG-ALLOWED and BATCH-ALLOWED must be mutually compatible.

RUN-PRIORITY

This parameter defines the execution priority (= task priority).

The parameter RUN-PRIORITY=*PARAMETERS (DEFAULT=n, MAXIMUM=n) an be used to define the maximum task priority a user may assign.

Example

An important production application (job handling) is to be run as a TP application with high priority and in a separate category.

With the aid of the JMU utility routine (see the “Utility Routines” manual [6 (Related publications)]) a job class is defined (//DEFINE-JOB-CLASS), the access right is specified (//GRANT-JOB-CLASS-ACCESS) and storage in the file SJMSFILE is performed.

//DEFINE-JOB-CLASS NAME=PRIO1,
  CLASS-LIMIT=5,
  CLASS-WEIGHT=2,
  JOB-PRIORITY=*PARAMETERS(DEFAULT=3),
  JOB-TYPE=*BATCH,
  TP-ALLOWED=*YES(CATEGORY=<name>),
  START-ATTRIBUTE=*TP,
  RUN-PRIORITY=*PARAMETERS(DEFAULT=150,MAXIMUM=128),
  NO-CPU-LIMIT=*YES,
  CPU-LIMIT=*PARAMETERS(DEFAULT=*NO-LIMIT,MAXIMUM=32767),
  SYSLST-LIMIT=*PARAMETERS(DEFAULT=*NO-LIMIT),
  START=*PARAMETERS(DEFAULT=*SOON,ALLOWED=...)

//SET-MODIFICATION-MODE is used to specify whether the JMU utility routine is to put the modification into effect immediately, in the current session, or/and write it in the SJMSFILE file, which is not evaluated until the next system startup.
The production application can be started simply by issuing /ENTER-JOB with JOB-CLASS=PRIO1.

Note

For reasons of compatibility, a logical OR link between the entries for the job class and the user ID is provided, the respective “higher” authorization having priority in each case.

Example

Job class	User catalog	Status
TP-ALLOWED=*NO	MAX-ALLOWED-CATEGORY=TP	TP permitted
RUN-PRIORITY=    *PARAMETERS(DEFAULT=150,                MAXIMUM=128)	MAXIMUM-RUN-PRIORITY=180	maximum priority=128