Commitment control support for DDM

IBM® i applications can commit or roll back transactions on remote IBM i operating systems.

However, DDM does not support the IBM i journaling commands (CRTJRN, CRTJRNRCV, and STRJRNPF). Before running applications, a user must create a journal on the target IBM i operating systems 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 client system. The STRCMTCTL command does not Support the Notify Object (NTFOBJ) command for DDM files. Another way to set up journaling on the remote system is to use the SBMRMTCMD DDM support to submit the journal commands to the server system 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. The protected conversation (PTCCNV) parameter allows a values of *YES when the address type is *SNA and *IP. To set PTCCNV(*YES)) for *IP address type, specify *RDB in the remote location (RMTLOCNAME) parameter and specify an RDB in the relational database (RDB) parameter. The RDB relational database directory entry can be either specify *IP or *SNA. Please refer to the Add RDB Directory Entry (ADDRDBDIRE) and Work with Relational Database Directory Entries (WRKRDBDIRE) commands to add a RDB directory entry.