Troubleshooting tools

When a map begins to run, the first thing that occurs is the validation of the input data-performed by comparing the data to the type tree definition. After data validation completes, the map rules are evaluated for the output cards and output objects are built.

When a map executes, invalid or unknown input data may be encountered and you may want to analyze what happened during the validation process. You may also want to analyze the output data if the map did not produce the expected results.

Many debugging aids are available to assist you through the troubleshooting process including:

  • A Command Server display of ongoing execution information
  • Command Server return codes and messages
  • Map audit log files, including data audit, execution audit, map settings, and card settings information
  • Map trace files
  • If an adapter is used, adapter-specific return codes and messages, audit log files, and trace files