For an input message from the TS application of type APPLI applies:
If a message sent to the UTM application is intended to start a service, the TAC must be at the beginning of the message.
If the message is to be appended to the message queue for a TAC queue or a temporary queue, the name of the queue must be at the beginning of the message. If the message is going to a temporary queue, no TAC or LTERM may exist in the application under the name of the temporary queue.
If the TAC is shorter than 8 characters, it must be separated from the rest of the message by at least one space.
If the specified TAC or the name of the queue is invalid, the event service BADTACS is started, provided it has been generated. Otherwise, the message K009 is sent to the TS application, unless a separate message module is being used in which PARTNER has not been generated as the destination for the message K009.
If the TS application starts a service then this service can read the message with the KDCS call MGET or FGET. If the TS application sends a message to a service-controlled queue then any service can read the message with the KDCS call DGET. If, during a read call, the KCLA length is shorter than the length of the message segment, only the requested part is read; the rest of the message is lost. The return code 01Z indicates that the message has not been read in its entirety.
Please note that the TS application must provide the name of the TAC or the queue in the “correct” code for the UTM application, i.e. in EBCDIC for a UTM application on BS2000 systems and in ASCII for a UTM application on Unix, Linux or Windows systems.
Alternatively, in applications on Unix, Linux or Windows systems, code conversion can be generated for the connection to the TS application (operand MAP=SYS1/SYS2/SYS3/SYS4 in the PTERM or TPOOL statement).