MAX_TRANS_NUM specifies the maximum number of transactions, no later than which ART for CICS server must reconnect to RM (after ART for CICS receives a reconnect request). Meaning, after receiving a reconnec request, an ART for CICS application server will reconnect to RM randomly (either during the next transaction in this case, or during any transaction no later than the one that
MAX_TRANS_NUM specifies).
-R MAX_TRANS_NUM can appear anywhere in a server's
CLOPT; however, if you omit
MAX_TRANS_NUM (as
MAX_TRANS_NUM is optional),
-R must be the last argument of the
CLOPT.
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 <Default ? Font>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.
To join 3270 terminal to ART Runtime, you must specify the MAXWSCLIENTS parameter in the
MACHINES section of the UBBCONFIG file.
MAXWSCLIENTS is the only parameter that has special significance for
ARTTCPL.
MAXWSCLIENTS tells the Oracle ART at boot time how many accesser slots to reserve exclusively for 3270 terminals.
For MAXWSCLIENTS, specify the maximum number of 3270 terminal that may connect to a node. The default is 0. If not specified, terminal may not connect to the machine being described.
Enable timeout mechanism between ARTTCPL/
ARTTCPH and TN3270 terminal emulators.
Numeric (in minutes). This numeric is a threshhold value, after which
ARTTCPL/
ARTTCPH begins to disconnect TN3270 terminal emulators if there isn't application data exchanged on the link.
0 means no timeout; a negative value is forbidden.
Numeric (in seconds). This numeric is a threshhold value, after which
ARTTCPL/
ARTTCPH begins to send keep-alive messages to TN3270 terminal emulators.
0 means to use the system default value; a negative value means this keep-alive feature is disabled. This option only supports Linux and AIX platforms.
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.
|
ARTSTR1 – <Default ? Font>CICS Runtime main server for synchronous terminal oriented transactions with
MAXACTIVE = 1.
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.
ARTTSQ – <Default ? Font>CICS Runtime Temporary Storage Queue Server
ARTTSQ manages temporary storage queues, it serves the functionalities required by EXEC CICS: WRITEQ TS, READQ TS and DELETEQ TS. Two versions of
ARTTSQ server are delivered :
ARTTSQ (for Oracle db), and
ARTTSQ_UDB (for UDB) .
TMS and
OPENINFO should be defined accordingly.
ARTTSQ publishes two main kinds of services:
ARTTSQP - CICS Runtime Temporary Storage Queue Pool Server
ARTTSQP manages temporary storage queues which are defined in TS pool. It serves the functionalities required by
EXEC CICS (
WRITEQ TS,
READQ TS and
DELETEQ TS). Two versions of
ARTTSQP server are delivered:
ARTTSQP (for Oracle DB) and
ARTTSQP_UDB (for UDB).
TMS and
OPENINFO should be defined accordingly. Every CICS region can have multiple
ARTTSQP servers, and different Tuxedo domains can use the same database; therefore, the TS queue can be shared among different CICS regions in Tuxedo domains.
The DBMS user indicated in the OPENINFO of the group containing the server, must have access to
ARTTSQP_INFO,
ARTTSQP_CONTENT and
ARTTSQP_MAN tables, either directly (objects are created in this schema) or through a
DBLINK.
The bind.sh script issues DB2
BIND command; you can change its parameter to meet your actual scenario. The changes you make will affect not only
ARTTSQP_UDB but also
ARTSRM_UDB and
ARTTSQ_UDB via commands like
buildartcics.
ARTTDQ – <Default ? Font>CICS Runtime Transient Data Queue Server
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 –
<Default ? Font>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.
ARTDPL can choose whether to invoke some special programs for themselves during its initialization and shutdown. There are two methods. One is specifying the "
-b suffix_name" or "
-d suffix_name" option in their
CLOPT of
UBBCONFIG file. The other specify the
PLTPI or
PLTSD parameters in the
system.desc configuration file. Both ways need to write the
program_list_table.desc configuration file. This function does not support the "
XA DISABLE" feature.
For CLOPT, when
ARTDPL specifies the
-b suffixname or
-d suffixname option, the server loads
program_list_table.desc configuration file to obtain the right program list (with
suffix_name). Then in
tpsvrinit() or
tpsvrdone(), the server executes these programs.
In the initialization programs, you may want to invoke some EXEC CICS commands, these command require ART CICS provided services.
ARTDPL (which invokes the initialization programs), needs to be configured last in the
UBBCONFIG file, so that it is booted last during ART CICS boot.The initialization programs can use the services provided in the previous application servers.
If ARTDPL specifies the
-d option, it executes some programs during shutdown. You must first shutdown
ARTDPL seperately, and then shutdown all remaining ART CICS servers. For example, you must use "
shutdown -g groupname -I SRVID" first, and then run
shutdown -y to shutdown the entire ART CICS region.
If you specify PLTPI or
PLTSD in the
system.desc file, when
ARTDPL boots or shustdown, it invokes the programs list where
SUFFIX is the same as the
PLTPI/
PLTSD value.
Specifies the SUFFIX value in the
program_list_table.desc to choose which programs the
ARTDPL want to execute during its initialization.
Specifies the SUFFIX value in the
program_list_table.desc to choose which programs the
ARTDPL want to execute during its shutdown.
|
Note:
|
For both -l and -L options, if there are multiple ARTDPL in one ART CICS region and -s is configured in such region, please set the same value for all -l specified in this region, and set the same value for all -L specified in this region. For more information about -L configurations, please refer to List of Groups Configuration File.
|
Sometimes, the length of the COMMAREA data returned by program is larger than the length of the
COMMAREA data initialized in Tuxedo client. In this case, you need to add one more FML field
CXMW_COMMAREAINLENGTH before
TPCALL to the Tuxedo client. The
CXMW_COMMAREAINLENGTH must be specified the total length of
COMMAREA which is initialized in Tuxedo client, and its data type is long. In this way, ARTDPL can
TPRETURN COMMAREA data with the total length
CXMW_COMMAREAINLENGTH which is definitely larger than the length of the data filled in
COMMAREA.
When the length of COMMAREA data returned by program is smaller than the total length
CXMW_COMMAREAINLENGTH, ARTPDL normally adds
X'00' (null padding character) at the end in the return FML field
CXMW_MESSAGE. If you want to strip the NULL padding characters to reduce the data communications between the Tuxedo client and ARTDPL and improve the performance, add “
-S” in the CLOPT options of ARTDPL. ARTDPL server will strip the padding characters and then
TPRETURN the
COMMAREA data with FML field
CXMW_MESSAGE.
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 - <Default ? Font>CICS Runtime main server for asynchronous oriented transactions with
MAXACTIVE = 1.
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 – <Default ? Font>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 (
CONVERSE) 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.
|
ARTCTR1 – <Default ? Font>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.
ARTWTRN – CICS Runtime application server for synchronous non-3270s clients oriented transactions with MAXACTIVE > 1.
ARTWTR1 – CICS Runtime application server for synchronous non-3270s clients oriented transactions with MAXACTIVE = 1.
It is critical and verified by WTR1 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 WTR1 Servers.
ARTCNX —
<Default ? Font>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.
If you use this parameter, you can start up to 62 ARTCNX servers, each server has up to 357,911 terminals numbers, between 0 to 357,910 (000 to zzz in base 71), in this case the
TRMID is composed as follow: x000 to xzzz (
x is the character in
-t parameter).
|
•
|
ARTCNX will check whether -t is unique in global scope when booting; if it is not, ARTCNX fails to boot.
|
|
•
|
You can use -t to change the auto-assigned TERMID prefix, but make sure the auto-assigned TERMID is not same as the one defined in terminals.desc.
|
Specifies the SYSID of a CICS region (the region which
ARTCNX belongs to). The
SYSID is limited to 4 characters and must be unique in each CICS region.
Specifies the APPLID of a CICS region (the region which
ARTCNX belongs to). The
APPLID is limited to 8 characters.
|
Note:
|
Users must set either -s or -a to configure at least one ARTCNX for each CICS region to associate the initialization parameters which are defined in system.desc; otherwise, if users set -s together with -a, warning messages will occur in ULOG, only -s will take effect, and -a will be ignored.
|
|
Note:
|
For both -l and -L options, if there are multiple ARTCNX in one ART CICS region and -s is configured in such region, please set the same value for all -l specified in this region, and set the same value for all -L specified in this region. For more information about -L configurations, please refer to List of Groups Configuration File.
|
ART_LOGON sends the "ART runtime welcome" panel and asks for
APPLID input.
gensess generates a globally unique session ID (unique in all CICS regions) with 16 characters for each terminal.
delsess removes the session ID when the corresponding terminal disconnects.
|
•
|
ARTLOGN must be unique in a CICS Runtime system.
|
|
•
|
ARTLOGN should be only configured when ISC_ENABLE=YES is specified; otherwise, the server will not boot.
|
The generic parameter CONV is mandatory for this server type, and must be defined as
CONV=Y, because
ARTLOGN is conversational.
ARTADM — Administration Server
DFLTUSER is passed to application server
ARTATRN though transaction request so that
ASSIGN USERID can get the expected userid. If
-u option is not specified, CICS default userid
CICSUSER takes effect.
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.
ARTSRM — CICS System and Resource Management Server.
ARTSRM centralizes the management of ART runtime information, which is generated and queried by applications. This server can be used for interval control for delaying the start of a transaction instead of using /Q. This server can also be used to release the runtime resources (such as file resources and ENQ resources) when some ART for CICS application server die abnormally.
ARTSRM does not support "Multiple Servers, Single Queue (MSSQ)" configuration.
System and Resource Management Server (ARTSRM) has three versions:
ARTSRM,
ARTSRM_ORA (for Oracle), and
ARTSRM_UDB (for UDB).
ARTSRM uses shared memory.
ARTSRM_ORA (for Oracle) and
ARTSRM_UDB (for UDB) use shared memory or database to store data; when configured to use database, the server utilizes DB to provide HA capability.
When your ARTSRM server uses shared memory and you do not specify
SRM_IPCKEY,
ARTSRM for the same region must be configured in the same Tuxedo group.
To use ARTSRM_ORA or
ARTSRM_UDB, database tables must be created before startup. The sample script to create these tables is named as
crsrmtable_{Oracle|UDB} and is placed at
$KIXDIR/tools. The Tuxedo group where
ARTSRM_ORA or
ARTSRM_UDB resides must configure
OPENINFO;
ARTSRM_ORA or
ARTSRM_UDB of the same region must use the same database.
When using ARTSRM_UDB, do the following steps to rebind.
When some servers die, ARTSRM releases the dead server acquired file resource and the dead server acquired ENQ resource.
ARTCSKL — ART for CICS TCP/IP Socket Listener.
ARTCSKL is the listener of ART for CICS TCP/IP socket and can perform the same functions as CICS TCP/IP listener CSKL. When client request comes, it passes the request to work task for processing, and then waits for another client request.
ARTCSKL can run in standard or enhanced mode; you can set the mode through
FORMAT parameter of ART for CICS TCP/IP socket listener configuration file (
listener.desc).
|
•
|
ARTCSKL is the only supported socket listener; user-written listener is not supported.
|
|
•
|
ARTCSKL and ARTATRN/ARTATR1 servers should be configured on the same machine.
|
Specifies the PORT that
ARTCSKL listens to. If this option is set, the
-g option will be ignored and all of other
ARTCSKL parameters use default values. This option can only work for IPv4 users.
