STARTTPM

The STARTTPM (Start Transaction Processing Monitor) op code is used to establish a commitment definition. This command specifies the level of record locking that occurs for the commitment definition to be started. You can specify some text that briefly describes the commitment definition to be started.

STARTTPM
Db (Database Object)
Level ( *LOW | *MEDIUM | *HIGH | *SERIAL)
Text (*NONE | Character Expression)
ExtraParms (Parm List)
Err (Indicator Variable | *EXTENDED)

Parts

Db

Required. The database connection for which transaction processing is to be started. Database Objects are defined with the DCLDB command.

Level

Optional. Specify the level of record locking that occurs for the commitment definition to be started.

*LOW - *CHG ReadUncommited - Do not issue shared locks and do not honor exclusive locks. When this option is in effect, it is possible to read an uncommitted transaction or a set of pages that are rolled back in the middle of a read. Dirty reads are possible.
*MEDIUM - *CS ReadCommited - Perform a scan with the same locking semantics as a transaction running at the READ COMMITTED isolation level. By default, SQL Server 2000 operates at this isolation level.
*HIGH - *ALL RepeatableRead - Perform a scan with the same locking semantics as a transaction running at the REPEATABLE READ isolation level.
*SERIAL - *ALL Serializable - Hold a shared lock until completion of the transaction instead of releasing the lock as soon as the required table, row, or data page is no longer required.

Text

Optional. Specify some text that briefly describes the commitment definition to be started.

ExtraParms

Optional. Specify some extra parameters to be used.

Err

Optional. Determines what the runtime will do if an error occurs while executing this command. The following rules apply:

Err (Indicator Variable) - The specified Indicator is set if an error occurred.
Err (*EXTENDED) - A program status flag is set whose status can be checked using the %ERROR built-in function.
If the Err keyword is not given and an error occurs, a runtime exception will be thrown, terminating the program.

Remarks

Important: You must start and end commitment control on SQL Server and System i with the STARTTPM and ENDTPM commands from your application. For the System i, do not employ the STRCMTCTL and ENDCMTCTL commands.

When running commitment control on the System i with DataGate, transaction processing must be started with the STARTTPM command. The AVR runtime uses the AdgTransaction object to initiate and control transactions. If you initiate commitment control commands via CALL/Parm, the runtime has no knowledge of the server transaction, and as a result, you will receive an exception in the Commit and Rollback statements.

STARTTPM

Parts

Remarks

See Also