IBM Z Software
Hide about this portal


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 Mar 23, 2018

RELATED IDEAS

zCEE API Toolkit support for VARCHAR in Cobol

See this idea on ideas.ibm.com

API Toolkit does not provide an efficient support for VARCHAR in Cobol.
Example Cobol copybook:
03 CUSTNAME.
49 CUSTNAME-X PIC X(080).
49 CUSTNAME-L PIC S9(04) COMP.

Resulting JSON:
"CUSTNAME" : {
"type": "object",
"properties": {
"CUSTNAME-X": {
"maxLength": 80,
"type": "string"
},
"CUSTNAME-L": {
"minimum": -9999,
"maximum": 9999,
"type": "integer"
}
}
}
Today, the fields are mapped in a 1:1 manner, but as an API consumer it just seems weird having to specify the length of a string field when it can just be computed by the gateway.
Ideally the JSON would look like:
"CUSTNAME" : {
"type": "string",
"maxLength": 80
}
During the import of the copybook in the API Toolkit, the tool could check for a specific pattern (1 data structure group with one integer and one PIC X, both using 49 level field) to identify that it's a VARCHAR. And the data transformation process would know that this field is to be split into 2 and would retrieve the length of the string.

Idea priority Medium
  • Guest
    Reply
    |     Mar 23, 2022

    This requirement is addressed by z/OS Connect V3.0.55 / APAR PH43628: https://www.ibm.com/support/pages/apar/PH43628
    For further details refer to the “ Developing APIs with the z/OS Connect Designer” topic in the z/OS Connect OpenAPI 3 Documentation:
    https://www.ibm.com/docs/en/zosconn/zos-connect/3.0?topic=developing-apis-zos-connect-designer

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.