Input Source Override - Echo (-IE)

Use the Input Source Override - Echo execution command (-IE) to override specifications in the compiled map file for a specific input card for a single execution of a map.

-IEcard_num[M['filename']]
[Ssize][W|!W][EN][EA][EF][ES][EW][AF][AI][PM][PB][PC][F'n'][U][!U]source
Option
Description
card_num
This is the card number of the input to override.
M'filename'
This is the metadata (XML schema or DTD) file location of the input card to override.
Specify filename as an absolute path along with the file name and enclosed in single quotes, for the metadata when parsing input XML. An example is:
M'k:\my_project_folder\myschema.xml'
Use this command option to override the Metadata location setting for the root type specified on an input card in the Map Designer GUI.
Ssize
This is the size of the data specified by source in bytes.
W
After a map runs for the first time, the WorkArea created for the input card is not deleted. On subsequent executions of the same map, the data for this input card is not validated and the WorkArea information for the card is retrieved from the existing WorkArea.
!W
The WorkArea for input is created when map execution begins.
EN
Use this command option to never call the external parser for document verification.
EA
Use this command option to always call the external parser for document verification.
EF
Use this command option to call the external parser for document verification only if validation fails.
ES
Use this command option to call the external parser for document verification only if validation is successful.
EW
Use this command option to call the external parser for document verification only for the well-formed document.
AF
Use this command option to fail on adapter warnings.
AI
Use this command option to ignore adapter warnings.
PM
Use this command option to apply the OnSuccess and OnFailure settings based on the success or failure of the map execution.
PB
Use this command option to apply the OnSuccess and OnFailure settings based on the success or failure of each burst.
PC
Use this command option to apply the OnSuccess and OnFailure settings based on the success or failure of the input card processing
Fn
FetchUnit defines the number of units of data to retrieve. The default value for FetchUnit is S (unspecified all).
U
Use this command option to apply the burst setting.
!U
Use this command option to not burst (integral mode).
source
This is the data to be used for the input.

For example, to pass the value ABC123XYZ to a map as the data for input card #2, type the following command:

-IE2 ABC123XYZ

If the data to be echoed contains spaces or hyphens, it must be surrounded by single quotes as shown in the following example:

-IE2 `ABC 123 XYZ'

If the echoed data contains single quotes or the null character (hex 00), use the S option to specify the number of bytes of echoed data. Changing the example above to use to the S option, the single quotes are omitted:

-IE1S11 ABC 123 XYZ

The examples above demonstrate using the Input Source Override - Echo execution command (-IE) in a map rule.

If you are using the Input Source Override - Echo execution command (-IE) in the Command Server command line and the data contains spaces or hyphens, in addition to surrounding the data to be echoed with single quotes, you must then add double-quotes outside the single-quotes as shown in the following example:

-IE2 "`ABC 123 XYZ'"

Also, if you are using the Input Source Override - Echo execution command (-IE) in the Command Server command line and the data contains single quotes or the null character (hex 00), in addition to using the S option to specify the number of bytes of echoed data, and omitting the single quotes, if the data contained them, you must also surround the data with double-quotes as shown in the following example:

-IE1S11 "ABC 123 XYZ"

One use for echoed input data is in conjunction with the RUN function to pass data from one map to another. For an example of using an echoed data source as an input argument using the RUN function, see the RUN function in the Functions and Expressions documentation. Another example of using an echoed data source is provided in the Platform API documentation.