Performing a search

This topic presents an example of the search process, from deciding which search dialog to use through defining the search criteria and reviewing the results.

In this example, you know there were problems with CSMI transactions trying to connect to a Db2 database some time after 2:00 P.M. on February 8.

To perform a search

1. From the EZTA easy menu, select All Components.
   All Components is the best choice because you want to see more than one component type (CICS, CTG and Db2) in a single view.
2. Set the time range by using
   • Duration field to specify 00:30 (half an hour)
   • Earliest ending time and date fields to specify 2:00 P.M. (14:00) on February 8 (2009/02/08).
3. Limit the search to CICS, CTG and Db2 components by specifying Y in the Exclude subsystems field for IMS.
4. Limit the number of records to be searched by specifying 999 in the Maximum to search field.
5. Limit the search to components that abended or exceeded a threshold in a policy definition by specifying Y in the Exceptions only field.
6. Specify the following product criteria:
   • Limit the CICS and CTG transactions to CSMI because those were the transactions that were experiencing a problem.

   • Limit the Db2 connection type to CICS because you know they were CICS calls.

                                     Component Search
     COMMAND ===>                                                   SCROLL ===> CSR
                                                                             MORE: +
     Set duration OR times:
     Duration               00:30:00         UTC/GMT
     Earliest ending time   14:00:00         and date  2009/02/08
     Latest ending time and date
                            hh:mm:ss.tt                yyyy/mm/dd
     
     Exclude subsystems:    CICS             CTG       DB2
                            IMS  Y
     Set general criteria:
     Maximum to search      999
     Exceptions only        Y                Orig UOW               (Y/N/blank)
     MQ correlation level   1                Scope                  (Local/All)
     CPU seconds between                     and
     Elapsed time between                    and
                            hh:mm:ss.tt                hh:mm:ss.tt
     Set product criteria:
     Fold to uppercase      Y
     CICS transaction *     CSMI             Task no
     CICS user ID                            Term ID *
     CICS region
     CTG application ID                      Txn type
     CTG transaction *      CSMI             Program
     CTG server                              User ID *
     DB2 authorized user                     Wks name*
     DB2 connection name                     Wks user*
     DB2 connection type    CICS
     DB2 subsystem ID                        Plan
     IMS transaction code                    PSB name
     IMS user ID                             Region 

7. Press the End key or click OK to process the search request.
   The COMP view is displayed:

   ddmmmyyyy hh:mm:ss ------ MAINVIEW WINDOW INTERFACE (Vv.r.mm) ----------------
   COMMAND ===>                                                  SCROLL ===> PAGE
   CURR WIN ===> 1       ALT WIN ===>
   +W1 =COMP==============MTH1=====*========ddmmmyyyy==hh:mm:ss====MVTA=====D====5
   C   Local        Local      Elapsed   Tran
   - Start Time   Stop Time     Time     Env  Identification ------- Target   Tran
    14:17:14.54  14:37:14.66 00:00:00.12 CTG  MTACTG71 MTACSME2 EXM  MTACTG71 CSMI
    14:17:14.54  14:37:14.65 00:00:00.11 DB2  MTACOM1N MTACSME2 DHO1 DHO1
    14:17:14.54  14:37:14.66 00:00:00.12 CICS MTACEME2 CSMI          MTACEME2 CSMI
    14:25:35.35  14:25:35.42 00:00:00.07 DB2  MTACOM1N MTACSME2 DHO1 DHO1
    14:25:35.35  14:25:35.43 00:00:00.08 CICS MTACEME2 CSMI          MTACEME2 CSMI
   

   Scroll right to see if any of these components was identified as abending or exceeding a threshold in a policy definition. The following image shows the right-hand portion of the COMP view. In this case, none of the components abended or used excessive CPU, but all of them exceeded the elapsed time threshold that was specified in a policy definition.
   

   ddmmmyyyy hh:mm:ss ------ MAINVIEW WINDOW INTERFACE (Vv.r.mm) ----------------
   COMMAND ===>                                                  SCROLL ===> PAGE
   CURR WIN ===> 1       ALT WIN ===>
   +W1 =COMP==============MTH1=====*========ddmmmyyyy==hh:mm:ss====MVTA=====D====5
   C   Local                                   Comp           CPU  Elap
   - Start Time  Trancode User ID  CPU seconds Code  Program  Exc  Exc  Appl ID
    14:17:14.54  CSMI     BMCALV1      0.00000       MTACOM1N      Y    MTACTG71
    14:17:14.54           MTASTC       0.01051 0C                  Y    DHO1
    14:17:14.54  CSMI     MTASTC       0.02765       EC02          Y    MTACSME2
    14:25:35.35           MTASTC       0.00568 0C                  Y    DHO1
    14:25:35.35  CSMI     MTASTC       0.02195       EC02          Y    MTACSME2 

The next logical step would be to correlate one or more of the problem components. A correlation view would identify all the components that are part of the same complex transaction, and illustrate the flow through CICS, CTG and Db2. For information about correlating components, see Correlating components.

For information about policy definitions, see Defining component policies.