Name

trade − Client shell level interface to the DEC/EDI Server. 

The command can either trigger a sub-environment in which multiple sub-subcommands are issued or can be used to issue a single command. 

The post option allows the caller to submit one or more files into the DEC/EDI server. Depending on the type of each file these will go either through the mapper on the server, to the converter, or directly to the communications service. 

The fetch option allows the caller to fetch one or more files from the DEC/EDI server. These files may have come directly from the communications service, or via the translator, or from another application. When coming from the translator or another application the files can optionally go via the mapper. 

The track option allows the caller to track objects within the DEC/EDI server. It can provide lists of objects which match certain selection criteria or it can return full information on an object such as Interchange Control Number. 

The exit option allows the caller to exit the trade sub-environment and return to the normal shell. 

Each suboption of the trade command is described individually in more detail in the sections which follow. 

When entering single commands from the command line, the shell that the user is in, for example the Bourne shell (sh), will interpret the command before being passed to the trade command. This can lead to characters being stripped off unless released from their special meaning. Examples of this are brackets (’(’, ’)’), and quotes (’"’). To release these from their special meaning, use the backslash (’\’) directly prior to the character to be released. For example, to specify -business_references=("A","B") from the Bourne shell you need to actally type -business_references=\(\"A\",\"B\"\)
 

 
 

Name

trade exit − The trade exit command causes the application client interface to exit. 
 
 
 

FORMAT

trade exit
 
 

 
 

Name

trade fetch − The trade fetch command enables the user to fetch one or more files from the DEC/EDI server.  These files may have come through the Translation Service (possibly via the Mapping Service) or directly from the Communications Service.  The type of file being fetched must be specified and can be one of the following:
 
 
 
 

•Application_file -- files are fetched from the Mapper on the Server. These files are also known as structured files. 
 
 

•Transmission_file -- files are fetched from the Communications Service on the Server, bypassing any  translation or mapping.  These files are also known as unstructured files. 
 
 

•Document -- files are fetched from the Translation Service on the Server, bypassing any mapping.  These files are also known as ’ihf’ files. 
 
 
 
 
 

FORMAT

trade fetch application_name [options] [file [file_options]]
 
 
 
 

Parameters

 
 

application_nameThe application_name is the name of the client application submitting the request to the Server.  This parameter is used by DEC/EDI as a means of authenticating the request. The client application must be registered as as  authorized application on the Server.  Applications are registered by using the CommandCenter Management Services Editor.  For more information, refer to DEC/EDI Configuring. 
 

This parameter is mandatory. 
 

fileThe file specification of one or more files into which files from the Server are to be placed.  If more than one file name is entered, the file options immmediately following each file refer only to that file.  See the "File Options" topic for further information on which File options can be (or must be) supplied with this parameter. 
 

If the Server is remote from the client, the client application must make sure that any file specified resides in a directory that allows write access to the DEC/EDI client information server process. This process uses the ’decedi’ account by default. 
 

This parameter is mandatory. 
 
 
 
 

Options

 
 

-link_idThe connection identifier of the connection from which files are directly received. The connection must have been defined by using the CommandCenter Communications Editor.  For more information, refer to DEC/EDI Configuring. 
 

This option is mandatory when the file option is -type=transmission_file. 
 
 
 

Format
 

    -link_id=<connection_id>
 
 
 

-test_indicatorIndicates whether the files in this request are to be treated as test files or live files. 
 
 
 

Format
 
 

    -test_indicator[=option]
 

Where option is one of:

live	Live files.  By default, both live and partner_test documents can be fetched.
mapper_test	Files tested from the Mapping Service.
partner_test	Files tested through all services from the trading partner.  By default, both live and partner_test documents can be fetched.

 
 
 
 
 
 
 
 
 
 
 

File Options

 
 

For each file to be fetched, a number of options that can be specified.  Whether a particular option is mandatory or not depends upon the file type (-type):
 

-type=	Mandatory Options
------	-----------------
application_file	-table_name
document	-type
transmission_file	-link_id, -type

 
 

Most optional file options are associated with the Mapper only and are not applicable when -type=transmission_file or -type=document:
 

-type=	Applicable Non-Mandatory Options
------	--------------------------------
application_file	All except for -table_name (which is mandatory).  These file options override any setup information in the Mapper itself and, if not specified, the defaults come from the Mapper.
document	-timeout
transmission_file	-timeout

 
 

The File options are associated with each file to be fetched and must be entered after the file specification on the command line.  For example:
 
#trade fetch my-app file.dat -type=application_file \
                             -table_name=mapping_tbl \
                             -output_file=mapper_out.dat
 

-business_referencesThis associates one or more user supplied business references with the document audit trail. If more than is supplied then each must be separated by a comma. Leading references may by omitted if a particular business reference slot is intended for the users reference. Up to 5 business references may be specified. 
 

This is applicable only when -type=application_file or -type=document. 
 
 
 

Format

    -business_references=<business_reference>

    -business_references=(<business_reference> [ , <business_reference>... ])
 
 
 

-commentA comment to add to the mapping audit trail. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -comment=<mapping_comment>
 
 
 
 
 

-debugThe file specification of the file on the client to which the Mapper debug output is to be written. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -debug=<file_specification>
    -nodebug
 
 
 

-error_logThe file specification of the file on the client to which the Mapper error log output is to be written. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -error_log=<file_specification>
    -noerror_log
 
 
 

-io_debugThe file specification of the file on the client to which the Mapper I/O debug output is to be written. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -io_debug=<file_specification>
    -noio_debug
 
 
 

-local_testThe file specification of the input file on the Server to use when the Mapper is in local test mode (-test_indicator=mapper_test). 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -local_test=<file_specification>
    -nolocal_test
 
 
 
 

-match_flagSpecifies which documents the Mapper is to match. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -match_flag[=option]
 

    Where option is one of: . 
 

 

    match_first -- match the first available document. 

    match_all -- match all documents. 
 
 
 
 

-named_applicationIndicates that the application name specified as a parameter is to be passed to the Mapper.  By default, the Mapper obtains application names from within the map. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -named_application
 
 
 

-object_nameA name distinguishing this object from other objects handled by the application. 
 

In the case of application files (-type=application_file), it can be used to initiate processing by the Mapper that is conditional on the object being of a particular type, for example, to select part of a map. 
 

In the case of in-house-files (-type=document), it is used to describe what the object is, for example, a purchase order or an invoice. 
 

This is NOT applicable for -type=transmission_file. 
 
 
 

Format
 
 

    -object_name=<object_name>
 
 
 

-output_fileThe file specification of the file on the client to which screen output from the Mapper is to be written. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -output_file=<file_specification>
 
 
 
 
 

-partner_nameThe name of the trading partner from whom this file was received. 
 

This is NOT applicable when -type=transmission_file. 
 
 
 

Format
 
 

    -partner_name=<partner_name>
 
 
 

-restart_fromThe number of the document from which mapping is to restart. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -restart_from=<mapping_restart_position>
 

    Where <mapping_restart_position> is an integer. 
 
 
 

-table_nameThe name of the mapping table to use if the services of the Mapper are required.  Mapping tables reside on the Server in the mapping table directory (/var/adm/decedi/maps/), but the directory specification need not be included with the table name. 
 

This is applicable only when -type=application_file and is a mandatory option. 
 
 
 

Format
 
 

    -table_name=<mapping_table_name>
 
 

-timeoutThe maximum number of seconds that the Application Client should wait for the file to become available.  If not specified, a timeout of zero seconds is assumed. 
 
 
 

Format
 
 

    -timeout=<number_of_seconds>
 
 
 

-typeThis specifies the type of file being fetched and whether it is to be fetched using the Mapper or not. 
 
 
 

Format
 
 

    -type[=option]
 

    Where option is one of:
 

-type=	Description
------	-----------
application_file	Fetch structured application files from the Mapper.  (This is the default for -type.)
transmission_file	Fetch unstructured transmission files directly from the Communications Service  on the server.
document	Fetch in-house files (DEC/EDI Version 1 internal format documents) from the Translation Service on the server.

 
 
 
 
 
 
 

Examples

 
 

 # trade fetch my-application \
              test_file.dat \
              -partner_name=their-application \
              -tracking_reference="invoice #1234"\
              -table_name=map_test_tbl
 

 
In this example, an application called my-application submits a request to fetch structured files that have been received from a trading partner called their-application, convert them into application file format using the mapping table map_test_tbl, and write them to the file test_file.dat in the user’s current working directory. Note that because the default file type is "application_file", the -type option is not necessary. 
 
 

      CLIENTEDI> fetch my-app test_file.dat \
                   -partner_name=acme-orders \
                   -table_name=map_test_tbl
 

 
In this example, an application called my-app submits a request to fetch structured application files that have been received from a trading partner called acme-orders, convert them into  application file format using the mapping table map_test_tbl, and write them to the file test_file.dat in the user’s current working directory. 
 

Note that because the default file type is "application_file", the -type option is not necessary. 
 
 

     CLIENTEDI> fetch my-app -link_id=OFTP_1  new_car_design.dat \
                       -type=transmission_file
 

 
In this example, an application called my-app submits a request to fetch transmission files coming into the server via the connection identifier, OFTP_1.  The transmission file is written into the file new_car_design.dat in the user’s current directory. 
 
 

     fetch my-app /usr/users/me/test_ihf.dat \
    -type=document -partner=acme-invoic \
    -object_name=edifact-invoic
 

 
In this example, an application called my-app submits a request to fetch document files that have been received from a  trading partner called acme-invoic and have an internal document identifier of edifact-invoic. 
 
 
 

 
 

Name

trade post − The trade post command enables the user to submit one or more files into the DEC/EDI Server.  These files may go through the Translation Service (possibly via the Mapping Service) or directly to the Communications Service. The type of file posted must be specified, and can be one of the following:
 
 
 
 
 

•Application_file -- files are posted to the Mapper on the Server. These files are also known as structured files. 
 
 

•Transmission_file -- files are posted to the Communications Service on the Server, bypassing any translation or mapping. These files are also known as unstructured files. 
 
 

•Document -- files are posted to the Translation Service on the Server bypassing any mapping. These files are also known as ’ihf’ files. 
 
 
 

Several command and file options are associated with the POST command: some are mandatory. 
 
 

 
 

FORMAT

trade post application_name [options] [file [file_options]]...
 
 
 
 
 

Parameters

 
 

application_nameThe application_name is the name of the client application submitting the request to the Server.  This parameter is used by DEC/EDI as a means of authenticating the request. The client application must be registered as as  authorized application on the Server.  Applications are registered by using the CommandCenter Management Services Editor. For more information, refer to DEC/EDI Configuring. 

This parameter is mandatory. 
 

fileThe file specification of one or more files to be posted to the Server.  If more than one file name is entered, the file_options immediately following each file refer only to that file. 

See the "File Options" topic for further information on which File options can be (or must be) supplied with this parameter. 
 

If the Server is remote from the client, the client application must make sure that any files specified allow read access to the DEC/EDI client information server process.  This process uses the ’decedi’ account by default. 
 

This parameter is mandatory. 
 
 
 
 
 
 

Options

 
 

-connection_dataThis provides information to the communications connection which overrides the defaults for that connection. This field is specific to the type of gateway referenced by the link_id. Please refer to the CommandCenter Trading Partner Editor’s on-line help for types support this feature, and what format they expect the data in. 

This is applicable only when -type=transmission_file. 
 
 
 

Format
 
 

    -connection_data=<connection_specific_string>
 
 

-link_idThe connection identifier of the connection to which files are posted directly.  The connection must have been defined using the EDIT CONFIGURATION command.  For more details, refer to DEC/EDI Command Reference. 
 

This option is mandatory when the file option is
 -type=transmission_file. 
 
 
 

Format
 
 

    -link_id=<connection_id>
 
 
 
 
 
 
 

-prioritySpecifies how the server is to process the files.  The default is -priority=normal.  The Translation Service builds high priority files into a single document interchange immediately. Normal priority files are built into document interchanges at scheduled intervals.  Similarly, the communications gateway triggers the sending of a high priority file immediately and normal priority files are sent at scheduled intervals. 
 
 
 

Format
 
 

    -priority[=option]
 

    Where option is one of:

    normal (D)

    high
 
 
 
 

-test_indicatorIndicates whether the files in this request are to be treated as test submissions or live submissions. 
 
 
 

Format
 
 

    -test_indicator[=option]
 

    Where option is one of:
 

live(D)	Live files.  This is the default.
mapper_test	Files tested through to the Mapping Service.
translation_test	Files tested through to the Translation Service.
partner_test	Files tested through all services to the trading partner.

 
 
 
 
 
 
 
 
 
 
 

File Options

 
 

For each file to be posted, there are a number of options that can be specified.  Whether a particular option is mandatory or not depends upon the file type (-type):
 

-type=	Mandatory Options
------	-----------------
application_file	-table_name
document	-partner_name, -object_name, -tracking_reference, -type
transmission_file	-link_id, -type

 
 
 
 

Most optional file options are associated with the Mapper only and are not applicable when -type=transmission_file or -type=document:
 

-type=	Applicable Non-Mandatory Options
------	--------------------------------
application_file	All except for -table_name (which is mandatory).  These file options override any setup information in the Mapper itself and, if not specified, the defaults come from the Mapper.
document	None
transmission_file	-tracking_reference

 
 

The File options are associated with each file to be posted and must be entered after the file specification on the command line.  For example:
 
 
 
 

 #trade post my-app file.dat -type=application_file\
                            -table_name=mapping_tbl \
                            -output_file=mapper_out.dat
 

 
 
 

-business_referencesThis associates one or more user supplied business references with the document audit trail. If more than is supplied then each must be separated by a comma. Leading references may by omitted if a particular business reference slot is intended for the users reference. Up to 5 business references may be specified. 
 

This is applicable only when -type=application_file or -type=document. 
 
 
 

Format

    -business_references=<business_reference>

    -business_references=(<business_reference> [ , <business_reference>... ])
 
 

-commentA comment to add to the mapping audit trail. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -comment=<mapping_comment>
 
 
 
 
 
 
 

-debugThe file specification of the file on the client to which the Mapper debug output is to be written. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -debug=<file_specification>
    -nodebug
 
 
 

-error_logThe file specification of the file on the client to which the Mapper error log output is to be written. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -error_log=<file_specification>
    -noerror_log
 
 
 

-io_debugThe file specification of the file on the client to which the Mapper I/O debug output is to be written. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -io_debug=<file_specification>
    -noio_debug
 
 
 

-local_testThe file specification of the input file on the Server to use when the Mapper is in local test mode (-test_indicator=mapper_test). 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -local_test=<file_specification>
    -nolocal_test
 
 
 
 
 
 
 
 
 
 

-named_applicationIndicates that the application name specified as a parameter is to be passed to the Mapper.  By default, the Mapper obtains application names from within the map. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -named_application
 
 
 

-object_nameA name distinguishing this object from other objects handled by the application. 
 

In the case of application files (-type=application_file), it can be used to initiate processing by the Mapper that is conditional on the object being of a particular type, for example, to select part of a map. 
 

In the case of in-house-files (-type=document), it is used to describe what the object is, for example, a purchase order or an invoice. 
 

This is NOT applicable for -type=transmission_file and is mandatory when -type=document. 
 
 
 

Format
 

    -object_name=<object_name>
 
 
 

-output_fileThe file specification of the file on the client to which screen output from the Mapper is to be written. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -output_file=<file_specification>
 
 
 

-partner_nameThe name of the trading partner for whom this file is destined. 
 

This is a mandatory option for -type=document. 
 

This is NOT applicable when -type=transmission_file. 
 
 
 

Format
 
 

    -partner_name=<partner_name>
 
 
 

-restart_fromThe number of the document from which mapping is to restart. 
 

This is applicable only when -type=application_file. 
 
 
 

Format
 
 

    -restart_from=<mapping_restart_position>
 

    Where <mapping_restart_position> is an integer. 
 
 
 

-table_nameThe name of the mapping table to use if the services of the Mapper are required.  Mapping tables reside on the Server in the mapping table directory (/var/adm/decedi/maps), but the directory specification need not be included with the table name. 
 

This is applicable only when -type=application_file and is a mandatory option. 
 
 
 

Format
 
 

    -table_name=<mapping_table_name>
 
 

-tracking_referenceThis is a tracking reference that the user can apply to the file being posted.  The reference can be used with the track command to track objects in the system. 
 

This is a mandatory option when -type=document. 
 
 
 

Format
 
 

    -tracking_reference=<reference>
 
 
 

-typeThis specifies the type of file being posted. 
 
 
 

Format
 
 

    -type[=option]
 

    Where option is one of:
 

application_file	Structured application files that will go to the Mapper.  (This is the default for -type).
transmission_file	Unstructured transmission files that will be sent directly to the  Communications Service on the server.
document	In-house files (DEC/EDI Version 1 internal format documents) that will be processed by the Translation Service on the server.

 
 
 
 
 
 
 

Examples

 

      trade post my-app -test_indicator=partner_test \
   test_file.dat \
   -partner_name=acme-orders \
   -tracking_reference="ORDER_1234" \
   -table_name=map_test_tbl
 

 

In this example, an application called my-app submits a request to post the application file, test_file.dat in the user’s current working directory to a trading partner called acme-orders as a test.  The file is to be converted into internal (in-house) format using the  mapping table map_test_tbl.  The file is given the reference ORDER_1234 so that it can be tracked using the TRACK command. 
 
 

Note: Because the default file type is "application_file", the -type option is not necessary. 
 
 

     trade post my-app -link-id=OFTP_1 \
    -connection_data="\new-car-design\80\\" \
    new_car_cad_design.dat \
    -type=transmission_file
 

 

In this example, an application called my-app submits a request to post the transmission file, new_car_cad_design.dat in the user’s current working directory using the connection OFTP_1 (defined in the server).  The OFTP virtual file name is to be new-car-design and the transmission file is to be transmitted using a record size of 80 characters. 
 

Note that this trade post request bypasses any mapping or conversion because the file type is "transmission_file". 
 

     trade post my-app -priority=high /usr/users/me/invoic_document.dat \
   -partner_name=acme-orders \
   -object_name=edifact-order \
   -tracking_reference=acme_ref \
   -type=ihf

 

 

In this POST command, an application called my-app submits a request to post the in-house file formatted document, /usr/users/me/invoic_ihf.dat to a trading partner called acme-orders at high priority.  The name of the internal document is specified as edifact-order and a tracking reference is given as acme_ref. 
 
 

 
 

Name

trade track − The trade track command enables the user to track objects within the DEC/EDI Server.  It can provide lists of objects that match certain selection criteria and it can return different types of information for the objects that meet this selection criteria (for example routing information or status). 
 

 
The output from the command shows each object’s primary tracking reference at the start of a new line, with its attributes and values on subsequent lines (indented).

 
The Track command can track only one kind of object at a time. The type of object being tracked must be specified and may be one of the following:
 
 
 
 

•Application_file -- files that have been posted or fetched via the Mapper on the Server. These files are also known as structured files. 
 
 

•Transmission_file -- files that have been sent or received via the Communications Service on the Server, or are waiting to be sent via the Communications Service. These files are also known as unstructured files. 
 
 

•Document -- files that have gone through or are waiting to go through the Translation Service on the Server. This also includes documents that are involved in Application-to-application agreements. These files are also known as ’ihf’ files. 
 
 
 
 
 

FORMAT

trade track application_name [options] selection_list...
 
 
 
 
 

Parameters

 
 

application_nameThe application_name is the name of the client application submitting the request to the Server.  This parameter is used by DEC/EDI as a means of authenticating the request.  The client application must be registered as as authorized application on the Server.  Applications are registered by using the CommandCenter Management Services Editor For more information, refer to DEC/EDI Configuring. 
 

This parameter is mandatory. 
 

selection_listThe selection_list is a space separated list indicating the values to obtain for each object found.  Note that not all selection values are applicable to all file types. (e.g. if -type=document is specified, then the selection_list value, "communications_data", returns no information.) 
 

If a selection value is applicable to only one type, then it is not necessary to explicitly specify that type (-type=) on the command line.  (For example, if the selector "acknowledgement" is selected, then -type=document can be omitted, since "acknowledgement" is applicable only for that file type.) 
 

The options available for the selection_list are shown in Table 1. 
 
 
 
 
 

Table 1: Selection Identifiers

Value	Description
-----	-----------
acknowledgement	Provides information about functional acknowledgments. Data displayed for file  types is: application_file -- n/a transmission_file -- n/a document -- Acknowledgement status, direction application id, and document count  of functional acknowledgment.
business_references	Provides information about business references associated with the objects.  Data displayed for file  types is: application_file -- n/a transmission_file -- n/a document -- Business references (1-5).
communications_data	Provides detailed information about transmission files that have passed through a communications service. Data displayed for file  types is: application_file -- n/a transmission_file -- OFTP: EERP ack sent, start position, dataset name, date, time, record size, record format. X400: message router id. PEDI: all PEDI header information.  document -- n/a
document	Provides information about the document type. Data displayed for file types is: application_file -- n/a transmission_file -- n/a document -- Standard, version, external document type, document control number, common access reference, message version and release, association assigned code, controlling agency.
functional_group	Provides information about functional groups within the interchange. Data displayed for file types is: application_file -- n/a transmission_file -- n/a document -- Group type, group control number and more.
history	Provides the detailed status history for documents and transmission files.
envelope_references	Provides all EDI envelope control references associated with the object, where applicable. Data displayed for file types is: application_file -- n/a transmission_file -- n/a document -- Interchange control number, group control number, document control number.
interchange	Provides specific information about the EDI interchange. Data displayed for file  types is: application_file -- n/a transmission_file -- n/a document -- Application interchange id and option, partner interchange id and option, segment terminator, element separator, subelement separator, release character, decimal notation character, etc.
mapper_details	Provides information about the maps associated with the objects.  Data displayed for file  types is: application_file -- n/a transmission_file -- n/a document -- Mapper run id.
routing	Provides all data associated with the routing of this object through the DEC/EDI server system. Data displayed for file  types is: application_file -- Application name, partner name, document type, direction. transmission_file -- Connection id, direction. document -- Application name, partner name, document type, direction.
status	Returns the current status of the object.  It can be one of the following: Completed -- The object has completed processing within the server.  Either it has successfully  reached completion or is has been cancelled. Available -- The object is available for fetching by an application. In Progress -- The object is currently being processed by the server. Failed -- The object failed to be processed by the server.
tracking_references	Provides all tracking references associated with the file. Data displayed for file types is: application_file -- Internal user reference. transmission_file -- Transmission file name. document -- User reference, document count, transmission file name.
other_data	Provides other miscellaneous data about documents and  transmission files. Data displayed for file  types is: application_file -- n/a transmission_file -- Character count, priority, DEC/EDI store file location. document -- Character count, segment count, priority, DEC/EDI store file location, X12 application file information, batching information, origial document number in the case of a resent document.
all	Provides ALL available audit information for documents and transmission files and ALL the tracking and routing information for application files.

 
 
 
 
 
 

Options

 
 

-application_nameSelect objects by the sending or receiving application.  This can be different from the application making the request (the application name specified as a parameter). 
 
 
 

Format
 
 

    -application_name=<application_name>
 
 
 

-beforeSelect objects that entered the system before the specified time. 
 
 
 

Format
 
 

    -before=<time>

    Where <time> is of the format:
 

    DD-MMM-YYYY:HH:MM:SS.CC

 
 
 
 

-business_referencesSelect objects by the business references associated with them. If a single business reference is supplied (i.e. no brackets and comma separated values), then each of the business reference slots in turn is checked for the supplied value. If brackets are used to introduce a list of values, then the values position is determined by where it occurs in the comma separated list of values supplied, and its value will only be tested against that of the associated business reference slot. For example, -business_references="ABC" will cause "ABC" to be checked against each of the 5 business reference slots, whilst -business_references=("","ABC") will
 cause "ABC" to be checked against only the second business reference slot.
 
 
 

Format
 
 

    -business_references=<business_reference>

    -business_references=(<business_reference> [ , <business_reference> ... ])
 
 

-current_statusSelect objects by status. 
 
 
 

Format
 
 

    -current_status[=option]
 

    Where option is one of:
 

    completed

    available

    failed

    in_progress
 
 
 

-databaseSelect objects from either the Live database, the Archive database or both databases. 
 
 
 
 

Format
 
 

    -database[=option]
 

    Where option is one of:
 

-live (D)	Select objects from the Live server audit database.
-archive	Select objects from the archived audit database.  By definition these will be of status purgeable or cancelled.
-both	Select objects from both the Live and Archive databases.

 
 
 
 

-directionSelect objects by direction. 
 
 
 

Format
 
 

    -direction[=option]
 

 
    Where "option" is one of:
 

    inbound

    outbound
 
 
 
 

-document_nameSelect object by the external document type name. (e.g.  invoic or 810)
 
 
 

Format
 
 

    -document_name=<external_document_id>
 
 
 

-link_idSelect object by the sending or receiving connection identifier. 
 
 
 

Format
 
 

    -link_id=<connection_id>
 
 

-map_idSelect object by the mapper run id associated with it. 
 
 
 

Format
 
 

    -map_id=<mapper_run_id>
 
 
 
 

-partner_nameSelect object by the sending or receiving partner. 
 
 
 

Format
 
 

    -partner_name=<partner_name>
 
 
 

-object_nameSelect objects by type, as specified when the objects were posted or fetched, for example purchase order or invoice. 
 
 
 

Format
 
 

    -object_name=<object_name>
 
 
 

-output_fileThe file specification of the file on the client to which output is written.  If you omit this option, then all output goes to standard output. 
 
 
 

Format
 
 

    -output_file=<file_specification>
 
 
 

-sinceSelect objects that entered the system after the specified time. 
 
 
 

Format
 
 

    -since=<time>
 

 
    Where <time> is of the format:

 
    DD-MMM-YYYY:HH:MM:SS.CC
 
 
 

-standardSelect objects by the edi standard used. 
 
 
 

Format
 
 

    -standard[=option]
 

 
    Where "option" is one of:
 

    edifact

    x12

    tdcc

    odette

    tradacoms
 
 
 
 
 
 
 

-test_indicatorSelect objects by the test mode used. 
 
 
 

Format
 
 

    -test_indicator[=option]
 

 
    Where "option" is one of:
 

    live

    mapper_test

    translation_test

    partner_test
 
 
 

-tracking_referencesSelect objects by tracking reference.  The reference can be that returned from the fetch or post command, or it can be a reference returned from a previous invocation of the TRACK command. 
 
 
 

Format
 
 

-tracking_references=<tracking_reference>
 
 
 

-typeIndicates which file of files to select. 
 
 
 

Format
 
 

    -type[=option]
 

    Where "option" is one of:
 

application_file	Select structured application files from the mapper.  (This is the default for -type).
transmission_file	Select unstructured transmission files directly from the communications service on the server.
document	Select in-house files (DEC/EDI version 1 internal format documents) from the translation service on the server.

 
 
 
 
 

-versionSelect objects by the version of the standard used to process them. 
 
 
 

Format
 
 

    -version=<version>
 
 
 
 
 
 

Examples

 
 

     #trade track my-app -direction=inbound \
-current_status=in_progress tracking_references
 

 
This track command gives tracking references for all incoming application files on the server system whose processing is still in progress. (-type defaults to application_file.) 
 

     #trade track my-app -standard=x12 \
-version=002003 status interchange
 

 
This track command reports on all x12 documents of version 002003 and prints out the current status and some of the ISA interchange fields.
 

 
Note that -type=document is not necessary in this case because the file type is implied in the selector, "interchange"
 

     #trade track my-app -type=transmission_file -direction=outbound \
-database=both -output_file=track_output.dat other_data
 

 
This track command reports miscellaneous information (sizes, and so on) on all live and archived transmission files in the server system  that are outbound and puts the result in a file called track_output.dat in the user’s current working directory.