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 Nov 8, 2017

RELATED IDEAS

Preserving service interface customisations in the API Toolkit service projects upon re-import of an updated copybook

See this idea on ideas.ibm.com

z/OS Connect API Toolkit allows COBOL copybook fields to be renamed within the Service Interface definition so that COBOL copybook field names are not exposed in the APIs. For example you may rename a copybook field from CPY-CUST-FR-NAME to customerName, so that JSON friendly name is exposed on the API interface.

Currently there are two issues with this process:
1. If you make changes to the source COBOL and re-import the copybook into the service via the API Toolkit all of the mapping is destroyed and you have to start again. This could potentially lead to issues in the APIs that are built on the service.

2. If you use zconbt to build a service archive file there is currently no way of renaming a COBOL copybook field. This limits the use of the field renaming feature if zconbt is used within a build pipeline for deployment of service archive files, as this effectively means the field renaming functionality cannot be used.

We require the ability to generate a persistent store of field renaming mappings so that they can be re-applied by the API Toolkit when a copybook is re-imported.

The persistent store of field renaming mappings should alos be used as input to zconbt when generating a service archive in batch so that consistent service archive files can be generated acorss the tooling.

It would also be useful to be able to define a dictionary of COBOL field names to JSON element name mappings and to have this automatically applied (or the option to apply) these to a copybook when it is imported.

Idea priority High
  • Guest
    Reply
    |     Jan 28, 2019

    This requirement is addressed by z/OS Connect Enterprise Edition API Toolkit V3.0.6.0:
    https://developer.ibm.com/mainframe/products/zosconnect/#section_download

    The API toolkit V3.0.6.0 has been enhanced. When re-importing changed data structures, existing custom data structure names (aliases) and remarks are preserved if the 01 level structure remains unchanged.

    For further details about Importing Data Structures, refer to the “Importing data structures or full programs” topic in the z/OS Connect EE V3.0 Knowledge Center:
    https://www.ibm.com/support/knowledgecenter/en/SS4SVW_3.0.0/designing/service_importdatastructures.html

0 MERGED

Need Option on adding/removing field in a service creation without importing copybook

During service creation(request/response), once we import the COBOL copybook into service container/commarea, neither we have any option to add/modify/remove any field nor copy/paste from the old values.
over 6 years ago in z/OS Connect 1 Delivered

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.