Managing Transaction Candidates requests

You can view and manage a Create Transaction Candidates request when AutoStrobe has completed one collection period (see the following figure).

To manage Create Transaction Candidates requests:

1. Select Option 4, MANAGE CANDIDATES, from the Strobe - AutoStrobe Options panel.
   The Strobe - AutoStrobe Process Candidates panel is displayed.
2. In the SWITCH TO AutoStrobe TRANSACTION OPTION field, type Y.

3. Press Enter.The Strobe - AutoStrobe Manage Transaction Candidates panel shown is displayed. It will appear by default whenever you select the Manage Candidates option, until you select the Batch Option on this panel.

   Strobe - AutoStrobe Manage Transaction Candidates panel

   

4. You manage requests using the following line commands:
   • Type V to view the information you supplied for the Create Transaction Candidates request.You might want to do so to verify that it contains the transactions, minimum thresholds, and collection periods you specified.
   • Type T to view the detail of the individual transactions in a completed Create Transaction Candidates request.Only completed transaction requests show suggested thresholds. See Viewing-the-List-of-Transaction-Candidates for more information.
   • Type D to delete a Create Transaction Candidates request.When you delete a Create Transaction Candidates request, you delete all the transaction candidates in the request, as well as their associated detail records. To be sure that you are not inadvertently deleting transaction candidates and thresholds you want to keep, view the entire request by typing V before deleting.

Fields for the Strobe - AutoStrobe Manage Transaction Candidates Panel

The following sections describe the fields displayed in the Strobe - AutoStrobe Manage Transaction Candidates panel.

Switch to AutoStrobe Batch Option

To display the AutoStrobe batch process candidates panel, type Y.

Status

The status of the Create Transaction Candidates request:

Status	Reason
PENDING	The relevant CICS region is not currently executing, but when it does run, AutoStrobe will monitor it to build a list of transaction candidates.
ACTIVE	The relevant CICS region is executing during a period for which data collection on transactions has been scheduled.
HELD	AutoStrobe has initiated or detected an event that causes it to suspend or prohibit data collection on transactions in the CICS region. The different HELD statuses include: HELD-AA: The Create Transaction Candidates request is held, because a user submitted an Add Active measurement for the CICS region. AutoStrobe retains the data for a collection period of a Create Transaction Candidates request only if it has collected data for the entire period. Therefore, if a measurement interrupts the data collection during a time period, AutoStrobe discards any data collected for that time period and extends the collection period by one day. HELD-IN: The Create Transaction Candidates request is held, until AutoStrobe finishes initializing the environment it needs to collect data about the transactions in the CICS region. HELD-SC: The Create Transaction Candidates request has a schedule that does not include the current day or time period. HELD-US: The user issued a hold against the Create Transaction Candidates request. AutoStrobe will hold it until the user releases it. HELD-AC: The security rules are enabled for the Strobe access filter. The owner of the Create Transaction Candidates request does not have the authority to access the CICS region.
COMPLTE	AutoStrobe built a list of transaction candidates for the Create Transaction Candidates request.

JOBNAME

The name of the CICS region for which AutoStrobe collected data on transactions.

STEPNAME

The stepname of the CICS region for which AutoStrobe collected data on transactions.

PROGRAM

The default IBM program name for CICS (DFHSIP) or the name in use at your site.

SYSTEM

The system ID on which AutoStrobe collected data on CICS transactions in multisystem environments.

DAYS LEFT

The number of days remaining in the candidacy period for the Create Transaction Candidates request.

QUALIFYING

The following fields describe the minimum thresholds specified on the Create Transaction Candidates request.

COUNT

The minimum number of times a transaction must run before it can qualify as a transaction candidate.

RESP

The minimum average response time in seconds that a transaction must meet before it can qualify as a transaction candidate.

CPU

The minimum average response time in seconds that a transaction must meet before it can qualify as a transaction candidate.