MRO bind time security

Edit online

MRO bind time security ensures that the server started task is authorized to establish a connection, or bind, to a CICS region.

If you start the server started task, and the OPEN_PIPE request fails with RESPONSE(SYSTEM_ERROR), REASON(IRC_CONNECT_FAILURE) , and subreason1= 176(decimal), you must set up MRO bind time security for the server. The server user ID must have READ authority to profile DFHAPPL.applid, where applid is the ID for the CICS region that is specified in the APPLID() parameter of your connection definition in your Data Virtualization Manager configuration file.

If you start a server started task, and the ALLOCATE_ PIPE request fails with RESPONSE(SYSTEM_ERROR), REASON(IRC_LOGON_FAILURE), and subreason1= 204(decimal), you need to set up MRO logon security for the server. The server user ID must be authorized with UPDATE authority to DFHAPPL.net_name RACF profile, where net_ name is the name that is used in the NETNAME() parameter of your connection definition in your Data Virtualization Manager configuration file.

Because RACF does a separate check for LOGON security, issue the following command:

RDEFINE FACILITY (DFHAPPL.netname) UACC(NONE)
PERMIT DFHAPPL.netname CLASS(FACILITY) ID(AVZS) ACCESS(UPDATE)
SETROPTS REFRESH RACLIST(FACILITY)