Tuxedo ART for IMS supports persistent message only for programs using ALT PCB. For the program switch through ALT PCB, when the target transaction is a persistent transaction, the message will be put into the /Q of that transaction. For how to define a persistent transaction, please refer to the imsresource.desc section.

For persistent message support, we differentiate the ARTIMPP into two running mode. One is ARTIMPP in normal mode, one is ARTIMPP in persistent mode. For how to define the two ARTIMPP server mode, please refer to ARTIMPP configuration section.

ARTIMPP in normal mode will advertise transactions as services and handle the normal service request from front end, such as terminal request, request from ARTIGW.The service request is scheduled by Tuxedo framework and is passed through Tuxedo IPC queue.

ARTIMPP in persistent mode will not advertise any services. It will monitor every /Q for the persistent transaction whose CLASS belong meet the"-l class_list" parameter of the ARTIMPP. It gets the message from the /Q of the persistent transaction and execute corresponding program for the transaction.

ARTIBMPT is also a server that is related to persistent message support. The transaction oriented BMP program that ARTIBMPT serves must only be persistent transaction. For what is "transaction oriented BMP“, please refer to ARTIBMPT configuration section. In transaction oriented BMP program, the GU operation will get message from the /Q of the transaction.