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

Payload string values that are too long cause Web Service and API runtime errors

CICS requires a maximum length to be specified (implicitly or explicitly) for all string fields in Web Services and APIs. However, interfacing systems often don't have max length restrictions on strings (especially if they are not mainframe-based systems).

This requires application schemas used with the CICS Assistants to set an arbitrary max length. If a string value exceeds the specified max length then the message is discarded at runtime with a parsing error.

Perhaps a new flag could be introduced in the XML/JSON Assistants to indicate the action to take when an incoming string exceeds the defined length: Error, Warning message, or Ignore.

Idea priority Medium
  • Guest
    Reply
    |
    May 22, 2018

    Whilst this requirement is valid, based on our current plans and priorities, it is not likely that this could be implemented in the next 12 months, or in the next CICS TS release. Correspondingly 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
    |
    Sep 26, 2017

    Will need to handle the case of a bug in the remote application or a malicious application sending an infinitely long string.

  • Guest
    Reply
    |
    Aug 10, 2017

    Given a warning option would be available, the application may want to code for handling truncation of the fields effected. There may be a way of generating a truncation flag for each field, by selecting an option in the web services assistant, when desiring a warning message on overflow.