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


Configuring an RRSF network

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

Before an RRSF node can communicate with other RRSF nodes, you must provide the node with information about its own operational characteristics and the operational characteristics of the nodes with which it is to communicate. The node you are configuring is referred to as the local node. The nodes with which it is to communicate, not including itself, are referred to as remote nodes. All of the nodes with which the local node is to communicate, including itself and its remote nodes, are referred to as target nodes. RACF® provides the following RRSF configuration facilities:
  • The SET command, to define operational characteristics of the local system
  • THE TARGET command, to define operational characteristics related to communications for a node
  • An optional RACF parameter library, which allows you to specify standard predefined sequences of configuration commands. These sequences can be automatically processed during initialization of RRSF, or manually processed by entering RACF operator commands.

To configure an RRSF network, you must configure each node in the network. To configure a node, run RACF configuration commands (SET and TARGET) on the node. The node you are configuring is the local node for the configuration commands that run on it. For example, suppose you have a network with two nodes, NODEA and NODEB. Then, to configure the network, you must run configuration commands on NODEA defining the characteristics of NODEA, the local node, and NODEB, a remote node for NODEA. You must also run configuration commands on NODEB defining the characteristics of NODEB, the local node, and NODEA, a remote node for NODEB. See Configuring a two-node network that uses APPC/MVS for an example of commands you could use to configure this two-node network.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014