Batch runs: queue, stop, pause and continue, and rerun

A batch import from CoreIQ, from a VSAM dataset or an IMS segment, no longer has to run to its end. A run started while another is going is queued instead of refused, and the job page says where it is in line. Runs that load the same tables never run together.

On the job page, Pause stops a run after the rows in flight are written, and Continue picks it up from the exact record where it stopped, with the same mappings. It stays one run under one number, and the page lists its parts. Stop ends a run for good, and a queued run can be removed from the queue.

Rerun starts a run again from the first record with the mappings as they are now, for example after Fix it. Rows already in the tables are skipped, so it adds the rows the first run refused, and any new records, without updating any rows already there. DataIQ shows what the rerun will do before it starts: each source and table, and which mappings changed since the run. A run is rerun once, so a double click or a retried call cannot start it twice.

When you save a fix from a run, its page now marks those causes as fixed, with what changed and the new mapping version.

AI clients can do all of this over MCP: list runs by status, stop, pause, continue, check and start a rerun.