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.
Hi,
I am disappointed by your decision to decline this request, even though 2 years ago (see below) you did agree to implement it.
Even so, I am optimistic that in the not too distant future you will reassess this request and put the COBOL CICS program listing (back) in line with the actual program, as it was many versions and years ago.
I wish you Happy Holidays and a Happy and Healthy New Year.
Danny Amir
IBM Enterprise COBOL for z/OS is a continuous delivery offering, and aims to satisfy the needs of a rapidly evolving market segment. Product strategy evolves and requirements are continuously evaluated against that strategy. This RFE has recently been reappraised against the wider product strategy and does not fall into IBMs delivery plans for the next 12 month. Whilst this RFE might be valid and we might look to deliver longer term, this RFE is being rejected at this time. The requirement will be kept in our internal RFE backlog and might be reassessed in the future.
This RFE is being accepted and will be updated once put into plan.
Without the items in the listing dump reading tools give misleading information as to what was passed in for verifying caller to the called module.
Thanks, Jay
When programmers develop and test CICS applications, particularly when they attempt to resolve a problem in a CICS application, it is important that they have a clear and accurate view of the program and of it's interface with other programs. Currently the program listing is misleading because:
A. DFHEIBLK and its layout do not appear in the LINKAGE SECTION, even though it is received as a parameter.
B. DFHEIBLK does not appear on the PROCEDURE DIVISION statement, even though it was sent by the calling program as the first parameter and received as such by the current program.
C. Often there will be reference in the source code to "EIB" fields but the programmer will not find the definition of those fields in any DATA DIVISION section, as they would any other data item.
The comments above apply to the compile listing printed at compile time and also to the listing displayed by Program Development Tools, such as the COBOL Explorer in FAZ. A similar problem exists with Debug Tool. When using the 3270 interface DFHEIBLK is easily monitored but not so using the RDz interface.
In short, I would say that the business case is "Make life easier for the programmer by displaying the program source clearly and fully with all parts in their native position in relation to the rest of the program source".
When programmers develop and test CICS applications, particularly when they attempt to resolve a problem in a CICS application, it is important that they have a clear and accurate view of the program and of it's interface with other programs. Currently the program listing is misleading because:
A. DFHEIBLK and its layout do not appear in the LINKAGE SECTION, even though it is received as a parameter.
B. DFHEIBLK does not appear on the PROCEDURE DIVISION statement, even though it was sent by the calling program as the first parameter and received as such by the current program.
C. Often there will be reference in the source code to "EIB" fields but the programmer will not find the definition of those fields in any DATA DIVISION section, as they would any other data item.
The comments above apply to the compile listing printed at compile time and also to the listing displayed by Program Development Tools, such as the COBOL Explorer in FAZ. A similar problem exists with Debug Tool. When using the 3270 interface DFHEIBLK is easily monitored but not so using the RDz interface.
In short, I would say that the business case is "Make life easier for the programmer by displaying the program source clearly and fully with all parts in their native position in relation to the rest of the program source".
Hi, can you please elaborate a bit more on the business case that you are trying to resolve with this RFE?
This RFE is still being investigated further.
Hi,
Inserted data (and code) are also needed for debug tools based on listing informations.
Denis