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.
This requirement has been evaluated and it is not something we are likely to implement, so correspondingly it is being rejected.
All this information, and a lot more, is provided in the TACB which is available in the various XPCABND related global user exits as well as the PEP. The TACB (and an abend can create more than one!) is where we've always added new abend related information; not only is the BEAR in there but there's also things like the TEA (useful for 0C4s), application context (where applicable), and now the vector registers and so on. These global user exits and the PEP are driven very close to when the actual abend occurred, any sort of processing in a HANDLE ABEND PROGRAM is always going to be a suspect since a lot may have happened in between. Doing something in the XPCxxx GLUEs and/or the PEP is going to be a much more useful, more accurate and is where we will generally add new information as/when required (vector registers being a recent case in point).
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
After an abend we generate formatted dump data tailored for our application, which provides specific information on our application data structures for our application programmers to diagnose the problem. We also display the values from ASSIGN ASRAPSW, ARSAREGS etc when applicable, but we found that after a bad LM/BR instruction sequence, ASRAREGS and ASRAPSW have no value. In this situation SDWABEA would provide more useful information than ASRAPSW.
Note that most application level programmers are not proficient at looking at CICS dumps, or the use of IPCS.
What is the purpose of making the BEAR available to the applications? Is it to put in their own messages or logs? Can you explain why the existing places where the BEAR is externalised is not adequate?