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

These servers are conversational to manage true conversational CICS transactions.

1. When starting, an ARTSTRN server publishes one service per transaction it offers.
2. When a user transmits a transaction request, the ARTTCPH managing the user performs a tpconnect to the corresponding transaction (service).
3. One ARTSTRN server offering this service receives the request with the associated commarea and screen and then processes the transaction.
4. After processing the transaction, the ARTSTRN server:
   • In the case of a Normal Pseudo-Conversational CICS transaction: On the RETURN {TRANSID} a reply is sent to the client, finishing the conversation by a tpreturn() returning the new 3270 screen, and the commarea.
   • In the case of a Conversational CICS transaction with loop of SEND & RECEIVE:
     • On the RECEIVE the ARTSTRN server transmits the prepared 3270 stream via tpsend(), then waits for a tpreceive, for the next user input to complete the RECEIVE
     • On the RETURN {TRANSID} the ARTSTRN server replies to the client, finishing the conversation by a tpreturn() returning the new 3270 screen, and the commarea.

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