Quick Start


Configuring Novell NetWare Client for APPC Using NetWare Requester

In the NetWare configuration that follows, the SNA profile is created using DOS requestor.

Creating the CSCON Configuration Profile

  1. Go to the SYSTEM/CSCON directory and invoke CSCON service.

  2. Select Configure Communication Services.

  3. Select NetWare for SAA.

  4. Create a 2.1 type service profile called appcpro (TSM requires a type 2.1 service profile).

  5. Select the newly created profile to create a host connection.

Creating a Host Connection

When you select Configure Host Connection from the Configure SAA Service Profile window, the Host Connection Configuration window appears.

  1. Enter c_netid for the SNA network ID.

  2. Enter c_independentlu for the Control Point Name.

  3. Enter the number of licenses you have for NetWare SAA for the Number Independent Sessions Supported.

  4. Place the cursor in the Host Attachment field and press the Insert key. Then select the type of LAN to be configured. We're selecting Token Ring in this example.

Configuring the SNA Token-Ring

After you select SNA Token Ring, the SNA Token Ring Configuration window appears.

  1. Enter 04 for Token Ring Source Service Access Point.

  2. Enter Primary for Token Ring Adapter Type.

  3. Enter vtam_xid for the Block ID and PUID for Token Ring Connection fields. If CPNAME is used in the VTAMLST, leave the default values for these two fields.

  4. Enter the logical adapter name from the IPX bind statement in the autoexec.ncf file. For example, in bind ipx to TOKENSAA net=ABCD, TOKENSAA is the logical adapter name.

  5. Exit CSCON.

Creating a Side Information File

  1. Go to the SYSTEM\NWSAA\CPIC directory and invoke the SIUTIL service.
    Note:The SIUTIL help facility clearly explains all of the fields.

  2. Select Create New Side Information File.

  3. Call the file MVSTIVSM.CPI.

  4. Select Add A Side Information Record.

  5. Call the record MVSTIVSM. This is the name to be used as symbolic destination in the client's dsm.opt file. Beware of case sensitive fields because certain levels of SIUTIL do not automatically change entries to uppercase letters, but TSM changes the symbolic destination to uppercase letters.

Defining Local LU Configuration

When you select Add a Side Information Record from the Side Information Records Command Menu window, the Local LU Configuration Data window appears.

  1. Enter the following:
    1. LU name: c_independentlu
    2. PU name: c_pu
    3. Detach PU Type: 1
    4. Security Type: 0
    5. LU Local Address: 0
    6. LU Session Limit: 8
    7. Network Name: c_netid

  2. Press Ctrl PgDn to go to the PLU Record.

Defining Partner LU Configuration

When you press Ctrl PgDn from the Local LU Configuration Data window, the Partner LU Configuration Data window appears.

  1. Enter the following:
    1. LU name: partner_lu (This is the Partner LU)
    2. Data Link Control Name: ITRN
    3. Network Adapter Number: 0
    4. Network Adapter Address: dest_addr
    5. LU Session Limit: 8
    6. Max Logical Record Size: 0
    7. Character Set: 0
    8. Local Program name: DSMC
    9. Remote Program Name: DSMSERV

  2. Press Ctrl PgDn to go to the Mode Record.

Defining the Mode Configuration Data

When you press Ctrl PgDn from the Partner LU Configuration Data window, the Mode Configuration Data window appears.

  1. Enter the following:
    1. Mode name: logmode
    2. Max Negotiable Session Limit: 8
    3. Automatic Activate Session Limit: 8
    4. Min Contention Winners Source: 0
    5. Min Contention Winners Target: 0
    6. Pacing size: 8
    7. Max RU size: 2048
    8. Min RU size: 256
    9. CNOS Flags: 6
    10. CNOS Termination Set: 4
    11. SAA Service Profile Name: appcpro (CSCON profile name)

  2. Press Enter to save your changes.

  3. Exit SITUIL.

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. At the NetWare server console prompt, enter the following commands:
    LOAD COMMEXEC
    CSLOAD APPCPRO
    LOAD CPIC_SAA SYS:\SYSTEM\NWSAA\CPIC\MVSTIVSM.CPI
    LOAD SYS:\TIVSM\DSMC
Note:Use CSUNLOAD APPCPRO to unload the appcpro profile.

Considerations for Using NetWare for SAA Clients

You can support two different service profiles on the NetWare for SAA client. For example, you could have a type 2.0 service profile for 3270 emulation and a type 2.1 service profile for TSM. There are two ways to accomplish this:

  1. Use two separate, physical LAN boards on the NetWare server.

    The advantage of using a separate board for the LU6.2 traffic is performance.

  2. Using the same physical board.

    NetWare for SAA can service a type 2.0 service profile and a type 2.1 service profile using the same physical board. For this to work, the SOURCE SAP (Service Access Point) for the 2.0 service profile should be changed to '08' and the 2.1 service profile should use a SOURCE SAP of '04'.

    Note:Using the same physical board does not work using SOURCE SAP '04' for the 2.0 service profile and SOURCE SAP '08' for the 2.1 service profile. The SOURCE SAP for the SNA connections are configured using CSCON.


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