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
We have no plans for enhancements in this area. Whilst for AFCF abends for example (VSWA deadlock detected if allowed to proceed) we have extra diagnostics such as *EXC AP 04B8, whose data item 3 gives information on the conflicting task. In that case we have the information to hand, and we know it applies because we have abended for a specific reason. That won't be the case for AFCI and AFCY and the reason for the purge,
This is a resubmit after 18months. The original one being RFE 67768 (DW 32147).
Comments from 67768:
1. John Tilling Mar 28, 2013 4:08 PM
Not sure about this. Can get purged for a variety of reasons , not just DTIMOUT. Assigning to Andy Wright for comment.
2. Andy Wright Apr 2, 2013 10:18 AM
This is a request for specific p.d. information in a situation that could be quite generic. If you look at AFCF abends for example (VSWA deadlock detected if allowed to proceed) we have extra diagnostics such as *EXC AP 04B8, whose data item 3 gives information on the conflicting task. But in that case we have the information to hand, and we know it applies because we have abended for a specific reason. That won't be the case here I think. I'm not sure how that level of detail could get passed up the stack from FCVS/RV into FCFR and so to EIFC. All we know is that fcfr_purged was returned, when we issue the AFCY abend. I think the key here is what would have led to the task suspending within file control prior to the purge/timeout and subsequent abend AFCY. We could see that in a trace - but that should already be there in a transaction dump trace too, as well as a system dump's. I wonder what the customer does with this info? Review the trace, see the culprit (purger, resource holder, etc) then act upon that. I suppose we could squirrel away some data from the cause of the suspend that resulted in the subsequent AFCY, then refer to that when cutting the abend. Perhaps some diagnostic area maintained by file control for subsequent p.d.?
3. John Tilling Apr 9, 2013 3:57 PM
We have no plans to make enhancements in this area. The AFCI and AFCY abends apply to purges which can happen for a number of reason not just DTIMOUT waiting for a file.