What does TSN_DB in the CA Datacom Change Data Capture (CDC) feature represent? The manual says that the program logic for the CDCU should be to read the first TSN record and then read all of the MNT records associated with the TSN record.
Article ID: 44764
Updated On:
Products
Datacom
DATACOM - AD
CIS
COMMON SERVICES FOR Z/OS
90S SERVICES
DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
COMMON PRODUCT SERVICES COMPONENT
Common Services
CA ECOMETER SERVER COMPONENT FOC
Easytrieve Report Generator for Common Services
INFOCAI MAINTENANCE
IPC
UNICENTER JCLCHECK COMMON COMPONENT
Mainframe VM Product Manager
CHORUS SOFTWARE MANAGER
CA ON DEMAND PORTAL
CA Service Desk Manager - Unified Self Service
PAM CLIENT FOR LINUX ON MAINFRAME
MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
GRAPHICAL MANAGEMENT INTERFACE
WEB ADMINISTRATOR FOR TOP SECRET
Xpertware
Issue/Introduction
Question:
What does TSN_DB in the CA Datacom Change Data Capture (CDC) feature represent? We're trying to find the relationship between the MNT table and the TSN table. The manual says that the program logic for the CDCU should be to read the first TSN record and then read all of the MNT records associated with the TSN record. How is the association established?
Answer:
The TSN_DB is the Datacom transaction sequence number of the task while in the CA Datacom Multi-user (MUF).
There is an entry in the CA_CDC_MNT table for every new Transaction Sequence Number (TSN) that CDC sees.
There can be multiple records in the CA_CDC_TSN table representing all the log records created during the life of this particular TSN number.
So, it is a many to one relationship between the TSN table and the single MNT table entry.
Additional Information:
Refer the CA Datacom® Core - 15.0 quide for information on Change Data Capture (CDC) feature
Sample CDC programs can be found here under Sample Programs, CA Datacom/DB
Environment
Release:
Component: DB
Component: DB
Feedback
Yes
No
Powered by
