Special considerations for CICS programs

When you record or stub CICS programs, you must review several special considerations that apply to CICS programs.

When you record or stub programs that run within CICS, you must consider the following points:

  • If CICS is restarted while a recording session is in progress, or while a CICS program is being stubbed, you must restart the recording session or the stub after CICS was restarted.
  • IBM z/OS Debugger uses profiles to select which programs Db2® calls to intercept. These profiles are used by the agent for z/OS and by developers who are using IBM z/OS Debugger to step through a program. The profiles are maintained by a transaction named DTCN, or in the case of the agent for z/OS, through the Profile Service. Within the profiles, you can specify multiple criteria such as: program name, user, transaction name, commarea contents, container name, container contents, client termID or client IP address, and others.
  • It is possible for Rational® Integration Tester users or IBM z/OS Debugger users to specify criteria that overlap. For example, a Rational® Integration Tester user might attempt to intercept Db2® calls for all programs invoked because of running transaction AAAA, while another Rational® Integration Tester user or IBM z/OS Debugger user attempts to intercept all programs invoked by user JDOE. In this case, if transaction AAAA is invoked by user JDOE, the running program is matched by both profiles. When a running program matches multiple profiles, IBM z/OS Debugger sends the events to the user who owns the oldest profile. For this reason, when you create the Db2® z/OS agent filter within Rational® Integration Tester, it is best practice to define criteria that only matches your program and no others.