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 Future consideration
Workspace z/OS Connect
Created by Guest
Created on Sep 21, 2023

RELATED IDEAS

Add affected service and IMS system to IMS Service Provider error messages in z/OS Connect

As of today when an IMS transaction service in z/OS Connect runs into a problem because the invoked transaction abends, doesn't respond in time or is stopped respectively the transaction cannot be invoked because of unsufficient authorization, z/OS Connect only prints an exception with a message returned by either IMS Connect, OTMA or the IMS Transaction Manager. If you have lots of IMS transaction services - maybe even multiple invoking the same transaction - it can become very hard to find out which IMS transaction service (and which API) was affected by the problem. The same applies if you have one z/OS Connect EE server connected to multiple IMS systems and maybe even a routing policy. It may be hard or even impossible to find out, which IMS system was involved into the problem. By adding both the affected IMS transaction service and also the IMS datastore name to the error message, problem analysis could be made much easier for both z/OS Connect + IMS admins and API / service + mainframe application developers. 

Idea priority High
  • Admin
    Demelza Farrer
    Reply
    |     Apr 30, 2024

    The points raised in this IDEA are:

    1. The lack of API and Service name

    2. The lack of IMS ID and Datastore name (are these the same thing?)

    3. Repeated stack traces making logs cluttered and debugging difficult

    For point 3 the repeating messages and stack traces are coming from the TMRA code and not something z/OS Connect has control over.
    This therefore will not be included within this IDEA and should be raised as a separated IDEA against IMS.

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.