IBM Support

IBM AnyNet Configuration (SNA over TCP/IP)

Troubleshooting


Problem

This document lists configuration considerations for AnyNet.

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.


Notes:
1.Before configuring AnyNet between two IBM eServer i5 systems, a TCP connection must be working between these systems. This can usually be tested by PINGing or TELNETing to the host system (target system) name. If you are unable to TELNET, complete the TCP/IP configuration.
2.References to the source system indicate the system that the APPC application is being initiated on. References to the target system indicate the system that is the destination for the APPC application.

Collect the Network Attributes from both systems (DSPNETA).

On the source system, create a HOST TABLE ENTRY by doing the following:
1.On the operating system command line, type the following:

CFGTCP

Press the Enter key.
2.Select Option 10, Work with TCP/IP host table entries, and press the Enter key.
3.Type 2 (to change) next to the HOST (target system) name, and press the Enter key.
4.Type + (plus sign) in the single field by HOST NAME, and press the Enter key.
5.Type HOSTNAME.RMTNETID.SNA.IBM.COM

where:
HOSTNAME is the local location name of the target system (per the Network Attributes)
RMTNETID is the default net ID of the target system (per the Network Attributes)
SNA.IBM.COM is a required HOST NAME extension.

To create an APPC controller (CRTCTLAPPC) on the source system, do the following:
1.On the operating system command line, type the following:

CRTCTLAPPC

Press the Enter key.
2.LINKTYPE must be *ANYNW.

Note: With the link type of *ANYNW, there will not be an attached line prompt or parameter.
3.Type the RMTNETID (Remote Net ID), which is the Local Net ID from the target system network attributes.
4.Type the RMTCPNAME (Remote Control Point Name).

Note: If the systems being configured for Anynet are already connected to an APPN Network Node using a non-Anynet link (SNA), we suggest not using the real Remote Control Point names, otherwise Anynet may not work properly. If this is the case, the recommendation is to use generic Control Point names, such as ANYNET or TCPIP, in the APPC controller and the QAPPNRMT Configuration List. Although generic Control Point names are used here as an example, it is acceptable to use the real Remote Control Point names where APPN Network Nodes are not involved.

The APPC devices are autocreated when establishing the connection.

To create the remote configuration list entry on the SOURCE system, do the following:
1.On the operating system command line, type the following:

WRKCFGL

Press the Enter key.
2.Locate QAPPNRMT, type 2 (to change) for the OPTION, and press the Enter key.
3.Page down to the first blank line for REMOTE LOCATION.
4.Type the HOST NAME and REMOTE NETID. These are the same as were typed in the TCP HOST NAME TABLE above.
5.Local Location is usually *NETATR.
6.The Remote Control Point must match the RMTCPNAME in the APPC controller description created above.
7.The CONTROL POINT NET ID usually matches the REMOTE NET ID.
8.The LOCATION PASSWORD and SECURE LOC are based on your system requirements. Change SECURE LOC to *YES if you want to have AUTOMATIC SIGNON with Passthru.

To activate AnyNet, do the following:
1.Verify that the Network Attribute ALLOW ANYNET is set to *YES
2.Confirm that one QAPPCTCP job is Active under subsystem QSYSWRK
3.Varyon the AnyNet APPC controller
4.Key WRKTCPSTS OPTION(*CNN). There should be two ports named APPCove, one with a status of *UDP, the other with a status of LISTEN.
To test the completed configuration, do the following:
1.From the source system, Telnet to the target system using the fully qualified name from the HOST TABLE ENTRIES (HOSTNAME.RMTNETID.SNA.IBM.COM). Do the same from the target system to the source system.
2. Use the Start Passthrough (STRPASTHR) command to specify the HOST SYSTEM NAME for the RMTLCNAME. When running the STRPASTHR command, the APPC device should be autocreated under the AnyNet controller.
3.Continue with the configuration of any other APPC application (ICF, DDM, or SNADS) as usual.
4.The Network Attribute parameter, ALWANYNET (Allow AnyNet Support) must be set to *YES using the CHGNETA command for the system to maintain an AnyNet configuration
Note: When changing ALWANYNET from *YES to *NO, ensure that the QAPPCTCP job in subsystem QSYSWRK has ended before changing it back to *YES. Otherwise, AnyNet may not start properly.

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"6.1.0"}]

Historical Number

22090321

Document Information

Modified date:
18 December 2019

UID

nas8N1017530