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
Created by Guest
Created on Aug 25, 2021

MQ support when called from subroutine

Please enhance ADDI to support MQ when variables involved in MQ statement are declared and resolved in one program and MQ calls is made from another program

Idea priority High
  • Guest
    Reply
    |
    Oct 19, 2021

    We have a workaround for this situation which is as follows:
    Two configuration files can be used: MQQUEUEINFO.TXT and MQQUEUEMGRINFO.TXT, please find them attached here.
    - In MQQUEUEINFO file on the left side, the program name is specified, in the middle the variable that is used in MQ call is specified, and on the right side, the QUEUE Name is specified.
    - In MQQUEUEMGRINFO file on the left side, the program name is specified, in the middle the variable that is used in MQ call is specified, and on the right side, the QUEUE MANAGER Name is specified.

    The files will be added in the MQ virtual folder, in the project, with type MQ.

  • Guest
    Reply
    |
    Sep 14, 2021

    As far as we understand your use case, the MQ parameters are passed from Main program to the subprogram and then Main program call the subprogram.

    PROGRAM-A create MQ queue name dynamically and then call PROGRAM-B where there is a MQ call (MQOPEN for example).
    In order to understand your use case better and see how we could improve our Cobol compiler, would it be possible to get we those 2 programs (and their Includes if MQ variables are declared there) or snipped source code that could highlight the following:
    - How PROGRAM-A creates MQ queue names;
    - How IMSGETID is populated with values and where, in which program;
    - How MQ variables are defined in PROGRAM-A and PROGRAM-B;
    - How the "CALL PROGRAM-B" statement is made, what parameters are used;
    - How the "PROCEDURE DIVISION" statement is defined in PROGRAM-A and PROGRAM-B.