Description

Syntax

Name field

Code a grpname on every JOBGROUP statement, as follows:
  • Each grpname must be unique.
  • The grpname must begin in column 3.
  • The grpname is 1 through 8 alphanumeric or national ($, #, @) characters.
  • The first character must be alphabetic or national ($, #, @).
  • The grpname must be followed by at least one blank.

Operation field

The operation field consists of the characters JOBGROUP and must be preceded and followed by at least one blank. It can begin in any column.

Parameter field

A JOBGROUP statement has two kinds of parameters - positional and keyword. All parameters are optional, however, your installation might require the accounting information parameter and the programmer's name parameter.

  • EMAIL=email-address
  • OWNER=userid
  • GROUP=RACF_group
  • PASSWORD=password
  • SECLABEL=seclabel
  • TYPE=SCAN,
  • HOLD=NO|YES
  • ERROR=(condition)
  • ONERROR=STOP|SUSPEND|FLUSH
  • SYSAFF=(affinity_list)
  • SYSTEM=(system_list)
  • SCHENV=scheduling_environment
  • Accounting information (positional)
  • Programmer name (positional)
Positional Parameters: A JOBGROUP statement can contain two positional parameters. They must precede all keyword parameters. You must code the accounting parameter first, followed by the programmer's name parameter.
Accounting information
Use the accounting information parameter to enter an account number or other accounting information. Same usage as accounting information parameter on a JOB statement.
Programmer name
Use the programmer’ name parameter to identify the person or group responsible for a job group. Same usage as programmer name parameter on a JOB statement.

Keyword Parameters: A JOBGROUP statement can contain the following keyword parameters. You can code any of the keyword parameters in any order in the parameter field after the positional parameters.

EMAIL=
The email address used to extract the user ID to be associated with the job group. Rules are the same as for EMAIL parameter on a JOB statement.
OWNER=
The user ID to be associated with the job group. Rules are the same as for USER parameter on a JOB statement.
GROUP=
The RACF® group to be associated with job group. Rules are the same as for GROUP parameter on a JOB statement.
PASSWORD=
The password (if required) and optional new password for the user ID associated with the job group. Password or password phrase can be specified.
Password phrases are also supported and are 9-100 characters in length.
Note: You cannot combine passwords and password phrases.
  • If the previous value is a password, then the new value must be a password.
  • If the previous value is a password phrase, then the new value must be a password phrase.
The difference between passwords and password phrases is the length. Both can be specified within apostrophes. JCL processing allows for any characters within apostrophes.

The security product used determines which characters are allowed, based on the values that are used.

SECLABEL=
The security label to be associated with the job group. Rules are the same as for SECLABEL parameter on a JOB statement.
TYPE=SCAN
The job group is checked for validity but not processed. Any error is recorded in the logging job. Since the internal structures for this job group are never created, any jobs that are subsequently submitted for this job group fails.
HOLD=NO|YES
The job group can be submitted in a held or a non-held state. If the job group is submitted in the held state, none of the jobs that are associated with this job group runs until the job group is released.
ERROR=(condition)
This parameter defines a set of conditions that must be evaluated after each job in the job group completes execution to determine if an error condition is to be raised. If the condition is true, the job group is marked as in error and the action defined by ONERROR= parameter is taken.
The syntax of condition is the same as used for the conditional syntax on the IF statement. Supported keywords that can be tested are:
Keyword Use
RC Indicates the return code of a job.
ABEND Indicates that an ABEND condition occurred.
¬ABEND Indicates that no ABEND condition occurred.
ABENDCC Indicates a specific system or user ABEND code.
FAIL Indicates that a job ended abnormally due to one of the following conditions: job ended by CC, a JCL error was detected, the job failed in end-of-memory, or the job failed in conversion.
¬FAIL Indicates that a job did not end abnormally due to one of the preceding conditions.
RUN Indicates that the job was executed.
¬RUN Indicates that the job was flushed from the job group.
The operators that you can use are:
Operator                    Operation                       Order
--------                    ---------                       -----

NOT operator:

Not or ¬ or !               NOT                             first

Comparison operators:

GT  or  >                   Greater than                    second
LT  or  <                   Less than                       second
NG or ¬> or !>              Not greater than                second
NL or ¬< or !<              Not less than                   second
EQ  or  =                   Equal to                        second
NE or ¬= or !=              Not equal to                    second
GE  or  >=                  Greater than or equal to        second
LE  or  <=                  Less than or equal to           second

Logical operators:

AND or  &                   AND                             third
OR  or  |                   OR                              third
Examples of ERROR=:
ERROR=(RC=4 | RC=8)
ERROR=(!ABEND AND RC=8)
ERROR=(ABENDCC=S0C4 OR ABENDCC=U1024)
ONERROR=STOP|SUSPEND|FLUSH
This is the action to take when a job group is determined to be in error. This applies when the condition defined on the ERROR= keyword is encountered or when a dependency is considered to fail.
STOP
No new jobs in the job group are started. Actively running jobs are allowed to complete. Jobs that are determined to be in error (based on the JOBGROUP ERROR= keyword or the condition in a dependency) can be resubmitted and the error state cleared if they run successfully.
SUSPEND
New jobs that have their dependencies satisfied are allowed to start. Jobs that are determined to be in error (based on the JOBGROUP ERROR= keyword or the condition in a dependency) are considered to have not run. These jobs can be resubmitted and the error state cleared if they run successfully.
FLUSH
All jobs that have not executed yet are canceled (flushed). No new jobs are started. When there are no longer any jobs running, the job group is marked completed.
SYSAFF=
Base system affinity for all jobs that are associated with this job group. Syntax is the same as SYSAFF= on the JOB card, except that independent mode is not supported for job groups. This specification is combined (ANDed) with any affinity specification for each job in the group.
SYSTEM=
Indicates the systems that are eligible to process the jobs associated with this job group. Syntax is the same as SYSTEM= parameter on the JOB statement. This list is combined (ANDed) with any affinity specification for each job in the group.
SCHENV=
Default scheduling environment for all jobs that are associated with this job group. Syntax is the same as SCHENV= on the JOB card. The list of systems where this scheduling environment is available is combined (ANDed) with the other affinity specifications for the job. Note that this implies that a job in a job group can have two scheduling environments specified - the one for the job group and another one for the job in the group.

Comments field

The comments field follows the parameter field after at least one intervening blank space. If you do not code any parameters on a JOBGROUP statement, do not code any comments.

Location in the JCL

A JOBGROUP statement must be the first statement in each job group.

Error on JOBGROUP statement

JOBGROUP statements terminate any currently active JCL being submitted (in much the same way as a JOB statement ends any current stream). A second JOBGROUP statement without an ENDGROUP statement is considered an error for the first JOBGROUP.

Examples of JOBGROUP statements

//RUN00001 JOBGROUP OWNER=IBMUSER,PASSWORD=IBMUSER