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.
No reply. Canceling RFE.
Feel free to open a new RFE if you are able to answer our previous questions.
Thanks.
Any updates regarding the 10 Apr 2019 comment?
Hi Gerald,
Any thoughts on our comment from 10 Apr 2019? Thanks.
IGYPS2160 in case of referencing a file record data-item as sending operand should be a Warning, not a Severe.
Attachment (Description): Result of running sample programme TestPtrF
Attachment (Description): JCL to run sample program TestPtrF
Attachment (Description): Sample programme : assign address of data-item in file record to pointer
An other workaround is to use a nested program as explained in sample "TestPtrF" in attachments.
Hi, even if we did ADDRESS OF according to the Standard, it would be limited to 01 record, 01 data items and the rule would be valid only until the next I/O. Would that be useful ?
Since one can access the data items in the file sections directly (MOVE file-item TO local-storage-item), the compiler must already establish addressability for data items in file sections.
Therefore, ADDRESS OF should be able to return the address of the data item instead of its content.
I assume these addresses are stable as long as no IO statements are performed on the file, so after a READ statement one would have to obtain the current address of any data item in the corresponding file section again with ADDRESS OF.
Whether the record format is fixed or variable does not matter in this context. If single records contain fields of varying length, then the field addresses vary as well, regardless of the RECFM.
There are IBM interfaces like BBOA1SRQ (http://www.ibm.com/support/knowledgecenter/en/SS7K4U_8.5.5/com.ibm.websphere.zseries.doc/ae/cdat_olaapis.html#cdat_olaapis__sendrequest) which require a pointer to the data item (requestdata).
The straight forward way would be via "SET requestdata TO ADDRESS OF data-item", but that does not work when data-item is in a FILE SECTION.
A workaround would be to copy the data item to the LOCAL STORAGE SECTION and then get the ADDRESS OF the data item in local storage, but that would mean copying potentially several kilobytes just to get their address.
This would be hard to figure out because the address of a file section tends to float.
For fixed format, why would this method be used? Couldn't you instead declare the record length and data and let the compiler figure it out?
Can't this be done in pure COBOL?
This RFE is under consideration and requires more time to evaluate.