ARTWTRN servers present application transactions as Tuxedo services and, when receiving a transaction request, execute the corresponding programs.

These servers are non-conversational in order to support pseudo-conversational CICS transactions.

1. When starting, an ARWTRN server publishes one service per transaction it offers.
2. Non-3270s clients submit the request to ARTWTRN via tpcall and then ARTWTRN/1 will receive the request.
3. One ARTWTRN server offering this service receives the request with the associated application data from FML buffer and then processes the transaction.
4. After processing the transaction, on the RETURN {TRANSID}, a reply is sent to the client and the ARTWTRN server finishes the conversation by a tpreturn() to return the application data and TRANSID with FML buffer.
5. If users change the application data and re-submit it to transaction, Non-3270s clients could submit the request to ARTWTRN according the TRANSID received in step 4.

Only transactions belonging to no tranclass or to a tranclass with MAXACTIVE > 1 are advertised by these servers.