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.
Hi there,
Initially implemented in z/OS Connect Extract/Forwarding in soon to be released APAR PH53070.
Many thanks,
Louisa
Hi Mike,
Here is the response from the development team:
Yes, we would provide the byte count in the individual extract Recap reports together with the record count. As you can appreciate, we have several extract types that would need to also provide the byte count, for product consistency. It would not be practical to modify them all at once for the sake of this small enhancement. Although the development phase would be small, there will be a significant impact and effort on our automated testing, plus packaging etc. For this reason, I would advocate a phased implementation where each extract is enhanced when there’s an opportunity to do so.
Regarding inclusion of TOTAL byte and record count in the SYSPRINT file EOJ messages, as Mike requested, it would be misleading to provide a total byte and record count until ALL the extracts have been enhanced to display them in their Recap reports. I therefore suggest this requirement be differed until such time.
So, in summary, we would provide the individual extract byte count in the recap report when practical, but not in the SYSPRINT file until all extracts are enhanced.
Please let me know if you have any concerns regarding this.
Louisa
Also, can you show the counts in two places?
Currently you supply stats at the end of each resource showing the record count, such as:
CPAOSX02 Extract has completed successfully
Data Set Name . . . . SYSCI.RW474.CIPA.RSSAMP.TRANCLAS
Record count . . . . 4,916
And also at the end of the job:
CPA0218I Record processing for SMF File SMFIN901 has started
CPA0220I SMF records for System PR18 start at 11/23/2022 23:50:02:17
CPA0222I SMF records for System PR18 end at 11/23/2022 00:47:03:36
CPA0219I End of File processing for SMF File SMFIN901 has started
CPA0229I CICS PA has completed processing, RC=0
V5R4M0 14:14:16 1/26/2023 CICS Performance Analyzer
End of File Record Counts
Can you show the count of JSON bytes in both places?
After message CPAOSX02 to show an individual extract's numbers.
And also at end of job, to show the total bytes written for all of the extracts?
For both Extracts and Forwarding.
Thank you,
Mike Giaquinto
Hi Louisa,
I'm not sure how best to answer that question but I'll try. Currently we use both the "Extracts" and "Forwarding" for statistics. We run trials with Extracts to validate what we want to send, then switch to Forwarding. For now we are only sending "Statistics". So hopefully "Statistics" is what they are asking for?
Mike
Hi there,
Thank you for raising this idea, the development team have looked into it and they have an outstanding question around which extract reports that you run? - for example JSON. They would like to understand which reports need to be modified with this information.
Looking forward to hearing a response,
Louisa Seers