Message dispositions

Each UPoC module must return a keyed list that instructs the TPS how to process specified messages. These lists are called message dispositions, and they are TPS context sensitive.

This table shows the supported dispositions:

Disposition Description
CONTINUE Returns for normal processing and gives to next module in stream. It can continue to:
  • trxid, where a transaction ID is returned.
  • fileset_ibdirpars, where an ordered list of files to be processed is returned.
  • fileset_ibdel, where an ordered list of files to be deleted is returned.

    Otherwise, a message handle is returned.

ERROR Places the message into the error database and removes it from the recovery database, if required.
KILL Ends message processing. (msgdestroy)
KILLREPLY Similar to KILL, but stops waiting for a reply message from the connection. This disposition should only be used in sms_ib_reply.
OVER Instructs the engine to place the message in the queue for the opposite direction. For example, an OVER message in the Inbound Data TPS is given to the OB Data TPS. Only valid in an inbound or outbound TPS.

Do not use the OVER disposition within the read and write UPoCs in the UPoC driver. The engine reports an error when it gets this disposition in the read and write UPoCs.

Do not use the OVER disposition within the Fileset FTP driver, where it destroys the message. The engine reports an error when it gets this disposition.

PROTO Places the message at the head of the Outbound Post-TPS Queue (that is, prepared for immediate delivery using the protocol driver). Use PROTO only in a TPS operating within a protocol thread.
SEND Skips further TPS processing. Sends the indicated messages through the translation thread to their destination.
REROUTE Chooses a different translation ID route after some translations of a message have taken place. This is used during translation, routing, and in the Route Detail Pre-/Post-Processor.