User`s guide

6
Using the Oracle Database Under openUTM 6-1
6 Using the Oracle Database Under openUTM
This chapter describes the Oracle Database-specific points that you should consider
when using Oracle Database 11g Release 2 (11.2) for BS2000/OSD under openUTM
(Universal Transaction Monitor). The following topics are discussed in this chapter:
■ SQL Operations
■ UTM Operations
6.1 SQL Operations
UTM application program units must use embedded SQL. Calls to the Oracle Call
Interface (OCI) are not allowed.
6.1.1 CONNECT
A connection is implicitly established when the UTM task is started. This connection
uses the data specified in the open string. Further explicit
CONNECT operations issued
by the program units are not allowed.
6.1.2 COMMIT
An explicit COMMIT statement is not allowed in UTM program units. The openUTM
will automatically issue one on a
PEND RE , FI , SP , or FC operation.
6.1.3 ROLLBACK
An explicit ROLLBACK statement is not allowed in UTM program units. The openUTM
will automatically issue a
ROLLBACK statement on encountering a PEND ER , RS , FR, or
RSET operation.
6.1.4 SAVEPOINT
The SAVEPOINT statement is not allowed in UTM program units.
6.1.5 Cursor Operations
A cursor is valid only until a PEND is run. Because of a possible task change during a
PEND KP , PA , or PR , you cannot perform operations on a previously filled cursor such as
OPEN or FETCH after a PEND KP , PA, or PR . However, you can open and fetch a new
cursor after
PEND KP . The alternative to using PEND KP is to use the PGWT-call (Refer
to the openUTM manual, Programming Applications with KDCS for COBOL, C and C++),