IBM Z Software
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).
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 updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server
This RFE is being rejected as we have no plans to provide a SIT parameter for a default abend code. Easier still than using a system event, is to put code in DFHPEP to detect the invalid abend code and to issue an EXEC CICS abend with a valid abend code instead. The name of the application and the abend code is passed to DFHPEP in a commarea. Another way would be to just write an audit msg to a TS to TD queue. The avoiding of flooding of DFHDU0212 could be achieved by suppressing them via XMEOUT exit. These are just ways to identify the problem so that the proper solution can be achieved, ie by fixing the applications.
I was thinking of using a system event as a temporary measure, ie as a means of taking a dump with a valid abend code and identifying the application, so that the applications can be fixed.
No, have not considered a system event, I guess that's part of the new event proccessing. Would need to test that to see what happens with an invalid abend code; would that suppress the WTO and provide the ability to control dump processing?
Have you considered using a system event? A system event can be emitted for an unhandled transaction abend. The event context information will include the application program id. You could capture relevant information to allow you to identify the programs to go and fix.