Skip to Main Content
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.

Status Submitted
Categories Editors
Created by Guest
Created on Feb 11, 2025

Cobol syntactic analyzer to handle multiple ENTRY statements

See this idea on ideas.ibm.com

Any ENTRY statement in a Cobol program is detected by the syntactic analyzer as unreacheable code when previous code contains a GOBACK.

However, a program with an entry doesn't necessarily begin from the PROCEDURE DIVISION. Any ENTRY can be used as the program entry point instead. 

The syntax analyzer is expected to provide feedback to the developer that is useful to identify compilation errors in advance. The actual behavior of the analyzer is useless for that purpose when an ENTRY is in place for two reasons. First, the "unreachable code" message warns the developer about an issue that will not produce any error during compilation. Second, the whole ENTRY code (and worse than that, any paragraph invoked from the ENTRY) is totally underlined and full of yellow markers at the right margin of the editor. This makes it impossible to identify the real issues the program has and, thus, the analyzer is not effective.

Idea priority High