Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Delivered
Categories Assembler
Created by Guest
Created on Mar 8, 2013

Improve ASMA972U messages

This message provides absolutely no useful information whatsoever to
determine the cause of the error. The statement number is totally
useless as there is no indication what the source of that statement
might have been. It could have been open code, a copybook, a macro,
etc. The storage dump of 80 bytes of zeroes is also totally useless.

The message description states truthfully that storage was exhausted
and suggests increasing the SIZE parameter. That might be useful in a
fraction of the cases where this message is produced. But the more
likely cause of this message is some recursion in the assembler input,
such as a macro calling itself.

At the very least, the assembler needs to identify the source of the
statement being processed, i.e. sysin or copy/macro member name, and
the statement number in that source. The message description also needs
to be augmented to suggest the recursion scenario.

It would also be a nice feature to implement a new feature, similar to
ACTR, that could limit the nesting depth of macros. It should be
settable by the user (as is ACTR), but have some reasonable default ,
maybe 25 or so. This could stop unintended recursion before virtual
storage was exhausted and would facilitate diagnosing this type of
program error.

Idea priority Medium
  • Guest
    Reply
    |
    Oct 5, 2015

    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)

  • Guest
    Reply
    |
    Oct 28, 2013

    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.

  • Guest
    Reply
    |
    Mar 12, 2013

    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.