iAddress™ offers powerful automation functionality that allows for you to easily and flexibly automate your address management processes. Using job configuration files, you can specify all the details of how your job is run – from the input files to the correction parameters to the output files. By command line options, you can override the config file options found in the next section specific to job and merge file numbers.

There is a limit of 8192 characters on the command line.

Format:

iAddress.exe filepath\filename.cfg [-logfile=_filename][-existingoutput={datestamp (default), error, overwrite}][-KEEP_IADDRESS_OPEN={Y(default),N}] [-J#][_FIELDNAME=_FIELDDATA][-F#][_FIELDNAME=_FIELDDATA] [-CADATE] [-USDATE]

Example: 
iAddress.exe “c:\work\config\job1.cfg”

It is important to note:

-J# (Job Number) must be specified for all _FIELDNAME=_FIELDDATA that is relevant to a job.

 -J# (Job Number) and -F# (Merge file Number) must be specified for _FIELDNAME=_FIELDDATA that is relevant to both a merge file and a job until -J# or -F# is re-specified the same value for J# and F# are assumed for all _FIELDNAME=_FIELDDATA that follow.

 If J# is re-specified then F# is cleared.

 Job numbers start at value 1 and increase.

 Merged file numbers start at value 0 and increase.

 The jobs and files are ordered the same way they were first selected in iAddress™.

Command Line Parameters

-logfile

Usage:

-logfile=”full/path/to/file.log”

Example:

iAddress.exe “c:\work\config\job1.cfg” -logfile=”c:\work\logs\job1.log”

Description:

By default, the log is written to the same folder that iAddress™ resides in (On a typical installation this is C:\Program Files\iAddress on a 32-bit OS; C:\Program Files (x86)\iAddress on a 64-bit OS). The log is named automate.log and is overwritten on subsequent runs. By using this parameter you can redirect the log output and gain some control over log storage.

-quiet

Usage:

 -quiet

Example:

 iAddress.exe “c:\work\config\job1.cfg” –quiet

Description:

This parameter causes iAddress™ to suppress Message Dialogs. While running in Quiet Mode, all dialogs that notify of a critical error in the application flow will cause iAddress™ to fatally exit with an error code of 1 (which can be checked in a batch file). All message dialogs are logged to the logfile (regardless of this parameter).

-existingoutput

Usage:

 -existingoutput={datestamp, overwrite, error}

Example:

 iAddress.exe “c:\work\config\job1.cfg” –existingoutput=overwrite

Description:

This parameter controls how iAddress™ handles the scenario when defined output files (Such as the save job,        labels or reports) already exist on the file system. The default is to datestamp the existing file.

Datestamp: Prepends the existing file with the creation date of the file, or the current date and time if it is unable to determine the creation date.

Overwrite: Overwrites the existing file. This will cause all the existing files to be deleted prior to iAddress™ running the job.

Error: Causes iAddress™ to trigger a fatal error before the job is run.

-KEEP_IADDRESS_OPEN

Usage:

-KEEP_IADDRESS_OPEN={Y(default),N}

Example:

iAddress.exe “c:\work\config\job1.cfg” –KEEP_IADDRESS_OPEN=N

Description:

This parameter controls whether iAddress™ remains open after the job is done.

-J#

Usage:

-J# [_FIELD_NAME]=[_FIELD_DATA]

Example:

• exe “c:\work\config\job1.cfg” –J1
• exe “c:\work\config\job1.cfg” -J1 -STANDARD_MAILING_DATE=2011-01-01 -F0 INPUT_FILE=C:\foo\file.xls

Description:

This parameter represents a job number and must be specified for all _FIELDNAME=_FIELDDATA that is relevant to a Job. See “Important to note:” section above for more information on the usage of -J#. See also the config file options section for fieldnames and data.

-F#

Usage:

 -F# [_FIELD_NAME]=[_FIELD_DATA]

Example:

• exe “c:\work\config\job1.cfg” –F0
• exe “c:\work\config\job1.cfg” -J1 STANDARD_MAILING_DATE=2011-01-01 -F0 INPUT_FILE=C:\foo\file.xls

Description:

This parameter represents a Merged file number and must be specified for all _FIELDNAME=_FIELDDATA that is relevant to a merged file. See “Important to note:” section above for more information on the usage of -F#. See also the config file options section for fieldnames and data.

-USDATE

Usage:

 -USDATE

Example:

• exe “c:\work\config\job1.cfg” –USDATE

Description:

This option creates a file in the execution path called “USDATE.tab”.  This file contains the start and end dates of the US mailing data currently loaded on your system. USDATE.tab is a tab delimited file. This information can be used to determine if you have the data for the mailing date that you have chosen.

-CADATE

Usage:

 -CADATE

Example:

• exe “c:\work\config\job1.cfg” –CADATE

Description:

This option creates a file in the execution path called “CADATE.tab”.  This file contains the start and end dates of the Canadian mailing data currently loaded on your system. CADATE.tab is a tab delimited file. This information can be used to determine if you have the data for the mailing date that you have chosen.