In the case of a catastrophic event, it is unlikely that GT.M can properly complete writing all journal records to the file. MUPIP JOURNAL processing reports the unfinished records or incomplete fenced transactions as "broken transactions". The broken transactions are extracted into a file (the broken transaction file). Any complete transaction that occurred in time after a broken transaction is also not played into the database but instead extracted out as a lost transaction into a different file (the lost transaction file). 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.

The -ERROR_LIMIT= qualifier to MUPIP JOURNAL enables processing to continue. It attempts to skip over errors until the number of errors exceeds the specified limit. The -INTERACTIVE qualifier to MUPIP JOURNAL lets an operator control whether processing continues once the -ERROR_LIMIT= limit has been exhausted.