Schema  > Products  > SRTransport  > Doc  > SRTransportES  > Audit Trail
 

SRTransport Audit Trail

Because it's your data :-) and because SRTransport can run unattended in the background, you need a powerful and clear way to to know what each transport has accomplished.

SRTransport leaves a very solid audit trail.

• A log file that contains detailed information about the transport.
• A reject file that contains any rejected records.
• A status code is returned indicating various levels of success or failure.

The Reject File

Rejected records are written to a reject file. A rejected record is any record that didn't get processed properly. The reject file does not contain source records that were disqualified from the transport.

The Log File

The log file shows all errors and all rejected records and why they were rejected. All messages from the database servers are logged here. Deadlock retries and reconnections to the database server are logged here.

You can write 4gl code in the transport, which writes into the log, events such as interesting conditions or totals and summaries, or any trace information, etc.

The log always ends with a summary like this:

   TRANSPORT COMPLETE

   ROWS TRANSPORTED <>

   ROWS DISQUALIFIED <>

   ROWS REJECTED <>

The message TRANSPORT COMPLETE indicates that all records in the source have been processed. Each record has been either transported, disqualified or rejected. The message TRANSPORT INCOMPLETE indicates that the transport was aborted in the middle, and that some records in the source have not been processed. The message ROWS DISQUALIFIED appears only if some rows have been disqualified, and only in version 4.0 and beyond.

Return Status

On completion, SRTransport returns a status code that can be used by the calling application or script.