Enabling/Disabling Import Status Files

See Also

By default, USoft Batch creates one status file during import task processing:

This file contains all records that were rejected.

Optionally, the following files can also be created:

This file contains all records of the import file that were successfully imported.

This file contains all the failure messages that are produced when records are rejected during an import.

The total size of these files is greater than or equal to the size of the external set. This is not always useful, and writing these files degrades performance. You can improve the performance by disabling the creation of these status files, if required.

You can disable the creation of the .SUC, ERR, and .MES files independently, using the following parameters:

ActionStartJob(<job name>[,[<task_name>:]create_suc=true|false])

ActionStartJob(<job_name>[,[<task_name>:]create_err=true|false])

ActionStartJob(<job_name>[,[<task_name>:]create_mes=true|false])

If no task name is specified, the parameters are set for the entire job. If a task name is specified, the parameter is set for that job task. The values "true" and "false" must be in lower case. By default, create_mes and create_suc are set to "false", and create_err is set to "true".

You should always create the .ERR file. You can then find all messages in the log file.

Parameter assignments are applied in the order of the parameter list, so it is possible to set a parameter for an entire job, and overrule it for a specific task. For example:

ActionStartJob(MYJOB,create_suc=false,MY_TASK:create_suc=true)

For example, running a job with multiple import tasks (one of which is IMPORT_TASK_1) with the following parameters:

IMPORT_TASK_1:create_suc=false,create_err=true

results in the .SUC file of task IMPORT_TASK_1 not being created. All other status files, including the .SUC files of other import tasks, will be created.

NOTE:

If you run the job more than once, the status files are overwritten by each new run.