Controlling incoming requests from remote nodes

Occasionally it is desirable to set up RRSF such that updates made on a local system get propagated outbound to other systems, but to prevent updates made on some set of the remote systems from being propagated back to the local system. While you cannot prevent the other system from trying to send you requests, the DENYINBOUND keyword of the TARGET command would enable a local system the ability to refuse an incoming request by creating a one-way outbound connection to a node on the network.

For more information about DENYINBOUND and ALLOWINBOUND kewords, see the discussion in Defining RRSF nodes to RACF using the TARGET command.

The OPERATIVE and DORMANT keywords on the TARGET command control whether incoming requests from the remote node are sent immediately or held.

Use the OPERATIVE keyword to request that a connection to a node be made active, or operative. When a connection with a remote node is made operative, all requests for the local node (such as directed commands) that are held in the OUTMSG data set of the remote node are sent to the local node. As long as the connection remains operative, new requests from the remote node are sent when they are placed in the OUTMSG data set.

Use the DORMANT keyword to request that a connection to a node be made inactive, or dormant. When a connection is dormant, RACF® saves requests from the remote node (such as directed commands) in its OUTMSG workspace data set on the remote node. The requests are held until the connection is made operative. Requests that have been received from the remote node, but not yet processed, are saved in the INMSG data set. RACF continues to process requests in the INMSG data set even if the connection is dormant.