Generating UTM-D

Communication between an R/2 UTM System and an external UTM application is based on UTM-D (UTM-VTV).

Distributed transaction processing with UTM-D requires a considerable amount of additional generation, so that UTM-D sessions are available between UTM applications.

The following KDCDEF instructions have been added with UTM-D. We have only made a short list of instructions here. You will find detailed information in the UTM brochure "Generating and Administering Applications".

Defining further BCAM application names
Example: BCAMAPPL B2111001

Definining a logical connection between a local (SAP) and remote (partner) application
Example: CON SI020101,PRONAM=HOST,LPAP=LWP0201

Defining a remote application (name and characteristics of the connection)
Example: LPAP LWP0201,SESCHA=PLU

Defining a session name for the connection between two applications
Example: LSES SW020101,LPAP=LWP0201

Defining the transaction code for the remote application
Example: LTAC X1SA,TYPE=D

Defining characteristics for sessions
Example: SESCHA PLU,PLU=N,CONNECT=Y

Determining global values for local application
Example: UTMD MAXJR=100

Addressing a Partner Process

A remote application must be addressed before messages can be sent to it. This is done with the APRO call. The following is specified:

The remote process and the remote application are addressed with their logical names. For KDCDEF generation, these logical names are defined in the LTAC statement and are linked with the actual names of the partner application in the RTAC operand.

The name of the logical process has the same function as the transaction code of the process. There are two ways of linking it with a partner application:

In this case addressing is one-tier, as the partner application does not have to be specified in the APRO call.

In this case addressing is two-tier. This is used when the same process is to be started in several applications (possibly on various computers).

The same application is running under all four applications (AW1, AW2, AW3 and AW4). The SAP application on the host computer can address the individual applications by the APRO call in the program. The SAP computer link-up supports this concept with the table XCOM. Here you can enter LPAP and LTAC for each partner. If you do not make an LPAP entry, one-tier addressing is assumed. However, two-tier addressing is recommended owing to its flexibility.

Parallel Connections

Parallel sessions are needed if you want to carry out several requests at the same time. For this you have to be able to set up several logical connections between the applications. To make this possible, additional BCAM applications have to be generated with the BCAMAPPL statement at one of the partners only. The CON statement adds the additional connections; the LSES statement adds the additional sessions required.

The TIME parameter in the LTAC statement:

The parameter TIME=(0,0) is necessary for defining the transaction code Y1SA for the DOUT driver. This is so that a driver is only started when a partner system session can be set up, as a DOUT driver simulates synchronous VTV communication (no longer as of UTM-D V2.0). If the value is greater than zero, the messages are taken by UTM and temporarily stored until a session can be set up between both sessions.

 KDCDEF Generation

The KDCDEF generation of the SAP R/2 application must always correspond with the partner UTM application. For KDCDEF generation the file with the UTM-D generation statements is specified via an additional procedure parameter.

The generation file KDCDEFD.HOST is delivered as an example.

This example contains the following statements:

  1. Statements for communication between two host applications.
  2. Two connections are generated, one for S43 as PLU and one for S43 as SLU.

  3. Statements for communication within an application (ideal for test purposes).

 UTM-D Generation

***************************************************************
* *
* UTM-D GENERATION FOR BS2000: *
* *
* xx serial number of the BCAMAPPL statement*
************************************************************
BCAMAPPL B2110101
BCAMAPPL B2110102
*
************************************************************
* SESSION CHARACTERISTICS FOR REQUEST RECEIVER / REQUEST INITIATOR
*
* SLU (secondary LU = request receiver - session)
*
* PLU (primary LU = request initiator - session)
*
* Automatic connection set up, so that it does not matter
* which application is started first.
* No pacing, so that protocol expense is reduced.

****************************************************************
SESCHA SLU,PLU=Y,CONNECT=Y,PACCNT=0
SESCHA PLU,PLU=N,CONNECT=Y,PACCNT=0

****************************************************************
* *
* LPAP defines remote application *
* *
* LPAP Lvsppaa *
* *
* L for LPAP *
* v Connection type W = WAN *
* L = LAN *
* H = HOST *
* s Session type P = primary (Request initiator) *
* S = secondary (Request receiver) *
* pp processor number of the remote application *
* aa serial number of the remote application *
* *
*****************************************************************************
* 1102 = HOST11, B43 (PLU und SLU)
*
LPAP LHS1102,SESCHA=SLU
LPAP LHP1102,SESCHA=PLU
*
* 0201 = SINIX2, CUA application (SAP only SLU)
*
****************************************************************
* CON describes the connection to the partner *
* *
* CON bbxxaayy (as BCAMAPPL) *
****************************************************************
* 1102 = HOST11, B43 (1 * PLU, 1 * SLU)
*
CON B2110201,PRONAM=HOST11,LPAP=LHP1102,BCAMAPPL=B2110102
CON B2110202,PRONAM=HOST11,LPAP=LHS1102,BCAMAPPL=B2110101
*
*****************************************************************
*
* LSES describes a session
*
* LSES Svppaaxx
*
* S Session
* v Connection type H = HOST
*
* pp Processor number of the remote application
* aa Application number of the remote application
* xx serial number
*
****************************************************************
*
* 1102 = HOST11, B43 (2 Sessions, 1 * PLU, 1 * SLU)
*
LSES SH110201,LPAP=LHS1102,RSES=SH111002
LSES SH110202,LPAP=LHP1102,RSES=SH111001
*
************************************************************
* Local connections / sessions for test purposes *
************************************************************
*
BCAMAPPL S4301
LPAP S4301,SESCHA=PLU
CON S4302,PRONAM=HOST11,LPAP=S4301,BCAMAPPL=S4301
LSES S32S1,LPAP=S4301,RSES=S43S2
*
BCAMAPPL S4302
LPAP S4302,SESCHA=SLU
CON S4301,PRONAM=HOST11,LPAP=S4302,BCAMAPPL=S4302
LSES S32S2,LPAP=S4302,RSES=S43S1
************************************************************
* Transaction codes *
************************************************************
*
LTAC X1SA,TYPE=D
LTAC Y1SA,TYPE=A,WAITTIME=(0,0)
*
LTAC Y2SA,TYPE=A,WAITTIME=(1,0)
*************************************************************