WebSphere® Application Server for z/OS® uses Workload Manager (WLM) services to report transaction begin-to-end response times and execution delay times.
For details on workload management, see z/OS MVS™ Planning: Workload Management. For details on WLM delay monitoring, refer to z/OS MVS Programming: Workload Management Services. Both are available on the z/OS Internet Library Web site.
When a new transaction enters the system, the WebSphere Application Server for z/OS application control region (ACR) starts the classify service. Delays associated with the WebSphere Application Server for z/OS ACR service class are counted separately for the BTE phase and the EXE phase. This support allows WLM to associate a performance block (PB) with an enclave to record delays that occur in the flow of a transaction. The state samples are collected on an ongoing basis and reported as a percentage of average transaction response time. The following table shows the states, their codes, the section of the RMF report where each is reported, the meaning, and suggested response.
State | Code | Report | Meaning | Response |
ACTIVE | ACTIVE SUB | Both BTE and EXE | WebSphere is actively processing request | |
ACTIVE_APPLIC | ACTIVE APPL | Both BTE and EXE | Application is running | Use application monitoring tool to determine the cause of the delay. |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
|
![]() ![]() |
![]() ![]() |
![]() ![]() |
||
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
|
WAITING TYPE 4 | TYP4 | BTE | OTS call to RRS. Occurs only in controller when controller is trying to commit a distributed transaction. |
|
![]() ![]() |
![]() ![]() |
![]() ![]() |
||
![]() ![]() |
![]() ![]() |
![]() ![]() |
||
WAITING DISTRIB | DIST | BTE | Controller as a client went outbound waiting for a response. |
|
![]() ![]() |
![]() ![]() |
![]() ![]() |
||
![]() ![]() |
![]() ![]() |
![]() ![]() |
||
WAITING REGULAR_THREAD | REGT | BTE | Waiting for a thread in the controller. Work is bottle-necked in the controller because it is receiving more requests than it can process. | Split the controller. |
WAITING SSL_THREAD | SSLT | BTE | Waiting for an SSL thread in the controller. Work is bottle-necked in the controller because it is receiving more requests for SSL handshakes than it can process. | Split controller
to increase SSL threads.
|
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
|
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]()
![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]()
![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
|
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]()
![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]()
![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
|
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
|
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
|
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |