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.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM High Level Assembler for z/OS and z/VM
Categories Assembler
Created by Guest
Created on Aug 22, 2022

RELATED IDEAS

COPYLIB DD for COPY code, SQLLIB DD for SQL INCLUDE

Assembler copy code and macros are distinct types of elements that can be mutually dependent. Because they are read from the same SYSLIB DD they need to be assigned different names. A COPYLIB DD for copy code would support matching named macros and copy code to be read from two different DD. SQL INCLUDE is another distinct type of assemble time input component element that similarly could use its own input DD (SQLLIB DD) particularly since it (unlike macros and copy code) is not specific to assembler. It is sometimes good practice for developers to assign the same name to different types of mutually dependent elements. For example, JCL that executes a load module created from a main program object module will consist of three different types of elements each of which can be assigned the same name.

Idea priority Medium
  • Guest
    Reply
    |     Aug 24, 2022
    Sorry, but the concept that the assembler has just one SYSLIB has been in the language and the implementation from the start (in the 1960s). Even if we accept the idea that it could be useful to have a COPY and MACRO file with the same name (which seems debatable), we feel that the amount of resources and time that would be needed to implement a separate COPY library concept (on MVS, CMS, VSE and Linux) would be far better spent on other enhancements.

    Also, splitting the libraries could create new problems. For example, at present, it is a standard debugging technique to be able to COPY a macro, so that error messages relating to the macro will show the relevant source lines, or to use the LIBMAC option which effectively does that automatically. Also, existing products will typically have a mixture of MACRO and COPY files in the same data set, so if the libraries were split most data sets would need to appear in both definitions, unless a COPY request would also try the MACRO library anyway.

    The Assembler does not know about SQL includes, which are presumably handled by the SQL preprocessor.

    Jonathan Scott, HLASM

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.