To build the NCPROUTE profile, create a data set and specify its
name in the //NCPRPROF DD statement in the NCPROUTE cataloged procedure.
You can find a sample in SEZAINST(EZBNRPRF). Include configuration
statements in this data set to define SNMP functions and to identify
the NCPROUTE gateways data set. For more information, see z/OS Communications Server: IP Configuration
Reference.
- RIP_SUPPLY_CONTROL supply_control
- Specifies one of the following options on a server-wide
basis:
- RIP1—Unicast/Broadcast RIP Version 1 packets (Default)
- RIP2B—Unicast/Broadcast RIP Version 2 packets (Not Recommended)
- RIP2M—Unicast/Multicast/Broadcast RIP packets (Migration)
- RIP2—Unicast/Multicast RIP Version 2 packets
- NONE—Disables sending RIP packets
Note: If RIP2 is specified, the RIP Version 2 packets are multicast over multicast-capable interfaces only. No RIP packets are sent over multicast-incapable interfaces. For RIP2M, the RIP Version 2 packets are multicast over multicast-capable interfaces and RIP Version 1 packets over multicast-incapable interfaces. For RIP2B, the RIP Version 2 packets are unicast or broadcast; this option is not recommended because host route misinterpretations by adjacent routers running RIP Version 1 can occur. For this reason, RIP2B may become obsolete in a future release. For point-to-point interfaces that are non-broadcast and multicast-incapable, the RIP Version 2 packets are unicast. - RIP_RECEIVE_CONTROL receive_control
- Specifies
one of the following options on a server-wide basis:
- RIP1—Receive RIP Version 1 packets only
- RIP2—Receive RIP Version 2 packets only
- ANY—Receive any RIP Version 1 and 2 packets (Default)
- NONE—Disables receiving RIP packets
Note: If the client NCP does not support variable subnetting, the default of ANY is changed to RIP1. - RIP2_AUTHENTICATION_KEY authentication_key
- Specifies
a plain text password authentication_key containing
up to 16 characters. The key is used on a router-wide basis and can
contain mixed case and blank characters. Single quotes (') can be
included as delimiters to include leading and trailing blanks. The
key will be used to authenticate RIP Version 2 packets and be included
in the RIP updates for authentication by adjacent routers running
RIP Version 2. For maximum security, set RIP_SUPPLY_CONTROL and RIP_RECEIVE_CONTROL
to RIP2. This will discard RIP1 and unauthenticated RIP2 packets.
A blank key indicates that authentication is disabled. The following
examples are examples of authentication passwords:
my password (no leading or trailing blanks) ' my password ' (leading and trailing blanks) ''abc'' (single quotes part of password) ' ' (5-character blanks) - SNMP_AGENT host_name
- Specifies the host name or IP address of the host running an SNMP daemon. Only one NCPROUTE server can use a particular SNMP agent at a time.
- SNMP_COMMUNITY community_name
- Specifies a community name that SNMP applications must use to access data that the agent manages. Protect this information accordingly.
- GATEWAY_PDS dsname
- Specifies the optional partitioned data set that contains GATEWAY information for each client NCP. Quotation marks are not needed when specifying dsname. One member for each NCP client of this data set must be configured to match the NCP NEWNAME parameter with the P suffix which is the same as the NCP’s RIT member name. See Step 8: Configure the NCPROUTE gateways data set (Optional) for information on defining the statements necessary for the members of this data set.
Note: You can use a semicolon in column 1 to permit
comments in the profile. Blank lines are also permitted.
Figure 1 shows the relationship between the data set names specified in the NCPROUTE cataloged procedure and the NCPROUTE profile, as well as the relationship between the members of the gateways PDS and the ncpload PDS.
Figure 1. NCPROUTE data sets relationship