Configuring SNA Server 3.0

Restriction: This topic applies to Windows environments only.

This procedure describes the steps for configuring the SNA Server, version 3.0. Be sure to complete all tasks. Use the values from your SNA Server Worksheet (3.0).

  1. Insert a Link Service
    1. Start the SNA Server Manager if it is not already running.
    2. In the Server Manager window, select the name of your SNA Server.
    3. Select the Link Service command from the Insert menu.
    4. Select DLC 802.2 Link Service in the Insert Link Service dialog box, then click Add.
    5. Click OK in the DLC 802.2 Link Services Properties dialog box to accept the default settings.
  2. Configure SNA Server Properties
    1. In the Server Manager window, select the name of your SNA Server.
    2. Select the Properties command from the View menu.
    3. On the General tab in the Properties dialog box, set the following:
      In this field... Specify the following...
      Network Name The SNA network name (NETID) of your VTAM system as defined in SYS1_VTAMLST(ATCSTRxx).

      Worksheet value E1.

      Control Point The control point name (CPNAME) for this server as specified in the PU definition of VTAM or NCP.

      Worksheet value E2.

    4. Click OK to close the Properties dialog box.
  3. Create and configure a connection
    1. In the Server Manager window, select the name of your SNA Server.
    2. Select the Connection command from the Insert menu, then select 802.2.
    3. On the General tab in the Connection Properties dialog box, set the following:
      In this field... Specify...
      Name A name for this connection.

      Worksheet value E3.

      Link Service SnaDlc1
      Support Dynamic Remote APPC LU Definition Enable
      Remote End Host System
      Allowed Directions Both Directions
      Activation The event that will activate this connection. We recommend that you select Server Startup.

      Worksheet value E7.

    4. Select the Address tab in the Connection Properties dialog box and set the following:
      In this field... Specify...
      Remote Network Address The 12-digit hexadecimal network address (MAC address) as defined in the MACADDR= parameter in VTAM or NCP controller definition.

      Worksheet value E8.

      Remote SAP Address The remote SAP address. For most installations, the default value of 04 is appropriate.

      Worksheet value E9.

    5. Select the System Identification tab in the Connection Properties dialog box and set the following:
      In this field... Specify...
      Network Name

      (Local)

      The SNA network name (NETID) of your VTAM system as defined in SYS1_VTAMLST(ATCSTRxx). (The Network Name specified in TASK 2 will automatically appear in this field.)

      Worksheet value E1.

      Control Point

      (Local)

      The control point name of your VTAM system as defined by the VTAM PU. (The Control Point name specified in TASK 2 will automatically appear in this field.)

      Worksheet value E11.

      Local Node ID The 8-digit hexadecimal local ID number for this server. The first three digits must match the IDNUM parameter in VTAM, and the last five digits must match IDBLK

      Worksheet value E12.

      XID Type Format 3
      Network Name

      (Remote)

      The SNA network name (NETID) of your VTAM system as defined in SYS1_VTAMLST(ATCSTRxx).

      Worksheet value E1.

      Control Point

      (Remote)

      The system services control point name (SSCPNAME) of the host node as specified in the PU definition of VTAM or NCP.

      Worksheet value E15.

      Remote Node ID Leave blank
    6. Select the 802.2 tab in the Connection Properties dialog box and verify that the Max BTU Length is less than or equal to MAXDATA in the VTAM PU definition.
    7. Click OK to close the Connection Properties dialog box.
  4. Create and configure the APPC Mode Definition
    1. In the Server Manager window, select the name of your SNA Server.
    2. Select the APPC command from the Insert menu, then select Mode Definition.
    3. On the General tab in the Remote APPC Mode Definition dialog box, set the following:
      In this field... Specify the following...
      Mode Name IBMRDB or an independent mode definition that you have defined in VTAM.

      If you use your own mode definition, it must support parallel sessions.

      Worksheet value E33.

    4. Select the Limits tab and set the following:
      In this field... Specify the following...
      Parallel Session Limit The DSESLIM value for your PU definition in SYS1_VTAMLST.

      Worksheet value E34.

      Minimum Contention Winner Limit Half the number specified in the Parallel Session Limit field.
    5. Complete the Limits tab by setting the following suggested values or specifying appropriate values for your network configuration:
      Field Name Suggested Value...
      Partner Minimum Contention Winner Limit 0
      Automatic Activation Limit 0
    6. Select the Characteristics tab and set the following suggested values or use values appropriate for your network configuration:
      Field Name Suggested Value...
      Pacing Send Count 7
      Pacing Receive Count 7
      Max Send RU Size 4096
      Max Receive RU Size 4096
      High Priority Mode Enabled
    7. Click OK to close the Local APPC LU Properties dialog box.
  5. Create and configure the local APPC LU
    1. In the Server Manager window, select the name of your SNA Server.
    2. Select the APPC command from the Insert menu, then select Local LU.
    3. On the General tab in the Local APPC LU Properties dialog box, set the following:
      In this field... Specify...
      LU Alias A name that represents this machine in its local SNA communications configuration.

      We recommend that you use the XDB Server name as the alias for this machine.

      Worksheet value E18.

      Network Name The SNA network name (NETID) of your VTAM system as defined in SYS1_VTAMLST(ATCSTRxx). The Network Name specified earlier should automatically appear in this field.

      Worksheet value E1.

      LU Name The LU name of this APPC LU as it is specified in VTAM.

      Worksheet value E20

    4. Select the Advanced tab in the Local APPC LU Properties dialog box and set the following:
      In this field... Specify the following...
      Member of Default Outgoing Local APPC LU Pool Disable
      Implicit Incoming Remote LU IBMRDB, an independent mode definition that you have defined, or <None>.

      If you use your own mode definition, it must support parallel sessions.

      LU6.2 Type Independent
      SyncPoint Support Disabled
    5. Click OK to close the Local APPC LU Properties dialog box.
  6. Create and configure the Remote APPC LU
    1. In the Server Manager window, select the name of your SNA Server.
    2. Select the APPC command from the Insert menu, then select Remote LU.
    3. On the General tab in the Remote APPC LU Properties dialog box, set the following:
      In this field... Specify...
      Connection The name of your connection
      LU Alias A name to represent the remote APPC LU in this server's SNA communication configuration.

      Worksheet value E26.

      Network Name The SNA network name (NETID) of your VTAM system as defined in SYS1_VTAMLST(ATCSTRxx). The Network Name specified earlier should automatically appear in this field.

      Worksheet value E1.

      LU Name The VTAM APPLID for DB2.

      Worksheet value E28 and A9.

      Uninterpreted LU Name The same VTAM APPLID specified in LU Name above, or nothing (leave blank).
    4. Select the Options tab in the Remote APPC LU Properties dialog box and set the following:
      Set this field... To...
      Supports Parallel Sessions Enabled
      Implicit Incoming IBMRDB, an independent mode definition that you have defined, or <None>

      If you use your own mode definition, it must support parallel sessions.

      Session-Level Security No Session-Level Security
    5. Click OK to close the Local APPC LU Properties dialog box.
    6. Select the Save command on the File menu to save this configuration, then restart the server to put the new configuration into effect.

      The connection is ready to use with XDB Link.