Job Record – Processing Options Details

Associated with each job  are optional processing options. Processing options allow you to configure the runtime policy when an error condition occurs.

The default policy on an error is to terminate the current job, email an error report to the administrator (if specified), and stop processing of any other jobs in the batch.  By setting the processing options this default behavior can be customised. For example, an SQL statement  that drops a table will fail if the table does not exist.  Setting the processing option to ‘2’, “Abort job but continue processing batch” is appropriate in this case.  Without this the failed SQL statement would cause any subsequent jobs to be unprocessed.  Another example is where you want the transfer to continue processing even if one or more of the rows being inserted fails.

The Processing Options tab is where you define how the job process is conducted, what happens if an error occurs, what alerts are sent and how threads should process.

To complete the Processing Options tab follow the steps below:

From within a Job Properties record click on the Processing Options tab to open the Job Properties window.



The Processing Options window is divided into five parts: Batch Process Options, Transfer Options, Alert Options; Logging Options and Thread Options.

Batch Process Options choose:

Abort Batch – if enabled (the default) then an error status on the job will cause SLIK to abort further processing of jobs in the batch.

Continue Batch – if enabled this causes SLIK to continue processing other jobs in the batch even if the job reported an error condition.

Transfer Options – choose:

Continue next row – during a table map or column map if a SQL or conversion error occurs on a row then default behaviour is to stop processing the transfer and record the job status as failed.  By enabling this option you can override this processing logic and have SLIK continue to process the balance of the rows to be transferred.  Note: any error rows will be still logged to the error log and the final Batch Run status will be recorded as Warnings.

Refresh Data – when SLIK processes a table or column map it performs an SQL insert statement on the destination table. If during the insert of a row the database reports an error due to a duplicate key constraint then the default behavior is to abort the transfer with an error. However this option allows you to customize the logic so that when a duplicate key is seen then SLIK will change the INSERT statement into an SQL UPDATE statement on all of the specified columns except the primary key columns.  This option has the effect of updating any existing rows and adding any new rows.

Outside Transaction  – as noted above SLIK performs all SQL statements and table/column mappings within a transaction.  This can be overridden if necessary to disable this automatic transaction feature.  It may be appropriate to disable transactions when executing certain SQL statements that are not supported inside a transaction by the target database.

Ignore data conversion errors – normally data conversion errors (eg, JDE OneWorld date conversion etc) are treated as failed jobs. By enabling this processing option you can have SLIK ignore individual conversion errors and continue processing.  Errors will still be logged to the SLIK error log.

Stop batch processing on no data  – if enabled this option causes SLIK to timeout on the current job if no data was found in a table/column map, EDI import or export or SQL statement operation.

Alert Options – choose:

Alert Operator on error – if an alert should be generated if the Job generates an error.

Alert Operator on warning – if a warning should be generated if the Job generates a warning.

Alert Operator on no data – when used in combination with the “Stop processing on no data” option, if enabled, SLIK will advise the administrator whenever a run returns no data.

Logging Options – choose

Never log error – if an error log entry is not to be created to record errors encountered when the Job processes.

Never log task – if a task log entry is not to be created to record task completed as the Job processes.

Thread Options – choose

Execute Concurrently (Batch,Report,Command) – if processes are to be run concurrently.  When enabled SLIK ensures the Batch/Report or Command operation starts successfully but does not wait for the operation to complete before moving on to process the next job.

Click on the Apply and OK buttons to save and close the new Job record or click on the Cancel button to close the Job Properties window without saving the Batch file.