Decision Management & Intelligence (ODM, DI)

Decision Management & Intelligence (ODM, DI)

Connect with experts and peers to elevate technical expertise, solve problems and share insights


#Data
#Data
#Businessautomation
 View Only

New Safeguards Against Misconfiguration in Decision Runtime for z/OS

By James Taylor posted Mon January 05, 2026 06:15 AM

  

Upgrading Decision Runtime for z/OS (DRz) can sometimes lead to subtle configuration issues that are difficult to diagnose. With the latest update - 9.5.0.1 (PH68487) - we’ve introduced additional protection to help identify these misconfigurations. Similar safeguards have also been added, as service, to 9.1.0.1 (PH68857) and 8.11.0.1 (PH68556).

 

A blue shield with a lock These enhancements focus on two key areas



1. Detecting Mixed Versions Between Datasets and USS Files

During upgrades, customers have occasionally updated one location but not the other, resulting in a mix of versions. This can cause the native layer (from datasets) and the Java core (from USS files) to run at different levels—an unsupported and unpredictable scenario.

  • Datasets (load libraries and related content), identified by the HBRHLQ high-level qualifier in the started task.

      

  • Unix System Services (USS) files, located via the HBRINSTPATH property in the HBRENVPR configuration.
     

   What's New?

On startup, DRz now verifies that the version level of the code at both locations match. If they don’t, startup will fail, and the zRES server will terminate. The job output will include an error message:

“The USS part of the product is not at the same version as the Datasets.”

 

 

2. Validating Client and Server Load Library Versions


Another common issue occurs when the zRES server is upgraded, but client applications still point to older libraries.

zRES version configuration location:

zRES server is configured to use a certain product version in the started task procedure JCL, and via the HBRINSTPATH parameter.


Client version configuration location:

  • Batch clients: SHBRLOAD in JCL STEPLIB
  • CICS: SHBRCICS in DFHRPL
  • IMS: SHBRIMS and SHBRLOAD in the DFSMPR procedure


While Decision Runtime for z/OS tolerates mismatches for fix packs (to allow staged upgrades), major version differences can lead to unpredictable behaviour.

   What's New?

When a client makes a cross-memory call, DRz now checks version compatibility:

  • If the call succeeds, the server logs a warning indicating a mismatch.
  • If the call fails, diagnostic data in HBRPSNAP will help IBM Support troubleshoot.

   What Should You Do?

  • During upgrades: Verify both HBRHLQ and HBRINSTPATH point to the same version.
  • After upgrades: Ensure client libraries match the server version.
  • Monitor logs: Watch for warnings about mismatched versions and plan remediation promptly.

These changes are designed to make your DRz environment more resilient and easier to maintain. For detailed instructions, refer to the official IBM documentation or contact IBM Support.

0 comments
22 views

Permalink

https://community.ibm.com/community/user/blogs/james-taylor2/2026/01/05/drz-new-safeguards-against-misconfiguration