CA IDMS Centralized Security Overview › CA IDMS Centralized Security › The SRTT

The SRTT

This section describes the Security Resource Type Table (SRTT).

Purpose of the SRTT

The Security Resource Type Table (SRTT) is a load module in which you store this information that CA IDMS centralized security needs at runtime:

• Each resource type to be secured.
• The system that will enforce security on the resource (internal or external).
• For resources to be secured externally, information that the external security system needs to service a security check request on the resource.

Using the SRTT

At installation, CA IDMS provides the default RHDCSRTT module. The security option for each resource defined by CA IDMS is set to 'OFF' (no security), and SVCNUM is set to the SVC number specified in the installation parameters.

You modify the RHDCSRTT module with an assembly of the #SECRTT macro. The SRTT is loaded at system start-up, and can be reloaded dynamically using the DCMT VARY NUCLEUS command for the RHDCSRTT module.

The scope of the SRTT is one or more CA IDMS systems, depending on your security scheme.

Security Options by Resource Type

For each resource type you can specify one of these security options in the SRTT:

• EXTERNAL—Security enforcement for the resource follows rules defined in the external security system.
• INTERNAL—Security enforcement for the resource follows rules defined to the CA IDMS internal security system.
• OFF—No security enforcement for the resource (the default at installation).

Generating the SRTT

The SRTT is created by issuing a sequence of #SECRTT macros.

The #SECRTT macro can specify one of four types of action:

• Initial—Denotes the beginning of the SRTT assembly.
• Entry—Specifies a security option for all occurrences of a given resource type.
• Occurrence override—Specifies a security option for one or more occurrences of a given resource type that overrides the entry specification for the resource type (not applicable to all resource types).
• Final—Denotes the end of the SRTT assembly.

Occurrence Overrides

For an individual occurrence of a database, task, or program, you can override in the SRTT the security option you specify for the corresponding resource type.

For example, you can omit an SRTT entry for the database resource type and create an occurrence override for database PROD specifying internal security. The result will be that any checks on resources associated with database PROD will be routed to internal security, while checks on resources associated with all other databases will not be checked.

Note: The resource name you give on an occurrence override is treated as a wildcard. In the previous example, all databases in the domain of the SRTT with names beginning 'PROD' are secured internally.

Performance Consideration

You may gain a performance advantage by using an override to turn off security for occurrences of a secured resource type. Runtime security processing checks for an occurrence override in the SRTT before checking resource authorizations in the security database.