Access Service User's Guide DirectConnect for AS/400

Home

Access Service User's Guide DirectConnect for AS/400

Appendix B Quick Reference

Transaction management

This section contains tables showing the relationship between the combination of TransactionMode, Allocate, and StopCondition property settings and transaction behavior.

The following four tables show the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of short.

*TransactionMode=short, Allocate=request, StopCondition=error*
Condition/Status	Effects of Settings on Processing
Does a rollback occur on an error?	The transaction rolls back immediately.
What is the status of connection after an error occurs?	The connection ends.
What happens if a begin transaction occurs?	A commit occurs and uses begin transaction behavior described in Table 5-9.
When the client application issues a commit or rollback, what happens?	A commit or rollback occurs.
If the request is a cursor or dynamic request, how does it behave?	The request behaves the same as TransactionMode=long.
In batch mode, what happens if an error occurs?	The batch ends and a rollback occurs.
When completed, is a batch job committed?	The batch commits if no errors occur.
After the batch commits, what is the status of the connection?	The connection ends.

The following table shows the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of short.

*TransactionMode=short, Allocate=request, StopCondition=none*
Condition/Status	Effects of Settings on Processing
Does a rollback occur on an error?	A rollback does not occur.
What is the status of the connection after an error occurs?	The connection continues.
What happens if a begin transaction occurs?	A commit occurs and uses begin transaction behavior described in Table 5-9.
When the client application issues a commit or rollback, what happens?	A commit or rollback occurs.
If the request is a cursor or dynamic request, how does it behave?	The request behaves the same as TransactionMode=long.
In batch mode, what happens if an error occurs?	The batch continues executing.
When completed, is a batch job committed?	The batch is always committed.
After the batch commits, what is the status of the connection?	The connection ends.

The following table shows the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of short.

*TransactionMode=short, Allocate=connect, StopCondition=error*
Condition/Status	Effects of Settings on Processing
Does a rollback occur on an error?	The transaction rolls back immediately.
What is the status of the connection after an error occurs?	The connection continues.
What happens if a begin transaction occurs?	A commit occurs and uses begin transaction behavior described in Table 5-9.
When the client application issues a commit or rollback, what happens?	A commit or rollback occurs.
If the request is a cursor or dynamic request, how does it behave?	The request behaves the same as TransactionMode=long.
In batch mode, what happens if an error occurs?	The batch request ends.
When completed, is a batch job committed?	The batch commits if no errors occur.
After the batch commits, what is the status of the connection?	The connection continues.

The following table shows the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of short.

*TransactionMode=short, Allocate=connect, StopCondition=none*
Condition/Status	Effects of Settings on Processing
Does a rollback occur on an error?	A rollback does not occur.
What is the status of the connection after an error occurs?	The connection continues.
What happens if a begin transaction occurs?	A commit occurs and uses begin transaction behavior described in Table 5-9.
When the client application issues a commit or rollback, what happens?	A commit or rollback occurs.
If the request is a cursor or dynamic request, how does it behave?	The request behaves the same as TransactionMode=long.
In batch mode, what happens if an error occurs?	The batch continues.
When completed, is a batch job committed?	The batch commit occurs, if no errors occur.
After the batch commits, what is the status of the connection?	The connection continues.

The following four tables show the effects of StopCondition and Allocate properties, based on a TransactionMode setting of long.

*TransactionMode=long, Allocate=request, StopCondition=error*
Condition/Status	Effect of Settings on Processing
Does a rollback occur on an error?	A rollback does not occur.
What is the status of the connection after an error occurs?	The connection continues.
What happens if a begin transaction occurs?	The begin transaction is ignored. Also, an informational message appears.
When the client application issues a commit or rollback, what happens?	If TransactionMode was originally short, and cursors and dynamics were all freed, the commit or rollback occurs and TransactionMode changes back to short. If TransactionMode was originally long, then a commit or rollback occurs.
If the request is a cursor or dynamic request, how does it behave?	If TransactionMode was originally short, and cursors and dynamics were all freed, a commit occurs and TransactionMode changes back to short. If TransactionMode was originally long, then the connection behaves the same as Allocate=request until all cursors and dynamics are freed
In batch mode, what happens if an error occurs?	The batch transaction ends.
When completed, is a batch job committed?	The batch does not commit.
After the batch commits, what is the status of the connection?	The connection ends if the commit or rollback occurs at the end of batch. Otherwise, the connection continues.

The following table shows the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of long.

*TransactionMode=long, Allocate=request, StopCondition=none*
Condition/Status	Effects of Settings on Processing
Does a rollback occur on an error?	A rollback does not occur.
What is the status of the connection after an error occurs?	The connection continues.
What happens if a begin transaction occurs?	The access service ignores the begin transaction command.
When the client application issues a commit or rollback, what happens?	If TransactionMode was originally short, and cursors and dynamics were all freed, the commit or rollback occurs and TransactionMode changes back to short. If TransactionMode was originally long, then a commit or rollback occurs.
If the request is a cursor or dynamic request, how does it behave?	If TransactionMode was originally short, and cursors and dynamics were all freed, a commit occurs and TransactionMode changes back to short. If TransactionMode was originally long, then the connection behaves the same as Allocate=request until all cursors and dynamics are freed.
In batch mode, what happens if an error occurs?	The batch continues.
When completed, is a batch job committed?	The batch does not commit.
After the batch commits, what is the status of the connection?	The connection ends if the commit or rollback occurs at the end of the batch. Otherwise, the connection continues.

The following table shows the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of long.

*TransactionMode=long, Allocate=connect, StopCondition=error*
Condition/Status	Effects of Settings on Processing
Does a rollback occur on an error?	A rollback does not occur.
What is the status of the connection after an error occurs?	The connection continues.
What happens if a begin transaction occurs?	The access service ignores the begin transaction command.
When the client application issues a commit or rollback, what happens?	If TransactionMode was originally short, and cursors and dynamics were all freed, the commit or rollback occurs and TransactionMode changes back to short. If TransactionMode was originally long, then a commit or rollback occurs.
If the request is a cursor or dynamic request, how does it behave?	If TransactionMode was originally short, and cursors and dynamics were all freed, the commit occurs and TransactionMode changes back to short. If TransactionMode was originally long, then the connection behaves the same as Allocate=request until all cursors and dynamics are freed.
In batch mode, what happens if an error occurs?	The batch request ends.
When completed, is a batch job committed?	The batch does not commit.
After the batch commits, what is the status of the connection?	The connection continues.

The following table shows the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of long.

*TransactionMode=long, Allocate=connect, StopCondition=none*
Condition/Status	Effects of Settings on Processing
Does a rollback occur on an error?	A rollback does not occur.
What is the status of the connection after an error occurs?	The connection continues.
What happens if a begin transaction occurs?	The access service ignores the begin transaction command.
When the client application issues a commit or rollback, what happens?	If TransactionMode was originally short, and cursors and dynamics were all freed, the commit or rollback occurs and TransactionMode changes back to short. If TransactionMode was originally long, then a commit or rollback occurs.
If the request is a cursor or dynamic request, how does it behave?	If TransactionMode was originally short, and cursors and dynamics were all freed, a commit occurs and TransactionMode changes back to short. If TransactionMode was originally long, then the connection behaves the same as Allocate=request until all cursors and dynamics are freed.
In batch mode, what happens if an error occurs?	The batch continues.
When completed, is a batch job committed?	The batch does not commit.
After the batch commits, what is the status of the connection?	The connection continues.

The following table shows the effect on processing when a begin transaction command occurs in a request.

Effects of *begin transaction* command on processing
Condition/Status	When begin transaction occurs...
Does a rollback occur on an error?	A rollback does not occur.
What is the status of the connection after an error occurs?	The connection continues.
What happens if another begin transaction occurs?	The access service ignores the begin transaction command.
When the client application issues a commit or rollback, what happens?	If TransactionMode was originally short, it changes back to short. If TransactionMode was originally long, then a commit or rollback occurs.
If the request is a cursor or dynamic request, how does it behave?	The request continues behaving as a short setting.
In batch mode, what happens if an error occurs?	The batch continues.
When completed, is a batch job committed?	The batch does not commit.
After the batch commits, what is the status of the connection?	The connection continues.


	Expand Search