Data Transformation Engine Command Server Reference Guide

Table Of Contents

Chapter 1 - Using a Command Server Troubleshooting Tools

Command Server Reference Guide

♦ Map trace files

♦ If an adapter is used, adapter-specific return codes and messages, audit log

files, and trace files

Command Server Display

Unless suppressed using execution commands, the Command Server displays

several pieces of information when you run a map including the Command Server

name, number of input objects found, number of output objects built, map

execution time and a message indicating the map status. This information displays

using a Command Server window on all Windows-based platforms or using a

console display on the UNIX-based platforms.

Ongoing feedback is shown during map execution and upon map completion. The

messages that result (each message has a corresponding return code) indicate

whether the map has completed and display the mapping results.

Command Server Return Codes and Messages

After a map completes, a message indicates the execution results. These

messages are also recorded in the appropriate audit logs.

Some return codes are only warnings indicating that the map did complete, but

some problems occurred. You can change the default behavior for the warning

codes by specifying Fail on Warnings or Ignore Warnings through the map

settings or by using the

–F or –Z execution command. See the Map Designer

Reference Guide, Integration Flow Designer Reference Guide, and Execution

Commands Reference Guide for more information.

Map Audit Logs and Trace Files

Audit logs and trace files provide information that can be used effectively for

debugging and troubleshooting purposes. There are many situations that occur

during map execution in which you would want the activities associated with the

processing of your data to be recorded in an audit log file or trace file. The

auditing and tracing of the map execution process can be accomplished at various

levels by specifying that the appropriate audit logs and trace files be enabled for

maps, input cards, output cards, or particular adapters. These audit log and trace

files may also be defined further to include summary or detail information about

execution statistics, data information, or adapter activity.

For information about map audit logs and trace files, see the Map Designer

Reference Guide.