Use the LIST keyword or the LISTPROTOCOL keyword on the TARGET command to list the attributes of RRSF nodes defined as targets for the local node. For a multisystem node, the LIST and LISTPROTOCOL keywords also display information about the systems that make up the node. If you specify the NODE keyword with LIST or LISTPROTOCOL, the output shows detailed information for the node. If you do not specify the NODE keyword, the output shows summary information for all nodes in the network. The output for the LIST and LISTPROTOCOL keywords is the same when you also specify the NODE keyword. If you do not specify the NODE keyword, the LIST keyword only lists protocol information for nodes that have multiple protocols defined, but the LISTPROTOCOL keyword lists protocol information for all nodes.

Tip: Use LISTPROTOCOL when you have a mixed protocol network and you want to quickly identify the protocol used by each node without displaying detailed information for each node.

You can request detailed information for one target node or for all target nodes by specifying the NODE keyword. You can specify the PROTOCOL and SYSNAME keywords with the NODE keyword to qualify the information that you want displayed. For example, specify TARGET LIST NODE(*) PROTOCOL(TCP) to request detailed information about all nodes that use the TCP/IP protocol. For information about the combinations of keywords that you can specify and the output that results, see z/OS Security Server RACF Command Language Reference. If you do not specify the NODE keyword, RACF® lists a summary of all the target nodes defined for the local node.

The TARGET LIST command for a node displays the values last specified for the workspace data sets on a TARGET command for the node, but these values are not necessarily the values that are in effect. See Defining the workspace data sets for information about why the values shown might not be the values in effect.

When using IPv6 on z/OS®, then the TARGET LIST command for a node displays a resolved address in IPv6 format. This also occurs when an IPv4 address is specified for the ADDRESS operand after the address is resolved with an OPERATIVE connection.