z/OS Security Server RACF System Programmer's Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Link failure

z/OS Security Server RACF System Programmer's Guide
SA23-2287-00

This problem is the equivalent of the problem scenario Coupling facility not available in terms of system connectivity, but the problem occurs after RACF® has already been in data sharing mode, which affects how MVS™ and RACF react to the problem. Typically, the link failure is detected when RACF attempts to use the coupling facility by way of the IXLCACHE macro; IRRX016I is issued. One of two recovery actions occur automatically:
  • If REBUILDPERCENT was specified in the coupling facility resource management (CFRM) policy for the RACF structure such that the percentage of system-weight losing connectivity has exceeded the limit, MVS initiates a rebuild for that structure. See RACF support of the rebuild interface for more information.
  • MVS decides not to initiate a rebuild. MVS makes this decision if, for example, REBUILDPERCENT was not specified in the CFRM policy for the RACF structure, a sysplex failure management policy is not active for specifying the system-weights, or the system-weights were specified but the loss-of-connectivity threshold was not reached. In all cases MVS notifies RACF that a rebuild is not being done, and RACF disconnects the system from the problem structure and issues message IRRX015I. If the system is a data sharing system, it enters read-only mode. If the structure is deallocated from the coupling facility by way of disconnection from all connectors, RACF attempts to connect to a structure in an alternate coupling facility, if available.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014