Commitment control support for DDM

 

iSeries™ applications can commit or roll back transactions on remote iSeries servers.

However, DDM does not support the iSeries journaling commands (CRTJRN, CRTJRNRCV, and STRJRNPF). Before running applications, a user must create a journal on the target iSeries servers for recoverable resources to be used under commitment control, start journaling the physical files that are to be opened under commitment control, and issue the Start Commitment Control (STRCMTCTL) command on the source server. The STRCMTCTL command does not Support the Notify Object (NTFOBJ) command for DDM files. Another way to setup journaling on the remote server is to use the SBMRMTCMD DDM support to submit the journal commands to the target server to journal the remote files.

For DDM conversations to use two-phase commitment control, the DDM conversations need to be protected. For DDM conversations to be protected, the appropriate DDM file must have been created with the protected conversation (PTCCNV) parameter set to *YES.

 

Parent topic:

Programming language considerations for DDM

 

Related concepts


Commitment control

 

Related reference


DDM architecture-related restrictions