I wanted to share a technical white paper I published that documents a novel solution to a CDC serialization challenge in Qlik Replicate during mainframe-to-cloud migration.
THE PROBLEM: STCK-based binary surrogate keys in mainframe MIS systems cause CDC serialization failures in Qlik Replicate when migrating to AWS Aurora PostgreSQL. The binary format breaks change event ordering and traceability during active migration.
THE SOLUTION — Binary Key Bridging Pattern: A dual-key architecture that preserves the original STCK binary key while generating a UUID surrogate key for cloud-native compatibility. This enables reliable CDC without data loss or event ordering failures during zero-downtime migration.
This pattern is part of a broader 5-layer Live Data Coexistence Framework (LDCF) that enables enterprise MIS modernization without system downtime.
Has anyone else encountered STCK binary key issues with Qlik Replicate on mainframe sources? Would welcome feedback from the Qlik engineering or product team.
