Any complete transaction that occurs after a broken transaction is a lost transaction. GT.M does not play it into the database but extracts it as a lost transaction into a file called the lost transaction file.

All broken and lost transactions are made available as the result of a database recovery.

The operational procedures and the application tools should provide a means of recovering and reprocessing the information in the broken and lost transaction files after a recovery or rollback that places content in these files.

If there are no fences, repair any application-level integrity problems. In either case, MUPIP INTEG -FAST provides an excellent quick test of whether the database can support new updates with relative safety.