SAP Configuration

CPI-C connections are referenced via logical destinations (symbolic destinations). These destination names can be selected by the user. The assignment of these symbolic destinations to the actual connections with LU and TP is made in the side info file.

The SAP environment contains the following side info files:

XCOM

An R/2 table for all connections initiated on the R/2 side.

sideinfo

An OS/2 file system file (normally found in D:\SAP\GW\sideinfo) that is required by the SAP gateway and from any external C-programs.

CUA Interface

Only the sideinfo table is required. The CUA Interface is comparable with a CPI-C connection to R/2. A destination is assigned to each R/2 system (e.g. K50). One exception to this occurs when IMS is employed instead of the CICS communications sub-system. In this case the LU6.1 Adapter (e.g. APPCBRDG) is allocated as destination. Specifying the start transaction xxxX1SA controls the choice of SAP system to be used.

A destination can be explicitly specified for each user in the sideinfo, but the LU pooling can also be used. The CM/2 Communications Manager supports this. In the sideinfo the local LU has to be identified with the following entry:

Local_LU=*

If no entry is maintained in the sideinfo for the local LU, then the default LU is automatically used. This has to be specified in the configuration. Working in this way makes sense only with independent LU.

R/2-R/3 Connections

R/2-R/3 connections are not supported on OS/2.

External Programs

The active partner must be identified. A sideinfo entry is needed for establishing a connection from the external program via SNA to R/2.

Initiating the Connection From R/2

An entry in the XCOM table is required if the connection is to be established from R/2 via SNA directly to an external program on the workstation. This contains the LU name as defined in CICS (terminal ID) and the name of the external program that is to be started on the workstation. There must also be a corresponding definition for this program in the Communications Manager Profile under the TRANSACTIONS PROGRAMS heading.

Example Sideinfo File

**********************
* SAP CPI-C SideInfo *
**********************
*
*--------------
* SAP R/2 K50
*--------------
*
DEST=K50
PROTOCOL=C
LOCAL_LU=*
LU=K50
TP=X1SA
MODE_NAME=LU62CPIC
CPIC_TRACE=1
*KEEP_SESSION=1
*
*----------------
* SAP R/2 BS2000
*----------------
DEST=S50
GWHOST=sb0002
GWSERV=sapgw01
PROTOCOL=C
LU=S50
TP=X1SA
CPIC_TRACE=1
*
*--------------
* SAP R/2 IMS
*--------------
DEST=K50IMS
PROTOCOL=C
LU=APPCBRDG
LOCAL_LU=LTRMRB2
MODE_NAME=LU62APPC
TP=K50X1SA
CPIC_TRACE=1
*
DEST=APPCBRDG
PROTOCOL=C
LU=APPCBRDG
LOCAL_LU=LTRMRB3
MODE_NAME=LU62APPC
TP=K50X2SA
CPIC_TRACE=1
*
*---------------
* SAP C-TestPGMe
*---------------
DEST=rcvdata1
GWHOST=p04308
GWSERV=sapgw00
PROTOCOL=E
LU=p04308
TP=rcvdata1
CPIC_TRACE=3

Example TXCOM Entry:

Not applicable, since the OS/2 gateway does not support connections from R/3.

Example XCOM entry:

Display ATAB table XCOM Table of the symbolic destinations for CPI-C

-------------------------------------------------------------------

Symbolische Dest. LU (Logical Unit) TP (Transaktion prog.) Comm.Type

-------------------------------------------------------------------

SCHULTZD FSIFACE MRB3 FSIFACE

SCHULTZKH GRAPHICS MRB2 IMSASYNC

EXT_IBM MRB3 CCPICPT2S