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.
Hi Arshia,
Although it is not possible to pass the history file DSN from the CICS region to the IDIS subsystem the desired outcome can be achieved by using a DumpRegistrationExits Control exit. The following example uses the jobname of the requesting CICS region to set the ENV.IDIHIST field ie the history file DSN.
/* Sample Dump Registration Control exit */
JobList.0 = 2
JobList.1 = "CICSPRD1 CICSPRD2 CICSPRD3"
JobList.2 = "AS680F1 CICSTST2 CICSTST3"
Hist.1 = "FAULTAN.PROD.CICS.HISTORY"
Hist.2 = "SIMCOCK.HISTORY"
HistDSN = "FAULTAN.DEFAULT.HISTORY"
Do i = 1 to JobList.0
Do j = 1 to Words(JobList.i)
If ENV.JOB_NAME = Word(JobList.i,j) Then
HistDSN = Hist.i
End
End
ENV.IDIHIST = HistDSN
Exit 0
Let me know if this gives you the level of control you need,
Thanks
Adrian
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Development Tooling
Product - IBM Fault Analyzer
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Enterprise Tooling
Product - IBM Fault Analyzer
Adrian,
This stemmed from a conversation you and I (or maybe FA Support and I) had back in mid/late 2014. When FA/CICS detected a storage overlay via the XEIIN exit and we had TranDump requested via the CFA transaction parameters for XEIIN, we had failures b/c we are using REXX to specify the history file in our IDICNF00 member without a default IDIHIST member defined. Because the REXX is not executed in this logic path, FA complained that no IDIHIST was defined. The solution was to specify a "default" IDIHIST in our IDICNF00 member for whenever the REXX is not invoked. This RFE is asking for FA/CICS to determine what History File is appropriate for the CICS region and pass that as part of the request to the IDIS STC. The IDIS STC can then use this passed History File rather than using our default/"fallback" history file. This would keep IDIS abends in the same history file as other abends from the same CICS region.
Please can I verify which dump request is being referred to in terms of CICS and IDIS ? For example a SVC dump request as a consequence of a storage overlay detection, and RFR dump etc.
Regards
Adrian Simcock