03/05/2021
Refresh this Rexx because i just used it to evaluate the impact of Asynchronous Duplexed Locking.
Very useful IFCID , should be better known.
All the accounting figures grouped by Connection Type.
Update : Ziip figures and correction of bugs - validated figures with BMC Mainview Performance Reporter (V11 tested).
The first period recorded should be deleted (similar problem with all accumulated data: meaningful only if there is a figures for the start and the end period)
06/04/2017
There is a problem with this IFCID because all the presentations and even DB2 manuals or SDSNMACS and SDSNIVPD contents let think that this IFCID can be output to SMF. Which is wrong (maybe a bug ?) , because if you do -START TRACE(STAT) CLASS(9) DEST(SMF) , you will never find IFCID 369 in your SMF records ...
In fact, the only way to get it is with the READS commands.
Below is the code to do this. Just submit this Rexx, it will start the trace , read the contents of the OPx buffer every x minutes and then report the data in a report dataset.
Why IFCID369 is interesting ? You can have the same information by doing sums on your accounting report (Check my REX101 program)
IFCID369 is interesting on my site because there is too much accounting data that it has been decided that the accounting records from CICS are only kept from 9:00 to 10:00. This means that the only way to have some hints on the CPU on another period that is not 09:00 to 10:00 is to go to SMF30 and look at your CICS STC consumption. With IFCID369, i can have a lot of accounting data, not all (the most interesting figure, the number of getpage, is not there !!! in fact everything reported by DSNDQWAC) on all period, in an aggregated version.
Have fun !
Duc
Follow this link on Github to get the Rexx
No comments:
Post a Comment