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 Aug 21, 2014

Add pipeline support for XML

Add pipeline support for XML similar to JSON pipeline.

Idea priority Medium
  • Guest
    Reply
    |
    Jan 14, 2019

    We have assessed this requirement. We have no current plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

  • Guest
    Reply
    |
    Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Transaction Processing
    Product - CICS Transaction Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server

  • Guest
    Reply
    |
    Dec 17, 2014

    This is a candidate for a future release.

  • Guest
    Reply
    |
    Dec 16, 2014

    Greetings,

    The additional support requested is to align the JSON and XML Restful offerings. With REST and XML, we use the WEB and TRANSFORM commands. This is the only option.

    With JSON and REST, we have the request/reply interface and the Restful interface. XML and REST have neither of these options available.

    For XML in a request/reply model, I understand this is very similiar to SOAP. We do have a significant number of applications that do use the request/reply model with XML that are not SOAP.

    Ideally, a container application could be bound as both XML and JSON regardless of the interface chosen. We do have the transform option available where the CICS application would be responsilble for issuing E.C. WEB commands. The RFE is asking for REST/XML to have the same options as REST/JSON. The client would be able to use either XML or JSON for the same CICS container application regardless of the interface chosen.

    Regards,
    Michael Karagines

  • Guest
    Reply
    |
    Aug 28, 2014

    Please can you clarify as it is not clear what is being requested.
    The JSON support in CICS is derived from the SOAP/XML support.CICS has had "pipeline support for XML similar to JSON pipeline" since CICS TS V3.1. And the ability to support "the same business logic" for "both JSON and XML" is already available for bottom-up scenarios. Top-down scenarios are slightly different, some advanced concepts are not shared between JSON and XML, so it might not be possible/convenient to provide both interfaces. But bottom-up support for this has been available for as long as we've supported JSON.