Investigating CICSPlex SM Web User Interface problems
This section describes how to diagnose and solve problems with the Web User Interface.
Where are server and web browser messages written
During the operation of the Web User Interface, messages are written to the console, web browser and EYULOG.
- Server messages
-
The Web User Interface server messages are mainly written to the CICSPlex® SM EYULOG of the Web User Interface server (and not of the CMAS).
Some messages are also written to the console. The Web User Interface server messages are explained in the Web User Interface Message Help.
- Web browser messages
-
Three types of Web User Interface messages are written to the web browser.
- Client
These messages reflect status during the operation of the Web User Interface.
- Editor
These messages reflect status during the operation of the View Editor.
- HTTP
These messages reflect the HTTP response codes. Web User Interface HTTP messages can sometimes be hidden by substitute HTTP messages that are issued by the web browser.
You can obtain help for the client and editor messages by clicking the message number or by accessing the contents page of the Web User Interface Message Help. You can obtain help for HTTP messages by accessing the contents page of the Web User Interface Message Help.
- Client
How to view status information about the Web User Interface server
The COVC status panel returns status information about the Web User Interface server.
COVC CICSPlex SM Web User Interface Control EYUVCTS
Status Details
CMAS Sysid : QSTX
Server Sysid : QSGW
CICSPlex SM Release : ****
Secure Sockets : No
Port : 05126
Hostname : mvsxx.company.com
TCP/IP Service Name : EYUWUI
TCP/IP Service Status : Open TCP/IP Family : IPV4
TCP/IP Address : 127.10.10.12
Current Status : Ready Time : 20:40:36
Applid : IYCQSTGW Date : 02/27/20**
PF 1 Help 3 Exit 12 Return
How to obtain the internal data structures of the Web User Interface
The COVC transaction provides access to the Web User Interface runtime environment. You can use COVC to format and manipulate the internal data structures of the Web User Interface.
- STARt
This starts the Web User Interface server if not already started during PLTPI processing.
- STOp
This shuts down the Web User Interface server.
- TRace
This displays the COVC trace flags panel, as shown in Table 1, giving you the opportunity to set appropriate trace levels.
- Dump This displays the Web User Interface control blocks using the CODB memory display. You can display a control block directly by specifying the control block on the COVC DUMP command, for example
COVC DUMP ANCHOR
displays the global anchor block. The control blocks that you can display are listed in Table 1.Table 1. Dump control blocks Dump control blocks Meaning Anchor Global anchor block Gslrt Global task block Res NLS resource block Mos Managed object block Mos VOMO objectManaged object block for object objectMos VOMA objectattributeManaged object block for attribute attributeof objectobjectMos VOMX objectactionManaged object block for action actionof objectobjectMos VOMP objectactionparameterManaged object block for parameter parameterfor actionactionof objectobjectView View cache block Cwi Web interface block Tasks User tasks block EYU0V cccEntry point and module header for named method within EYU9VKEC load module. Attention: The CICSPlex SM COVC DUMP keyword should be used only at the request of IBM Support. You must take steps to ensure that this transaction is used only by authorized personnel because of the access to system control areas that it provides. Improper or unauthorized use of COVC DUMP may have serious consequences, including without limitation loss of data or system outage. Customers are solely responsible for such misuse.
Typical end-user problems
Here are some typical end-user problems that you might encounter with possible solutions.
| Problems | Possible solutions |
|---|---|
| User unable to sign on, even when specifying reconnect | Check HTTP cookie support is enabled in the user's web browser. |
| Apparently random characters displayed on web browser | Ensure correct code page translation table (DFHCNV) is in use. |
| Can't see graphical attribute presentations | Check that you are using a Java-enabled web browser and that it is enabled. |
| Message EYUVC1200E displayed | Ensure that the user's web browser has HTML frame support and that it is enabled. |
| Message EYUVH0400E displayed (or HTTP 400 message) | Ensure that the HTTP request is set up correctly:
|
| Message EYUVH0503E displayed (or HTTP 503 message) or no response from server | Check that your Web User Interface server is active and the CICS® Web Interface operational. |
| Message EYUVH404E displayed (or HTTP 404 message) | Check that the URL being used to access the server was entered correctly and valid. If accessing a help page ensure that the help page exists. |
| Missing data fields in views | Some attribute fields are derived from CICS CMF performance class monitoring data. In order for these fields to function correctly, you need to ensure that the CICS monitoring facility is active by setting the CICS system initialization parameters MNPER and MNRES to YES. |
For further information about the messages, access the contents page of the Web User Interface Message Help. For the client message, you can also obtain help by clicking on the message.