EGL Server Guide for iSeries

Application run-time considerations

The following sections describe the considerations to keep in mind during application run time.

Starting and ending commitment control cycles

To use iSeries Commitment Control Services for single-system iSeries applications, you must explicitly start and end a commitment control cycle using the start commitment control (STRCMTCTL) command to start the commitment control and the end commitment control (ENDCMTCTL) command to end the commitment control. EGL Server for iSeries does not implicitly start or end commitment control cycles for single-system iSeries applications. However, DB2(R) implicitly starts commitment control automatically for applications that use SQL I/O statements. After commitment control is started for the job, both native database I/O and SQL I/O can use the common commitment control that iSeries provides.

For EGL client/server applications and Web applications, commitment control is started by the run-time CL for the application.

If necessary, the commitment control for an SQL application can be changed by modifying the FDAPREP REXX program and is further controlled by a user-defined SYMPARM during generation.

If no commitment control cycle is active and the application attempts to open a file requiring commitment control, the application ends with an error condition. Messages in the job log explain the exact nature of the error. The application ends abnormally under these conditions because it might attempt to explicitly commit changes to a file, but that is possible only with an active commitment control cycle.


[ Top of Page | Previous Page | Next Page | Table of Contents ]