Set up a journal on the source server and the target server - aws_mainframe_modernization_service - connect_cdc_mimix_share - Latest

1. Prepare a journal on the source server.

   For all Db2 for i, tables from which you replicate data, you must create or have available one or more journals and accompanying receivers.

   A single journal is often sufficient for all the tables, but you can use multiple journals. A unique Connect CDC process (Db2 for i Change Selector) reads each journal. A table cannot be assigned to more than one journal.

   You can create new journal objects or use existing ones. To create a new journal object and assign tables to it.

   The journal you use for your tables must be distinct from the journal that Connect CDC creates for its metabase tables.

   If you use an existing journal:

   • Do not use QSYS/QAUDJRN, the system audit journal.

   • You may use a QSQJRN journal, a library’s default SQL journal, but be aware that it can grow very large: all tables created within that library using the SQL CREATE TABLE statement are automatically assigned to QSQJRN (as long as the table creator has sufficient authority to write to the journal).

   Note: Do not setup journaling for user tables in the product or install library regardless of whether or not you opt to use the QSQJRN.

   • Make sure the journal’s authorization is *ALL for those users who may start or end journaling for tables that you want journaled.

   • Special examples of this requirement are the user profiles that sign on to IBM i machines on sending and receiving server connections from Connect CDC Director. To use the Connect CDC Director to journal tables for you, the journals’ authorizations must permit access to these users. You can use the IBM i DSPOBJAUT command to display a journal’s authorities, and the GRTOBJAUT command to grant authorities to a journal.

   • Review the journal definition’s settings for change management and delete management of journal receivers. It is important that these receivers, which are the buffers that contain the data-change records that Connect CDC captures and replicates, are not deleted until some time after all their entries are captured and committed. To help ensure this, assign the task (using the journal definition) of changing receivers to IBM, and assign the task (using Connect CDC Director) of deleting receivers to Connect CDC. Even if your site has an existing method of change management in place, it is highly recommended that you assign delete management to Connect CDC to safeguard the data to be replicated. To display or change your journal’s definition, issue the CHGJRN command. If the system is to do change management, set Manage receivers to *SYSTEM (set it to *USER if Connect CDC does change management). If Connect CDC is to do delete management, set Delete receivers to *NO.

   • Assign the tables.

   For tables that are not currently being journaled, issue the STRJRNPF command to start journaling.

   For tables that are currently being journaled, check the table attributes (Display file description, DSPFD) to make sure Journal images is set to *BOTH (changes to the table are journaled with before-images as well as after-images).

   If Journal images is not set to *BOTH, issue the ENDJRNPF command to end journaling and restart journaling (STRJRNPF) with Journal images set to *BOTH.

2. Prepare a journal on the target server.

You must create or specify existing journals and accompanying receivers that include before-images for all receiving files (tables) at an IBM i target server.

If your receiving table is an IBM i logical file, you must journal only the underlying physical file(s) referenced by the logical file.