When you set monitoring for a:
Program—CA InterTest for CICS detects and prevents errors before they occur. That means monitored programs will not abend or commit storage violations. CA InterTest for CICS monitors the program from whatever terminal it executes, even if it executes as part of a non‑terminal owning task. Use the replacement, protection, or special options screen if you want to restrict monitoring to a specific terminal.
Transaction—CA InterTest for CICS monitors all of the transaction's programs.
Terminal—CA InterTest for CICS monitors every program that executes at that terminal.
Note: CA InterTest for CICS will not monitor programs that begin with the prefix DFH (IBM CICS programs) or IN25 (CA InterTest for CICS programs).
If you set monitoring for a transaction or terminal, and a program executing as part of that transaction or at that terminal is stopped at an automatic breakpoint, CA InterTest for CICS automatically creates an individual entry in the monitoring table for that program. This lets you set breakpoints and monitoring options specifically for that program. Similarly, if you specify .ALL in the Program Names field on the Function Selection Menu or if you specify a generic program name, CA InterTest for CICS creates an individual monitoring table entry for any program monitored under that entry when it stops at an automatic breakpoint.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|