Deciding where resources should be installed

With Business Application Services, you can issue a single request and have resources installed throughout the CICSplex. The key is to define a resource as broadly as possible and install it in as many CICS® systems as possible at one time. A single resource definition can be used to install multiple instances of the resource in multiple CICS systems. And that same resource definition can be used to install both local and remote resources. For example, a single transaction definition could be used to install local transactions in your application-owning regions (AORs) and remote transactions in your terminal-owning regions (TORs).

To determine what resources to install and where to install them, CICSPlex® SM checks the target scope, related scope, and resource group values in your resource assignments, resource descriptions, and the associations between them. The information in these definitions is processed as follows:

Resource assignments (RASGNDEF objects) take precedence. Any values that you explicitly define in a resource assignments are used, regardless of any other values you may specify.
For any values that are not found in a resource assignment definition, CICSPlex SM checks the resource assignment-to-description association (RASINDSC object) and uses the values it finds there.
For any values that are not found in either the resource assignment or the resource assignment-to-description association definition, CICSPlex SM checks the resource description (RESDESC object) and uses those values. The resource description values serve as defaults, if no other values are specified.

So you could identify the standard target and related scope values for your enterprise in one or more resource description definitions. Then, for particular assignment purposes (of a particular resource type, for example), you could override those standard values by specifying different values in the resource assignment or resource assignment-to-description association definition.