Background jobs are asynchronous jobs which are addressed to an asynchronous service of its own or a remote application. Background jobs are particularly suitable for time consuming or non-time critical processing, in which the result has no direct effect on the current dialog.
Background jobs consist of the transaction code (TAC) of the program unit used to start the background job (service TAC) and possibly a message for the program unit. The type of transaction code determines whether the job is to be processed as an asynchronous job or as a dialog message.
Background jobs can be created as follows:
by an input from a terminal
by an MQ call from a service of the UTM application
by a message from another application that communicates with the UTM application via the LU6.1, LU6.2 or OSI TP protocol
by an input from another application connected via the transport system interface
by a UTM message when the message is assigned the message destination MSGTAC (i.e. event-driven, see "Asynchronous service MSGTAC") or is assigned the TAC of an asynchronous service as the user-specific message destination
Background jobs can be restarted after abnormal termination of a service (redelivery), see "Redelivery with background jobs" or sent to the dead letter queue.