IBM BJ0NJML Integration Guide - Page 112

Regeneration of Interface Tables Regeneration of Interface Tables When columns are added or deleted from the system database tables, you must regenerate all local and remote interface tables that are associated with those object structures. You regenerate interface tables by using the Create Interface Tables option on the Select Action menu in the External Systems application. If you select the Rename Existing check box, the application backs up existing data in the corresponding interface table to the INTERFACETABLENAME_BAK table. If necessary, restore the data to the new table. If you do not back up the table, the table is dropped and the data is lost when you regenerate the table. You cannot regenerate an interface table when the MXIN_INTER_TRANS queue table contains a record that points to that interface table. When a row exists in that queue table, the corresponding inbound transaction is ready to process, or the inbound transaction is in error. The interface table creation process does not check for records in the MXOUT_INTER_TRANS queue table. Deletion of Interface Tables and Records When one or more related inbound transaction records are successfully processed in an interface table, the corresponding record is deleted from the MXIN_INTER_TRANS queue table. This means that the transaction was delivered successfully to the inbound Java Message Service (JMS) queue. Records are deleted from the MXIN_INTER_TRANS queue table, never from the individual interface tables. The system administrator determines when and how to delete records from the interface tables. For outbound transactions, the external system must manage the deletion and archiving of data in the queue table and interface tables. An administrator must manage the archiving of data in the interface tables. You cannot delete interface tables by using the user interface or by deleting the corresponding object structure. If necessary, a system administrator can drop the table. 98 Integration Guide