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
Categories Runtime
Created by Guest
Created on Sep 30, 2022

Tolerate unknown elements for SOAP web services

One of our web service applications is getting a DFHPI1007 error calling a remote service from CICS (so CICS is the web service consumer).

It turned out, that the server system added some optional elements to their web service response in their recent release.

To ensure backward and forward compatibility for minor web service releases, it is essential to tolerate new (optional) elements on both sides (service provider and consumer).

Maybe, it could be configured by feature toggle, so other CICS customers would be able to still use the strict parsing.

Unknown elements could be collected in a separate container, so the application would be able to recognize and handle unknown elements (not needed for our purposes, but might be for other customers).

Idea priority High
  • Guest
    Reply
    |
    Jun 7, 2023

    If the requirement is not likely to be implemented, we have to recommend our application developers to not use CICS web services. We cannot guarantee, that the service consumer versions will be always aligned with the service provider versions at the same time.

  • Guest
    Reply
    |
    Dec 23, 2022
    CICS Development: Looking at current plans, it is not likely that this would be implemented in the next 12-24 months, so correspondingly this requirement is being rejected. You have an opportunity to resubmit in twelve months time if you wish it to be considered then.