This portal is to open public enhancement requests against IBM Z Software products. 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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
We have our own XMNOUT exit to suppress SMF110 records for CSMI and some exception records. Our exit works fine until we need to do OMEGAMON maintenance which does OMEG REMOVE and OMEG INIT.
Normally the sequence of the XMNOUT program is KOCOME00 first then our exit as they are defined in that order in PLTPI. In the SMF110 suppression works fine.
However, OMEGAMON maintenance changes the order because the exit was removed and enabled by OMEG REMOVE and OMEG INIT transactions. In this case the SMF110 suppression does not work because KOCOME00 ignores the RC from our exit and always returns RC=0.
I talked to the OMEGAMON Support who advised to use the Global data area to suppress CSMI transaction. But there is no other way to suppress the SMF110 exception records.
I would like to suggest
- KOCOME00 for the exit should return the previous exit program's non zero RC.
- Or OMEGAMON should provide another way to suppress the SMF110 exception records. Maybe a similar way to the CSMI in the Global data area.
Note : the exception records we are suppressing are for file string wait. The number of string wait exception records are generated around one million a day, all of them are string wait for ESDS file. We define strings=1 for all ESDS files to avoid the wait in the VSAM codes.
This issue was reported to IBM (TS015928462). The support advised to raise a RFE record.
Idea priority | Low |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Hello, thank you for opening this product enhancement request. I am pleased to announce this enhancement has been delivered with PTF UJ96771. Please reach out if you have any further questions. Regards IBM OMEGAMON Product Management