Sending user IDs and passwords

Syntax

–au userid

Specifies a valid user ID.

The server authentication mode determines whether a user ID is required. The mode is specified in the RCCRUNM JCL. This option indicates that user ID is invoking the rccbuild command. The password provided through MKSecure for the user ID or through the -ap option validates the user ID and then the user ID is validated as authorized to initiate a Remote Build task for the identified Remote Build server. All dataset accesses occur under the authority of the user ID associated with the Remote Build server task. That is, the Remote Build server surrogate ID or the Remote Build server execution ID (if the -rl option is specified).

-rl roleID

If the role-based Resource Manager is activated, roleID indicates the specific role for which this Remote Build user is authorized. If it is not activated, this argument is ignored.

The value supplied for the roleID is first used to validate the Remote Build user's specific role and is used later as the RACF® user ID under which the Remote Build job will run.

A typical set of roles are: Developer, Builder, and Tester. Each role has an associated user ID. For example, the identifiers for the typical set of roles could be: RBDEVP, RBBULD, and RBTEST.

The Security Administrator defines Role IDs. If the role ID is not specified, the invoker of the command is verified as authorized to access resources identified by the “BCC.REMOTE.BUILD resource ID. If this option is specified, the invoker is verified as authorized to access resources identified by the “BCC.REMOTE.BUILD.roleID resource.

-ap password

Specifies a TSO password. The server authentication mode determines whether a TSO password is required. This is specified in the RCCRUNM JCL.

Note: If you are using the Secure Password Protection feature, the –ap parameter can be omitted. The client uses the encrypted password in the file .rccSecure.

Platforms

z/OS® MVS™, z/OS UNIX® System Services