Data Transformation Engine Services Guide

Chapter 8 – Using Messaging Adapters
35
General Rules for Messaging Adapter Commands
The general rules that apply when specifying adapter commands are:
♦ Each command must begin with a hyphen.
♦ Command characters can be upper case, lower case, or mixed case.
♦ Command strings are parsed in left to right order.
♦ The order of commands is not important.
♦ Command files can contain multiple lines.
♦ Space characters:
 Spaces preceding the first command are ignored.
 At least one space between commands is required (that is, -KEEP -TRACE).
 Line breaks can be used in place of the required space that must be between commands. The
line breaks are converted to spaces prior to processing.
 A space is required preceding a variable value (that is, -TRACE+S
full_path ).
For Windows Sources and Targets on the Command Line
When using execution commands on Windows platforms, the adapter commands specified must begin
with a single quote and end with a single quote. Each of the adapter commands is separated by a space.
For example, -IMTUX1 ‘
command command ’.
For UNIX Sources and Targets on the Command Line
When using execution commands on UNIX platforms, the adapter commands specified must begin with
a double quote, followed by a single quote and end with a single quote, followed by a double quote.
Each of the adapter commands is separated by a space.
For example, -IAMQS1 “‘
command1 command2 ’”.
Messaging Adapter Transactions
Map definitions provide settings that control the scope of messaging-adapter transactions in terms of
how transactions are sent, received, and committed.
Messages as a Data Source
On the sending side of data transformations, there are two data processing modes: burst mode and
integral mode.
For each input card in a map, integral and burst modes are defined in the Map Designer Input Card
dialog box with the InputData > CardMode setting: Burst or Integral.
or