User Defined Table Names

When multiple jobs run simultaneously, they cannot use the same user-defined table. In this situation you must use the user_table job parameter to ensure that each job uses its own set of user-defined tables.

The syntax of the user_table parameter is:

ActionStartJob(<job name>[, [<task name>:]user_table::

<old table name>=<new table name>])

If no task name is specified, the parameters are set for all import tasks in the entire job. If a task name is specified, the parameter is set for that import task in the job. You must specify the unique name of the task as defined in the job, not the name of the import task. The job name, task name, parameter name and old table name are case-insensitive. The new table name is converted to upper case.

For example, suppose the external sets of an import task are defined as follows:

External Set	Driving Set	Use User Table	User Table
SET_SCHEDTOUR	Y	N
SET_RESERVATION	N	Y	RESERVATION
SET_PARTICIPANT	N	Y	PARTICIPANT

When only one job executes this import task, you must create the RESERVATION and PARTICIPANT tables and run the job as follows:

ActionStartJob(MyJob)

In this case, USoft Batch will use the database RESERVATION and PARTICIPANT tables for temporary storage of the external sets.

When two jobs must execute this import task simultaneously, you must create tables RESERVATION1, RESERVATION2, PARTICPANT1 and PARTICIPANT2 and run the two jobs as follows:

ActionStartJob(MyJob,

'MyTask:user_table::reservation=reservation1',

'MyTask:user_table::participant=participant1')

ActionStartJob(MyJob,

'MyTask:user_table::reservation=reservation2',

'MyTask:user_table::participant=participant2')

In this case the first job will use the database tables RESERVATION1 and PARTICIPANT1, while the second job uses RESERVATION2 and PARTICIPANT2.