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.

Add a new idea Subscribe
Status Not under consideration
Workspace COBOL Compilers
Created by Guest
Created on Nov 25, 2020

RELATED IDEAS

Enterprise Cobol - Way to not display the IGZ0201W message at runtime

For a file in Variable format with read acces, the COBOL runtime performs a check on the LRECL.

By default, if the LRECL does not match the program statement this triggers an abend and an IGZ0035S message.

If we declare a FILE-STATUS on the file, there is no more abend, but there remains the emission of a message IGZ0201W:

IGZ0201W A file attribute mismatch was detected. File file-name in program program-name had a record length of record-length-1 and the file specified in the ASSIGN clause had a record length of record-length-2.

For files in Fixed format with read access, a solution consisting of declaring the RECORDS CONTAINS 0 CHARACTERS clause allows to read files with any LRECL.
Unless we are mistaken, there is no equivalent for files in Variable format.

We would like a solution:
- or so that the message IGZ0201W does not appear at runtime,
- or allowing to read Format V files with any LRECL.

Idea priority Low
  • Guest
    Reply
    |     Jan 28, 2021

    :-(

  • Guest
    Reply
    |     Jan 26, 2021

    We have evaluated this RFE. Even though this RFE is a good idea, runtime performance is the main reason why we have chosen to keep the current design. Any changes to the current file I/O architecture will result in a performance degradation.

  • Guest
    Reply
    |     Jan 13, 2021

    The "RECORD IS VARYING FROM x TO y (DEPENDING ON...)" solution defines an LRECL of y+4 and does not solve the problem: there will be an IGZ0035S or IGZ0201W message at runtime, if the absence or the presence of a FILE-STATUS, if the LRECL of the read file has a value other than y+4.

    It should be possible to define an UNBOUNDED clause at the file level:

    - either on the FD clause:

    RECORD IS VARYING IN SIZE FROM min TO UNBOUNDED DEPENDING ON var-recordsize.

    - and / or on the record description:

    01 ANYSIZE-RECORD.
    02 PIC X OCCURS min TO UNBOUDED.

  • Guest
    Reply
    |     Dec 22, 2020

    Please try using RECORD IS VARYING FROM x TO y (DEPENDING ON) and let us know if this is not sufficient. Thanks.

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.