Quick Start


Configuring the OS/2 Client for APPC Using Communication Manager/2

The example configuration that follows uses Communication Manager/2 (CM/2) level 1.0. To begin the configuration process for CM/2, follow these steps:

  1. From the OS/2 Desktop, double click on the Communication Manager /2 icon.

  2. Double click on the Communication Manager Setup icon. The Communication Manager Setup window appears.

  3. Press the Setup button. The Open Configuration window appears. See Figure 16.

    Figure 16. Open Configuration Window

    Open Configuration Screen

  4. Enter a new name in the Configuration field. If you want a description, enter it in the Description field.

  5. Press the OK button. Answer Yes to any messages that appear.

  6. On the Communications Manager Configuration Definition - APPC window, select Token-ring or other LAN types for the Workstation Connection Type.

  7. Select CPI Communications for the Feature or Application.

  8. Press the Configure... button.

After you have followed the previous steps, the Communication Manager Profile List Sheet window is displayed. All of the profiles listed need to be configured. The profiles are:

DLC - Token-ring or other LAN types
SNA local node characteristics
SNA connections
SNA features

The following sections show you the CM/2 windows and the information that you need to fill in.

Note:See CM/2 .ndf File for 3172 or 3745 Gateways for the sample .ndf file that would be created by completing the following procedure.

In the Communications Manager Profile List Sheet window, double click on DLC - Token-ring or other LAN types. The Token Ring or Other LAN Types DLC Adapter Parameters window appears. See Figure 17.

Figure 17. Token Ring or Other LAN Types DLC Adapter Parameters Window

Token Ring Parameters Screen

  1. Enter the c_netid in the C&SM LAN ID field.

  2. Press the OK button.

In the Communications Manager Profile List Sheet window, double click on SNA local node characteristics. The Local Node Characteristics window appears. See Figure 18.

Figure 18. Local Node Characteristics Window

Local Node Characteristics Window

  1. Enter the c_netid in the Network ID field.

  2. Enter the c_independentlu in the Local node name field.

  3. Select End node - no network node server for the Node type. You need to select End node to network node server if you are connecting to an APPN network node server.

  4. Enter the vtam_xid in the Local node ID fields. These values can be left with zeros if CPNAME is used in the VTAMLST.

  5. Press the OK button to return to the Communications Manager Profile List Sheet window.

In the Communications Manager Profile List Sheet window, double click on SNA connections. The Connections List window appears. See Figure 19.

Figure 19. Connections List Window

Connections List Window

  1. Select To host in the Partner type group box.

  2. Press the Create... button.

When you press the Create... button in the Connections List window, the Adapter List window appears. See Figure 20.

Figure 20. Adapter List Window

Adapter List Window

  1. Select Token-ring or other LAN types if you are using token ring.

  2. Press the Continue... button.

When you press the Continue... button in the Adapter List window, the Create a Connection to a Host window appears. See Figure 21.

Figure 21. Create a Connection to a Host

Create a Host Connection Window

  1. Enter the dest_addr in the LAN destination address field.

  2. Enter the c_netid in the Partner network ID field. This is the network identification number of the adjacent CP (3745-NCP) that the client workstation is generated to. In this example, it is the client's network ID.

  3. Enter a value in the Partner node name field. This is the SSCPNAME in VTAMLIST. For the OS/2 client, this can be any value you want. BCTSO is used in this example.

  4. Enter the vtam_xid in the Node ID fields. These values are required for the host link connection definition. It could be zeros if CPNAME is used in the VTAMLST.

  5. Press the Define Partner LUs... button.

When you press the Define Partner LUs... button in the Create a Connection to a Host window, the Create Partner LUs window appears. See Figure 22. Defining Partner LUs generates the DEFINE_PARTNER_LU_LOCATION statement. This ensures that the FQ_OWNING_CP_NAME parameter is in the .ndf file.

Figure 22. Create Partner LUs

Create Partner LUs Screen

  1. Enter the partner_lu in the LU Name field.

  2. Enter a value in the Alias field. The Partner LU alias can be any value you want.

  3. Press the Add button to add the Partner LU to the list.

  4. Press the OK button to return to the Connections List window.

  5. Press the Close button to return to the Communications Manager Profile List Sheet window.

In the Communications Manager Profile List Sheet window, double click on SNA features. The SNA Features List window appears.

  1. Select Partner LUs in the Features list.

  2. Select the Partner LU you previously defined in the far right list. In this example, the Partner LU name is A4VTIVSM2.

  3. Press the Change... button.

When you press the Change... button in the SNA Features List window, the Change a Partner LU window appears.

  1. Update the Partner LU network ID if it is different from the client's network ID (s_netid).
    Note:This updates the FQ_PARTNER_LU_NAME parameter in the DEFINE_PARTNER_LU statement. This is important if the client and server are on different networks.

  2. Press the OK button to return to the SNA Features List window.

If you decide to create a new mode instead of using the predefined one (#BATCH), you need to complete the following steps:

  1. In the SNA Features List window, select Modes from the Features list.

  2. Press the Create... button to create a new mode. The Create a Mode Definition window appears.

  3. Enter logmode in the Mode Name field.
    Note:The mode name must match the VTAM's log mode defined in the mode table entry.

  4. Press the OK button to return to the SNA Features List window.
Note:You shoulduse the #BATCH mode for TSM.

  1. In the SNA Features List window, select CPI Communications side information from the Features list.

  2. Press the Create... button. The Create CPI Communications Side Information window appears. See Figure 23. Use this window to create a symbolic destination name if you want to use one in the options file (dsm.opt).

    Figure 23. Create CPI Communications Side Information Window

    Create Side Information Window

  3. Enter a value in the Symbolic destination name field. You can enter anything. The value that you enter here should also be the symbolic destination name in the client's dsm.opt file.

  4. Enter the Fully qualified name (s_netid and partner_lu) of the partner LU, or use the Alias.

  5. Enter the server program name in the TP name field. This can be any value you want.

  6. Select Same or None for the Security type.

  7. Select the mode you just created from the Mode name field. Select #BATCH if you did not define one.

  8. Press the OK button.

Notes:

  1. If the same OS/2 client wants to have access to another host server, such as a VM or MVS server, via the same gateway, you need to define another partner LU, a CPIC side information record, and a new mode if it is using a different mode name. You can quickly add the following statements to the .ndf file for the new server:
    DEFINE_PARTNER_LU
    DEFINE_PARTNER_LU_LOCATION
    DEFINE_PARTNER_MODE
    DEFINE_CPIC_SIDE_INFO

  2. The VTAM SWNET Major Node defined the independent LU with MODETAB and DLOGMODE for the first server. This should not have any effect if the second server is using a different MODETAB and DLOGMODE. When the client establishes a connection to the server, the mode that is defined on the client overrides the mode defined in the VTAM SWNET Major Node definition.

Starting the Tivoli Storage Manager Client

  1. Edit the dsm.opt file, giving the symbolic destination a value of MVSTIVSM. For example:
    +--------------------------------------------------------------------------------+
    |commmethod snalu6.2                                                             |
    |symbolicdestination mvstivsm                                                    |
    +--------------------------------------------------------------------------------+

  2. Ensure that CM/2 is started.

  3. Start the TSM program

Considerations for Using OS/2 Clients

TSM does not allow the user to choose the local LU for the client program. If CM/2 supports other applications that use independent LUs, you need to specify a default LU for TSM by adding the following statement to your .ndf file:

DEFINE_DEFAULTS DEFAULT_LOCAL_LU_ALIAS (<local LU alias>)

After adding this statement you need to run CMVERIFY /E to verify your changes and dynamically update the SNA information in CM/2.

Note:You must manually add this statement to the .ndf file. The Communication Manager Setup program provides no means for doing so.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]