Analyze WebSphere Application Server Transactions

From the Interactive Analysis menu, select Option 13.

CA MAT --------------------- Interactive Analysis --------------------------- OPTION ===> Enter option to analyze the monitored job: Profile: BIGBATCH Options: NORMAL CA MAT Monitor Information Subsystem Details ------------------------------------------- ------------------------------ 0 OverView - Monitor session information 10 DB2 - View all SQL 1 TaskView - Activity by task 11 IMS - IMS Transactions 2 DelayView - Program delays 12 JVM - Java Virtual Machine 3 CodeView - Program activity 13 WAS - WebSphere Trans. 4 TimeView - Samples by time 14 CIC - CICS Summary Stats 5 DataView - Dataset information 15 IDMS - CA IDMS Activity 6 TranView - Activity by transaction 7 ModView - Module layout 8 PoolView - Buffer pools 9 USSView - Unix System Services ACTIVE - switch context to ACTIVE WAIT - switch context to WAIT NORMAL - switch context to NORMAL ALL - switch context to ALL Press END to exit analysis

The WebSphere Transactions panel displays.

CA MAT ------------ WebSphere Transactions ----------------- Row 1 to 6 of 6 COMMAND ===> SCROLL ===> CSR Primary commands: MOde URL/Application/Via/Current, Profile: WAS7 GARbage, WAS (Environment info), SQL Mode: URL Line commands: A - Application Classes S - SQL V - Via Classes D - Delays C - Current Classes N - URL Name LC Transaction URL Active% InvWait% VolWait% Total% Visual ________________________________ _______ ________ ________ ______ _________ >----------------------------------------------------------------------------- __ common/GoWait 53.82 0.00 0.00 53.82 ========> __ common/GoDB2MF 28.45 0.00 0.00 28.45 ====> __ common/GoReflect 13.49 0.00 0.00 13.49 => __ /burn/go 4.13 0.00 0.00 4.13 __ common/GoGobble 0.10 0.00 0.00 0.10 __ common/GoCache 0.02 0.00 0.00 0.02 ****************************** End of Table *******************************

The WebSphere Transactions panel presents activity and perfomance information for the transaction URLs that are monitored by CA Mainframe Application Tuner.

The fields in this panel are desceibed next.

Transaction URL: Name of the sampled transaction URL.
Active%: Percentage of all WebSphere transactions measured where CA Mainframe Application Tuner detected program code to be executing.
InvWait%: Percentage of all WebSphere transactions measured where CA Mainframe Application Tuner detected program code to be in an involuntary wait.
VolWait%: Percentage of all WebSphere transactions measured where CA Mainframe Application Tuner detected program code to be in a voluntary wait.
Total%: Sum of active, voluntary, and involuntary waits.
Visual: Visual representation of the Total% value.
Total Count: Total number of URL instances detected.
Avg Resp: Average response time for the transaction in milliseconds.
Max Resp: Maximum response time for the transaction in milliseconds.
Min Resp: Minimum response time for the transaction in milliseconds.

When no URL filters are specified in the WebSphere monitoring criteria panel (see "Monitoring Criteria for WebSphere Application Server"), CA Mainframe Application Tuner does not collect Class data (Application, Via, or Current) or activity statistics. Only WebSphere transactions, garbage collection, environment, and SQL data is collected. In this case, a list of transactions displays, which you can use to define URL filters for subsequent monitors.

CA MAT ------------ WebSphere Transactions ----------------- Row 1 to 7 of 7 COMMAND ===> SCROLL ===> CSR Primary commands: GARbage, WAS (Environment info), SQL Profile: WAS4 Mode: URL Line commands: N - URL Name Total Avg Max Min LC Transaction URL Count Resp Resp Resp ________________________________ ______ ________ ________ ________ ------------------------------------------------------------------------------ __ /burn/goReflect 1 13293.00 13293.00 13293.00 __ /burn/goDB2MF 1 10073.00 10073.00 10073.00 __ /burn/go 1 2808.00 2808.00 2808.00 __ /burn/gogobble 1 39.00 39.00 39.00 __ /burn/goCache 1 24.00 24.00 24.00 __ /burn/goVector 1 2.00 2.00 2.00 __ /burn/goWait 1 0.00 0.00 0.00 ********************************* End of Table ******************************* Transaction only mode

From the WebSphere Transactions panel, enter the MOde primary command on the COMMAND line and press Enter to see all classes of the selected type (Application/Via/Current). For example:

Type MO A to see all the Application classes.
Type MO V to see all the Via classes.
Type MO C to see all the Current classes.

The WebSphere Classes panel displays.

CA MAT ----------------- WebSphere Classes ----------------- Row 1 to 4 of 4 COMMAND ===> SCROLL ===> CSR Primary commands: MOde URL/Application/Via/Current Profile: WAS5 GARbage, WAS (Environment info), SQL Mode: Appl. Line commands: D - Delays NC - Class Name S - SQL NM - Method Name LC Class Name Method Name Line # Active% InvWait% ________________________ ________________________ ________ _______ ________ >----------------------------------------------------------------------------- __ common/IoPerform read Compiled 48.03 0.00 __ common/CpuPerform exercise Compiled 47.35 0.00 __ common/GoHeader processRequest 41 4.19 0.00 __ common/GoHeader processRequest 42 0.43 0.00 ******************************** End of Table ********************************

This panel shows a high-level display of classes for the selected mode.

From the WebSphere Transactions panel, use line commands A (Application Classes), V (Via Classes), or C (Current Classes) to see the classes that are associated with the selected transaction, as shown following.

CA MAT ----------------- WebSphere Classes ----------------- Row 1 to 2 of 2 COMMAND ===> SCROLL ===> CSR Primary commands: GARbage, WAS (Environment info) Profile: WAS5 Type: Appl. Line commands: D - Delays NC - Class Name S - SQL NM - Method Name Transaction: /burn/go LC Class Name Method Name Line # Active% InvWait% ________________________ ________________________ ________ _______ ________ >----------------------------------------------------------------------------- __ common/IoPerform read Compiled 48.03 0.00 __ common/CpuPerform exercise Compiled 47.35 0.00 ******************************** End of Table ********************************

The WebSphere Classes panel provides information about the classes and methods that are called by the WebSphere application.

You can also see the method name and line number for the selected transaction URL. Compiled in the Line # column indicates that the method was compiled dynamically and that there is no line number

From the WebSphere Transactions panel, use line command D (Delays) to see the delay category for the selected transaction, as shown following.

Possible delay categories are

IO delay
network delay
SQL delay
JMS delay

other delay

CA MAT  ------------------ WebSphere Delays ----------------- Row 1 to 1 of 1
COMMAND ===>                                                SCROLL ===> CSR

Primary commands: GARbage, WAS (Environment info)            Profile: WAS5
                                                                Type: URL
Transaction: /burn/go
 Class Name: *
Method Name: *
Line Number: *

Delay           Active% InvWait% VolWait% Total% Visual
_______________ _______ ________ ________ ______ __________
------------------------------------------------------------------------------

Other Delay      95.38    0.00     0.00    95.38 ========>
********************************* End of Table *******************************

The WebSphere Delays panel reports the delays that are attributed to the selected transaction or class.

From the WebSphere Transactions panel, use line command S (SQL) to see the SQL statement information for the selected transaction, as shown following.

CA MAT ---------- WebSphere SQL Statements ----------------- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> CSR Primary commands: GARbage, WAS (Environment info) Profile: WAS5 Type: URL Line commands: S - Display SQL Transaction: /burn/go Class Name: * Method Name: * Line Number: * Total Avg Resp Max Resp Min Resp LC SQL Statement Count Time (ms) Time (ms) Time (ms) ________________________________ _________ _________ _________ _________ ------------------------------------------------------------------------------ __ update COT_School set COT_School 0 0.00 0.00 0.00 __ select ordertype as ordertype, c 0 0.00 0.00 0.00 __ select count(*) as kount, state 0 0.00 0.00 0.00 ********************************* End of Table *******************************

The WebSphere SQL Statements panel reports the SQL statement information that is associated with the selected transaction or class.

If a statement has been truncated on this panel, you can use line command S again to see the full text of the selected SQL statement.

Or, you can use the SQL primary command to see all detected SQL statements in the following step.

From the WebSphere Transactions panel, enter the SQL primary command on the COMMAND line and press Enter to see all detected SQL statements, as shown following.

CA MAT ---------- WebSphere SQL Statements --------------- Row 1 to 6 of 102 COMMAND ===> SCROLL ===> CSR Primary commands: GARbage, WAS (Environment info) Profile: WAS7 Type: ALL Line commands: S - Display SQL T - Transactions Transaction: * Class Name: * Method Name: * Line Number: * Total Avg Resp Max Resp Min Resp LC SQL Statement Count Time (ms) Time (ms) Time (ms) ________________________________ _________ _________ _________ _________ ------------------------------------------------------------------------------ __ select count(TEXT8), 50 112.00 219.00 77.00 __ insert into btsrfr.TR 2 96.00 174.00 18.00 __ update btsrfr.TRI85TB 1 68.00 68.00 68.00 __ update btsrfr.TRI85TB 1 62.00 62.00 62.00 __ update btsrfr.TRI85TB 1 62.00 62.00 62.00 __ update btsrfr.TRI85TB 1 61.00 61.00 61.00

From the WebSphere SQL Statements panel, use line command T (Transactions) to see the transactions that are associated with the selected SQL statement, as shown following.

CA MAT ----------- WebSphere Transaction Detail ----------------- Row 1 to 1 COMMAND ===> SCROLL ===> PAGE Primary commands: GARbage, WAS (Environment info), STMT Profile: WASAZB1 Type: ALL Line commands: A - Application Classes V - Via Classes C - Current Classes N - URL Name SQL Stmt: select count(TEXT8), TEXT8 from btsrfr.TRI85TB group by TEXT8 order LC Transaction URL Active% InvWait% VolWait% Total% Visual ________________________________ _______ ________ ________ ______ _________ >----------------------------------------------------------------------------- __ /burn/goDB2MF 7.16 0.00 0.00 7.16 ========> ******************************** End of Table ********************************

If the SQL statement text is truncated on this panel, you can use the STMT command to see the full text of the SQL statement.

From the WebSphere Transaction Detail panel, you can again use line commands A (Application Classes), V (Via Classes), or C (Current Classes) to see the classes that are associated with the selected transaction, as shown following.

From any of the WebSphere panels, enter the WAS (Environment info) primary command on the COMMAND line and press Enter to see information about the WebSphere environment, as shown following.

CA MAT ---------------- WebSphere Environment -------------- Row 1 to 9 of 9 COMMAND ===> SCROLL ===> CSR Primary commands: GARbage Profile: WAS7 WebSphere Environment ------------------------------------------------------------------------------ Process ID: 50332345 JVM: IBM Corporation 1.4.2 Application Server: WebSphere - z/OS 5.1 Initial Heap Size: 268.6 (MBytes) Maximum Heap Size: 268.4 (MBytes)

From any of the WebSphere panels, enter the GARbage primary command on the COMMAND line and press Enter to see information about the WebSphere garbage collection information, as shown following.

CA MAT  --------- WebSphere Garbage Collection ------------ Row 1 to 17 of 25
COMMAND ===>                                                  SCROLL ===> CSR

Primary commands: WAS (Environment info)                    Profile: WAS7

Garbage Collection
------------------------------------------------------------------------------

# of Events   Initial: 8         Final: 11
            Monitored: 3          Rate: 0.034    (events/sec)

Initial Heap Size: 269.0     (MBytes)
  Final Heap Size: 269.1     (MBytes)
   Occupancy Rate: 0.02      (% of time GC was running during monitor)

------------------------------------------------------------------------------

Memory Usage   (percentage of heap during monitor session)
------------------------------------------------------------------------------

Min =    8.3% (    22.3MB)   Max =   72.8% (   195.8MB)
------------------------------------------------------------------------------

% Heap ---------1---------2---------3---------4---------5
  90
  80

The WebSphere Garbage Collection panel provides information about WebSphere memory usage during the monitoring session.