IBM AnyNet and SNA/APPN Configuration

Resolving The Problem

Important Note: Starting in i 7.1, AnyNet (a method used to run SNA communications traffic over IP) is no longer supported. Users of AnyNet are encouraged to migrate to Enterprise Extenders as a replacement. For information about migrating to Enterprise Extenders from AnyNet, see the Migrating from AnyNet to Enterprise Extender topic in the IBM i Information Center.

If you have an existing SNA/APPN configuration and are also configuring IBM AnyNet, the Control Point Name cannot be used from a remote IBM iSeries family of servers Network Attributes for the system for the ANY parameter (RMTCPNAME, RMTLOCNAME). Connectivity problems may be encountered.

SNA applications such as Display Station Passthrough may receive the following messages: CPF8933 with RC80140001: route to specified location not found.

Users may also see SRCB6007101 msg-state 4060 F/#1MTASK: The request for a route has failed. ROUTE_NOT_AVAILABLE condition has been detected. No destination NN or Virtual nodes available for intermediate routing.

To solve this problem, use the Display APPN Information (DSPAPPNINF) command. This will show valid routing information. If you require a *LENNODE type connection like AnyNet between two APPN network nodes, configure the RMTCPNAME in the AnyNet controller description as something other than the actual control point name on the adjacent system.

Configuring an AnyNet (*LENNODE) controller and using the actual Control Point Name may cause a continuous topology update problem. If a problem occurs, the Control Point Presentation Services (CPPS) or the topology routing services (TRS) task continually shows a high CPU utilization (greater than 30%). When the number of network nodes and improperly configured *LENNODES increases in a network, the problem becomes more severe.