Implementing MRO security
This topic tells you how to implement CICS® multiregion operation (MRO) security.
- Security implications of choice of MRO access method
Either MVS™ cross-memory services or the CICS Type 3 SVC can be used for interregion communication (function shipping, transaction routing, distributed transaction processing, and asynchronous processing). - Bind-time security with MRO
The CICS interregion communication (IRC) facility supports MRO through the use of DFHAPPL.applid profiles in the FACILITY class. - Logon security checking with MRO
Logon security checking is performed whenever a CICS region logs on to the CICS-supplied interregion communication (IRC) program, DFHIRP. - Link security with MRO
Link security restricts the resources that a user can access, depending on the remote system from which they are accessed. The practical effect of link security is to prevent a remote user from attaching a transaction or accessing a resource for which the link userid has no authority. - Specifying link security for MRO connections
- User security with MRO
- Transaction, resource, and command security with MRO
- Transaction routing security with MRO
- Function shipping security with MRO
When CICS receives a function-shipped request, the transaction that is invoked is the mirror transaction. - Distributed program link security with MRO
The CICS distributed program link (DPL) facility enables a program (the client program) to call a CICS program (the server program) in a remote CICS region. The client program may be a CICS program or a non-CICS program. - Security checking done in AOR with MRO
dfht551.html |
Last updated: Sunday, 4 June 2017