If the new CICS program entry is found, CA InterTest for CICS also tries to find the InterTest Monitoring Table entry that belongs to the program that got control directly. This lets the new CICS program assume all options, such as breakpoints, that were declared for the program that is about to receive control.
If found, the new InterTest Monitoring Table entry is assumed to be together with all the options associated with this entry. However, CA InterTest for CICS carries the FOL= option over such a Monitoring Table switch so that the FOL= option remains active for the remainder of the monitoring effort, even though the Monitoring Table entry that is now in control might not have a FOL= option declared. This means that any options, such as breakpoints, that you want to see applied to the program that is receiving control can be declared for the Monitoring Table entry associated with the program.
Moreover, you can declare these options in the most convenient way; for example, breakpoints can be declared by displacements, and the UBP= and BYP= options can be declared for displacements and for addresses. The addresses ensure that if CA InterTest for CICS cannot find the CICS program and InterTest Monitoring Table entries, it continues monitoring under the Monitoring Table entry of the program that passed control.
Important! CA InterTest for CICS disregards the Exclusion Table during the search for the new Monitoring Table entry because monitoring cannot be interrupted at the place of the wild branch. Before CA InterTest for CICS can interrupt monitoring, it has to know where control is returned so that later it can resume monitoring. However, the location to which control is returned depends on the design of the monitored program, and CA InterTest for CICS cannot predict that. This is why monitoring cannot be interrupted on a wild branch.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|