Journal for metabase tables - Connect_CDC - aws_mainframe_modernization_service - connect_cdc_mimix_share - Latest

AWS Mainframe Modernization - Data Replication for IBM i

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
AWS Mainframe Modernization > AWS Mainframe Modernization Service
Version
Latest
Language
English
Product name
AWS Mainframe Modernization
Title
AWS Mainframe Modernization - Data Replication for IBM i
Copyright
2024
First publish date
2003
Last updated
2024-02-01
Published on
2024-02-01T23:02:31.099696

When Connect CDC Director installs the metabase tables on the IBM i host, it creates a system-managed journal (QSQJRN is a library’s default SQL journal) and a receiver (log) with default parameters in the product library for transaction recovery. Connect CDC Director automatically issues the following commands to create the metabase:

CREATE collection <library>
CRTJRNRCV JRNRCV(<library>/QJQJRN0002) THRESHOLD (500000)
CHGJRN JRN <library>/QSQJRN) JRNRCV(<library>/QSQJRN0002) MNGRCV(*SYSTEM) DLTRCV/*YES)

To maintain the data integrity of the metabase and the queue tables contained within it, the metabase must be journaled. That means that, like any DBMS table that is journaled, the system writes whatever information it needs so that transactions can be rolled back or rolled forward, whichever is appropriate to maintain data consistency.

That usually means that before and after images of updates to rows are written to the journal, along with records that indicate transaction boundaries. Other records are written as well, for example, file and journal operations. Use the DSPJRN command to review what is written.

To change the way the metabase journals are being managed, use the CHGJRN command.

For information on journaling and journal record formats, consult IBM documentation.