News
Abstract
This page is for listing the known limitations in releases of Decision Runtime for z/OS 9.5.x. Workarounds are provided where possible.
Content
|
|
|
Installation and configuration
| Limitation | Workaround | Version |
|---|---|---|
| In creating the WOLA load library (see Creating the WOLA load library), you must obtain local adapters for Liberty. | To obtain optimized local adapters for Liberty, go to Securing optimized local adapters on Liberty for z/OS. | 9.5.0 |
IBM zRule Execution Server for z/OS
| Limitation | Workaround | Version |
|---|---|---|
File descriptors to UNIX System Services (USS) files are closed when HBRD runs. In Decision Runtime for z/OS 9.1, the performance of the embedded batch mode for calling Operational Decision Manager is significantly greater. In this mode, the ODM rule server and the client COBOL program run within the same address space. Previously, this configuration shared characteristics with the remote z/OS RES server mode, which limited performance. As part of the performance optimization, the HBRD component now removes the UNIX environment association from the address space. A side effect of this is that file descriptors to USS files are closed when HBRD runs. | USS file operations must not span the HBRD call. If they do, the file handles might be unexpectedly closed, leading to potential issues. This is generally not a concern if the HBRD is invoked at the end of the program, which is the typical usage pattern. | 9.5.0 |
| In the Rule Execution Server console, you can display the execution statistics of a ruleset. These statistics include the "Last execution date" value. The session caching for z/OS shows the status of this value as In Progress even after rule execution finishes. | If you use the Last execution date value, you must start zRule Execution Server for z/OS with the following setting equal to true: - DHBRNOSESSIONCACHE=true | 9.5.0 |
| Limitation | Workaround | Version |
|---|---|---|
| When running in batch mode (for example, HBRTARGETRES=EMBED), you must avoid manipulating USS files from your COBOL program after issuing HBRDISC to disconnect from Operational Decision Manager (ODM). If the file pointers predate HBRDISC, any subsequent access to those files fails. | This behavior is due to the enhanced mechanism to support access to ODM from a single address space, and the cleanup that occurs during disconnect. If you must access USS files across the HBRCONN/HBRDISC boundary, you can set the property HBRFASTEMBED=NO to revert to the original batch mode, which is slower. | 9.5.0 |
[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSNB5ZA","label":"IBM Decision Runtime for z\/OS"},"ARM Category":[{"code":"a8m3p0000008uP6AAI","label":"Install"},{"code":"a8m3p0000008uPBAAY","label":"Performance"},{"code":"a8m3p0000008uPNAAY","label":"Vulnerability"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.5.0"},{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSQPJS","label":"IBM Operational Decision Manager for z\/OS"},"ARM Category":[{"code":"a8m3p0000008uPMAAY","label":"ODM on z"}],"Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
13 March 2026
UID
ibm17236335