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 Delivered
Workspace z/OS Connect
Created by Guest
Created on Jul 7, 2018

fieldformat not changed - case sensitive

We imported a pl/1 Structur. After import alle the fields in lower case changed to uppercase, this is not nice, because the developper has to change the format every time he changes the service.

It would be good if the fields keep the format defined in the PL/1 File - stay case sensitive.

This would reduce the development affort a lot.

Idea priority Medium
  • Guest
    Reply
    |
    Feb 15, 2021

    Thank you for your comments.

    This RFE is in "Uncommitted Candidate" state. This means that it is has been accepted and is being prioritised against all other RFEs in this Uncommitted Candidate state. Your comments are helpful in aiding us to prioritise this and other RFE. Thank you for your continued engagement and we hope to provide this capability in an upcoming release of z/OS Connect EE.

    As soon as development starts on this item we will move this RFE to "Planned for Future Release" state to indicate that we are working on it.

  • Guest
    Reply
    |
    Feb 12, 2021

    Please add this feature for all programs, we would like it for our COBOL Copybooks.

    +1 to Jerker Emilsson's comment

  • Guest
    Reply
    |
    Nov 25, 2020

    I want to highlight the need for this option to retain the case sensitivity when importing Cobol Copybooks in zCEE toolkit. Today this creates a lot of extra work to rename every interface to be able to expose delightful api's. Both IMS/CICS services in zCEE design is our primary target.

  • Guest
    Reply
    |
    Aug 11, 2020

    This would be incredibly useful at our shop as we have a need to retain case sensitivity for COBOL COPYBOOKs. Currently we need to manually fix every field, and many of these copy books can be quiet large.

  • Guest
    Reply
    |
    Jun 27, 2019

    Perhaps there should be an option to convert PL/1 or Cobol names to camelCase

  • Guest
    Reply
    |
    Nov 12, 2018

    For COBOL as well please

0 MERGED

COBOL field name dash replaced with hiphen

Merged
COBOL field name dash replaced with hyphen on z/OS connect
almost 6 years ago in z/OS Connect 1 Delivered
0 MERGED

Retain case upon importing Copybook in Z/OS Connect EE

Merged
When the copy book is imported into the tool kit, it converts automatically to Capital case. But would like to retain the case as what is there in the imported file.
about 6 years ago in z/OS Connect 1 Delivered
0 MERGED

[z/OS Explorer][IBM z/OS Connect EE API toolkit]Service Definition ? import copybook - auto-convert field name to upper case.

Merged
When import a Cobol copybook to a service, the tool will auto-convert field name to upper case, and we need to manually change it back to lower camel case in ‘Interface Rename' column.
about 4 years ago in z/OS Connect 3 Delivered
1 MERGED

API Toolkit should respect CaSe in Cobol Copy Records

Merged
Our Developers would like the camelCase used in field names of their Cobol copy records to be respected by the API Toolkit and carried over, as such, to the Interface Names. Similar to RFE 122184 that pertains to PL/1
about 6 years ago in z/OS Connect 1 Delivered