Viewing the Status of a Transaction Monitoring Request

You can view the status of a transaction monitoring request using the Strobe - AutoStrobe Transaction Request Status panel. From this panel, you can find the following information about a transaction monitoring request:

CPU and response time thresholds that you specified
CPU and response time thresholds AutoStrobe observed
The transaction ID that triggered either a measurement or a warning when it exceeded a threshold
How often a transaction ran
Status of the request

A transaction monitoring request can have the following statuses.

Status	Reason
PENDING	The CICS region is not currently executing. When it does run, AutoStrobe will monitor for those specified transactions that exceed a threshold.
MONITOR	Transaction monitoring is currently taking place in the target CICS region.
HELD	AutoStrobe has initiated or detected an event that caused it to suspend or to prohibit monitoring of the CICS region. The HELD statuses include: HELD-AA: The transaction monitoring request is held, because a user submitted an Add Active measurement in the CICS region. After the measurement completes, AutoStrobe resumes monitoring the transactions. HELD-IN: The transaction monitoring request is held, until AutoStrobe finishes initializing the environment it needs for monitoring transactions in the CICS region. HELD-WN: A transaction exceeded a threshold and its monitoring request’s AUTOACTION parameter was set to WARNING. AutoStrobe holds the transaction monitoring request until the user releases it. HELD-MS: A transaction exceeded a threshold and its monitoring request’s AUTOACTION parameter was set to MEASURE. AutoStrobe holds the transaction monitoring request until the user releases it. HELD-SC: The transaction monitoring request has a schedule that does not include the current day or time period. HELD-US: The user issued a hold against the transaction monitoring 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 transaction monitoring request does not have the authority to access the CICS region under which the transaction was running.
COMPLTE	A scheduled transaction monitoring request completed the last day in its monitoring schedule.

In addition, you can manage your transaction monitoring requests from this panel using line commands. See Managing-Transaction-Monitoring-Requests for more information.

To view the status of a transaction monitoring request:

Select Option 2, AUTOSTROBE REQUEST STATUS from the Strobe - AutoStrobe Options panel.The Strobe - AutoStrobe Request Status panel is displayed.
Type Y in the SWITCH TO AUTOSTROBE TRANSACTION OPTION field.
Press Enter.The Strobe - AutoStrobe Transaction Request Status panel is displayed. It will appear by default whenever you select the AutoStrobe Request Status option, until you select the Batch Option on this panel.
Tip
To see the entire status panel, scroll to the right twice.

Strobe - AutoStrobe Transaction Request Status Panel

Scroll to the right once to display the next section of the transaction request status, as shown in the following figure.

Strobe - AutoStrobe Transaction Request Status Panel - Scroll Right Once

Scroll to the right again to display the third section of the transaction request status, as shown in the following figure:

Strobe - AutoStrobe Transaction Request Status Panel - Scroll Right Twice

Fields for the Strobe - AutoStrobe Transaction Request Status Panel

The following sections describe the fields in the Strobe - AutoStrobe Transaction Request Status panels.

SWITCH TO AUTOSTROBE BATCH OPTION

To display the AutoStrobe add monitoring request panel for batch programs, type Y.

Status

The status of the monitoring request. See Viewing the Status of a Transaction Monitoring Request for an explanation of the different statuses.

Jobname

The name of the CICS region that was monitored.

Program

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

Step name

The step name of the CICS region that was monitored.

System

The system ID on which transaction monitoring took place. This field is displayed only in a multisystem environment. Valid values can be a specific system ID or *ALL to view monitoring requests on all MVS images. Default is the current system.

Measurement

The date, time, and the transaction ID columns for the transaction whose abnormal behavior triggered a measurement. The transaction ID appears under the Cause label.

Threshold Information

The following fields describe the threshold values that triggered a measurement during a transaction monitoring period.

Type

The type of threshold that the transaction exceeded to trigger a measurement. The values can be CPU time or response (RESP) time.

Specified

The original CPU and response (RESP) time thresholds on the transaction monitoring request. When either of these thresholds is exceeded, AutoStrobe triggers a measurement.

Observed

The average CPU or response time threshold that AutoStrobe observed that triggered a measurement.

Tran Count

The number of times the triggering transaction ran during the monitoring period.

Ownerid

The owner of the transaction monitoring request.

Viewing Transaction Status Using the Strobe - Status Panel

You can also use the Strobe - Status panel to find the measurement status of your transaction monitoring request. If a transaction triggered a measurement you will see TRAN-< transaction ID > listed under the AUTO REAS column. For example in the following figure, TRAN-DMCC indicates that transaction DMCC triggered a measurement for job WPACI620.

Strobe - Status Panel for Transaction Monitoring Requests