Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We are setting up our task with z/OS DB2 as source endpoint and Kafka as target endpoint. We will be running this in production for a few months and then we have a requirement to change the target endpoint of the task from Kafka to Kinesis. Basically, at that point in time, the task will be doing incremental loads and we want to continue the incremental loads to Kinesis but don't want to duplicate what has already been loaded in Kafka.
So, I am wondering whether we can stop the task and change the target in the same task?
Also, is it possible to schedule the task to run during a given start and end time and the next schedule will pick up from where the previous left off?
Thanks
Hi,
Yes, you should be able to change the target endpoint.
There are three ways to schedule tasks.
1) In the replicate GUI under server use the scheduling tool. See the replicate user guide
2) You can use the RestAPI and make calls to the commands stop/status/start (supported and recommended method) Please see QEM developer documentation.
3) You can use the replicate command line to do the same as above (not supported - feature could change or be depreciated anytime).
Thanks,
Michael
Hi @adbdkb
You can change target endpoints, but as the state manager is allocated to the previous target, you'll need to start the task from a timestamp so the task can reallocate a new one. The task logs will have a source timestamp that it stopped at so you can pick up from where you left off using that timestamp.
Please test this in a dev environment as you may not be able to use the resume option when switching targets.
Hi,
Yes, you should be able to change the target endpoint.
There are three ways to schedule tasks.
1) In the replicate GUI under server use the scheduling tool. See the replicate user guide
2) You can use the RestAPI and make calls to the commands stop/status/start (supported and recommended method) Please see QEM developer documentation.
3) You can use the replicate command line to do the same as above (not supported - feature could change or be depreciated anytime).
Thanks,
Michael
Hi @adbdkb
You can change target endpoints, but as the state manager is allocated to the previous target, you'll need to start the task from a timestamp so the task can reallocate a new one. The task logs will have a source timestamp that it stopped at so you can pick up from where you left off using that timestamp.
Please test this in a dev environment as you may not be able to use the resume option when switching targets.
Thank you. And yes, currently trying to do this in development environment.
Where do I specify to start the task from a timestamps?
Hi,
Under run / advanced option you will it.
Thanks,
Michael
On the drop down menu next to the run button, you will find advanced Run Options.
Thanks.
What is Source Change Position here
@adbdkb
1. there is the user guide :
2. there are other forum and article :
SCN is for Oracle database sources and LSN is for SQL Server source. They're a system timestamp relevant to the corresponding database. It refers back to a specific source record to start the task.
IBM DB2 for z/OS also has its own Source Change Position you can use. I don't know the exact format of it so you will need to start another forum post or a case to get the answer for this.