Background jobs are asynchronous jobs sent to an asynchronous service of the local application or of a remote application. We therefore also refer to local queuing or remote queuing.They are particularly suitable for long-running or non-time-critical processes, the result of which has no direct influence on the current dialog.
They consist of the transaction code (TAC) of the program unit with which the background job begins, and possibly an asynchronous message. The transaction code determines whether the job is processed asynchronously or as a dialog job.
Background jobs can be initiated by means of:
input at a terminal
a call from an UTM-Client program with the OpenCPIC carrier system
a message from another application that communicates with the UTM application by means of the LU6.1 or OSI TP protocol
input from another application connected via the transport system interface
an MQ call from a service of the local application or a remote UTM application
UTM messages (i.e. event-driven)
Background jobs are redelivery-capable, i.e. they can be restarted after abnormal termination of an asynchronous service and the asynchronous messages can then be redelivered.
Alternatively, or after the last redelivery attempt, openUTM can put the incorrectly processed message of an asynchronous service in a separate queue, the dead letter queue. Messages to an asynchronous service of a remote application via the LU6.1 or OSI-TP protocol can also be put in the dead letter queue if these messages cannot be delivered due to a permanent error in the remote application.