Collecting data by using ISPF

This section explains how to use the Collect Report Data (CRD) function of Buffer Pool Analyzer, respectively the equivalent function of DB2® Performance Expert.

About this task

To collect data by using ISPF, perform the following steps:


  1. Start ISPF from your TSO/E session.
  2. Start the FPEJINIT exec.

    The exec automatically determines whether Db2 Performance Expert or the Buffer Pool Analyzer stand-alone product is installed on your system. If Db2 Performance Expert is installed on your system, the exec starts Db2 Performance Expert and you need to perform steps 3 to 4 to reach the Collect Report Data function. Otherwise, the exec directly starts the Collect Report Data function. If you see the Collect Report Data panel (shown in step 4), continue with step 5.

    IBM® OMEGAMON for Db2 Performance Expert panel is displayed:
                     IBM OMEGAMON for DB2 Performance Expert
     Command ===>  ________________________________________________________________
     Select one of the following.
     __ 1. Create and execute reporting commands
        2. View online DB2 activity - Classic Interface
        3. Trace collection, Explain, and Admin functions
        4. Maintain parameter data sets
        5. Customize report and trace layouts
        6. Exception profiling
     F1=Help    F2=Split    F3=Exit    F9=Swap    F12=Cancel
  3. Select the following options to specify the Db2 subsystem from which you want to collect data, as follows:
    1. Select option 3 (Trace collection, Explain, and Admin functions). The Online Monitor Main Menu panel is displayed.
    2. Select option 1 (Options). The Options panel is displayed.
    3. Select option 1 (Db2 Subsystem). The Db2 Subsystem subpanel is displayed.
    4. Specify the Db2 subsystem and return to the Online Monitor Main Menu panel:
                             Online Monitor Main Menu                         
       Command ===>  ________________________________________________________________
       Select one of the following.
       __  1. Options
           2. Control Exception Processing
           3a. Collect Report Data - General
           3b. Collect Report Data - For Buffer Pool Analysis
           4. Explain
       F1=Help    F2=Split    F3=Exit    F9=Swap    F12=Cancel    F16=Look
  4. On the Online Monitor Main Menu panel select option 3b, Collect Report Data - For Buffer Pool Analysis.
    The Collect Report Data for Buffer Pool Analysis panel is displayed:
     06/23/13 10:16    Collect Report Data - For Buffer Pool Analysis
     Command ===>  ________________________________________________________________
    PM01DC11              DC11
     Select one of the following.
     __ 1. Configure task
        2. Activate task
        3. Display task status
        4. Stop task
        Task Description                            Status
        collect_data_for_buffer_pool_activity___    Data available
     F1=Help    F2=Split    F3=Exit    F9=Swap    F12=Cancel    F16=Look

    Above the options menu, you see the name of the Db2 subsystem that you specified in step 3d.

    You use this panel to configure and control a collect task. You can work with one task at the same time. If you leave Buffer Pool Analyzer (the stand-alone product) or Db2 Performance Expert before a task has finished, the task is stopped (no configuration settings are saved, no data is available). A task has finished when it is configured, activated, and all data has been collected.

  5. Select one of the following options:
    • Configure task

      This step is mandatory and must be performed before you can use any other options. See Configuring a collect task, which describes how to specify details of the collect task.

    • Activate task

      Use this option to activate the collect task that you have configured.

    • Display task status

      Use this option if you want to see status details of an activated collect task. These details are described in Interpreting trace status summary and trace messages.

      The overall status of a collect task is shown in the Status field. Depending on how a collect task was configured, one of the following status descriptors is shown:
      • Not yet activated: A collect task was configured but not yet activated.
      • Activate issued: A configured task was activated and started.
      • Waiting for start: A scheduled task was configured and activated, but the start time is not yet reached.
      • Collecting data: A task is active and is collecting data.
      • Waiting for next interval: A task was configured to collect data in intervals. The task is active, but waiting for the next interval to take place.
      • Data available: An activated task has stopped and written its data to the output data set.
      • Stopped: An activated task has finished, either because it was stopped by you or because a configured stop condition was reached.
    • Stop task

      Use this option to stop an activated collect task. If a Db2 trace is currently collecting data, this option also stops the Db2 trace.

  6. In the Task description field, type a description for the collect task.