Three kinds of services published by ARTDPL can be accessed by Tuxedo clients. User can choose one of them depending on real scenario.

• Type A: <sysid>_<program>

  DPL <program> can be advertised by ARTDPL as a Tuxedo service. And the prefix of service name is the CICS region <sysid>_ which current ARTDPL server belongs to. If client tries to call this service and exchange the COMMAREA with ARTDPL server, the following FML32 fields must be present in the request:

  CX_USERID 

  CXMW_MESSAGE 

  Meanwhile, the FML32 filed CX_PROGRAM must not be present, because ARTDPL server can realize the name of DPL program to be executed from the service name.

  You can enable the mirror transaction and TWA. Please refer to next section for the details.
• Type B: MIRROR_<transid>
• Type C: <applid>_MIRROR_<transid>

  Mirror transaction can also be advertised by as a Tuxedo service. And the prefix of service name is the MIRROR_ or <applid>_MIRROR_. In this case, mirror transaction and TWA is always enabled. User needs configure the mirror transactions and their TWA size in the transactions.desc at first. If client tries to call these two services and exchange the COMMAREA with ARTDPL server, the following FML32 fields MUST be present in the request:

• CX_USERID
• CXMW_MESSAGE
• CX_PROGRAM

  To use RECORD as the data buffer to call ARTDPL server, you should configure IN-TYPE and OUT-TYPE for the called program in programs.desc. When you use RECORD, Tuxedo clients can only use Type A services.