Troubleshooting zRule Execution Server for z/OS
zRule Execution Server for z/OS provides diagnostic information to help you troubleshoot potential issues.
The following table provides details of available diagnostic information. See also Troubleshooting and support
.
| Description | Location | For more information |
|---|---|---|
| ALIG abend | An ALIG abend is caused by the zRule Execution Server for z/OS® program definitions being incorrectly installed. | In this situation, compare your configuration to the supplied HBRCSD job to determine what might be causing the problem. |
| Console does not open | You cannot open the console from your web browser. |
|
| Error messages. | At the z/OS console or equivalent. | See Managing console security. |
| JVM error | You can find more diagnostic information in log files that can be found in the directory that is specified by ++HBRWORKPATH++/logs. | If a JVM error occurs on the server, check the HBRPRINT and associated logs for information. |
| LPAR connection error | If the console shows an executable unit (XU) as started, registered, and passing diagnostic tests but your z/OS® application cannot connect to the server, the application tried to connect to a server in a different LPAR. The HBRCONN API call returns a completion code of HBR_RC_SERVER_NOT_DEFINED (3005) when you try to connect to a server in another LPAR. | To correct this problem, take one of the following actions:
|
| Nonzero JOBSTEP condition code. | In the SDSF JESMSGLOG log for zRule Execution Server for z/OS. | See JOBSTEP condition codes. |
| Logs listing errors that occur on zRule Execution Server for z/OS in RULE mode. | In the working directory for the server instance, which is specified by ++HBRWORKPATH++/logs. |
None. |
| Logs listing errors that occur on zRule Execution Server for z/OS when running in CONSOLE, TEST, or HTDS mode. | In the working directory for the server instance, which is specified by ++HBRWORKPATH++/logs. Logs for the embedded Liberty profile can also be located at ++HBRWORKPATH++/servers/<SSID>/logs. |
None. |
| Logs that contain information to help IBM® technical support with problem determination. | SYSnnnnn logs. | None. |
| Logs for zRule Execution Server for z/OS running on a CICS® JVM server. | In the CICS system logs and the HBRPRINT log. | See Troubleshooting and support
|
| Logs listing JVM errors that occur on zRule Execution Server for z/OS running on a CICS JVM server. | In the working directory for the CICS JVM server instance, which is specified by ++HBRWORKPATH++/logs. | SeeTroubleshooting and support
|
| The runtime variable, HBRTRACELEVEL, in the dataset defined by the HBRENVPR DD statement, specifies the types of diagnostic information to be logged. To capture the most detailed information, set the trace level to ALL. | Diagnostic information for rule execution errors is written to log files in the directory that is specified by ++HBRWORKPATH++/logs, where ++HBRWORKPATH++ represents the working directory for the server instance. | See the ++HBRTRACELEVEL++ variable in the SHBRPARM(HBRCMMN) data set member in z/OS configuration variables. |
| Messages that provide ruleset execution status or identify errors that were encountered by zRule Execution Server for z/OS. | In the system log in the HBRPRINT DD statement. | See Messages. |
| Completion and reason code are returned to the z/OS application (COBOL or PL/I application). Information is also returned in certain cases in the HBRA-RESPONSE-MESSAGE field. | In the following HBRA-CONN-AREA data area
fields:
HBRA-CONN-AREA is in the ++HBRHLQ++.SHBRCOBC(HBRWS) data set member for COBOL applications, and ++HBRHLQ++.SHBRPLIC(HBRWSP) data set member for PL/I applications. |
See zRule Execution Server for z/OS Completion codes and reason codes. |
| zRule Execution Server for z/OS does not start. | If you cannot start the zRule Execution Server for z/OS check the JOBSTEP condition code for more information. | If you cannot start zRule Execution Server for z/OS, check the JOBSTEP code and refer to JOBSTEP condition codes
|