GDSX (Extended General Device Support) Manual

Design and Development

Extended General Device Support (GDSX) Manual—529931-001

2-37

Transaction Management Facility

TMF protects transactions originating from the user tasks of a GDSX application.

GDSX supports four pseudo TMF procedures:

•

^ABORTTRANSACTION

•

^BEGINTRANSACTION

•

^ENDTRANSACTION

•

^RESUMETRANSACTION

Except for ^BEGINTRANSACTION, these pseudo procedures have the same syntax

and function as their TMF counterparts. You must set the TMF configuration

parameter to 2 to have these procedures work properly from a user task.

TMF Configuration Parameter

The TMF configuration parameter can be set for three processing modes:

See GDSX Configuration Parameters on page 2-46 for an explanation of how to set

configuration parameters.

Using the Pseudo Procedures

In a user task, you use ^BEGINTRANSACTION and ^ENDTRANSACTION to define

the elements of a transaction. When processing successfully completes for all

elements of the transaction, the transaction is said to be complete.

If any of the elements cannot be processed, the transaction is incomplete and an error

is returned to the user task. When an error is returned, the user task must determine

what to do next. One choice is to cancel the transaction with a call to

^ABORTTRANSACTION. Any elements of the transaction that were completed at the

time ^ABORTTRANSACTION is called are backed out of the system, as if the

transaction had never taken place. For example, data written to a database is

removed and the database is returned to the state it had before the new data changed

it.

If a user task needs to suspend processing of a TMF transaction to do processing

unrelated to the TMF transaction, the transaction’s status can be changed to pending

Mode Description

0 TSCODE does not permit any TMF processing from a user task, and it will not

pass a TMF transaction from an external process to another process, such as

Pathway. This is the default setting.

1 TSCODE does not permit any TMF processing from a user task; however, it will

pass a TMF transaction from an external process to another process.

2 TSCODE permits TMF processing from a user task, but it will not pass a TMF

transaction from an external process to another process.