SNA Connection under UNIX

The parameters for the R/2 host connection are placed in the sideinfo side info table.

For SNA connections the SAP Gateway always reads the local side info file. If details are available in the XCOM table on the host, they are ignored.

C is the only possible protocol type:
The partner program is an R/2 System and can be accessed via SNA.

The following topics describe the special features of the sideinfo table on UNIX platforms, arising from the configuration of the respective SNA communications subsystem:

SINIX with Transit:
If you are connecting a SINIX system to an SNA host, you need the SNA communications subsystem Transit from SNI .
In a transit environment you do not have to set up a side info table, as it is included in transit generation.
You will find details on transit generation in the section "Communications Subsystems for SNA" under
SINIX: Transit

AIX with SNA Services

On an AIX platform, the side info table contains the following parameters:

DEST Symbolic destination with the number of the communication profile
Number of the communication profile
LU Communication profile of the lineTP Name of the SAP transaction in the DC system
CICS: X1SA
IMS: :xxxX1SA
GWHOST Computer, on which the SAP Gateway is runningGWSERV SAP Gateway servicePROTOCOL Protocol type I, E, C, F or R (see Side Info Parameters)

Special feature

If you are implementing the SAP Gateway (CPI-C Handler) in an IBM environment, you must make an entry in the side info file for each communication profile.

Lines to the same partner must be numbered in ascending order (e.g. DEST=K50_1).

Examples for CICS

When implementing the CICS data communication system on the R/2 host, the following scenarios are possible:

A program written in C on the AIX platform communicates directly with the R/2 system (without the SAP Gateway) via CPI-C/LU6.2.
The following parameters must be defined in the sideinfo:

DEST=K50P
LU=K50T00
TP=X1SA

One of the following partners communicates with the R/2 host via the SAP Gateway:

The host computer and the service of the SAP Gateway must be defined in the sideinfo of the calling system:

DEST=K50
GWHOST=is0001
GWSERV=sapgw00
PROTOCOL=C

The following parameters must be defined in the sideinfo on the host computer of the SAP Gateway:

DEST=K50_1
LU=K50T01
TP=X1SA

DEST=K50_2
LU=K50T02
TP=X1SA

DEST=K50_3
LU=K50T03
TP=X1SA

If the calling program and the SAP program are on the same host computer, then there is only one sideinfo table with all the parameters detailed above.

Examples for IMS

When implementing the IMS data communications system on the R/2 host, the following scenarios are possible:

A program written in C on the AIX platform communicates directly with the R/2 system (without the SAP Gateway) via CPI-C/LU6.2.
The following parameters must be defined in the sideinfo:

DEST=K50IMSP
LU=BRDGT00
TP=K50X1SA

One of the following partners communicates with the R/2 host via the SAP Gateway:

The host computer and the service of the SAP Gateway must be defined in the sideinfo of the calling system:

DEST=K50IMS
GWHOST=is0001
GWSERV=sapgw00
PROTOCOL=C

The following parameters must be defined in the sideinfo on the host computer of the SAP Gateway:

DEST=K50IMS_1
LU=BRDGT01
TP=K50X1SA

DEST=K50IMS_2
LU=BRDGT02
TP=X1SA

DEST=K50IMS_3
LU=BRDGT03
TP=K50X1SA

If the calling program and the SAP program are on the same host computer, then there is only one sideinfo table with all the parameters detailed above.

HP-UX with SNAplusLink

On a HP-UX platform, the side info table contains the following parameters:

DEST Symbolic name (destination) of the target systemGWHOST System, on which the SAP Gateway is runningGWSERV SAP Gateway servicePROTOCOL Protocol type (see section Side Info Parameters)
LU Remote LU6.2 Profile of the SNA configurationMODE_NAME Mode Name Profile of the SNA configurationTP SAP transaction in a DC system:
CICS: X1SA
IMS: xxxX1SA
CPIC_TRACE Trace switch: 0, 1, 2 or 3
(see environment variable CPIC_TRACE)
CONV_TYPE Switch: 1 = Mapped Conversation
0 = Basic Conversation
KEEP_SESSION Session switch for IMS: 1 or 0

Special Features

The parameter MODE_NAME must be defined. In the SNAplusLink configuration, the Local_LUs must be located in the default LU pool.

Examples for CICS

When implementing the CICS data communication system on the R/2 host, the following scenarios are possible:

A program written in C on the HP-UX platform communicates directly with the R/2 host (without the SAP Gateway) via CPI-C /LU6.2.

DEST=K50P
LU=K50T00
TP=X1SA
MODE_NAME=LU62TST1

One of the following partners communicates with the R/2 host via the SAP Gateway:

The host computer and the service of the SAP Gateway must be defined on the calling system:

DEST=K50
GWHOST=is0001
GWSERV=sapgw00
PROTOCOL=C

The following side info parameters must be defined on the host computer of the SAP Gateway:

DEST=K50
LU=K50T00
TP=X1SA
MODE_NAME=LU62TST1

If the calling program and the SAP program are on the same host computer, then there is only one sideinfo table with all the parameters detailed above.

Examples for IMS

When implementing the IMS data communications system on the R/2 host, the following scenarios are possible:

A program written in C on the HP-UX platform communicates directly with the R/2 host (without the SAP Gateway) via CPI-C /LU6.2.

DEST=K50IMSP
LU=BRDGT00
TP=K50X1SA
MODE_NAME=LU62APPC

One of the following partners communicates with the R/2 host via the SAP Gateway:

The host computer and the service of the SAP Gateway must be defined on the calling system:

DEST=K50IMS
GWHOST=is0001
GWSERV=sapgw00
PROTOCOL=C

The following side info parameters must be defined on the host computer of the SAP Gateway:

DEST=K50IMS
LU=BRDGT00
TP=K50X1SA
MODE_NAME=LU62APPC

If the calling program and the SAP program are on the same host computer, then there is only one sideinfo table with all the parameters detailed above.