Progress/400
Product Guide


Specifying Transaction Control Techniques

To use server-based transaction control, start journaling and start the OS/400 commitment control facility.

You can specify remote client-based transaction control with the TRANSCTL option of the DataServer (-Dsrv) connection parameter. This is the syntax for -Dsrv TRANSCTL:

SYNTAX
-Dsrv TRANSCTL=value 

In remote client-based transaction control, the remote client uses a Progress local before-image file (LBI). Table 8–1 describes how to use -Dsrv TRANSCTL to implement transaction control.

Table 8–1: DataServer (-Dsrv) Arguments
Keyword
Description
COMMIT
Specifies that commitment control extends to all of the files in the Progress/400 database. A journal receiver must exist for the file to enable transaction management. If you are not journaling a DB2/400 file, the application does not open the file and returns an error.
LBI
Specifies that the remote clients use a local before-image file to manage main transactions and nested subtransactions. If you use local before-imaging, you cannot use OS/400 journaling; the two are not interchangeable. LBI works for single-user mode only.
NONE
Specifies that transaction control is not in effect.
OPTIONAL
Specifies that the DataServer opens a file regardless of whether commitment control is on or off. If commitment control is off for a file, you cannot undo transactions that affect that file. This is the default behavior for the Progress/400 DataServer.

For example, the following CONNECT statement makes sure that a DataServer application does not open any file for which commitment control is not active:

CONNECT as4sh -db mydb2400 -H serv1 -N TCP -S sparesrv
  -Dsrv TRANSCTL=COMMIT. 


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095