Restart add table process

As soon as even a tiny error occurs in the Add-Table process (migration from V605 to V701), the entire environment must be restored.
Not being able to set up the Add-Table process means in detail:
- Return to the V701 initial delivery state
- Drop of all created tablespaces
- Create Table
- Load Table
- Add Table

This is not done in a few minutes, but requires almost 2 hours. And don't forget, during this time the RTC application is not available.
From our point of view it is absolutely necessary to make the Add-Table process restartable.
Especially when you consider that nowadays we talk about agile processes and machine learning.
Basically, the RTC processes Create, Unload and Load should also be restartable. For us, however, it is absolutely important that the Add-Table process is restartable first.

A completely different alternative would be to expose the entire DDL process.
Every DBA would then be able to restart the process from the point where it was interrupted, after the error situation has been corrected.
In addition, you would not have to worry about the status of the database, and in the event that a reorg is required in the meantime (Case TS002683859),
and how to create the imagecopy dataset (Case TS004718055).