•
|
The EXCI CALL interface, which consists of six commands that allow you to:
|
•
|
The EXCI EXEC CICS interface, which provides a single composite command that performs all six commands of the EXCI CALL interface in one invocation.
|
Each EXCI ART CICS program must be defined as a DPL service in the
resource/program.desc file. The seventh column must contain the
CICS SYSID, and the service is advertised with the name:
<SYSID>_<PROGRAM>.
If all DPL requests are done with SYNCONRETURN and not under the RRMS control, no Resource Manager is required in the Tuxedo Client. The initialization is done during the first EXCI request process and the Tuxedo session is terminated at the end of the client process.
If RRMS is used or one DPL request is done without SYNCONRETURN, the Tuxedo Client process must be built with one Resource Manager. At the initialization, the Resource Manager is opened and the transaction is begun at the beginning of the Client process. If one of these steps is not successful, the Client process aborts. At the normal end of the client process, the transaction is committed if it was not explicitly done by the client program (
RSSCMIT). At the abnormal end of the client process, the transaction is rolled back. In each of these cases the Resource Manager is closed and the Tuxedo session is terminated.
The COBOL precompiler supports EXCI CALL or only one CICS command,
EXEC CICS LINK with the next described options. The C precompiler only supports
EXCI EXEC CICS LINK.
ART CICS supports DFHXCIS API for making EXCI requests (
DFHXCIS is a procedure API that client programs make
EXCI CALL).
In case of EXEC CICS LINK, the
RETCODE command option is mandatory with
EXCI but forbidden with
NOEXCI, and the
APPLID option is
EXCI specific. Without
EXCI the
SYSID option can be used.
before IDENTIFICATION DIVISION line.
•
|
PROGRAM() and RETCODE() are required for the LINK command in EXCI.
|
•
|
SYSID is not recognized in EXCI.
|
•
|
COMMAREA must be present if LENTGH or DATALENGTH is present.
|
The MT_EXCIAPPPROFILE environment variable provides the application profile file name generated by the genappprofile
ARTKIX tool. The default file name is
$HOME/.tuxAppProfile.
The value of $USER environment variable when there is no security level set inside the Tuxedo ubbconfig The value of
USERID input in genappprofile tool when enabling security level inside the Tuxedo ubbconfig, the value of
USERID is got from .tuxAppProfile and passed by DPL request.
The value of $USERNAME environment variable no matter whether there is any security level set inside the Tuxedo ubbconfig or not.
The EXCI interface uses the <applid> CICS application ID to address the appropriate CICS region. The relationship between
<applid> and
<sysid> is made via a specific DPL server service named
<applid>_info.
The -a user parameter value of the DPL server command line (CLOPT) is used as
<applid> value for the
_info service.
If the <applid> is omitted by the client (without
APPLID(<applid>)
EXCI EXEC interface option), the
default_info service is called. This service is advertised by the first DPL booted server.
The _info service returns the
<sysid> associated to the server by the
-s user parameter of the server command line.
•
|
<applid>_CSMI, where <applid> is the CICS application ID to address the appropriate CICS region. This service is called if <transid> is not specified but <applid> is specified in EXCI interface by the client.
|
•
|
CSMI. This service is called if both <applid> and <transid> are not specified in EXCI interface by the client.
|
•
|
<applid>_MIRROR_<transid>, where <applid> is the CICS application ID to address the appropriate CICS region, and <transid> is the transaction ID. This service is called if both <applid> and <transid> are specified in EXCI interface by the client.
|
•
|
MIRROR_<transid>, where <transid> is the transaction ID. This service is called if <applid> is not specified but <transid> is specified in EXCI interface by the client.
|
•
|
The TRANSID has no meaning. There is no control on it. It is only passed to the DPL service in the EIBTRNID field in DFHEIBLK structure.
|
•
|
The COMMAREA length is limited to 32763 bytes.
|
•
|
Only VERSION-1 is supported.
|
•
|
The initial user USER-NAME is only used to generate a user-token without any control.
|
•
|
The DPL UOWID is kept for compatibility only, and is not set and tested.
|
•
|
The PIPE-TYPE has no meaning. The recognized values for PIPE-TYPE are only X'00' and (X'C3' or X'D8) ( X'C3' and X'D8' are the possible ASCII values for X'80' EBCDIC depending code-page). On other value the response code is set to 12 and the reason code to 498.
|
•
|
The recognized values for SYNC-TYPE are only X'00' and (X'C3' or X'D8') ( X'C3' and X'D8' are the possible ASCII values for X'80' EBCDIC depending code-page). On other value the response code is set to 12 and the reason code to 499.
|
The DFHXCRM replaceable-module is not treated.
The SRRCMIT and
SRRBACK functions are available.
ATRCMIT and
ATRBACK functions are not supported.
SRRCMI and
SRRBACK fuctions must be coded as:
To use EXCI EXEC CICS Link command, the
system.desc,
transactions.desc, and
program.desc configuration files should be configured.