Recording and virtualizing DPL calls in CICS® Transaction Server
You can record and virtualize CICS® Distributed Program Link (DPL) calls with CICS® Transaction Server versions 5.2, 5.3, 5.4, and 5.5. To do so, install and configure Rational® Integration Tester CICS® TS Agent in the CICS® regions that are making the DPL requests.
About this task
These are the system elements that are required to record and virtualize DPL calls:
For information about software requirements, see Testing applications on z/OS.-
Rational® Test Control
Panel, which coordinates
communications between
Rational® Integration
Tester, its
Agent, and the RITAGENT batch service. Each component must register with it.
- The RITAGENT batch service, which registers through the RTCPURL program parameter in the RITAGENT JCL.
- Rational® Integration Tester, which registers through the server settings user interface.
- Rational® Integration Tester, which registers its address through the CICS Stub Server Bind Address and CICS Stub Server Port settings of the Library manager.
-
Rational® Integration
Tester
CICS® TS Agent which must be installed and
configured on the same z/OS® computer as the CICS® region under test. The agent consists of two
parts:
- The CICS® exit, RITEXITC, which monitors CICS® DPL calls.
- The RITAGENT batch service, a job that is based on the RITAGENT template JCL. The
service sets up local internal communications to the CICS® exit through the BINDADDR and
PORT program parameters in the RITAGENT JCL. Note: If the RITAGENT batch service and RITEXITC are running on the same computer, set BINDADDR to 127.0.0.1.
Using channels and containers
In
Rational® Integration
Tester version 9.0.1, you can
transfer data between programs through channels and containers. You can record and stub DPL
requests by using channel and containers.
Important: When you name the channels
and containers, ensure that you do not use RITCHANNEL and
HRVUSEDCONTAINER.