The DPUT (delayed free message PUT) call enables you:
to send messages to USER queues, TAC queues or temporary queues. The messages to TAC queues can also be time-driven.
to enter time-driven asynchronous jobs with their messages or message segments in a message queue (output jobs to LTERM partner, background jobs to local asynchronous services, background jobs to remote asynchronous services which were previously addressed using an APRO AM call)
to log user information concerning these jobs
to create confirmation jobs within a job complex plus the associated user information
to pass print options (= RSO parameter list) for RSO printers (only on BS2000 systems)
You enter the desired point in time in the KDCS parameter area (see table on "DPUT call without job complex"). At the given time, the job is entered in the queue of jobs to be executed. In other words, the time-driven job is not executed exactly at the specified time, but at this time at the earliest.
The message segments generated using DPUT are collected by openUTM and are terminated at the next PEND call. Following the end of a transaction, the message segments are sent as a single message to the appropriate queue. Exception: If formatted message segments are sent to terminals, each of these segments forms a separate message.
Because of the various functions, the DPUT call has two formats:
DPUT call without job complex, and
DPUT call within a job complex.
The format of the DPUT call is described in detail below. For further information on message queuing refer to section "Message Queuing (asynchronous processing)".