Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
The Remove TCP/IP Route (RMVTCPRTE) command removes a previously identified route from the Transmission Control Protocol/Internet Protocol (TCP/IP) configuration.
Five parameter values uniquely define a route. These values are the route destination (RTEDEST), the subnet mask (SUBNETMASK), the type of service (TOS), the internet address of the next system on the route (NEXTHOP), and the preferred binding interface (BINDIFC). For default routes and default multicast routes (*DFTROUTE and *DFTMCAST), the NEXTHOP, TOS and BINDIFC values uniquely define the route because the SUBNETMASK is always *NONE.
Note: When a RMVTCPRTE command is entered using option 4 of the Work with TCP/IP Routes display, a confirmation display is shown. This display warns that the removal of a route might affect active TCP connections and that unpredictable results might occur. A confirmation display is not shown when the RMVTCPRTE CL command is issued directly.
Restrictions:
Top |
Keyword | Description | Choices | Notes |
---|---|---|---|
RTEDEST | Route destination | Character value, *DFTROUTE, *DFTMCAST | Required, Positional 1 |
SUBNETMASK | Subnet mask | Character value, *NONE, *HOST | Required, Positional 2 |
TOS | Type of service | *MINDELAY, *MAXTHRPUT, *MAXRLB, *MINCOST, *NORMAL | Optional, Positional 3 |
NEXTHOP | Next hop | Character value | Optional |
BINDIFC | Preferred binding interface | Character value, *NONE | Optional |
Top |
Specifies the route destination being removed. You must specify all 4 bytes that make up an internet address though some of the bytes may be equal to 0. For example, a route to all the hosts on the 9.5.11 subnetwork is identified by entering 9.5.11.0 for the route destination. Used in combination with a subnetmask, type of service value, and next hop, the route destination uniquely identifies a route to a network or system.
Note: When RTEDEST(*DFTMCAST) is specified, then SUBNETMASK(*NONE) must also be specified and the NEXTHOP parameter must be a local TCP/IP interface (on this system).
Any combination thereof means that you may specify a route, such as 9.5.0.0 to the hosts on the 9.5 subnet, even though all 9.5.x.x addresses are class A network addresses.
Exceptions:
Top |
Specifies a bit mask that identifies to TCP/IP which bits of the value specified for the route destination (RTEDEST) compose the network and subnet portions of the internet address. By defining the network portion and subnetwork portion of the RTEDEST address, the subnet mask also defines which bits of the RTEDEST address make up the host portion. The mask is a 32-bit combination that is logically ANDed with the internet address to determine a particular subnetwork. The bits of the mask set to the value one (1) determine the network and subnetwork portions of the address. The bits set to the value zero (0) determine the host portion of the address.
Top |
Specifies the type of service to be used. The type of service defines how the internet hosts and routers should make trade-offs between throughput, delay, reliability, and cost.
*NORMAL: Normal service is used for delivery of data.
*MINDELAY: Minimize delay means that prompt delivery is important for data on this connection.
*MAXTHRPUT: Maximize throughput means that a high data rate is important for data on this connection.
*MAXRLB: Maximize reliability means that a higher level of effort to ensure delivery is important for data on this connection.
*MINCOST: Minimize monetary cost means that lower cost is important for data on this connection.
Top |
Specifies the internet address of the next system (gateway) on the route.
Top |
Preferred Binding Interface (BINDIFC). Specify the IP interface this route will be bound to. The bind is absolute.
Note: This parameter is useful only when there are multiple interfaces defined on your system for the same network. BINDIFC allows you to define which interface should be used to reach the network for a particular route destination. In this way you can distribute traffic (load balancing) across multiple interfaces so all routes do not use the same interface to reach the network.
If the IP interface you specify is active, this route will bind to it, otherwise it will follow the normal route binding rules (which are also used when BINDIFC is defined as *NONE).
Top |
Example 1: Removing a Route
RMVTCPRTE RTEDEST('132.65.0.0') SUBNETMASK('255.65.0.0') TOS(*MINDELAY) NEXTHOP('9.5.15.1')
This command removes the route identified as 132.65.0.0 with a subnetmask of 255.65.0.0, a type of service of *MINDELAY, and a next hop of 9.5.15.1.
Example 2: Removing a Default Route
RMVTCPRTE RTEDEST(*DFTROUTE) SUBNETMASK(*NONE) NEXTHOP('186.34.76.92')
This command removes a host route identified as a default route (*DFTROUTE). The subnetmask is specified as *NONE and the type of service defaults to *NORMAL. The subnetmask, type of service, and next-hop value differentiate this *DFTROUTE from the other possible eight *DFTROUTE entries.
Top |
*ESCAPE Messages
Top |