In the CLOPT, the following syntax is used:
ARTTCPL – Terminal Control Program Listener.
The terminal control program (ARTTCP) is a group of Tuxedo servers that manage the connections of 3270 terminal emulators to CICS Runtime. When you run programs, the
ARTTCP connects terminal emulators to the network ports assigned to
ARTTCP.
ARTTCP communicates with the emulator using a Telnet protocol.
The ARTTCP server is composed of two types of servers: a single
ARTTCP listener (
ARTTCPL) process and one or more
ARTTCP handler (
ARTTCPH) processes. The
ARTTCPL process establishes a well-known listening port address to which terminal emulators may connect. The
ARTTCPH process listens on this port and accepts incoming connection requests. The
ARTTCPH process establishes your user session for the connection and handles all subsequent screen I/O for the terminal emulator. As a performance enhancement, each
ARTTCPH process can manage multiple sessions simultaneously. When you disconnect the emulator from the port, the
ARTTCPH terminates the session.
ARTSTRN servers present application transactions as Tuxedo services and, when receiving a transaction request, execute the corresponding programs.
|
3.
|
One ARTSTRN server offering this service receives the request with the associated commarea and screen and then processes the transaction.
|
|
•
|
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.
|
It is critical and verified by STR1 servers at boot time that MIN and
MAX number of servers are set to 1. The goal of these servers being to guarantee the parallel processing of only one transaction in a group (with
MAXACTIVE = 1), to start or let Tuxedo start a few servers offering the same transactions will be self-defeating for STR1 Servers.
Since MIN and
MAX are set to 1 the Tuxedo argument RQADDR, become unnecessary, and should be avoided for simplicity.
ARTTSQr manages temporary storage queues, it serves the functionalities required by EXEC CICS: WRITEQ TS, READQ TS and DELETEQ TS.
ARTTSQ publishes two main kinds of services:
ARTTDQ manages transient data storage queues, it serves the functionalities required by EXEC CICS: WRITEQ TD, READQ TD and DELETEQ TD.
ARTTDQ publishes one service per declared queue as the name of the TDQueue suffixed by “_TDQ”:
A group of resources must be assigned to a single ARTTDQ server to avoid trying to publish the same service twice. This is checked at boot time and will generate error messages during the boot phase when not respected, but no action will be taken.
ARTDPL – CICS Runtime server for distributed program link execution.
Only programs with the attribute REMOTESYSTEM(sysid) positioned to DPL, will be advertised by DPL servers, and only by servers with this sysid as system indicated thru the
-s option
ARTATRN servers present application transactions as Tuxedo services and when receiving a transaction request, execute the corresponding programs.
In contrast to ARTSTRN servers, these servers are transactional in order to manage true CICS transactions. They are only called from other servers (START TRANSID) and never directly from terminals or clients.
When starting, an ARTATRN server publishes one service per transaction it offers. These transactions are named "ASYNC_{transaction_name} (.
|
2.
|
One ARTATRN offering this service receives the request with the associated message, then processes the transaction.
|
ARTATR1 servers are a specialized version of
ARTATRN servers presenting only transactions with
MAXACTIVE = 1, whereas
ARTATRN servers present transactions with
MAXACTIVE > 1.
It is critical, and verified by ATR1 servers at boot time, that MIN and
MAX number of servers are set to 1. The goal of these servers is to guarantee the parallel processing of only one transaction in a group (with
MAXACTIVE =1). To permit Tuxedo to start several servers offering the same transactions would be self-defeating for ATR1 Servers.
Since MIN and
MAX are set to 1, the Tuxedo argument
RQADDR, becomes unnecessary, and should be avoided for simplicity.
ARTCTRN – CICS Runtime server for conversation oriented transactions with
MAXACTIVE > 1.
ARTCTRN servers present application transactions as Tuxedo services and when receiving a transaction request, execute the corresponding programs.
In contrast to ARTSTRN servers, these servers are transactional in order to manage true CICS transactions. They are only called from other servers (CNVERSE) and never directly from terminals or clients.
When starting, a ARTCTRN server publishes one service per transaction it offers. These transactions are named
{SysId}_{transaction_name}.
The {SysId} is the name of this region defined in the
-s parameter.
|
2.
|
One ARTCTRN offering this service receives the request with the associated message, then processes the transaction.
|
The generic parameter CONV is optional for this server type; if you use it, it must be defined as
CONV=N, because the
ARTATRN is transactional.
ARTCTR1 – CICS Runtime main server for conversation oriented transactions with
MAXACTIVE=1.
ARTCTR1 servers are a specialized version of
ARTCTRN servers presenting only transactions with
MAXACTIVE = 1, whereas
ARTCTRN servers present transactions with
MAXACTIVE > 1.
It is critical, and verified by ARTCTR1 servers at boot time, that
MIN and
MAX number of servers are set to 1. The goal of these servers is to guarantee the parallel processing of only one transaction in a group (with
MAXACTIVE =1). To permit Tuxedo to start several servers offering the same transactions would be self-defeating for
ARTCTR1 servers.
Since MIN and
MAX are set to 1, the Tuxedo argument
RQADDR, becomes unnecessary, and should be avoided for simplicity.
ARTCNX — CICS Runtime connection server for user connection management.
The generic parameter CONV is mandatory for this server type, and must be defined as
CONV=Y, because
ARTSTRN is conversational.
ARTADM — Administration Server
|
•
|
The ARTADM server on the master node must be started as the first server in the target application.
|
|
•
|
The ARTADM server on the slave node must be started as the first server on the node.
|
The ARTADM server on the master node offers a service for the internal communications with the
ARTADM servers running on the slave nodes.
To build the ARTCKTI server, execute the following command as the Tuxedo administrator with write permission for the
$KIXDIR/bin directory:
$MQM is the path that WebSphere MQ has been installed.
