The rule of strict dialog also applies to distributed processing, i.e. in communications between two partners, after a message to the partner you have to receive a response before you can send another message to this partner.
The period between receiving a dialog message and sending the next dialog message is called a processing step. The next message may either be a response, in which case the processing step is equivalent to a dialog step, or a message to another partner.
A job submitter can simultaneously interact with multiple job receivers. The next programming step in the job submitter only starts when all the responses have been received from the job receivers. A separate program unit run is generally started for each processing step (exception: PGWT).
The job-submitting service can be either a dialog service or an asynchronous service.
Exchange of dialog messages
You use MPUT to send and MGET to receive dialog messages between partner services in the same way as with dialog messages without distributed processing.
If a job-receiving service exchanges messages with a job submitter it behaves as if it were communicating with a terminal: you have to enter blanks in the KCRN field when using MGET and MPUT.
When exchanging messages with a job receiver, a job-submitter service must specify the service ID of the job receiver in the KCRN field (see "Addressing remote services").