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 Not under consideration
Workspace COBOL Compilers
Created by Guest
Created on Aug 30, 2021

Entreprise COBOL V6+ - IGYOS4081-U when MDECK(NOCOMPILE) + SQL options and no valid DBRMLIB

When compiling with MDECK(NOCOMPILE) and SQL options to resolve COPY and EXEC SQL INCLUDE, the compiler raises an IGYOS4081-U error if the DBRMLIB ddname is not declared, or if file associated with the DBRMLIB ddname does'nt have a valid format.

The MDECK(NOCOMPILE) option only concerns the processing of the source, and even in the presence of the SQL option, the EXEC SQL statements are not processed, (only EXEC SQL INCLUDE are processed), and therefore cannot give rise to the production of a DBRM.

The DBRMLIB should not be accessed, therefore not checked, when using MDECK(NOCOMPILE) option, even in the presence of the SQL option.

Idea priority Low
  • Guest
    Reply
    |
    Sep 18, 2021

    Existing clients might rely on the error message being issued. As a result, we cannot not remove it at this point in time.
    However, you can workaround this issue by specifying a dummy DBRMLIB in their JCL to avoid the error.