WebSphere Application Server for z/OS Version 5 uses Workload Manager (WLM) services to report transaction begin-to-end response times and execution delay times. The WLM data collected by Resource Measurement Facility (RMF) is captured in two phases of the RMF report:
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. You can use this information in the RMF report to determine where some of your system's performance problems may be occurring.
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 TYPE1 | TYP1 | EXE | EJB collaborator delay | |
WAITING TYPE2 | TYP2 | EXE | Resource manager delay | Called a J2C connector to perhaps DB2, CICS, IMS. Investigate other resource manager using their monitoring tools. |
WAITING TYPE3 | TYP3 | EXE | Servant called to a different distributed object server using RMI/IIOP |
|
WAITING TYPE 4 | TYP4 | BTE | OTS call to RRS. Occurs only in controller when controller is trying to commit a distributed transaction. |
|
WAITING REGIST TO WORKTABLE | WORK | BTE | An indication of contention within the controller while trying to process concurrent requests. | If delay is excessive, consider adding another controller and splitting work off to it. |
WAITING OTHER_PRODUCT | OTHER | BTE | Indicates a configuration problem in DNS or TCP/IP | Check to make sure all the DNS servers are running. You might want to look at OPING or ONSLOOKUP. |
WAITING DISTRIB | DIST | BTE | Controller as a client went outbound waiting for a response. |
|
WAITING SESS_NETWORK | REMT | BTE | Time spent waiting for a TCP/IP session to be established on the network. | The two session delays should be observable in conjunction with TYP3 delays. Look at TCP/IP configuration. |
WAITING SESS_SYSPLEX | SYSP | BTE | Time spent waiting for a TCP/IP session to be established on the sysplex. | The two session delays should be observable in conjunction with TYP3 delays. Look at TCP/IP configuration. |
WAITING REGULAR_THREAD | REGT | BTE | Waiting for a thread in the controller. Work is bottlenecked 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 bottlenecked in the controller because it is receiving more requests for SSL handshakes than it can process. | Split controller
in increase SSL threads.
|
WAITING SESS_LOCALMVS | LOCL | BTE | Time spent communicating with a different distributed object server using local optimized communication. |
|