Communications Setup and Scenarios for 2-Tier SNA Client Configuration

  Setting up 2-tier SNA Client Configuration for Attachmate - MPTN
  Setting up 2-tier Client Configuration for Attachmate - IEEE 802.2
  Setting up 2-tier SNA Client Configuration for RUMBA MPTN
  Setting up 2-tier SNA Client Configuration for RUMBA IEEE 802.2 DLC

Setting up 2-tier SNA Client Configuration for Attachmate - MPTN
Several SNA vendors implement two-tier direct-connect products, including Attachmate and RUMBA. You can configure CONNX to work with these SNA clients, provided that the CONNX client is installed on the same client PC as the SNA vendor client. CONNX detects the supported SNA client stacks automatically.
1. Start the Attachmate Extra! Personal Client 32-bit or Extra! Office 32-bit Client application.
2. Select APPN Node+APPN Configurator from the menu.
3. Under Sections, select Node Definition and then click the Add button.
The Local Node tab appears.
The values in this tab define the local computer to the network. For this example, the network name is APPN; the CP (Control Point) Name is CONNXPC.
4. Select Data Link Control under Sections and then click the Add button.
The Add Data Link Control dialog box appears
5. Select MPTN as the DLC type in the DLC Type list box, and then click the OK button.
The MPTN tab appears in the APPN Configurator window.
6. Enter a symbolic name, in this case MPTNDLC.
7. Select Port under Sections in the APPN Configurator window and then click the Add button.
The Add Port Definition dialog box appears.
8. Select MPTN as the DLC Type in the DLC Type list box, and then click the OK button to return to the APPN Configurator window.
The Port tab appears in the right pane. Representative information is complete.
9. Select Link under Sections, and then click the Add button.
The Add Link Definition dialog box appears.
10. Select MPTN as the DLC link type in the DLC Type list box, and then click the OK button to return to the APPN Configurator window.
11. Accept the defaults in the Definition Tab in the right pane.
12. Select the MPTN tab in the right pane.
13. Check the Swap NetID/LU Name in the Domain check box.
14. Select Mode under Sections, and click the Add button.
The Mode tab appears.
15. Enter the IBMRDB mode name in the Mode Name text box.
These values are compatible with the IBMRDB mode definition as displayed by the OS/400 DSPMODD command.
16. Select Local LU 6.2 under Sections, and then click the Add button.
The Local LU (LU 6.2) tab appears.
In order to be consistent with previous examples, both the Local LU name and the Local LU alias are defined as CONNXPC. Note that the NAU address field is 0; this value defines an independent local LU.
17. Select Partner LU (LU 6.2) under Sections, and then click the Add button.
The Partner LU (LU 6.2) tab appears.
In order to be consistent with previous examples, the target AS/400 and the owning control point name are defined as APPN.CONNX400.
The Attachmate MPTN driver maps the dotted TCP/IP address to a netid.luname via the hosts file, which is located in either the \winnt\system32\drivers\etc or the \windows directory for Windows. For example:
012.345.678.901 connx400.appn.sna.ibm.com #Anynet
Note that the host file transposes the netid.luname. The sna.ibm.com suffix is discarded.
The Attachmate MPTN configuration is complete. These values are used later in the CONNX client configuration dialog box.