User`s guide

ManualsBrandsSiemens ManualsComputer equipmentBS2000/OSD

Developing an Oracle Database/openUTM Application

8-4 Oracle Database Installation and Administration Guide

corresponding programming language compilers. See the example procedure

UTM.DEMO.P.KDCROOT

for the compilation of the

KDCROOT

table module.

4. Linking the openUTM application program:

The openUTM application program is produced by linking the

KDCROOT

table

module with the openUTM program units.

You must include the stub module XAOSTUB:

INC-MOD LIB=ORAUID.XAO.LIB,ELEM=XAOSTUB

Note: Instead of writing the binding procedure, you should use the

example procedure

UTM.DEMO.P.PROBIND

and apply modifications

when needed.

If you must write your own binding procedure, then study the

exampl

e carefully before writing one.

5. Starting the openUTM application:

An example procedure for starting the openUTM application can be found in the

UTM.DEMO.P.PROSTRT

When starting the openUTM application, you must specify the start parameters

for openUTM

, as well as for the Oracle Database.

The openUTM start parameters are described in the openUTM manual Usin

openUTM Applications under BS2000/OSD.

The start parameter for using the XA interface for coor

dinated inter-operation with

Oracle Database 10g is:

.RMXA RM="Oracle_XA",OS="<ORACLE open string>"

8.4.1 Defining an Open String

This section describes how to construct an open string. The transaction monitor uses

this string to open the database. The maximum number of characters in an open string

is 256, and the maximum number of open strings is 8. Construct the string as follows:

Oracle_XA{+required_fields...}[+optional_fields...]

where the

required_fields

are:

■

Acc

P/user/access_info

■

SesTm

session_time_limit

and the

optional_fields

are:

■

db_name

■

MaxCur

maximum_no_of_open_cursors

■

SqlNet

connect_string

■

DbgFl

value_from_1_to_15