OA69163: OMEGAMON DATA PROVIDER 2026 Q1 MAINTENANCE

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• OMEGAMON DATA PROVIDER 2026 Q1 MAINTENANCE
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All OMEGAMON Data Provider users.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: OMEGAMON DATA PROVIDER 2026 Q2          *
  *                      MAINTENANCE                             *
  ****************************************************************
  This APAR includes fixes and new features.
  
  OMEGAMON Data Broker:
  
  -  Default list of cipher suites extended
  
     The default list of cipher suites for OMEGAMON Data Broker
     has been extended to include the following TLS 1.2 cipher
     suites at the start of the list:
  
     1. TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
     2. TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
     3. TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
     4. TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
  
     The additional cipher suites prevent a "no cipher suites in
     common" error where both of the following conditions are
     true:
  
     -  OMEGAMON Data Broker uses TLS 1.2 with the default cipher
        suite list to connect to OMEGAMON Data Connect.
  
     -  OMEGAMON Data Connect is running in a Java virtual
        machine where TLS_RSA_* cipher suites have been disabled.
        For details, see JDK issue JDK-8344767.
  
  OMEGAMON Data Connect:
  
  -  Prerequisites: Java 17-21 (was: 17 only)
  
     Previously, OMEGAMON Data Connect required Java 17, 64-bit
     edition.
  
     OMEGAMON Data Connect has been updated to accommodate changes
     to default character encoding introduced in Java 18.
  
     OMEGAMON Data Connect can now run on Java 17-21, 64-bit
     edition.
  
  -  Mask values of string fields
  
     You can now configure OMEGAMON Data Connect to use masks
     to transform string field values in TCP, HTTP, Kafka, and
     STDOUT output.
  
     For each field that you want to transform, you specify
     a mask that consists of the following properties:
     -  The range of character positions to be masked
     -  A mask character
  
     For example, you can transform the values of sensitive
     fields such as user IDs from the original value EC27182
     to the masked value EC2xxxx.
  
     You can specify masks in a global-level transform that
     applies to all outputs and in output-level transforms
     for each output. Output-level transforms replace any
     global-level transform.
  
  -  Kafka output: topic name can include placeholders for
     product code and table name
  
     The value of the topic configuration parameter can now
     include the following placeholders:
     -  {product_code}
     -  {table_name}
  
     You can use these placeholders to specify custom per-table
     topic names.
  
     For example, given the following configuration:
  
     connect:
       output:
         kafka:
           topic: domain-a.{product_code}-{table_name}.v1
  
     OMEGAMON Data Connect sends data from table ascpuutil of
     product km5 to the following topic:
  
     domain-a.km5-ascpuutil.v1
  
  -  Fix garbled log messages on z/OS
  
     In some situations on z/OS, OMEGAMON Data Connect
     log messages were garbled. The garbling was caused by a
     mismatch between the encoding of the Java output stream
     System.out and the value of the Spring Boot property
     logging.charset.console.
  
     To fix this issue, on z/OS, OMEGAMON Data Connect now sets
     logging.charset.console to match the System.out encoding.
  

Problem conclusion

Temporary fix

Comments

• User Action:
  
  New users installing OMEGAMON Data Provider for the first time:
  
  1. SMP/E Apply the fix.
  
  2. See the "Installing" topic in the OMEGAMON Data Provider
     product documentation.
  
  Existing users upgrading:
  
  1. For more detailed descriptions of what's new, see the
     "What's new" topic in the OMEGAMON Data Provider
     product documentation.
  
  2. See the "Upgrading" topic.
  
  Reference:
  
  -  OMEGAMON Data Provider product documentation:
  
     https://ibm.com/docs/odp
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UJ99735

Modules/Macros

• KAY11PAX KAY11ZIP KAY1BDP  KAY1LDP  KAY1ODP  KAY4BDP  KAY4LDP
  KAY4ODP  KAYB0001 KAYBNETL KAYOPEN
  

Fix information

• Fixed component name

  OMEGA DATA PROV

• Fixed component ID

  5698B6605

Applicable component levels

• R110 PSY UJ99735

     UP26/06/03 P F606

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.