zRule Execution Server for z/OS® log files

Log files are stored in the ++HBRWORKPATH++/logs directory and they are ASCII encoded text files that are written to by the zRule Execution Server for z/OS. When you encounter a problem, these logs are necessary for problem determination.

They contain product messages that are issued during the initialization and execution of the rule engine. By default the HBRTRACELEVEL is set to WARNING so that only warning and error messages are written to these logs. If HBRA-CONN-COMPLETION-CODE and HBRA-CONN-REASON-CODE are returned to the calling application as non 0 or if the Rule Execution Server console encounters an error, then more information is found in these logs. For further diagnosis of the problem, HBRTRACELEVEL might be set to FINE or ALL and the problem re-created so that extra diagnostic trace is written to the logs. It is recommended only when you do problem determination and it is not recommended for a production environment.

If you are not experiencing problems in your Rule Execution Server console or rule execution then you can leave these logs alone. However, when you encounter a problem, these logs are necessary for problem determination.

Note: When a rule application prints messages, the standard output is available in HBRSSID-runtime-0.log when HBRTRACELEVEL is set to INFO or higher. Standard error messages are logged when the HBRTRACELEVEL is set to WARNING or higher.

The following log files are created when zRule Execution Server for z/OS starts:

Table 1. Log files located in `++HBRWORKPATH++`/logs when running in all modes
Log file name	Purpose	Behavior
HBRSSID-runtime-0.log	zRule Execution Server for z/OS and rule engine product messages are written to this log on startup and if a problem occurs during initialization or rule execution.	This log file grows up to 10 MB in size. At this point the log file is closed, rotated out, and a new file HBRSSID-runtime-0.log is opened. Successively older files are named by adding 0, 1, 2, incrementally into the base filename. HBRSSID-runtime-0.log always contains the current log, HBRSSID-runtime-1.log the next most recent log and so on.
HBRSSID-runtime-0.log.lck	A lock file to indicate that the log file is in use.	This file does not contain data and is transient

Table 2. Log files located in `++HBRWORKPATH++`/servers/<SSID>logs when running in CONSOLE, TEST, and HTDS modes
Log file name	Purpose	Behavior
res-console.log0.log	The Rule Execution Server console web application writes initialization messages to this log file.	This file is appended to on console restart and contains the initialization messages for the Rule Execution Server console. This file is only required to be kept in the case of a failing Rule Execution Server console.
messages.log	The embedded Liberty profile writes log messages here.	The file is created when the zRule Execution Server for z/OS starts in CONSOLE, TEST, or HTDS mode. It contains the log messages from the embedded Liberty profile. This log file is backed up to "messages_<date.and.time>.log" when the server is stopped and restarted.

You do not need a utility to format or print the log files. They are ASCII encoded so you can use viascii on the host or transfer them in binary format and read them on your distributed machine.