Limitations on zRule Execution Server for z/OS®

The Rule Execution Server console is supported on zRule Execution Server for z/OS platforms but some features are not available or work differently.

Overview of the differences

Some views and commands are not available in the Explorer, Diagnostics, and Server Info pages, and the Diagnostics page displays different test results.

Server Info page

The Server Info page also displays the Configuration details column, which provides more details on the execution units.

Diagnostics page

The diagnostics that are run on the Rule Execution Server console are slightly different on zRule Execution Server for z/OS:

The Local XU connectivity tests do not exist in the zRule Execution Server for z/OS architecture. Instead, the XU connectivity through TCP/IP test is run.
The Rule Session Execution and Rule Session Second Execution tests do no exist. TCP/IP Test Execution and TCP/IP Second Test Execution are run instead.

XU connectivity through TCP/IP: Checks whether at least one XU is connected to the Rule Execution Server console through TCP/IP. This test executes the ruleset /test_ruleapp/1.0/test_ruleset/1.0 on all the visible execution units. If no XU connection is detected, an error message is displayed.
TCP/IP Test Execution: Tests that the XUs that are connected to the console through TCP/IP can run the ruleset. This test is not run if the XU connectivity through TCP/IP or Create Ruleset tests fail.
TCP/IP Second Test Execution: Executes the ruleset again to check the update. This test is not run if the TCP/IP Test Execution test fails.