Note: Stop the Apply Engine, if it is still running.
- Start SQDUtil, using the same source URL as the Engine using the "move" parameter to reconnect to the MF publisher, which will resume publishing from the start of the last "uncommitted" Unit-of-Work. The file system written to by SQDUTIL must be able to accommodate the published "cdcraw" data which will be maintained in its original form, EBCDIC in the case of zOS source change data.
- When Kafka becomes operational Start a special version of the Engine where the source URL points to the file created by SQDUTIL. If multiple files had been created, the engine would need to be restarted after each file was processed, using the same input file name or a reparsed special Engine (depending on how the files are managed).
- Once the single or last file has been processed, the special Engine will stop normally.
- Start the normal Apply Engine to resume normal operation.