User`s guide

Developing an Oracle Database/openUTM Application
openUTM Product Set 8-3
An Oracle Database/openUTM application requires the following information for
execution:
■ Information about the application
■ Username/password with access protection
■ Information about the terminal and communication partners
■ Information about the transaction codes
These properties collectively form the configuration, which is stored in the
KDCFILE file. The configuration definition is carried out by the KDCDEF utility.
This section gives the descriptions for three commands that are important for
connecting to the Oracle database. They are:
■ DATABASE
When the Oracle Database/openUTM application is generated, you must
specify that openUTM communicates with the Oracle Database. Enter the
following command to specify openUTM communication with the database:
DATABASE TYPE=XA,ENTRY=XAOSWD
where TYPE=XA specifies the use of the XA interface and ENTRY=XAOSWD
specifies the name of the XA switch for the Oracle database (for dynamic
registration).
■ OPTION
If you specify the corresponding GEN operand in the OPTION command, then
the
KDCDEF utility also produces the source-code for the KDCROOT table module.
The syntax of
OPTION is as follows:
OPTION [DATA=filename][,GEN={KDCFILE|ROOTSRC|NO|ALL}]
[,ROOTSRC=filename][,SHARETAB=filename]
[,TEST={N[o]|Y[ES]}]
■ MAX
Another important operand is APPLIMODE , which is specified in the MAX
command. This determines restart behavior after a system failure. The syntax
of
MAX is as follows:
MAX APPLINAME=name[,APPLIMODE={S[ECURE]|F[AST]}]
[,ASYNTASKS=number][...]
APPLIMODE = SECURE means that openUTM continues after an application
malfunction with a coordinated warm-start of the openUTM application and
the Oracle database.
If you specify APPLIMODE = FAST , then no openUTM application restart is
executed, as openUTM stores no restart information. In the event of an error,
the application starts from scratch. Transactions that are still open after an
openUTM-application malfunction are rolled back automatically.
See the UTM.DEMO.P.KDCDEF file for an example procedure for building the KDCFILE
and the
KDCROOT table module.
3. Translating the KDCROOT table module and openUTM program units:
The source of the KDCROOT table module should be compiled with the BS2000
Assembler and the openUTM program units should be compiled with the