Clients who support their applications often will copy data from their databases in one environment to another for testing or development activities, to report against older data, or for many other reasons. It is very easy using the BACKUP command of the CA Datacom/DB DBUTLTY program to take a backup of the whole database. This backup data can then be loaded into the target environment with a single LOAD command. Alternatively, each area in the database can be backed up separately and then loaded into the target as desired.
In certain cases with either method, it is possible for a table to not be loaded, and the job to produce a message "TABLE NOT LOADED". Here is an example report showing this situation:
In this case, Table TBS was not loaded (Box A), although the input file shows there were 68,915 records. Looking at the description of these tables further, Table TBS was defined with Datacom ID 2 in the source system (Input Box B), but it was defined with Datacom ID 46 in the target system (Output Box C). As noted in the CA Datacom/DB DBUTLTY documentation for the LOAD command, "If you are loading data from a backup, the LOAD function only restores the data if the table IDs are identical when LOADID=YES (the default). LOADID=NO can be used to match on table names, but LOADID=NO cannot be specified if either URI=NO is specified or if any table in the area was not defined to CA Datacom® Datadictionary™ with RECOVERY=Y. REMAP= can be used to force matching on different table names. This feature is available only for areas loaded as URI."