Archecker table level restore utility does not compatible of handling Informix engine complex table schema clauses

Individual Table restoration 'archecker' utility only support simple schema definition contents as the schema file. However, Informix engine support complex clauses when setting up a table.

E.g. When fragmenting a table based on interval based fragmentation to store each year data in a separate fragment, 'Archecker' table level restoration utility is not intelligent enough to apply the following fragment clause straight away during the table restoration attempt:

Fragment by range( ) Interval(NUMTOYMINTERVAL(1,'YEAR')) store in()

Luckily, there is a painful work around solution IBM suggests us to follow-up the steps as follows:

1) Create an additional table level restore (tlr) table with the required schema using the required fragmentation clause.
2) Even if we need to restore on the same dbspace through 'Archecker', setup the 'Archecker' script with the source/target details *without* the fragment/partition details.
3) Execute the normal 'Archecker' command.
4) drop the original table name and rename the tlr table (in step 1) back to the original table name .

This will obviously be a big challenge to any non-DBA person to restore such a table easily and fast manner during an emergency situation. Even for an experience person , it takes considerable time to setup the initial schema file manually as required.

So, the suggestion will be either to extend the 'Archecker' functionality to support such complex table clauses those are support by Informix engine or provide an individual table level restoration functionality through Ontape/OnBar mechanisms to avoid the above complexity to end user.