Specifying CICSPlex SM resource names in profiles

You can create RACF® profiles for CICSPlex® SM views for a specific CICS® system, a group of CICS systems, or all systems comprising a CICSplex.

About this task

The lists contain the resource names for CICSPlex SM views to be used in RACF profiles.

CICSPlex SM views are divided into groups that reflect the functions they perform. Within each functional group, the views are divided by their type. Functional groups can be even further qualified with the addition of a context and, for some groups, a scope or platform. You can control access to a specific set of views (and their associated action commands) by identifying the set in a profile, using one of the following resource name formats:

function.type.context
function.type.context.scope

where:

function

is the name of the CICSPlex SM function to be affected:

ANALYSIS: Real-time analysis
BAS: Business application services
CLOUD: Platforms and applications
CONFIG: CMAS configuration
CSD: CICS System Definition
MONITOR: Resource monitoring
OPERATE: Operations
TOPOLOGY: CICSplex configuration
WORKLOAD: Workload management

type

is the specific or generic name of an area that qualifies the CICSPlex SM function to be affected. The specific names are:

AIMODEL: CICS AIMODEL
APPLICTN: CICS bundle resources and resources only installable by CICS bundles
APPLICATION: Applications deployed in platforms
BRFACIL: Link3270 Bridge Facility
CONNECT: CICS connections
DB2DBCTL: DB2/DBCTL resources and subsystems
DEF: CICSPlex SM definitions
DOCTEMP: Document templates
ENQMODEL: CICS global enqueue models
ENTJAVA: CorbaServers and deployed DJARs
EXIT: CICS exits
FEPI: CICS FEPI resources
FILE: CICS files
IPCONN: IPIC connections
JOURNAL: Journal models
PARTNER: CICS partners
PLATFORM: Platforms
PROCTYPE: CICS BTS Process types
PROFILE: CICS profiles
PROGRAM: CICS programs
REGION: CICS region data
RQMODEL: CICS request models
TASK: CICS active tasks
TCPIPS: TCP/IP services
TDQUEUE: CICS transient data queues
TERMINAL: CICS terminals
TRAN: CICS transactions
TSQUEUE: CICS temporary storage queues
UOW: CICS units of work

The type must be valid for the specified function. Table 1 lists the valid function.type combinations.

context

Context is the specific or generic name of the CMAS or CICSplex to be affected by the designated function and type. If the function is CONFIG, the context can be a CMAS or a CICSplex. For all other functions, the context must be a CICSplex.

scope

Scope is the specific or generic name of a CICS system in the CICSplex identified as the context. Do not specify scope when the context is a CMAS, the type is DEF (except when handling CSD resources) or when the function is CLOUD.

Note:

In this section only, the term scope means CICS systems. It does not mean the scope (CICS system groups) you have defined as part of the CICSplex environment, nor does it refer to a BAS logical scope.
To include all of the systems comprising a CICS system group when their names do not match a generic system name, you must establish a profile for each system.