Programming Example of Working With Local sideinfo File

RFC_OPTIONS rfc_opt; /* Parameter for RFC connection */

RfcEnvironment (...); /* Install error handling function */

rfc_opt.mode = RFC_MODE_CPIC ; */ RFC to SAP R/2 */

rfc_opt.destination = "K50"; /* Entry with this destination */
/* must be in local sideinfo */
/* file and for SAP gateway */

rfc_opt.connopt = NULL /* Connect parameters in */
/* sideinfo file */

rfc_opt.client = "000" /* Client in SAP R/2 */

rfc_opt.user = "RFCTEST" /* CPIC user */

rfc_opt.password = "SECRET" /* Password */

rfc_opt.language = "E" /* Logon language */

rfc_opt.trace = 0 /* No RFC trace */

rfc_handle = RfcOpen (&rfc_opt); /* Open RFC connection */

...

Local sideinfo file

The local sideinfo file must either be in the same directory as the RFC client program or be defined with its full path and file name using the environment variable SIDE_INFO.

Windows: set SIDE_INFO=d:\rfctest\sideinfo

The entry for the above test can be defined as follows:

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

sideinfo file for the SAP gateway running on IBM-AIX machines

DEST=K50_1
LU=K50T1
TP=X1SA

DEST=K50_2
LU=K50T2
TP=X1SA

DEST=K50_3
LU=K50T3
TP=X1SA

The extension _n(n=1,2,,...) makes it possible for the SAP gateway to establish a LU6.2 connection to the R/2 System via different SNA connections.

sideinfo file for the SAP gateway running on HP-UX machines

DEST=K50
LU=K50T
TP=X1SA
LOCAL_LU=LU0001
MODE_NAME=LU62SAP1

  • Specifications about LOCAL_LU are not required if at least one local LU is defined in the LU pool in the SNA-configuration on HP-UX.
  • The LU6.2-mode ’LU62SAP1’ defined as MODE_NAME above must be defined in the SNA-configuration on HP-UX and in IBM-Host.