Implementing Security with IBM RACF › Control Job Submission Under RACF

Control Job Submission Under RACF

Depending on your security options, CA WA CA 7 Edition can perform submit checking to validate the authorization of a USERID to submit jobs for another USERID. The SECURITY statement describes the options available to perform submit checking.

This example defines a submit (SU@MIT) resource that CA WA CA 7 Edition can validate.

RDEFINE SU@MIT (USERID1) DATA('userid1 submission class') OWNER(CA7USERS)
UACC(NONE)

RDEFINE

Identifies the RACF command used to define general resources.

SU@MIT

Identifies the resource class type for CA WA CA 7 Edition submission checking. If you have specified a resource type other than SUBMIT (see the SECURITY statement SCLASS keyword), substitute its value for SU@MIT. Also, for resource types other than SUBMIT, modify the CA Common Services security exit CAS9SAFC.

(USERID1)

Identifies the USERID that other user IDs can submit.

DATA

Describes the submission resource class.

OWNER(CA7USERS)

Identifies a predefined RACF user or group profile that owns this resource.

UACC(NONE)

Identifies the universal access level for this resource. In this case, NONE.

This example grants submit authority for USERID2 to submit for USERID1.

  PERMIT USERID1 CLASS(SU@MIT) ID(USERID2)

PERMIT

Identifies the RACF command used to grant access to a resource.

USERID1

Identifies the USERID that the ID USERID2 in this example can submit.

CLASS(SU@MIT)

Identifies the resource class type. If you have specified a resource type other than SUBMIT (see the SECURITY statement SCLASS keyword), substitute its value for SU@MIT.

ID(USERID2)

Identifies the USERID that is given submit authority for another ID.