Tivoli Header

Quick Start


Configuring AIX SNA Server/6000 Clients Using SMIT

Define the Data Link Control (DLC)

  1. Select Devices.
  2. Select Communication.
  3. Select Token Ring Adapter.
  4. Select Services.
  5. Select Data Link Controls.
  6. Select Add a Token Ring Data Link Control.

Getting to SNA Server/6000 via SMIT

  1. Select Communications Application and Services.
  2. Select SNA Server/6000.
  3. Select Configure SNA Profiles.

Creating the Initial Node Definition

To create the initial node definition, follow these steps:

  1. From the Configure SNA Profiles window, select Initial Node Setup.
  2. Select token_ring for this configuration. The Initial Node Setup screen appears. See Figure 30.

    Figure 30. Initial Node Setup Screen

    +--------------------------------------------------------------------------------+
    |                               Initial Node Setup                               |
    |                                                                                |
    |Type or select values in entry fields.                                          |
    |Press Enter AFTER making all desired changes.                                   |
    |                                                                                |
    |                                                        [Entry Fields]          |
    |  Control Point name token_ring              +       [F13833D0]                 |
    |  Control Point type                                  appn_end_node           + |
    |  Local network name                                 [DEIBMFD]                  |
    |  XID node ID                                        [05df333d]                 |
    |                                                                                |
    |  Optional link station information:                                            |
    |                                                                                |
    |  Link station type                                   token_ring                |
    |  Link station name                                  []                         |
    |* Calling link station?                               yes                     + |
    |  Link address                                       []                        X|
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |F1=Help             F2=Refresh          F3=Cancel           F4=List             |
    |Esc+5=Undo          F6=Command          F7=Edit             F8=Image            |
    |F9=Shell            F10=Exit            Enter=Do                                |
    +--------------------------------------------------------------------------------+
  3. Enter c_independentlu for the Control Point name.
  4. Select appn_end_node for the Control Point type.
  5. Enter c_netid for the Local Network Name.
  6. Enter vtam_xid for the XID node ID. This is the IDBLK and IDNUM defined in the 3745 VTAMLST. This node id is essential in a cross-domain environment where the server application host machine is not the same as the host machine that the workstation is generated to.
  7. The rest of the fields can be left with the defaults.
  8. Press Enter to save your input.
  9. Press PF3 to return to the Configure SNA Profiles window.
    Note:
    The Initial Node setup is similar to OS/2 CM/2 define Local Node Characteristics. This can also be done in SMIT under the Advanced Configuration/Control Point window.

Creating the Link/Mode/Side Information

  1. Select Advanced Configuration.
  2. Select Links.
  3. Select Token Ring from the Token Ring Physical Units window.
Note:
The screens in Figure 31 and Figure 32 are actually composite screens. You need to use Page Down and Page Up to view all of the parameters. The values that you need to change are shown in bold print.

Token Ring SNA DLC

  1. Select Add a profile.
  2. Enter a name for the profile. For example, tok0.00001.

    Figure 31. Add Token Ring SNA DLC Profile Screen

    +--------------------------------------------------------------------------------+
    |                     Add Token Ring SNA DLC Profile                             |
    |                                                                                |
    |Type or select values in entry fields.                                          |
    |Press Enter AFTER making all desired changes.                                   |
    |                                                                                |
    |[TOP]                                                   [Entry Fields]          |
    |  Profile name                                       [tok0.00001]               |
    |  Data link device name                              [tok0]                   + |
    |  Force disconnect time-out (1-600 seconds)          [120]                     #|
    |  User-defined maximum I-Field size?                  yes                     + |
    |                                                                                |
    |
      ·
      ·
      ·
    | | Receive window count (1-127) [8] #| | Ring access priority 0 + | | Inactivity time-out (1-120 seconds) [48] #| | Response time-out (1-40, 500 msec intervals) [4] #| | Acknowledge time-out (1-40, 500 msec intervals) [1] #| | Local link name [F13833D0] | | Local SAP address (04-ec) [04] X| | Trace base listening link station? no + | | If yes, Trace format long + | | Dynamic link stations supported? yes + | | | | Link Recovery Parameters | |
      ·
      ·
      ·
    | | | | Dynamic Link Activation Parameters | | Solicit SSCP sessions? yes + | | CP-CP sessions supported? no + | | Partner required to support CP-CP sessions? no + | | | | Dynamic Link TG COS Characteristics | |
      ·
      ·
      ·
    | | | | Dynamic Link TG COS Characteristics | |
      ·
      ·
      ·
    | | | | Comments [] | |[BOTTOM] | | | |F1=Help F2=Refresh F3=Cancel F4=List | |Esc+5=Undo F6=Command F7=Edit F8=Image | |F9=Shell F10=Exit Enter=Do | +--------------------------------------------------------------------------------+
  3. Enter c_independentlu for the Local Link Name.
  4. Under Dynamic Link Activation Parameters:
    1. Change Solicit SSCP sessions to yes.
    2. Change CP-CP sessions Supported to no.
  5. Press Enter to save the profile.
  6. Press PF3 to return to the Token Ring Physical Units window.

Token Ring Link Station

  1. From the Token Ring Physical Units window, select Token Ring Link Station.
  2. Select Add a Profile. There is one link-station defined per server. Use most of the default parameters.
  3. Enter a name for the profile. This value can be anything and the server name can be the profile name. BCTSO is the name of the profile in this example.
  4. Press Enter to create the profile. The Add Token Ring Link Station Profile window appears. See Figure 32.

    Figure 32. Add Token Ring Link Station Profile Window

    +--------------------------------------------------------------------------------+
    |                       Add Token Ring Link Station Profile                      |
    |                                                                                |
    |Type or select values in entry fields.                                          |
    |Press Enter AFTER making all desired changes.                                   |
    |                                                                                |
    |[TOP]                                                   [Entry Fields]          |
    |  Profile name                                       [BCTSO]                    |
    |  Use APPN Control Point's XID node ID?               yes                     + |
    |* SNA DLC Profile name                               [tok0.00001]             + |
    |
      ·
      ·
      ·
    | | Adjacent Node Address Parameters | | Access routing link_address + | | If link_name, Remote link name yes [] | | If link_address, | | Remote link address [400010000002] X| | Remote SAP address (04-ec) [04] X| | | | Adjacent Node Identification Parameters | |
      ·
      ·
      ·
    | | | | Link Activation Parameters | | Solicit SSCP sessions? yes + | | Initiate call when link station is activated? yes + | | Activate link station at SNA start up? yes + | | Activate on demand? no + | | CP-CP sessions supported? no + | |
      ·
      ·
      ·
    | | | | Restart Parameters | |
      ·
      ·
      ·
    | | | | Transmission Group COS Characteristics | |
      ·
      ·
      ·
    | | | | Comments [] | |[BOTTOM] | | | |F1=Help F2=Refresh F3=Cancel F4=List | |Esc+5=Undo F6=Command F7=Edit F8=Image | |F9=Shell F10=Exit Enter=Do | +--------------------------------------------------------------------------------+
  5. Place the cursor in the SNA DLC Profile name field and press PF4. Select the Token Ring SNA DLC that was created above. It is tok0.00001 in this example.
  6. Under Adjacent Node Address Parameters, enter dest_addr for the Remote link address
  7. Under Link Activation Parameters, do the following:
    1. Change Solicit SSCP sessions to yes.
    2. Change Initiate call when link station is activated to yes. This denotes that this is a calling link station.
    3. Change Activate link station at SNA start up to yes.
    4. Change CP-CP sessions Supported to no.
  8. Press Enter to save your changes.
  9. Press PF3 until you return to the Advanced Configuration window.

Defining LU 6.2 Session

  1. Select Sessions.
  2. Select LU 6.2.

LU 6.2 Mode

  1. Select LU 6.2 Mode.
  2. Select Add a Profile.
  3. Enter the profile name. You can use the same name as the mode name in the next step. See Figure 33.

    Figure 33. Add LU 6.2 Mode Profile Window

    +--------------------------------------------------------------------------------+
    |                            Add LU 6.2 Mode Profile                             |
    |                                                                                |
    |Type or select values in entry fields.                                          |
    |Press Enter AFTER making all desired changes.                                   |
    |                                                                                |
    |                                                        [Entry Fields]          |
    |* Profile name                                       [TSMAPPC]                  |
    |  Mode name                                          [TSMAPPC]                  |
    |  Maximum number of sessions (1-5000)                [8]                       #|
    |  Minimum contention winners (0-5000)                [4]                       #|
    |  Minimum contention losers (0-5000)                 [0]                       #|
    |  Auto activate limit (0-500)                        [0]                       #|
    |  Upper bound for adaptive receive pacing window     [16]                      #|
    |  Receive pacing window (0-63)                       [7]                       #|
    |  Maximum RU size (128,...,32768: multiples of 32)   [1024]                    #|
    |  Minimum RU size (128,...,32768: multiples of 32)   [256]                     #|
    |  Class of Service (COS) name                        [#CONNECT]                 |
    |                                                                                |
    |  Comments                                           []                         |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |F1=Help             F2=Refresh          F3=Cancel           F4=List             |
    |Esc+5=Undo          F6=Command          F7=Edit             F8=Image            |
    |F9=Shell            F10=Exit            Enter=Do                                |
    +--------------------------------------------------------------------------------+
  4. Enter logmode for the Mode name This is the client's LOGMODE.
    Note:
    This must match the VTAM's logmode defined in the mode table entry.
  5. Press Enter to save your changes.
  6. Press PF3 to return to the LU 6.2 window.

Partner LU6.2 Profile

  1. From the LU 6.2 window, select LU 6.2 Partner LU.
  2. Select Add a profile.
  3. Enter the profile name. This name can be any value. BCTSO is used in this example. See Figure 34.

    Figure 34. Add LU 6.2 Partner LU Profile

    +--------------------------------------------------------------------------------+
    |                         Add LU 6.2 Partner LU Profile                          |
    |                                                                                |
    |Type or select values in entry fields.                                          |
    |Press Enter AFTER making all desired changes.                                   |
    |                                                                                |
    |                                                        [Entry Fields]          |
    |* Profile name                                       [BCTSO]                    |
    |  Fully qualified partner LU name                    [DEIBMA4.A4VTSM2]          |
    |  Partner LU alias                                   [A4VTSM2]                  |
    |  Parallel sessions supported?                        yes                     + |
    |  Session security supported?                         no                      + |
    |  Conversation security level                         none                    + |
    |                                                                                |
    |  Comments                                           []                         |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |F1=Help             F2=Refresh          F3=Cancel           F4=List             |
    |Esc+5=Undo          F6=Command          F7=Edit             F8=Image            |
    |F9=Shell            F10=Exit            Enter=Do                                |
    +--------------------------------------------------------------------------------+
  4. Enter the s_netid.partner_lu for the Fully qualified partner LU name.
  5. Enter the Partner LU Alias. This value can be anything.
  6. Press Enter to save your changes.
  7. Press PF3 to return to the LU 6.2 window.

Partner LU 6.2 Location

  1. Select Partner LU 6.2 Location. This is the same as the DEFINE_PARTNER_LU_LOCATION statement in CM/2. It is required for any cross-domain environment.
  2. Select Add a profile.
  3. Enter the profile name. This name can be any value. BCTSO is used in this example.

    Figure 35. Add Partner LU 6.2 Location Profile Window

    +--------------------------------------------------------------------------------+
    |                      Add Partner LU 6.2 Location Profile                       |
    |                                                                                |
    |Type or select values in entry fields.                                          |
    |Press Enter AFTER making all desired changes.                                   |
    |                                                                                |
    |                                                        [Entry Fields]          |
    |* Profile name                                       [BCTSO]                    |
    |  Fully qualified partner LU name                    [DEIBMA4.A4VTSM2]          |
    |  Fully qualified owning Control Point (CP) name     [DEIBMFD.FDW]              |
    |  Local node is network server for LEN node?          no                      + |
    |  Fully qualified network node server name           []                         |
    |                                                                                |
    |  Comments                                           []                         |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |F1=Help             F2=Refresh          F3=Cancel           F4=List             |
    |Esc+5=Undo          F6=Command          F7=Edit             F8=Image            |
    |F9=Shell            F10=Exit            Enter=Do                                |
    +--------------------------------------------------------------------------------+
  4. Enter s_netid.partner_lu for the Fully qualified partner LU name.
  5. Enter c_netid.cp_name for the Fully qualified owning Control Point (CP) name. cp_name must be the SSCPNAME of the workstation's network. In this environment, the SSCPNAME is FDW.
  6. Press Enter to save your changes.
  7. Press PF3 until you return to the LU 6.2 window.

Side Information

  1. Select LU 6.2 Side Information.
  2. Enter any name for the profile. The name that you enter here must also be the symbolic destination specified in the client's dsm.opt file. BCTSO is used in this example.

    Figure 36. Add LU 6.2 Side Information Profile Window

    +--------------------------------------------------------------------------------+
    |                      Add LU 6.2 Side Information Profile                       |
    |                                                                                |
    |Type or select values in entry fields.                                          |
    |Press Enter AFTER making all desired changes.                                   |
    |                                                                                |
    |                                                        [Entry Fields]          |
    |* Profile name                                       [BCTSO]                    |
    |  Local LU or Control Point alias                    [F13833D0]               + |
    |  Provide only one of the following:                                            |
    |     Partner LU alias                                []                       + |
    |     Fully qualified partner LU name                 [DEIBMA4.A4VTSM2]          |
    |  Mode name                                          [TSMAPPC]               +  |
    |  Remote transaction program name (RTPN)             [ANYTHING]                 |
    |  RTPN in hexadecimal?                                no                      + |
    |                                                                                |
    |  Comments                                           []                         |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |F1=Help             F2=Refresh          F3=Cancel           F4=List             |
    |Esc+5=Undo          F6=Command          F7=Edit             F8=Image            |
    |F9=Shell            F10=Exit            Enter=Do                                |
    +--------------------------------------------------------------------------------+
  3. Enter c_independentlu for the Local LU or Control Point alias. This can be selected from the PF4 list.
  4. Enter s_netid.partner_lu for the Fully qualified partner LU name or select the Partner LU Alias name.
  5. Select the Mode name from the PF4 list. This is the mode you have just created.
  6. Enter the Remote transaction program name (RTPN). This can be any name. ANYTHING is used in this example.
  7. Press Enter to save your changes.
  8. Press PF3 until you return to the Advanced Configuration window.

Verify Configuration Profiles

  1. Select Verify Configuration Profiles from the Advanced Configuration window. This can also be done from any window that has the verify option.

    Figure 37. Advanced Configuration Window

    +--------------------------------------------------------------------------------+
    |                             Advanced Configuration                             |
    |                                                                                |
    |Move cursor to desired item and press Enter.                                    |
    |                                                                                |
    |  Links                                                                         |
    |  Sessions                                                                      |
    |  SNA System Defaults                                                           |
    |  Control Point                                                                 |
    |  Gateway Definitions                                                           |
    |  Security                                                                      |
    |  Verify Configuration Profiles                                                 |
    |  Export Configuration Profiles                                                 |
    |  Import Configuration Profiles                                                 |
    |  Migrate Configuration Profiles                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |F1=Help             F2=Refresh          F3=Cancel           F8=Image            |
    |F9=Shell            F10=Exit            Enter=Do                                |
    +--------------------------------------------------------------------------------+

Starting the Tivoli Storage Manager Client

  1. Edit the dsm.sys file, giving the symbolic destination a value of BCTSO. For example:
    +--------------------------------------------------------------------------------+
    |servername               bctso                                                  |
    |commmethod               snalu6.2                                               |
    |  symbolicdestination    bctso                                                  |
    +--------------------------------------------------------------------------------+
  2. Ensure that SNA/6000 is started. This can be done by using the 'sna -start sna' command or via SMIT under the Manage SNA Resources window.
  3. Start the TSM program.

Considerations for Using the SNA Services/6000 Client

The SNA Services/6000 setup is the same as the SNA Server/6000 setup except for one important difference-the partnerluname in the dsm.sys file specifies the "Connection Profile" name of the file that has the partner LU definition and not the actual partner LU name. This difference is attributed to the way that SNA Services/6000 implements the partner LU.


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