Introduction to intercommunication security

In a single CICS® system, you use security to make sure that terminal users can access only those parts of the system they need to work with.

For interconnected systems, the same basic principles apply, but now you also include definitions for connections, sessions, and partners. You also need to allow for the fact that users of one CICS system can initiate transactions and access resources in another CICS system.

This topic assumes that you are already familiar with setting up security for a single CICS system.

In particular, you should understand the following concepts:

An interconnected group of CICS systems differs from a single CICS system in that you may have to define a user profile or group profile more than once. (See RACF user profiles and RACF group profiles for information on defining these profiles.) That is, you may have to define these profiles in each CICS system that is using a separate RACF database, and in which a user is likely to want to attach a transaction or access a resource. When planning these profiles, you must consider all cases in which a user could initiate function shipping, transaction routing, asynchronous processing, distributed program link, distributed transaction processing, or external call interface (EXCI). For descriptions of these methods of intercommunication, see Distributed transaction processing overview.



dfht582.html | Timestamp icon Last updated: Sunday, 4 June 2017