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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Enterprise Tooling
Product - High Level Assembler (HLASM)
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Enterprise Tooling
Product - High Level Assembler (HLASM)
To help diagnose this sort of issue APAR PM84549 was raised to display additional data.
As described in the APAR conclusion:
PROBLEM CONCLUSION:
HLASM has been modified to provide additional information following the Statement Status report. A data set allocation report will be printed which includes the data set names and if applicable, the member name of allocated SYSIN and SYSLIB data sets. The current line number of the SYSIN data set being processed will be printed. Where a SYSLIB member name is printed, its current line number will be printed.
If the last opcode to be processed was a macro, then a Backward Chain report will be printed consisting of the names of up to the last 8 macros. For each macro being reported, the name of
the data set from which it was loaded will be printed and if the macro was loaded from a member, that member name will be printed.
I agree that this enhancement should be provided by HLASM - diagnosing recursive macro calls can be problematic.
As suggested, it ought to be a value that a user can set.