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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Whilst this RFE is a valid COBOL Standard requirement, 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 IBM Enterprise COBOL for z/OS compiler release. Correspondingly this requirement is being declined at this point. The requirement will be kept in our internal RFE backlog. As we work towards becoming aligned with the COBOL Standard, this RFE might be reassessed in the future. You also have an opportunity to resubmit in 12 months time if you wish it to be reconsidered then.
For performance, promote data-item defined with a VALUE clause and never modified in procedure as CONSTANT (and use value in immediate assembler instructions) unless if data-item has a VOLATILE attribute (Cobol V5+).
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
This is a valid feature and inline with our multi-year strategy. We are accepting this RFE and will update it once it has been put into plan.
ninjanken, are you thinking something like this?
WORKING-STORAGE SECTION.
01 status-table.
05 status-ent.
10 PIC X VALUE '0'.
10 PIC X(5) VALUE 'ACTV'.
05.
10 PIC X VALUE '1'.
10 PIC X(5) VALUE 'DEL'.
05.
10 PIC X VALUE '2'.
10 PIC X(5) VALUE 'CAPT'.
01 se-max PIC 9(4) COMP.
LINKAGE SECTION.
01 status-entries.
05 status-entry OCCURS UNBOUNDED
DEPENDING ON se-max
INDEXED BY seidx.
10 se-status-code PIC X.
10 se-status PIC X(5).
PROCEDURE DIVISION.
COMPUTE se-max = LENGTH OF status-table
/ LENGTH OF status-ent
SET ADDRESS OF status-entries
TO ADDRESS OF status-table
DISPLAY se-max
Now that you bring it up I have used something like this before.
Still think having a calculated constant would make this simpler, however. Plus this is not the only use case; its just one example.
Thanks for your comments!
Frank
ninjanken, are you thinking something like this?
WORKING-STORAGE SECTION.
01 status-table.
05 status-ent.
10 PIC X VALUE '0'.
10 PIC X(5) VALUE 'ACTV'.
05.
10 PIC X VALUE '1'.
10 PIC X(5) VALUE 'DEL'.
05.
10 PIC X VALUE '2'.
10 PIC X(5) VALUE 'CAPT'.
01 se-max PIC 9(4) COMP.
LINKAGE SECTION.
01 status-entries.
05 status-entry OCCURS UNBOUNDED
DEPENDING ON se-max
INDEXED BY seidx.
10 se-status-code PIC X.
10 se-status PIC X(5).
PROCEDURE DIVISION.
COMPUTE se-max = LENGTH OF status-table
/ LENGTH OF status-ent
SET ADDRESS OF status-entries
TO ADDRESS OF status-table
DISPLAY se-max
Now that you bring it up I have used something like this before.
Still think having a calculated constant would make this simpler, however. Plus this is not the only use case; its just one example.
Thanks for your comments!
Frank
Doesn't the OCCURS DEPENDING CLAUSE already address this
status-entry OCCURS 0 to 9999 TIMES DEPENDING ON SE-MAX
The tima has come for cobol to have such a functionality. ;-)
Added to GSE ADL watchlist.