### Configuring for APPC communications at CM/2

This section describes how to configure APPC for a CM/2 workstation that is connected to a token-ring Local Area Network (LAN) and the required workstation software.

#### Prerequisites

- IBM OS/2 WARP Version 4.0 plus FixPak 5 or later
- Communications Manager/2 Version 1.11 or later

#### Terminology

Below is a table of standard APPC terms and the equivalent CM/2 terms.

Standard Term | CM/2 Term
--- | ---
Network Name | Network Name
LU Name | Local Node Name
Partner LU Name | Partner Node Name
Local LAN Address | Local MAC Address
Adjacent LAN Address | LAN Destination Address

#### Communications Manager/2 configuration variables

Use Table 1 to create a worksheet that defines the listed symbols. These symbols and their corresponding values are used to configure CM/2 for communication with an APPC/MVS and/or CICS host. The worksheet consists of two parts:

1. Symbols that must be matched with a partner platform (for example, MVS/APPC or CICS) are under the heading NETWORK VALUES.
2. Symbols that are local to the workstation are under the heading LOCAL VALUES.

Note: | The values defined in Table 1 are compatible with an appropriately configured APPC/MVS or CICS host. A workstation configured with these values supports Remote Edit/Compile/Debug sessions with APPC/MVS and/or Remote Debug sessions with APPC/MVS and/or CICS. It also supports access to Remote VSAM using SdU via APPC/MVS and access to IMS fully qualified databases using Remote DL/I. In this configuration, it is assumed that CICS and APPC/MVS both reside on the same MVS host. If this is not the case and you require assistance, contact your IBM representative.

#### Performing CM/2 APPC configuration

This example assumes that CM/2 configuration files already exist, that is, you have already installed CM/2 and only require APPC configuration. If this is not the case, install CM/2 as described in CM/2 Installation and Configuration Guide and resume at this point. Prior to APPC configuration, it is recommended that you copy your default CFG and NDF files (usually located in the C:\CMLIB directory) to another set of files that you can name to CVSCFG. For example, assuming that your default configuration is named BASIC, move to the C:\CMLIB directory and then enter on an OS/2 command line:

    COPY BASIC.* CVSCFG.*

This creates a copy of the various files that comprise your default configuration. The steps below modify this file to contain APPC definitions while leaving other existing definitions intact. If you are modifying an existing configuration, as is the case of the example that follows, some definitions from your worksheet might already exist and need not be supplied by you.

Perform the following steps to modify the configuration CVSCFG:

##### Selecting the CVSCFG configuration file

1. Double-click on the CM/2 icon.
2. Double-click on the CM/2 Setup icon. The Communications Manager Setup window appears, as shown in Figure 1.

   Note: The CM/2 windows shown in the examples are taken from CM/2 Version 1.11. If you are using a newer version of CM/2, the windows might have a slightly different layout.

3. Select the Setup push button. The Open Configuration window appears, similar to Figure 2.
4. Select CVSCFG from the Configurations list.
5. Select the OK push button.
6. Select the Description as desired.
7. When prompted, select the Yes push button to confirm that CVSCFG will be used for this workstation.
8. The Communications Manager Configuration Definition - CVSCFG window appears, as shown in Figure 3. Make sure that you have selected the Additional definitions radio button; otherwise, the window might appear different from the window in the figure.

##### Defining your workstation to the network

Before the workstation can communicate within a network, it must be recognized by that network. This means that the workstation must be properly defined in the Communications Manager Local Node Characteristics window. If the workstation has already been defined to the network, verify that the definitions are complete and consistent with the worksheet values. Otherwise, perform the following steps to define these values:

1. Select the option Token-ring or other LAN types.
2. Select APPC APIs from the Feature or Application list.
3. After selecting APPC APIs, the Communications Manager Configuration Definition - CVSCFG window, shown in Figure 4, changes as a result of your choice.
4. Select the Configure push button.
5. The APPC APIs through Token-ring window appears, as shown in Figure 5.
6. In the Network ID field, enter the NETWORK value.
7. In the Local node name field, enter the LUNAME value.
8. For the Local node type, select End node - no network node server. This allows you to configure directly to the token-ring at the communications controller.

   If you want to connect your host through an APPN network node, select End node - to a network node server. Our example does not address this form of connection.

9. Select the Advanced push button.
10. The Communications Manager Profile List window appears, as shown in Figure 6.
11. Select SNA local node characteristics from the Profile Name list.
12. Select the Configure push button.
13. The Local Node Characteristics window, shown in Figure 7, appears.
14. Confirm that the values you entered in the APPC APIs through Token-ring window are what you need for Network ID, Local node name, and Local node type.
15. Enter the value of NODEID in the Local node ID field to identify the workstation with NODEID as opposed to CPNAME.
16. Select the Options push button.
17. The Local Node Options window appears, as shown in Figure 8.
18. In the Local node alias name field, enter the LUALIAS value. This can be the same as the local node name (LUNAME).
19. Select Activate Attach Manager at start up.
20. Select the OK push button.
21. The Local Node Characteristics window appears, as shown in Figure 7.
22. Select the OK push button.
23. The Communications Manager Profile List window appears, as shown in Figure 6.

##### Defining a connection

Before the workstation can communicate with the host, a corresponding connection must be defined. If the connection is already defined, verify that the definitions are complete and consistent with the worksheet values by stepping through the following windows. If you are defining a new connection, enter the field values as you move from one window to the next.

1. Select SNA connections from the Profile Name list.
2. Select the Configure push button.
3. The Connections List window appears, as shown in Figure 9.
4. Select To host as the partner to which you are connecting, as this example shows. Alternatively, you can connect to a network node.
5. If a connection to your host already exists, select the connection corresponding to the value of LINKNAME. In our example, LINKNAME is HOST0002.
6. Assuming the connection to your host is already defined for emulators, select the Change push button. If no such connection exists, select the Create push button.
7. The Adapter List window, shown in Figure 10, appears.
8. Since this example assumes a token-ring LAN, select Token-ring or other LAN types.
9. Select the Continue push button.
10. Since you selected To host in Figure 9, the Connection to a Host window appears,as shown in Figure 11.

1. In the Link Name field, enter the LINKNAME value.
2. Check the Activate at startup box to initialize this link when CM/2 is started.
3. For the Local PU name field, if this is the only host connection defined and Use this host connection as your focal point support (see step 8) is selected, this field defaults to CPNAME. Otherwise, enter the value of LOCALPU.
4. Assuming that VTAM recognizes this station by NODEID as opposed to CPNAME, specify its hexadecimal value here.
5. In the LAN destination address field, enter the LANADDRESS value. For this type of connection, LANADDRESS refers to the token ring at the communication controller.
6. In the Partner network ID field, enter the PARTNERNET value.
7. In the Partner node name field, enter the PARTNERCP value.
8. If this is the only host connection defined from this workstation, check the Use this host connection as your focal point support box. If other host connections exist, only one can be so designated. To explore the alternative of not using host focal point services for a connection, see the bibliography for this section.

##### Defining the partner LU

You can define the partner LU and an alias for the MVS/APPC LU. For example, you can specify that HOSTLU is an alias for PARTNERNET.PARTNERLU.

Skip this step if you selected End node to network server in the Local Node Characteristics window, shown in Figure 7.

1. From the Connection to a Host window, shown in Figure 11, select the Define Partner LUs push button.
2. The Partner LUs window appears, similar to Figure 12.
3. In the Network ID field, enter the value for PARTNERNET.
4. In the LU name field, enter the value for PARTNERLU.
5. In the Alias field, enter the value for PLUALIAS.

   Note: An alias is case sensitive. `HOSTLU` is a different alias than `hostlu`.

6. Select the Add push button.
7. Select the OK push button.

###### Returning to the Communication Manager profile list

1. From the Connection to a Host window, shown in Figure 11, select the OK push button.
2. The Connections List window appears, as shown in Figure 9.
3. Select Close.
4. The Communications Manager Profile List window appears, as shown in Figure 6.

###### Proceeding to the SNA features list

1. From the Communications Manager Profile List, select SNA features.
2. Select the Configure push button.
3. The SNA Features List window appears.

##### Configuring the remote debugger to run as a server

To configure a server for the Remote Debugger:

1. Select Transaction program definitions from the Features list.
2. Select the Create push button. The Transaction Program Definition window appears, as shown in Figure 13.
3. Enter the Transaction program (TP) name using the value of LOCALTP (COBVSDT).
4. Using the value of TPPATH, enter the OS/2 Program path and file name as:

       drive:\OS2\CMD.EXE

5. Using the value of TPPARM, enter the program parameter string as:

       /C drive:\ibmcobol\BIN\CCX1APCD.CMD

6. Select the Continue push button. The Additional TP Parameters window appears, as shown in Figure 14.
7. For the Presentation type, select VIO - windowable.
8. For the Operation type, select Non-queued, Attach Manager started.
9. Select the OK push button.
10. Select the Close push button on the SNA Features List window.
11. The Communications Manager Profile List window appears, as shown in Figure 6.

##### Verifying Your configuration

1. Select the Close push button and the Communications Manager Configuration Definition - CVSCFG window appears, as shown in Figure 15.
2. Select the Close push button, and the Communication Manager - Checking Values window appears, as shown in Figure 16. A progress indicator will appear on top of this window to indicate that CM/2 is verifying your APPC configuration.

   If there are any errors in the APPC profile. you can identify them by examining the First Failure Support Technology/2 log within the FFST/2 folder on your OS/2 desktop. Make whatever corrections are necessary and repeat the steps above to verify your configuration. Your configuration can also be verified by issuing the following on an OS/2 command line within the CMLIB directory:

       CMVERIFY CVSCFG

3. After your configuration has been verified, stop and restart CM/2 with the newly modified configuration file to activate your APPC configuration.