This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
How to change Correl-ID on DB2 z/OS using DB2 Connect from Microfocus Enterprise Server?
We are from Banco Santander Brasil.
As a global project, we are moving some applications from z/OS mainframe environment to Microfocus Enterprise Server on Linux.
Microfocus Enterprise Server product accesses DB2 z/OS through DB2 Connect v.126.96.36.199 with SB 13485.
We need a solution to change the correl-id coming to DB2 z/OS to identify the transactions/jobs that are running in the Microfocus environment.
The connection to DB2 is established at the start of Microfocus CICS regions, and maintains it as long as there are requests to execute transactions/jobs.
Microfocus changes the SQL_ATTR_INFO_PROGRAMNAME field with the transid/jobname every run. However, we have verified that the correl-id arriving at DB2 z/OS is always the same - that is, it maintains the correl-id of the initial connection.
As exposed on TS010192068 IBM case, DB2 Connect does not honor the change in the SQL_ATTR_INFO_PROGRAMNAME field on every run.
We need an enhancement so that SQL_ATTR_INFO_PROGRAMNAME is modified on every run to make it possible to identify the job/transaction on DB2 z/OS.
This maintenance is extremely important for monitoring the environment.
Can you please consider this implementation in the next release of DB2 Connect?
Do not place IBM confidential, company confidential, or personal information into any field.