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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
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
After careful consideration, we have come to the conclusion that we will have to reject this requirement.
Rationale for rejecting this item:
COBOL calls DFSMS macros to do physical I/O for all files. The logging of SMF records is done by DFSMS, not directly by COBOL. COBOL leverages the same behavior of the I/O macros as in other non-COBOL the programs.
For VSAM file, when DFSMS opens a file by setting the flag bit "OUT", it can support both input and output operations. A running program may potentially contain reads. This should be taken into account would using the statistic records. The same logging could have happen from a non-COBOL program.
Thanks.
We have received the files and continuing to investigate.
I've recreate the problem with a simple Cobol program which open the file in I-O, read a record and write a record, and the flag SMF62MC1 is set to x'9A', which means '0' in the bit INPUT Processing. I attach, the source of the program (source.pgm.txt), the jcl (JCL.pgm.txt), record smf 62 in TRS format(smf62.trs) and dump dfdss of the vsam file in trs format (dfdss.vsam.trs).
The job name is SISILE25 and the record is the last one in the file (number 35).
Hi, can you please provide us with a test case to show the problem ? We looked at our code. We are using the "right" macro.
Also, are you using any temp files (optional files).
Any change here might effect other I/O's. So we have to be careful with this.
IBM is continuing to evaluate this RFE and will update it once we have more info.