Resource-limiting attributes affect the total resources available to a job and all its tasks when such attributes are included in the job attribute list. Resource-limiting attributes include the following:
-
ELAPSEDLIMIT
-
MAXIOTIME
-
MAXLINES
-
MAXPROCTIME
-
MAXWAIT
-
PRINTLIMIT
While these attributes can also be set for specific tasks, the accumulated resource usage of the job and all its tasks cannot exceed the values set for these attributes for the job.
Some of the job attribute values are inherited by the tasks initiated by a job. The inheritance status of each attribute is listed in the Task Attributes Programming Reference Manual.
The HOSTNAME task attribute has no effect when it is used in a job attribute list, but an AT <hostname constant> specification can be used instead. Refer to AT Host Name for details.
If a particular task attribute is assigned values more than once in a job attribute list, the last assignment overrides the previous ones.
The job attribute list is terminated by the appearance of any construct that is not a job attribute assignment.
USER is accepted as a synonym for the USERCODE task attribute when it is entered as part of a job attribute list. If the USER statement is the first statement of a job, it is interpreted as part of the job attribute list rather than as an executable statement. The specified USERCODE is validated during the compilation as a new usercode logging on for the duration of the job execution.
Note: | When a usercode assignment occurs in the <job attribute list>, job attributes associated with the usercode in the USERDATAFILE are applied to the job and to the job compilation. A usercode assignment (either through a USER statement or a <task attribute assignment>) occurring in the <statement list> affects only the USERCODE and ACCESSCODE attributes. If the usercode of the job is changed, job messages stop appearing at the originating terminal even though the job continues to execute normally. Refer to USER Statement for details. |
File equations cannot be included in the job attribute list. A statement beginning with FILE is interpreted as a file declaration and terminates the job attribute list.
Example
The following example job includes a number of common job attribute assignments:
?BEGIN JOB COMPJOB; CLASS = 3; USERCODE = JOHN/JUAN; CHARGECODE = SHIPPING; MAXPROCTIME = 60; PRIORITY = 80; RUN (WALLY)POSTAGE/SUMMARY ON SHIPPK; ?END JOB.