Previous Topic: Implementing Security for BatchNext Topic: BATCH Considerations


About the BATCH Facility

CA Top Secret views BATCH as a facility that must be protected and authorized for use. Each batch job must be associated with an ACID and a password so that CA Top Secret can tell which resources it can access and how they can be accessed. To CA Top Secret, a batch job's ACID is exactly like a user ACID, in that it has an associated user record with a set of specific access authorizations. In fact, it is usually assigned a TYPE(USER) parameter specification when created. All system entry restrictions that can be designated for a user ACID are available for a batch job ACID.

Any user requiring access to BATCH must be explicitly authorized to access this facility. Users are given access to BATCH through a TSS CREATE entry when initially defining a new ACID to CA Top Secret, or through a TSS ADD entry for an ACID already defined to CA Top Secret.

Examples: granting access

This example gives users access to BATCH through when initially defining a new ACID:

TSS CREATE(USER01) TYPE(USER)
                   NAME(USER01)
                   DEPARTMENT(TECHDPT)
                   PASSWORD(WHISPER)
                   FACILITY(BATCH)

This example gives users access to BATCH for an ACID already defined:

TSS ADDTO(USER01) FACILITY(BATCH)