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 COBOL Compilers
Created by Guest
Created on Jul 24, 2014

Warning Message when using VLR(Standard) and FILE STATUS=4 COBOL V5

COBOL Version 5:
If no File Description exists for the smallest and the largest Record, the file status is 04, as difference to COBOL Version 4.
So for cleaning the programs, i like to set the VLR(standard) option.
But then i want to get a warning (or an informational), if i have forgotten to declare the smallest descriptor and the largest descriptor.
Because getting this information in development is much earlier than getting the problem in production.

Idea priority Medium
  • Guest
    Reply
    |
    Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - COBOL Compilers

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - COBOL Compilers

  • Guest
    Reply
    |
    Feb 11, 2015

    This RFE has been delivered in Enterprise COBOL, V5.2

  • Guest
    Reply
    |
    Sep 11, 2014

    This RFE has been put into plan.

  • Guest
    Reply
    |
    Aug 15, 2014

    This is inline with our long term strategy and is a valid feature, but has not been put into plan yet. Once it does, this RFE will be updated.

  • Guest
    Reply
    |
    Jul 25, 2014

    With this Warning message from Compiler you can use VLR(Standard) and you can recognize all problematic programs at compile time. The problematic ones go with VLR(compat) to production. So there is much more time for either completing file description or better handling of file status including fs=04 - and then setting VLR(standard), of course.