Review What Happened

In this part of the demo session:

When you executed PLIDEML, CA InterTest for CICS detected and prevented an abend caused by invalid data in one of its called subroutines.
CA InterTest for CICS displayed the automatic breakpoint at the statement which called the subroutine, rather than the statement that triggered the breakpoint, because CA InterTest for CICS was not monitoring the subroutine.
You set composite support for PLIDEML so that CA InterTest for CICS would monitor its subroutines: ASBIN25 and PSBIN25.
Setting composite support lets you test and debug a called subroutine with full symbolic support and take advantage of all CA InterTest for CICS features.
When you re-executed PLIDEML, CA InterTest for CICS redisplayed the automatic breakpoint, this time at the actual statement in subroutine ASBIN25 that caused the error.
You corrected the error by overtyping the contents of the invalid field.
You then set an unconditional breakpoint in the other subroutine, PSBIN25, and resumed program execution. When control passed to PSBIN25, CA InterTest for CICS halted execution at the breakpoint you set.
The ability to halt execution at any statement in a subroutine means you can test a subroutine just as if it were a main program.
You removed the unconditional breakpoint and continued program execution.