Syntax and parameters of the JOB statement

JOB statements identify up to 64 specific jobs for which specific actions are to be taken if REGULAR or ACTION messages from the job are involved in a message flooding situation. During intensive mode processing, if the specified job requires action to be taken against it, the actions are taken from those specified on the JOB statement. You can use the JOB statement to override the DEFAULT (or built-in) actions for this specific job. The JOB statement has the following syntax form.

JOB jobname [action][,action]

The JOB statement applies to the previously specified REGULAR or ACTION msgtype statements. Zero to 64 JOB statements should follow each REGULAR or ACTION msgtype statement.

action

If specified, is one or more of the actions as defined for the DEFAULT statement. If an action is not specified, the DEFAULT or built-in default actions are used.

jobname

The job name, which is 1 to 8 characters in length. You can use wildcard characters * and % when you specify a job name:

An asterisk (*) matches a substring of any characters for any length (0 to n).
A percent sign (%) matches a single character.

Note: Message flood automation assigns the job name NONAME to operating system services that issue messages that are not attributable to a particular job. The system assigns the name IEESYSAS to system services that occupy their own address spaces. Message flood automation cannot distinguish the difference between started tasks running in different address spaces with the same name.

Syntax rules:

The JOB specification must begin in column 1 and must be separated from the jobname by a single blank character.
The jobname is separated from the first action, if specified, by a single blank character. More than one blank character causes any following string to be treated as comment text.
The action parameter specifications are separated by a comma. There must be no blank characters on either size of the comma.
Comment text can follow the last action. There must be at least one blank character between the action and the beginning of the comment text. If action is not specified, there must be at least two blank characters. There is no need to preface the comment text with either an asterisk (*) or open comment specification (/*).

Example:

JOB PROD1001
JOB PROD1002   comment: note >1 blank required before comment
JOB PROD1003 LOG,NOAUTO
JOB PROD1004 LOG,NOAUTO comment: note only 1 blank required
JOB AOC%NV* LOG,AUTO,RETAIN
JOB LLA* LOG,AUTO