Configuration Example

The configuration is performed with SNA Server Admin. This is also used for starting and stopping connections.

For a complete and consistent example configuration, see the following topic:
Connecting R/3 and R/2 on an IBM Host

For a detailed description of SNA Server Admin, refer to the Microsoft SNA SERVER Administration Guide.

The configuration is explained below using step-by-step examples:

Here you define the Network Name and Control Point Name (PU Name).

z.B.: Network Name: DESAPW00

Control Point Name: PTRMXB

Here you define the connection to the SNA network.

Connection Name: Token1

Link Service: SnaDlc1

802.2 Setup:

Remote Network Adress: 400072A3FFFF

Local Node Name:

Local Node ID: D9D 4E7C2

Remote Node Name:

Network Name: DESAPW00

Control Point Name: SAP3

Remote Node ID:

Remote End: Host System

Activation: On Server Startup

Allowed Directions: Outgoing- Incoming Calls

Connections via an Independent LU 6.2

LU 6.2 Type: Independent

LU Alias: LU#0

Network Name: LTRMXB0

Enable Automatic Partnering: yes

LU Alias: K50

Network Name: DESAPW00

LU Name: K50

Uninterpreted LU Name: K50

Supports parallel sessions: yes

Enable Automatic Partnering: yes

LU Alias: K43

Network Name: DESAPW00

LU Name: NN

Uninterpreted LU Name: NN

Supports parallel sessions: yes

Enable Automatic Partnering: yes

K50 and K43 are partner Lus of LU#0. LU#0 is listed twice in your ‘Partner’ directories; Log Modes SNASVCMG and LU62SAP1 are used.


Mode Name: SNASVCMG:

Parallel Session Limit: 2

Minimum Contention Winner Limit:: 1

Partner Min Contention Winner Limit:: 1

Automatic Activation Limit: 1

Enable Automatic Partnering: No

High Priority Mode: Yes

Pacing Send & Receive Count: 0

Max Send & Receive RU Size: 256


Mode Name: LU62SAP1:

Parallel Session Limit: 8

Minimum Contention Winner Limit:: 4

Partner Min Contention Winner Limit:: 4

Automatic Activation Limit: 0

Enable Automatic Partnering: No

High Priority Mode: Yes

Pacing Send & Receive Count: 8

Max Send & Receive RU Size: 4096

The two modes are not a component of Microsoft SNA Server Distribution, and must be created. The definition of the SNASVCMG LOGMODE must be the same as the definition in the SNA network.

Set System Variable for Side Info File

You must define the name and directory of the valid side info file through the side_info system variable:

Example: G:\usr\sap\C11\G44\data\sideinfo

Proceed as follows:

  1. Start the ‘CONTROL.EXE’ program using the ‘Control Panel’ icon in Windows NT.
  2. Select the ‘System’ icon in the Control Panel window. You can set system and user environment variables in the window that you now see.

Alternatively you can set the side_info system variable by inserting the following key (REGEDT32).

Key Name: SYSTEM\CurrentControlSet\Control\Session Manager\Environment

Class Name: <NO CLASS>

Last Write Time: 8-23-94 - 5:35p

Value 0

Name: ComSpec


Data: %SystemRoot%\system32\cmd.exe


Value 3

Name: side_info

Type: REG_SZ

Data: G:\usr\sap\C11\G44\data\sideinfo


Setting up Invokable TPs

Invokable TPs can be used for starting conversations from R/2 to other systems or to external programs. Invokable TPs are implemented as WinNT Services. Each invokable TP requires a Sideinfo entry that describes the target of the conversation that is to be held using the invokable TP.

The following entry contains variable names enclosed in angle brackets. These variable names must be replaced with the identifiers valid in your installation:

The invokable TP itself is a copy of the following program:

The invokable TP is created using the following command:
copy gwhost.exe <TP-NAME>.exe

Take care to distinguish between upper and lower case in <TP-NAME>.

Do not forget to repeat this step if you install a new version of gwhost.exe.

The NTSCMGR.EXE utility program (in the same path as the SAP programs) helps you set up the service. It creates a service entry that allows a TP to be started. You call the NTSCMGR.EXE utility as follows:

-b \\<GW-MACHINE>\sapmnt\<SID>\SYS\exe\run\sapntstarttp.exe
-p \\<GW-MACHINE>\sapmnt\<SID>\SYS\exe\run\<TP-NAME>.exe

Caution: The command illustrated in the above example has to be entered in a single line.

You now have to change the start mode of the service in a way that causes the <TP-NAME>.exe program to be started under the user ID of the gateway administrator <SIDADM>: To do this Start the ‘CONTROL.EXE’ program using the ‘Control Panel’ icon in Windows NT.

Select the Services icon in the Control Panel window. The <TP-NAME> service is selected, in the ‘Startup’ menu the gateway administrator account is selected. If you now enter the gateway administrator’s password, you can then start the <TP-NAME> service.

As a result, the Registry database will now contain the following entry:

Key Name: SYSTEM\CurrentControlSet\Services\<TP-NAME>

Name: DependOnGroup

Name: DependOnService
Data: LanmanWorkstation LanmanServer

Name: DisplayName
Type: REG_SZ
Data: <TP-NAME>

Name: ErrorControl
Data: 0x1

Name: ImagePath
Data: \\<GW-MACHINE>\sapmnt\<SID>\SYS\exe\run\sapntstarttp.exe

Name: ObjectName
Type: REG_SZ
Data: <SIDADM>

Name: Start
Data: 0x2

Name: Type
Data: 0x10

Key Name: SYSTEM\CurrentControlSet\Services\<TP-NAME>\Security

Installation Example

The symbolic destination of the R/3 target system (host: hs5001, dispatcher port=sapdp93) is BIN.

The executable programs can be found in the following directory: \\gw\saploc\P22\SYS\exe\run

The valid side info file sideinfo can be found in the following directory: \\gw\saploc\P22\G44\data

The installation consists of the following steps:

  1. Log on as the local administrator
  2. Set system variable:
  3. Call Registry Editor (REGEDT32.EXE).
  4. Define the new value in the HKEY_LOCAL_MACHINE on Local Machine window:
    1. Directory: SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2. Edit ® Add Value

    Value Name: side_info
    String: \\gw\saploc\P22\G44\data\sideinfo.

  5. Select Control Panel ® System. Set the side_info environment variable to the following path: \\gw\saploc\P22\G44\data\sideinfo
  6. Generate invokable TP:
  7. CD \\gw\saploc\P22\SYS\exe\run
    COPY gwhost.exe BIN.exe

  8. Enter services:
  9. CD \\gw\saploc\P22\SYS\exe\run
    NTSCMGR install BIN -m gw
    -b \\gw\saploc\P22\SYS\exe\run\sapntstarttp.exe
    The service will now be modified so that it can run under the gateway administrator’s ID.

  10. Make the side info entry:

Edit \\gw\saploc\P22\G44\data\sideinfo:

You can start the TP BIN after restarting the SNA Server and the Service BIN.