OA67938: OMEGAMON DATA PROVIDER 2025 Q2 MAINTENANCE

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• OMEGAMON DATA PROVIDER 2025 Q2 MAINTENANCE
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All OMEGAMON Data Provider users.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: OMEGAMON DATA PROVIDER 2025 Q2          *
  *                      MAINTENANCE                             *
  ****************************************************************
  This APAR includes new features and minor fixes.
  
  OMEGAMON Data Broker:
  
  -  No changes
  
  OMEGAMON Data Connect:
  
  -  Load configuration from multiple files and other sources
  
     For easier maintenance, you can now split the connect.yaml
     configuration file into multiple files. You can share files
     between instances of OMEGAMON Data Connect in locations
     outside of user directories. You can set parameters in
     environment variables, overriding values in files.
  
  -  Publish to multiple Prometheus endpoints
  
     OMEGAMON Data Connect now offers a choice of two options for
     Prometheus output:
  
     -  As before: one root-level metrics endpoint
  
        URL path: /metrics
  
     -  New: one or more named metrics endpoints
  
        URL paths:
  
        /metrics/<endpoint_name_1>
        /metrics/<endpoint_name_2>
        ...
  
        where the endpoint names are your choice.
  
  -  Java system property java.net.preferIPv6Addresses=system
  
     The example Java command line to run OMEGAMON Data Connect,
     and the corresponding Java command lines in the supplied
     sample JCL member and shell script, now explicitly set the
     Java system property java.net.preferIPv6Addresses to "system"
     rather than implicitly using the default value "false".
  
     "system" offers more flexibility for determining whether
     OMEGAMON Data Connect resolves hostnames to IPv4 or IPv6
     addresses.
  
  -  z/OS: sample JCL member and shell script now set
     _BPXK_AUTOCVT=OFF
  
     The sample JCL member and shell script for starting
     OMEGAMON Data Connect now deactivate automatic code page
     conversion on z/OS by setting the environment variable
     _BPXK_AUTOCVT=OFF.
  
     On z/OS, automatic code page conversion can cause the Java
     virtual machine to misinterpret OMEGAMON Data Connect
     configuration files.
  

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:

  UJ97499

Modules/Macros

• KAY11PAX KAY11ZIP KAYCONN
  

Fix information

• Fixed component name

  OMEGA DATA PROV

• Fixed component ID

  5698B6605

Applicable component levels

• R110 PSY UJ97499

     UP25/07/04 P F507

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.