Suggest an Idea

[AnthonyWest]

We have tables in DB2 that get loaded through processes (using the LOAD utilities in DB2). This prevents Replicate from picking up the changes (even though it does detect that the table has been technically updated, it does not pull those changes). The message that gets generated is: subtype 83 operations (load replace or load resume) can be configured using the internal parameter "db2LoadOption". We would expect in this situation that the R4Z function on the DB2 side would push all the data in the table when this status is detected (effectively like a full reload). We are aware we can schedule a task in Replicate to periodically do a task reload, however that requires either separate tasks (from non-full load tasks) or reloading all the tables in the task, and also has the downside of not being linked to the table data load. Also we could use the API services, however, that requires development on our Db2 system which is not feasible. We would prefer the intended behavior for these tables to push the data for these tables (when encountering the status 83), in full to the downstream task. This will prevent manual interventions or scheduling complex tasks to reload, and also development on the source DB2 side which is technically not feasible.

In Short we are asking to have Replicate enhanced for DB2 (z/OS) to push the table data in full over to Replicate (from the R4Z most likely) when the status 83 (db2LoadOption) is encountered.

[jonmm]

This would go a long way to simplifying the integration and interactions needed with DB2 sources and the replicate tool. Would really like to see this functionality built in to address the "table load" gap with DB2 tables and CDC tasks within Replicate.

[Shelley_Brennan]

Thank you for the suggestion.  If Replicate were to suspend a table when it detected a subtype 83 operation, would that suffice for your use case?  In this scenario, you could be notified that a table was suspended and reload just the individual table in the task. 

[jonmm]

Hello Qlik,

That would be a step in the right direction, however that is really only OK for a "once in a blue moon" activity, unfortunately we have a lot of tables that  do this LOAD activity daily (but rarely more frequently, but possible). So this needs to be more automated. Either the task needs to have an option to auto reload LOADED tables when the status is detected, or if the table goes into Suspended status, the task needs an option to allow SUSPENDED tables to be auto-reloaded. Either way would accomplish addressing the issue technically, but the need is to automate the reload not to notify there is an issue.

Thanks, 

Jon

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.