# GROUP parameter - IBM-JCL

Parameter Type
Keyword, optional

Note: Do not specify this parameter for a started task; if GROUP is specified, the job will fail.

Purpose
Use the GROUP parameter to specify a RACF-defined group to which a RACF-defined user is to be connected. RACF places each RACF-defined user in a default group; the GROUP parameter is needed only to specify a group other than a user’s default group.

If the installation contains the feature for propagation of the user and group identification, the USER and PASSWORD parameters are required, and the GROUP parameter is optional on JOB statements only for the following:

• Batch jobs submitted through an input stream, such as a card reader, if:
– the installation requires that all jobs have RACF identification.
• Jobs submitted by one RACF-defined user for another user. In this case, the JOB statement must specify the other user’s userid and may need a password. The group id is optional.
• Jobs that execute at another network node that uses RACF protection. Otherwise, the USER, PASSWORD, and GROUP parameters can be omitted from JOB statements. RACF uses the userid, password, and default group id of the submitting TSO/E user or job.

Considerations for an APPC Scheduling Environment
The GROUP parameter has no function in an APPC scheduling environment. If you code GROUP, the system will check it for syntax and ignore it.

1.Syntax

GROUP=group-name

2.Subparameter Definition

group-name
Identifies the group with which the system is to associate the user. group-name is 1 through 8 alphanumeric or national ($, #, @) characters. The first character must be alphabetic or national ($, #, @).

3.Defaults
If you do not code the GROUP parameter, but do code the USER and PASSWORD parameters, the system assigns the RACF default group name associated with the specified userid. However, the default group name is not passed to JES and thus is not available to JES installation exits.

4.Example of the GROUP Parameter