Previous Next

A Job in USoft Batch is essentially a procedure: a series of operations that form a functional whole and that are performed in a predefined sequence each time the job is called.

Callers of a job can be made to pass input parameters, much in the same way as in other programming environments for remote procedure calls (RPCs).

A Job can also pass output parameters back to the caller. However, more typically, the output of a Job is simply the result of data manipulation on the server. This result may or may not be queried after the job has run, and independently of it. Data manipulation executed by USoft Batch is run against the USoft Engine, not directly against the database. In this sense, USoft Batch jobs may be said to implement business rules.

Jobs raise errors and produce error messages as is customary in comparable RPC environments. Also, asynchronous job execution is customarily logged to file in the conventional way.

Once you have defined a Job, you may have it validated. USoft Batch will then parse all the SQL statements in the Job, checking whether they are syntactically correct.



collapsePlanning a job
collapseDefining input parameters (if you need them)
collapseDefining job action
collapseSetting up a callable job
collapseValidating the job
collapseDelivering the job
collapseExecuting the job



See also

BatchRunner Internal Component

Parameters and Variables


Error handling

Commit Type and Abort Mode settings