TARGET (Manage RRSF nodes)

Purpose

Use the TARGET command to:

List the operational and network protocol attributes of one or more RRSF nodes.
Add or modify an RRSF node.
Convert a remote RRSF node from one network protocol to another.
Add a network protocol or modify protocol attributes for an RRSF node.
Activate or inactivate an RRSF node or a protocol instance for an RRSF node.
Specify a prefix and other attributes for the workspace data sets allocated and used by each RRSF node.
Purge a workspace data set for an RRSF node.
Delete an RRSF node or a protocol instance for an RRSF node.

Before using the TARGET command for the first time, you should be familiar with the information in "RACF remote sharing facility (RRSF)" in z/OS Security Server RACF System Programmer's Guide. To help you determine the information you will need to issue the TARGET command, complete the worksheet found in "RRSF initialization worksheet and scenario" in z/OS Security Server RACF System Programmer's Guide.

Issuing options

The following table identifies the eligible options for issuing the TARGET command:

As a RACF® TSO command?	As a RACF operator command?	With command direction?	With automatic command direction?	From the RACF parameter library?
No	Yes	No	No	Yes

For general information about issuing RACF operator commands, see RACF operator commands.

Related commands

To specify and enable options for automatic direction using RRSF, see SET.
To restart functions of the RACF subsystem address space, see RESTART (Restart RACF subsystem functions).
To stop the RACF subsystem address space, see STOP (Stop RACF subsystem).

Authorization required

You might require sufficient authority to the proper resource in the OPERCMDS class. For details about OPERCMDS resources, see "Controlling the use of operator commands" in z/OS Security Server RACF Security Administrator's Guide.

Syntax

For the key to the symbols used in the command syntax diagrams, see Syntax of RACF commands and operands. The complete syntax of the TARGET command is:


subsystem-prefixTARGET
	[ DELETE \| DORMANT \| OPERATIVE ]
	[ DESCRIPTION('description') ]
	[ LIST ]
	[ LISTPROTOCOL ]
	[ LOCAL ]
	[ MAIN ]
	[ NODE(nodename \|`*`) ]
	[ PREFIX(qualifier …) ]
	[ PROTOCOL( [ APPC( [ LUNAME(luname) ] [ TPNAME(profile-name) ] [ MODENAME(mode-name) ] ) ]
	[ TCP( [ ADDRESS(address) ] [ PORTNUM(number) ] ) ] ) ]
	[ PURGE(INMSG \| OUTMSG) ]
	[ SYSNAME(sysname \|`*`) ]
	[ WDSQUAL(qualifier) ]
	[ WORKSPACE( { [ STORCLAS(class-name) ] [ DATACLAS(class-name) ] [ MGMTCLAS(class-name) ] \| [ VOLUME(volume-serial) ] } [ FILESIZE([ nnnnnnnnnn \| 500 ] ) ] ) ]

Parameters

subsystem-prefix

Specifies that the RACF subsystem is the processing environment of the command. The subsystem prefix can be either the installation-defined prefix for RACF (1 - 8 characters) or, if no prefix has been defined, the RACF subsystem name followed by a blank. If the command prefix was registered with CPF, you can use the MVS command D OPDATA to display it or you can contact your RACF security administrator.

Rule: You must specify the subsystem prefix when issuing the TARGET command.

DELETE | DORMANT | OPERATIVE

Specifies whether to delete, inactivate, or activate an RRSF node or a network protocol instance for an RRSF node.

DELETE

Deletes an RRSF node or a protocol instance for the local node.

Subsequent attempts to perform operations requiring the existence of a deleted node fail and a message is issued.

When you delete a node, any workspace data sets for the node that are currently allocated are deallocated. If the workspace data sets are empty, they are also deleted.

The local node cannot be deleted until all target nodes are deleted.

The local system of a multisystem node cannot be deleted until all other targets are deleted. The TARGET command identifies the local system as the system with the SYSNAME that matches the CVTSNAME of the system the command is to run on.

For a multisystem node, the local MAIN system can be deleted only after all of its remote targets are deleted.

The MAIN system of a remote multisystem node can be deleted only after all other peer systems of that remote multisystem node are deleted.

You cannot delete a remote node with an active connection to the local node. You must first inactivate the connection using the DORMANT operand of the TARGET command.

The DELETE operand cannot be specified with DORMANT or OPERATIVE. The only operands that can be specified with DELETE are NODE, LOCAL, PROTOCOL, PURGE, and SYSNAME.

If the PURGE operand is specified with DELETE, the PURGE operand is processed first, regardless of the order in which the operands are specified.

DORMANT

Inactivates an RRSF node or a protocol instance for an RRSF node and places it in the DORMANT state.

While a node is dormant, all network communication with the node is stopped. No RRSF work or output is sent or received by the node. Existing work at the dormant node is completed but the resulting output, if any, is held in the workspace data set. Any RRSF work or output intended for a dormant node is held in the workspace data set of the sending node and is released when the dormant node becomes operative.

Once a node is dormant, the workspace data sets are allocated, if not already allocated. Therefore, no changes to the PREFIX or WORKSPACE characteristics of the data sets are allowed. See the descriptions of those operands for more information

For the local node, if you specify a protocol name for which no protocol instance exists, it is created.

If either the remote node or local node is a multisystem node, you must define a MAIN system for the multisystem node before specifying DORMANT.

The DORMANT operand cannot be specified with DELETE or OPERATIVE.

If the PURGE operand is specified with DORMANT, the DORMANT operand is processed first, regardless of the order in which the operands are specified.

OPERATIVE

Activates an RRSF node or protocol instance for a node, places it in the OPERATIVE state, and sends any new or previously held requests to the node.

The OPERATIVE operand attempts to activate the node or protocol instance for the node only if the PREFIX for the node is defined and sufficient WORKSPACE and PROTOCOL attributes are defined.

When a node is made operative, the workspace data sets are allocated, if not already allocated. Once the node is operative, no changes to the PREFIX or WORKSPACE characteristics of the data sets are allowed. See the descriptions of those operands for more information

If the node is already operative when the OPERATIVE operand is specified, the connection to that node is refreshed. No existing workspace or protocol information can be changed.

If the node is the local node and the APPC server is already registered, the server is reregistered and the APPC transaction program (TP program) is restarted for local and remote nodes.
If the node is the local node and the TCP listener process is already active, the listener is restarted.

For the local node, if you specify a protocol for which no protocol instance exists, it is created.

For a remote node, activating a second protocol converts its connection with the local node to the new protocol and, upon successful conversion, deletes the original protocol. For details about converting from one protocol to another, see the topic on changing the protocol for a connection in z/OS Security Server RACF System Programmer's Guide.

If either the remote node or the local node is a multisystem node, you must define a MAIN system to the multisystem node before specifying OPERATIVE.

The OPERATIVE operand cannot be specified with DELETE or DORMANT.

If the PURGE operand is specified with OPERATIVE, the PURGE operand is processed first, regardless of the order in which the operands are specified.

DESCRIPTION('description')

Specifies a comment that describes the node. The description is displayed in the TARGET LIST output for the node.

Rules:

The maximum length of the description is 32 characters.
If the description contains any lowercase characters, they are translated to uppercase characters.
If parentheses, commas, blanks, or semicolons are part of the description, the character string must be enclosed in single quotation marks.
If a single quotation mark is part of the description, and the entire character string is enclosed in single quotation marks, two single quotation marks must be entered together for each single quotation mark within the character string.
If the first character of the description is a single quotation mark, then the string must be entered within single quotation marks and two single quotation marks must be entered for the first character.

LIST

Lists the current operational and protocol attributes of one or more nodes.

For a multisystem node, the LIST operand displays information about the node and about the member systems that comprise the node.

The LIST function is the default function of the TARGET command under any one of the following conditions. Note that when PROTOCOL(protocol) is indicated, the protocol name must be specified without protocol attributes.

No other TARGET operand is specified.
Only PROTOCOL(protocol) is specified.
Only NODE(*) is specified.
Only NODE(*) and PROTOCOL(protocol) are specified.
Only NODE(nodename) is specified.
Only NODE(nodename) and SYSNAME(sysname) are specified.
Only NODE(nodename) and PROTOCOL(protocol) are specified for a remote node. (See Note.)
Only NODE(nodename), SYSNAME(sysname), and PROTOCOL(protocol) are specified for a remote multisystem node. (See Note.)
Only NODE(nodename) and SYSNAME(*) are specified.
Only NODE(nodename), SYSNAME(*), and PROTOCOL(protocol) are specified for a remote multisystem node.

Note: When PROTOCOL(protocol) is specified with the name of the local node, LIST is not the default function. Instead, a protocol instance for the specified protocol, if not already established, is added to the local node. For information about adding a protocol instance to the local node, see z/OS Security Server RACF System Programmer's Guide.

When LIST is specified in combination with any other operand, LIST displays the operational and protocol attributes as they exist after RACF processes the other TARGET operands.

The LIST operand displays a summary or a detailed list of information for a node, depending on the options specified with NODE, if any, as shown in Table 1.

When NODE is omitted, a summary is displayed for all nodes known to the node where the command executes.

Table 1. Type of output displayed when you specify LIST with the following TARGET options
TARGET LIST options	Local node	Single-system node	Multisystem node
None	Summary	Summary	Summary
PROTOCOL(protocol)	Summary	Summary
NODE(nodename)	Detailed	Detailed
NODE(nodename) PROTOCOL(protocol)
NODE(*)			Detailed
NODE() PROTOCOL(protocol*)
NODE(nodename) SYSNAME(systemname)		Not applicable
NODE(nodename) SYSNAME(systemname) PROTOCOL(protocol)
NODE(nodename) SYSNAME(*)
NODE(nodename) SYSNAME() PROTOCOL(protocol*)

PROTOCOL(protocol): Displays a summary of only nodes, including systems on multisystem nodes, that contain an instance of the specified protocol.
NODE(nodename): For a remote single-system node or the local node, displays a detailed list of the specified node.
For a multisystem node, displays a summary for each member system of the multisystem node.
NODE(nodename) PROTOCOL(protocol): When specified with no other operands for a remote node, displays a detailed list of the specified node only when it contains an instance of the specified protocol. If it does not, no node information is displayed.
When specified with LIST and other operands for a remote node, protocol information is displayed after all other operands are processed. If the specified protocol instance does not exist for the specified node, it is added and then listed.

Note: For the local node, these options add a protocol instance for the specified protocol if it does not already exist.
NODE(*): Displays a detailed list, sorted by node name, of all known nodes including systems on multisystem nodes.
NODE(*) PROTOCOL(protocol): Displays a detailed list, sorted by node name, of only nodes, including systems on multisystem nodes, that contain an instance of the specified protocol.
NODE(nodename) SYSNAME(systemname): Displays a detailed list of the specified system.
NODE(nodename) SYSNAME(systemname) PROTOCOL(protocol): Displays a detailed list of the specified system for a remote multisystem node only if the system contains an instance of the specified protocol. If it does not, no system information is displayed.
NODE(nodename) SYSNAME(*): Displays a detailed list of each system in the multisystem node.
NODE(nodename) SYSNAME(*) PROTOCOL(protocol): Displays a detailed list of only those systems in the specified node that contain an instance of the specified protocol.

LISTPROTOCOL

Lists the current operational and protocol attributes of one or more nodes and lists the protocol name of each listed node.

Specify LISTPROTOCOL when you have a mixed protocol network and want to list protocol attributes with the summary information for each remote node. By contrast, LIST displays a summary list that includes protocol information only when the node has more than one protocol defined. The LISTPROTOCOL option allows you to avoid displaying a detailed list of all nodes and systems when you want to review protocol information.

LOCAL

Defines the node specified with the NODE operand as the local node and defines any other TARGET operand as a local node attribute. You can define only one local node.

If you omit LOCAL, the specified node is defined as a remote node.

Rule: You must define the local node before attempting to activate a remote node. This is because information about the local node is used to allocate and process the RRSF workspace data sets of the remote node.

Once you define a node as the local node, you need not specify LOCAL on subsequent TARGET commands issued for the same node or for systems you add to the local multisystem node.

MAIN

Defines the system specified with the SYSNAME operand as the main system in a multisystem node.

Rules:

Define the same main system on each system in the multisystem node and on each node that communicates with the multisystem node.
Define the main system of a multisystem node before attempting to activate or inactivate any system in the multisystem node.
For a remote node, you must specify MAIN and SYSNAME when adding another protocol to the main system of a multisystem node.

NODE(nodename |*)

Defines the name of a new RRSF node or specifies the name of the node being listed or modified.

Rule: You must define a node name for the local node and any node that communicates with the local node.

nodename

Specifies the name of the node.

Guideline: Choose a name that is meaningful because users frequently specify node when issuing the RACLINK command and when specifying the AT and ONLYAT operands of several RACF commands.

Syntax rules:

The maximum length is 8 characters.
The first character of the name must be one of the following:
A - Z, # (X'7B'), $ (X'5B'), or @ (X'7C')
Each remaining character of the name must be one of the following:
A - Z, 0 - 9, # (X'7B'), $ (X'5B'), or @ (X'7C')

*

Specifies all nodes and systems when specified with only the LIST operand. If any other operand of the TARGET command is specified with NODE(*), the command fails.

PREFIX(qualifier …)

Defines the high-level qualifiers that RACF uses to determine the workspace data set names for the specified node. (Use the WORKSPACE operand to specify the other attributes of the workspace data sets.)

Rule: You must define the prefix for a node before using the OPERATIVE or DORMANT operand.

Once the workspace data sets are allocated (when you issue OPERATIVE or DORMANT), you cannot change the prefix.

qualifier

Specifies one or more data set qualifiers as the highest level qualifiers of the workspace data set names. If you specify multiple qualifiers, they must be separated by periods.

The maximum length of the PREFIX value is 19 characters including periods.

Example:

PREFIX(RSFJ.WORK.NODE1)

Important: When selecting a prefix, ensure that the workspace data sets are protected by a data set profile, and that the user ID associated with the RACF subsystem address space has authority to create and access them.

Guideline: Define the same prefix for each member system in a local or remote multisystem node.

PROTOCOL

Specifies the name of the network protocol or defines protocol attributes for the specified node. You can change protocol attributes only when the node is in the initial, DORMANT, or DEFINED state.

The local node can support multiple protocol instances. For remote nodes, adding a second protocol instance is intended to convert the protocol of the node. For details about converting from one protocol to another, see the topic on changing the protocol for a connection in z/OS Security Server RACF System Programmer's Guide.

For a remote node, you can specify the protocol name without protocol attributes to qualify other TARGET keywords when multiple protocols exist for the specified node. Specifying the protocol name is optional when the remote node has only one protocol instance.

Example:

TARGET NODE(NODE5) PROTOCOL(TCP) DESCRIPTION('MY TCP NODE')

If no protocol instance exists for the specified node and protocol, RACF attempts to create it unless one of the following conditions is found:

LIST is the default function of the TARGET command.
For details describing when LIST is the default function, see the LIST operand.
PROTOCOL is specified with the DELETE or LIST operand.

Tip: When you specify PROTOCOL(TCP) with no protocol attributes for the local node, a usable protocol instance for the specified protocol is created based on default values for the local node. (The same does not apply when you specify PROTOCOL(APPC) because you must specify APPC protocol attributes.)

When you specify a protocol name with no other operands for a remote node, the TARGET LIST function displays information for only nodes that contain the specified protocol instance. (See the description of TARGET LIST for more details.)

Specify only one protocol name per TARGET command. If you specify more than one protocol, only the second one is processed. To define multiple protocols for a node, issue multiple TARGET commands.

Do not specify PROTOCOL for the local node when it is running in local mode.

APPC

Specifies that APPC is the network protocol for the node. This is the default value.

LUNAME(luname)

Defines or changes the logical unit (LU) name associated with the node. You can define or change the LU name when the node is in the initial or DEFINED state. For the local node, you can also change the LU name only if no remote APPC node is already using it and only when the local node is in the initial or DORMANT state.

The LU name can be found in the ACBNAME specification in the APPCPMxx member of SYS1.PARMLIB for the node.

Rule: You must define an LU name for the local node and an LU name for a remote node before making the connection between them dormant or operative.

luname

Specifies the LU name as either one of the following:

An unqualified LU name of 1 - 8 characters.
A qualified LU name of 1 - 17 characters in the form of netid.luname, where netid and luname are each 1 - 8 characters separated by a period.

The output of the TARGET LIST command contains the qualified LU name if it is defined.

The LUNAME value you specify is used to determine the names of the RRSF workspace data sets. See the description of the WORKSPACE operand for details.

RACF performs no validity checking on the specified LU name value. You must ensure that the specified LU name is correct.

TPNAME(profile-name)

Defines or changes the APPC transaction program (TP) profile for the node.

profile-name: Specifies a 1 - 64 character name.

If TPNAME is omitted, the default value is IRRRACF.

MODENAME(mode-name)

Defines or changes the APPC mode name that designates the network properties for the session to be allocated.

For information about APPC modes, see z/OS Communications Server: SNA Programmer's LU 6.2 Guide.

mode-name: Specifies a 1 - 8 character name consisting of alphanumeric characters.

If MODENAME is omitted, the default is IRRMODE. If omitted, the MODENAME value is listed as <NOT SPECIFIED> in the TARGET LIST output.

TCP

Specifies that TCP/IP is the network protocol for the node. The TCP option is valid only for systems running z/OS V1R13 and higher.

ADDRESS(address)

Defines or changes the host name or IPv4 address of the remote node. You need not define ADDRESS for the local node.

address: Specifies a 1 - 255-character address expressed as a host name or a static IP address. Lowercase characters in the host name are translated to uppercase characters. An IP address may be specified as an IPv4 address or an IPv6 address (if TCP IPv6 is enabled on the system).

If omitted, the default value for the local node is 0.0.0.0, or :: if TCP IPv6 is enabled on the system. If omitted for a remote node, the address is listed as <NOT SPECIFIED> in the TARGET LIST output.

You must define ADDRESS for a remote node before activating it using the OPERATIVE operand.

RACF performs no validity checking on the specified ADDRESS value. You must ensure that the specified address is correct.

If IPv6 is enabled on the system, TARGET LIST detailed output will display resolved IPv6 addresses, where possible.

PORTNUM(number)

Defines or changes the port number.

number: Specifies the port on which the node establishes the TCP socket to listen for requests initiated by a node.
This value must be in the range of 1 to 65535. However, network conventions and existing port assignments will likely further restrict the value that you can choose.

If PORTNUM is omitted, the default value is 18136.

Guidelines:

Accept the default value unless port 18136 is already in use.
Use the same port for all RRSF nodes.

PURGE(INMSG)

PURGE(OUTMSG)

Specifies that all entries in the INMSG or OUTMSG workspace data set for the specified node are to be purged.

You can purge an INMSG or OUTMSG workspace data set only when the node is dormant.

When PURGE is specified with DORMANT, the DORMANT operand is processed first, regardless of the order in which the operands are specified.

When PURGE is specified with DELETE or OPERATIVE, the PURGE operand is processed first, regardless of the order in which the operands are specified.

SYSNAME(sysname | *)

Defines the name of a new system in a multisystem node or specifies the name of the system being modified or listed. You cannot change the name of a system. If the specified name does not exist for the node, it is created.

If the SYSNAME operand is specified, you must also specify NODE. The SYSNAME operand is required for multisystem nodes. If it is not specified, RACF assumes that the node is a single-system node. The SYSNAME operand is not required if LIST is specified or defaulted.

When the TARGET command is for the local node, and you specify OPERATIVE or DORMANT, RACF compares the SYSNAME you specified with the CVTSNAME of the system where the command is to run. If they do not match, RACF does not process the OPERATIVE or DORMANT operand. The same is true for a SYSNAME value of a target system that does not match its CVTSNAME when you specify SYSNAME(*) with OPERATIVE or DORMANT for the local node. In addition, because a conversation should not exist between the systems of a multisystem node, RACF issues an informational message and places it in the SYSLOG. This message might help diagnose why an expected conversation was not established.

sysname

Specifies the name of the system in a multisystem node.

The sysname value must match the value in the CVTSNAME field of the system being modified or listed.

Syntax rules:

The maximum length is 8 characters.
The first character of the name must be one of the following:
A - Z, # (X'7B'), $ (X'5B'), or @ (X'7C')
Each remaining character of the name must be one of the following:
A - Z, 0 - 9, # (X'7B'), $ (X'5B'), or @ (X'7C')

*

Specifies all systems currently defined for the specified node but only when specified with the NODE, DORMANT, OPERATIVE, DELETE, PURGE, or LIST operand.

Tip: Use SYSNAME(*) to issue a common set of TARGET commands on all the systems in a multisystem node.

When specified with DORMANT, OPERATIVE, DELETE, or PURGE, the requested action is attempted for all systems defined for the specified node. If any other operand of the TARGET command is specified with SYSTEM(*), the command fails.

Specify SYSNAME(*) with LIST to display a detailed list of each system in a specified node. If NODE(*) is specified, SYSNAME must be specified as SYSNAME(*) or omitted.

WDSQUAL(qualifier)

Specifies a substitute qualifier for RACF to use to determine the names of the workspace data sets for the specified RRSF node.

qualifier: Specifies a data set name qualifier consisting of 1 - 8 characters. The first character must be alphabetic.

For details about the naming conventions for work space data sets, see "Workspace data sets" in z/OS Security Server RACF System Programmer's Guide.

Guideline: Specify WDSQUAL when the CVTSNAME of the local node or the LU name of a remote APPC node would not render syntactically valid names for the workspace data sets.

For the local node, WDSQUAL specifies the second qualifier of the workspace data set names. If you omit WDSQUAL, the second qualifier defaults to the CVTSNAME name of the local system. The WDSQUAL value also propagates as the second qualifier of the workspace data set names for remote TCP nodes, but not for APPC nodes.

For a remote node, WDSQUAL specifies the third qualifier of the workspace data set names, substituting for the remote qualifier value.

You can change WDSQUAL for a node that is either in the defined or initial state. You cannot change WDSQUAL for a node in the DORMANT nor OPERATIVE state. If you preallocated the workspace data sets, you cannot change the WDSQUAL value.

Important: When selecting a WDSQUAL qualifier, ensure that the workspace data sets are protected by a data set profile, and that the user ID associated with the RACF subsystem address space has authority to create and access them.

WORKSPACE

Specifies the data set characteristics of two workspace data sets for the specified node. RRSF uses these two message queues to control information and messages associated with work being processed for the node.

The values you supply with the PREFIX, WDSQUAL, and WORKSPACE operands are used to determine the fully qualified names, size, and data management characteristics of the workspace data sets.

For details about the naming conventions for work space data sets, see "Workspace data sets" in z/OS Security Server RACF System Programmer's Guide.

If you opt to preallocate the workspace data sets, see "Defining the workspace data sets" in z/OS Security Server RACF System Programmer's Guide for details.

Guideline: Allow RACF to allocate your workspace data sets for you.

Unless already allocated, RACF allocates two workspace data sets for each node whenever you activate or inactivate the node using the DORMANT or OPERATIVE operands. No workspace data sets are allocated for peer systems in the same multisystem node or for non-main members between two multisystem nodes.

Once the workspace data sets are allocated, you cannot change the data set characteristics by specifying options of the WORKSPACE operand, although you can modify WORKSPACE values. When you display WORKSPACE information using the TARGET LIST command, be aware that the values listed might not be values in effect at the time the data sets were allocated.

Guideline: For multisystem nodes, ensure that all workspace data sets are allocated on shared resources so that all member systems of the multisystem node can access each workspace data set.

With the WORKSPACE operand, you can specify that RACF allocate your workspace data sets on a particular volume or use system-managed storage (SMS). The STORCLAS, DATACLAS, and MGMTCLAS suboperands of WORKSPACE apply to an SMS allocation. The VOLUME suboperand applies to a non-SMS allocation. The FILESIZE suboperand applies to either.

STORCLAS(class-name): Specifies the SMS storage class name. For an SMS allocation, STORCLAS is required.
DATACLAS(class-name): Specifies the SMS data class name. For an SMS allocation, DATACLAS is optional.
MGMTCLAS(class-name): Specifies the SMS management class name. For an SMS allocation, MGMTCLAS is optional.
VOLUME(volume-serial): Specifies the volume serial number. For a non-SMS allocation, VOLUME is required. The volume-serial specified must be a valid volume on the system where the TARGET command is issued.
You cannot specify VOLUME with either STORCLAS, MGMTCLAS, or DATACLAS.
FILESIZE(nnnnnnnnnn |500): Specifies that the space allocated for the workspace data sets should be sufficient to contain nnnnnnnnnn records in each data set. If you omit FILESIZE, the default value is 500 records.
The allowable range of values for FILESIZE is 1 - 2147483647 records. RACF invokes Access Methods Services to issue the DEFINE CLUSTER command that allocates the RRSF work data sets and specifies your FILESIZE value as the RECORDS value. Note that your actual allocation might be less than specified if you specify a FILESIZE value that exceeds the current maximum RECORDS value.

Examples


Example 1	Operation	User ADMIN wants a summary list of the current operational attributes for all nodes in the RRSF configuration.
	Known	The RACF subsystem prefix is `<`.
	Command	`<TARGET`
	Defaults	Because no operands are specified, LIST is the default. Because NODE is not specified, the command defaults to a summary listing for all target nodes known to the node the command runs on.
	Output	See Figure 1.

Example 2	Operation	User ADMIN wants a summary list of protocol status information for all target nodes and a detailed list of protocol status information for the local node.
	Known	The RACF subsystem prefix is `<`.
	Command	`<TARGET LISTPROTOCOL`
	Defaults	None.
	Output	See Figure 2.

Example 3	Operation	User ADMIN at POKMVSA wants to define POKMVSA as the local APPC node for an RRSF configuration, list the node, and make it operative.
	Known	The RACF subsystem prefix is `@`. POKMVSA has DFP non-SMS running. The volume that contains the workspace data sets is DASD01. The high-level qualifier for the workspace data sets is SYS1.RACF. The APPC LUNAME is MF1AP001. APPC and VTAM® have been installed and configured. Because the LIST operand is specified in combination with other TARGET operands, the information displayed provides the operational and protocol attributes as they exist after the processing of the other operands.
	Command	`@TARGET NODE(POKMVSA) LOCAL DESCRIPTION('POUGHKEEPSIE MVS SYSTEM A') PREFIX(SYS1.RACF) WORKSPACE(VOLUME(DASD01)) PROTOCOL(APPC(LUNAME(MF1AP001))) OPERATIVE LIST`
	Defaults	The APPC TP name defaults to IRRRACF. FILESIZE defaults to 500.
	Output	See Figure 3.

Example 4	Operation	User ADMIN at NODE1 wants a detailed list of the current operational attributes for the local node, which has both APPC and TCP protocol information defined.
	Known	The RACF subsystem prefix is `<`.
	Command	`<TARGET LIST NODE(NODE1)`
	Defaults	None.
	Output	See Figure 4.

Example 5	Operation	User ADMIN at NODE1 wants to define NODE2 as a remote TCP/IP node for an RRSF configuration, list the node, and make it operative.
	Known	The RACF subsystem prefix is `<`. NODE1 has DFP non-SMS running. The volume that contains the workspace data sets is DASD01. The high-level qualifier for the workspace data sets is SYS1.RRSF. The TCP/IP host name is MVS5.POK.OURS.COM. Because the LIST operand is specified in combination with other TARGET operands, the information displayed provides the operational and protocol attributes as they exist after the processing of the other operands.
	Command	`<TARGET NODE(NODE2) PROTOCOL(TCP(ADDRESS(MVS5.POK.OURS.COM))) PREFIX(SYS1.RRSF) WORKSPACE(VOLUME(DASD01)) OPERATIVE LIST`
	Defaults	The TCP PORTNUM defaults to 18136. FILESIZE defaults to 500.
	Output	See Figure 5.

Example 6	Operation	User ADMIN wants to purge the OUTMSG workspace data set for node POKMVSB.
	Known	The RACF subsystem prefix is `@`. POKMVSB must be dormant to purge the workspace data sets. When the PURGE and DORMANT operands are specified together, the DORMANT operand is processed first.
	Command	`@TARGET NODE(POKMVSB) PURGE(OUTMSG) DORMANT`
	Defaults	None.
	Results	User ADMIN receives an informational message. `@IRRM021I RACF SUBSYSTEM PURGE OF NODE POKMVSB OUTMSG FILE SYS1.RACF.POKMVSA.OUTMSG IS COMPLETE. @IRRM002I RACF SUBSYSTEM TARGET COMMAND HAS COMPLETED SUCCESSFULLY.`

Example 7	Operation	User ADMIN wants to delete node POKMVSC from the set of known target nodes.
	Known	The RACF subsystem prefix is `@`. POKMVSC is already dormant.
	Command	`@TARGET NODE(POKMVSC) DELETE`
	Defaults	None.

Figure 1. Summary TARGET LIST output

<TARGET                                                                 
IRRM009I (<) LOCAL RRSF NODE NODE1 IS IN THE OPERATIVE ACTIVE STATE.    
IRRM091I (<)      - LOCAL NODE TCP LISTENER IS ACTIVE.                  
IRRM091I (<)      - LOCAL NODE APPC LISTENER IS ACTIVE.                 
IRRM009I (<) REMOTE RRSF NODE NODE2 IS IN THE OPERATIVE ACTIVE STATE.   
IRRM009I (<) REMOTE RRSF NODE NODE3 IS IN THE OPERATIVE PENDING         
             CONNECTION STATE.                                          
IRRM009I (<) REMOTE RRSF NODE NODE4 IS IN THE OPERATIVE PENDING         
             CONNECTION STATE.                                          
IRRM009I (<) REMOTE RRSF NODE NODE5 IS IN THE OPERATIVE PENDING         
             CONNECTION STATE.

Figure 2. TARGET LISTPROTOCOL output

<TARGET LISTPROTOCOL                                                 
IRRM009I (<) LOCAL RRSF NODE NODE1 IS IN THE OPERATIVE ACTIVE STATE. 
IRRM091I (<)      - LOCAL NODE TCP LISTENER IS ACTIVE.               
IRRM091I (<)      - LOCAL NODE APPC LISTENER IS ACTIVE.              
IRRM009I (<) REMOTE RRSF NODE NODE2 PROTOCOL APPC IS IN THE OPERATIVE
             ACTIVE STATE.                                           
IRRM009I (<) REMOTE RRSF NODE NODE3 PROTOCOL APPC IS IN THE OPERATIVE
             PENDING CONNECTION STATE.                               
IRRM009I (<) REMOTE RRSF NODE NODE4 PROTOCOL TCP IS IN THE OPERATIVE 
             PENDING CONNECTION STATE.                               
IRRM009I (<) REMOTE RRSF NODE NODE5 PROTOCOL TCP IS IN THE OPERATIVE 
             PENDING CONNECTION STATE.

Figure 3. Detailed TARGET LIST output for a local APPC node

@TARGET NODE(POKMVSA) LOCAL DESCRIPTION('POUGHKEEPSIE MVS SYSTEM A') 
 PREFIX(SYS1.RACF) WORKSPACE(VOLUME(DASD01)) PROTOCOL(APPC(LUNAME(MF1AP001))) 
 OPERATIVE LIST
IRRM010I (@) RSWJ SUBSYSTEM PROPERTIES OF LOCAL RRSF NODE POKMVSA:
   STATE       - OPERATIVE ACTIVE                                        
   DESCRIPTION - "POKR MVS SYSTEM A"                                      
   PROTOCOL    - APPC                                                    
                 LU NAME          - MF1AP001                             
                 TP PROFILE NAME  - IRRRACF                              
                 MODENAME         - <NOT SPECIFIED>                      
                 LISTENER STATUS  - ACTIVE                               
   TIME OF LAST TRANSMISSION TO   - <NONE>                               
   TIME OF LAST TRANSMISSION FROM - <NONE>                               
   WORKSPACE FILE SPECIFICATION                                          
         PREFIX                   - "SYS1.RACF"                          
         WDSQUAL                  - <NOT SPECIFIED>                      
         FILESIZE                 - 500                                  
         VOLUME                   - DASD01                               
         FILE USAGE                                                      
                 "SYS1.RACF.NODE1.INMSG"                                 
                                  - CONTAINS 0 RECORD(S)                 
                                  - OCCUPIES 1 EXTENT(S)                 
                 "SYS1.RACF.NODE1.OUTMSG"                                
                                  - CONTAINS 0 RECORD(S)                 
                                  - OCCUPIES 1 EXTENT(S)

Figure 4. Detailed TARGET LIST output for a local node that supports multiple protocols

<TARGET LIST NODE(NODE1)                                              
IRRM010I (<) RSWJ SUBSYSTEM PROPERTIES OF LOCAL RRSF NODE NODE1:      
   STATE       - OPERATIVE ACTIVE                                     
   DESCRIPTION - <NOT SPECIFIED>                                      
   PROTOCOL    - TCP                                                   
                 HOST ADDRESS     - 0.0.0.0                            
                 IP ADDRESS       - 9.57.1.243                         
                 LISTENER PORT    - 18136                              
                 LISTENER STATUS  - ACTIVE                             
   PROTOCOL    - APPC                                                  
                 LU NAME          - MF1AP001                           
                 TP PROFILE NAME  - IRRRACF                            
                 MODENAME         - <NOT SPECIFIED>                    
                 LISTENER STATUS  - ACTIVE                             
   TIME OF LAST TRANSMISSION TO   - <NONE>                             
   TIME OF LAST TRANSMISSION FROM - <NONE>                             
   WORKSPACE FILE SPECIFICATION                                        
         PREFIX                   - "SYS1.RRSF"                        
         WDSQUAL                  - <NOT SPECIFIED>                    
         FILESIZE                 - 500                                
         VOLUME                   - TEMP01                             
         FILE USAGE                                                    
                 "SYS1.RRSF.NODE1.INMSG"                               
                                  - CONTAINS 0 RECORD(S)               
                                  - OCCUPIES 1 EXTENT(S)               
                 "SYS1.RRSF.NODE1.OUTMSG"                              
                                  - CONTAINS 0 RECORD(S)               
                                  - OCCUPIES 1 EXTENT(S)

Figure 5. Detailed TARGET LIST output for a remote TCP/IP node

<TARGET LIST NODE(NODE2)                                                
IRRM010I (<) RSWJ SUBSYSTEM PROPERTIES OF REMOTE RRSF NODE NODE2:       
   STATE       - OPERATIVE ACTIVE                                       
   DESCRIPTION - <NOT SPECIFIED>                                        
   PROTOCOL    - TCP                                                    
                 HOST ADDRESS     - MVS5.POK.OURS.COM                  
                 IP ADDRESS       - 9.57.1.13                           
                 LISTENER PORT    - 18136                               
                 AT-TLS POLICY:                                         
                   RULE_NAME      - RRSF-CLIENT                         
                   CIPHER ALG     - 35 TLS_RSA_WITH_AES_256_CBC_SHA     
                   CLIENT AUTH    - REQUIRED                            
   TIME OF LAST TRANSMISSION TO   - 16:45:39 DEC 15, 2010               
   TIME OF LAST TRANSMISSION FROM - 16:45:40 DEC 15, 2010               
   WORKSPACE FILE SPECIFICATION                                         
         PREFIX                   - "SYS1.RRSF"                         
         WDSQUAL                  - <NOT SPECIFIED>                     
         FILESIZE                 - 500                                 
         VOLUME                   - DASD01                              
         FILE USAGE                                                     
                 "SYS1.RRSF.NODE1.NODE2.INMSG"                          
                                  - CONTAINS 0 RECORD(S)                
                                  - OCCUPIES 1 EXTENT(S)                
                 "SYS1.RRSF.NODE1.NODE2.OUTMSG"                         
                                  - CONTAINS 0 RECORD(S)                
                                  - OCCUPIES 1 EXTENT(S)