Transaction Restrictions

Other than memory and disk space, there is no restriction on the number of nesting levels in transactions. However, it is important to remember that having many levels in a transaction affects system performance.

You cannot use the following statements while a transaction is active. Doing so causes a fatal error.

CLEARFILE statement
SET TRANSACTION ISOLATION LEVEL statement

You cannot use the EXECUTE or PERFORM statements in a transaction to execute most InfoSphere® DataStage® commands and SQL statements. However, you can use EXECUTE statement and PERFORM statement to execute the following InfoSphere DataStage commands and SQL statements within a transaction:

Table 1. Commands permitted in a transaction
CHECK.SUM	INSERT	SEARCH	SSELECT
COUNT	LIST	SELECT (RetrieVe)	STAT
DELETE (SQL)	LIST.ITEM	SELECT (SQL)	SUM
DISPLAY	LIST.LABEL	SORT	UPDATE
ESEARCH	RUN	SORT.ITEM
GET.LIST	SAVE.LIST	SORT.LABEL

If a BASIC statement in a transaction has an ON ERROR clause and a fatal error occurs, the ON ERROR clause is ignored.