Using AutoStrobe to Identify CICS Transactions for Monitoring

AutoStrobe provides the following two functions to help you to detect when CICS transactions are behaving abnormally:

  • Create Transaction Candidates
    The Create Transaction Candidates function builds a list of CICS transactions that are candidates for monitoring. You can use this list as input into the Monitor Transactions function.
  • Monitor Transactions
    The Monitor Transactions function monitors CICS transactions and triggers a measurement or warning whenever a transaction exceeds an average CPU or response time threshold.

You can use these functions together to tune your CICS transactions (see AutoStrobe Support for CICS Transaction Processing).

If you already know what transactions you want AutoStrobe to monitor for abnormal behavior, see Using AutoStrobe to Monitor CICS Transactions. Otherwise, you can use AutoStrobe to create a list of potential CICS transactions for monitoring. Read this section to learn how to create a list of CICS transaction candidates by submitting a Create Transaction Candidates request.

Both AutoStrobe and Strobe for CICS must be licensed for the processors on which AutoStrobe will be used for creating CICS transaction candidates lists for monitoring.

This section explains how to:

  • Build a list of transaction candidates by submitting a Create Transaction Candidates request
  • View the status of a Create Transaction Candidates request
  • Submit an Add Active measurement request from a transaction candidates list
  • Submit a transaction monitoring request from a transaction candidates list.

AutoStrobe can also create candidates for batch monitoring and can automatically monitor batch performance. See AutoStrobe Batch Candidate Lists and Monitoring and Managing AutoStrobe Batch Candidate Processing and Monitoring for more information.

This section contains the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*