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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
We are using the functions display-of and national-of to dynamically change between encodings.
Like this:
MOVE FUNCTION DISPLAY-OF (
FUNCTION NATIONAL-OF (
INPUT-DATA (1:INPUT-LENGTH),
CHARSET-CCSID), 277)
TO OUTPUT-DATA (1:EXPECTED-OUTPUT-LENGTH)
INPUT-DATA and OUTPUT-DATA are located in LINKAGE section as very large PIC X variables, and are dynamically allocated, to only contain the amount of storage we need.
This code is used from Rexx in a TSO environment, and in batch environments.
In batch, we have no problems with this, but in the TSO environment, the program dumps before executing a line of code.
We found that this is because COBOL allocates a very large amount of storage, for that move statement.
This is because COBOL determines the maximum possible amount needed at compile time, and then allocates that at runtime, we dump in TSO environment.
Splitting the move into two, removes this issue.
We would request an improvement, that determines the amount of storage needed at runtime, instead of at compile time.
Thank you
Idea priority | Low |
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.
Thanks. This Idea is being accepted for a future release and will be updated once put into plan.
Hi, can you please provide the definitions of the data items and a test case that demonstrates the issue?