Since the transaction does not originate from a terminal directly connected to the CICS region (ie. a non-terminal task) monitoring must be set up to route the debugging session to a designated terminal. Since the "twin" task originates outside of CICS, InterTest is unaware that this is a new task and will monitor this new task as well.
To confirm that this is the case, press PF12 to display the MONITORING STATUS screen. If the screen shows both the "Waiting at breakpoint" and "Currently monitoring" entries, then the terminal is handling several debugging sessions. The currently attached session is listed under "Waiting at breakpoint" and the other debugging session(s) are likely waiting to get attached and are listed as "Currently monitoring". The tasks can switch back and forth with each step (PF10) depending upon CICS and its dispatching logic.
There are two simple solutions:
- Prevent the transaction from starting while a programmer is debugging the related program;
-- One of many possible causes could be load balancing of proxy servers that route the web requests to the CICS region.
-- Try removing the load balancing
- Alternatively, remove the initial breakpoint the moment it gets hit, and then continue single stepping through the program as before.
-- Removing the initial breakpoint will allow InterTest to single step through one unique task.