# <comment lines start with the ’#’ character>
ACTION=<action name>
<parameter>=["]parameter value["]

The keywords, such as

ACTION

are not case-sensitive. White space after the equal sign is optional as are quotes around parameter values. Parameter values can contain embedded environment variables that are evaluated at run-time. Environment variable names must be surrounded by ’#’ characters, for example

#SSAWORKDIR#

is a valid environment variable. Any empty lines are ignored.

At the beginning of the input file, a mandatory parameter

work-directory=

should be initialized with the full path of the desired Identity Resolution Server working directory. For example:

work-directory=c:\InformaticaIR\work

or assuming that the Identity Resolution Server has the

SSAWORKDIR

environment variable set (as it should):

work-directory=#SSAWORKDIR#

The Identity Resolution Server working directory can be overridden for each individual action by giving the

work-directory=

parameter after the

action=

statement.

The following actions and parameters are supported.

Rulebase creation

action=rulebase-create
rulebase-name= <dbtype>:<number>:<user>/<password>@<service>

For example:

action=rulebase-create
rulebase-name="odb:0:myuid/mypassw@oraserve"

or using dictionary alias

action=rulebase-create
rulebase-name=ids:rulebase

Rulebase deletion

action=rulebase-delete
rulebase-name= <dbtype>:<number>:<user>/<password>@<service>

For example:

action=rulebase-delete
rulebase-name="odb:0:myuid/mypassw@oraserve"

Database creation

action=database-create
database-name=<dbtype>:<number>:<user>/<password>@<service>

For example:

action=database-create
database-name="odb:1:myuid/mypassw@oraserve"

or using dictionary alias

action=database-create
database-name=ids:database

System creation

action=system-create
system-name=<name of the system to be created>
sdf-name= <name of the system definition file which describes the new system>
rulebase-name=<dbtype>:<number>:<user>/<password>@<service>
database-name=<dbtype>:<number>:<user>/<password>@<service>

For example:

action=system-create
system-name=mysystem
sdf-name="#SSAWORKDIR#/mailinglist.sdf"
rulebase-name="odb:0:myuid/mypassw@oraserve"
database-name="odb:1:myuid/mypassw@oraserve"

System deletion

action=system-delete
system-name=<name of the system to be deleted>
rulebase-name=<dbtype>:<number>:<user>/<password>@<service>

For example:

action=system-delete
system-name=mysystem
rulebase-name="odb:0:myuid/mypassw@oraserve"

Run User-Defined Job (User Job)

action=job-run
job-name=<name of the pre-defined User Job to be run>
system-name=<name of the system to be deleted>
rulebase-name=<dbtype>:<number>:<user>/<password>@<service>
work-directory=<working directory of the Console Server>

For example:

action=job-run
job-name="run-name-relates"
system-name=mysystem
rulebase-name="odb:0:myuid/mypassw@oraserve"
work-directory=c:\InformaticaIR\work

After the job starts, a detailed message including the run number for each step is written to the output file.

Stop Job

action=job-stop
rulebase-name=<dbtype>:<number>:<user>/<password>@<service>
system-name=<name of the system associated with the job>
run-number=<number of a started job>

For example:

action=job-stop
system-name=mysystem
rulebase-name="odb:0:myuid/mypassw@oraserve"
run-number=1

When stopping a job started using

idsbatch

, check the output from the preceding

job-run

action to determine the value of the

run-number

parameter.