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 Delivered
Workspace z/OS Connect
Created by Guest
Created on Oct 8, 2020

RELATED IDEAS

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit ZCEE-I-137 Simplified JSON structures when generating bottom-up services from CICS channel applications.

[z/OS Explorer][z/OS Connect]Definition ? inconsistent API response field structure for CICS Commarea and CICS Container. Merged

The swagger response field structure generated for CICS Commarea and CICS Container are inconsistent.  An additional level (operation name) will be created for CICS Container in swagger request/response body.

Unnecessary outermost level (operation name) and next level (copybook name) are auto-added in swagger response body.

Suggestion
1) Swagger layout for CICS Commarea and Container should be same.
2) Swagger layout should be same as copybook. For example, copybook 01 level is the outermost field in swagger.

Idea priority Medium
  • Guest
    Reply
    |     Oct 19, 2020

    Thank you for raising this requirement. It is being closed as a duplicate of existing RFE 112810:
    http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=112810

    Please add your support by voting and/or commenting on it.

  • Guest
    Reply
    |     Oct 16, 2020

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS Connect Enterprise Edition
    Component - Product functionality
    Operating system - IBM z/OS
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Development Tooling
    Product - IBM Explorer for z/OS
    Component - Client
    Operating system - Windows
    Source - None

  • Guest
    Reply
    |     Oct 8, 2020

    Attachment (Description)

    [zOS Explorer][...
    [zOS Explorer][zOS Connect]Definition – inconsistent API response field structure for CICS Commarea and CICS Container.pdf
    Open full size
    [zOS Explorer][zOS Connect]Definition – inconsistent API response field structure for CICS Commarea and CICS Container.pdf

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.