Special Monitoring Situations › Special Monitoring Situations › Production Environment Monitoring › Monitor the Entire Production System

Monitor the Entire Production System

You usually want to avoid monitoring the entire production system because of the high overhead involved. But what if your production system has a serious error and you cannot isolate the problem program? In that case, instruct CA InterTest for CICS to monitor all the programs in the production system for every user or for a specific user only.

If your system is experiencing sporadic problems that are difficult to isolate, you might want to monitor all programs executed by the user experiencing the problems. In a secure CICS region, use the following global monitoring command with the user ID option for the user experiencing the problem:

CNTL=ON,PROG=.ALL,USR=cics‑userid

Note: Ensure each user signs on to CICS before executing programs.

While CA InterTest is monitoring all of the programs, use the Active Tasks display (Primary Menu Option 2.5 Monitoring Active Tasks) to check for problems. When CA InterTest for CICS finds that a program is about to commit an error, it halts the program at an automatic breakpoint and automatically creates a Monitoring Table entry for that program. The monitoring status report provides that information. As soon as you see that CA InterTest for CICS has identified the problem program, turn monitoring off for the system and monitor the problem program for a single user or at a single terminal until you resolve the error.

Alternatively, monitor a certain percentage of your programs until CA InterTest for CICS finds the problem program.

Example

You might monitor 10 percent of your programs one week, another 10 percent the next week, and a third 10 percent the following week.

This approach minimizes overhead, and takes advantage of the ability of CA InterTest for CICS to track down problems that are otherwise very difficult to resolve.