Parallel configurations of AnyNet and Enterprise Extender

It is possible to migrate to Enterprise Extender while maintaining existing AnyNet® definitions, but a new remote logical unit (LU) must be defined to handle AnyNet connections. The following example explains how this is done.

For this example, assume that you have two systems: SYSA and SYSB. SYSA has the following configuration:

• One APPC controller of type *ANYNW that has a remote control point value of TCPIP.
• One entry on the QAPPNRMT configuration list for each remote node that defines the remote node and sets the control point name as TCPIP.
• One entry on the TCP Host table added that has the "SNA.IBM.COM" suffix, and the remote SNA host name and remote network ID that has the same suffix.
• The ALWANYNET Network attribute set to *YES.

When migrating from AnyNet to HPRIP, you need to create a new LU on SYSB and SYSA. In this example, the new LUs are called ANYSYSA and ANYSYSB.

If the QAPPNLCL configuration list has not been created on SYSA, create the new LU by issuing the following command:

CRTCGL TYPE(*APPNLCL) APPNLCLE((ANYSYSA 'HPRIP LU'))

If the QAPPNLCL configuration list already exists, then use this command:

CHGCGL TYPE(*APPNLCL) APPNLCLE((ANYSYSA 'HPRIP LU'))

Then the configuration list entries for the remote must be changed. First, add the new remote LU to the configuration list with the following CL command:

ADDCFGLE TYPE(*APPNRMT) APPNRMTE((ANYSYSB *NETATR ANYSYSA TCPIP *NETATR))

Next, the SYSB entry must be removed from the configuration list using this command:

RMVCFGLE TYPE(*APPNRMT) APPNRMTE((SYSB *NETATR SYSA))

The equivalent commands should be issued on SYSB. Then controllers should be created for SYSB in SYSA and for SYSA in SYSB using the CRTCTLAPPC CL command.

After this is accomplished, you should be able to start sessions to LU SYSB, in which case the communications media would be Enterprise Extender. For AnyNet communications, ANYSYSB LU should be used.