Migrating to Enterprise Extender with the existing AnyNet definitions maintained
It is possible to migrate to Enterprise Extender while keeping the 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, with 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 that has the suffix SNA.IBM.COM, and that has the remote SNA host name and the remote network ID with the same suffix.
- The ALWANYNET Network attribute set to *YES.
When migrating from AnyNet to Enterprise Extender (HPRIP), you must create new LUs on SYSB and SYSA. In this example, the new LUs are called ANYSYSA and ANYSYSB.
To migrate from AnyNet to Enterprise Extender (HPRIP), follow these steps:
After you complete these steps, you are able
to start sessions to LU SYSB, with Enterprise Extender as the communications
media. For AnyNet communications, ANYSYSB LU is used.