On Wed, 14 Jul 2010 08:29:36 -0500, Ken Hansen 
<[email protected]> wrote:

>In former times,  Coupling Facility CPU utilizations were reported as High 
values (90-100% busy).   This made it difficult to determine fail-over 
capabilities and was later amended by an IBM APAR the produced more 
realistic results. But in returning to this topic,  I am seeing the TYPE70 
records 
showing the ICF as 100% busy (z/OS 1.9) and the RMF Reports Coupling 
Facility reports showing the same thing.
>
>Yet when I go to the TYPE74 structure records, I see low CPU utilization 
time values that indicate the Coupling Facility is much less busy (5% to 18% 
of the RMF interval time).
>
>Can anyone tell me how I can reconcile this deference?

Short answer:  Use the type 74's, as RMF does.

Our RMF Mon III CF Report shows:

 CF Policy: NORMAL      Activated at: 05/06/10 18.15.31  
                                                         
 ----- Coupling Facility ------  ------ Processor -------
 Name      Type  Model Lvl  Dyn  Util% Def Shr Wgt Effect
                                                         
 CF01      2097    E40  16  OFF   2.8    1   1    950   1.0 
 CF02      2097    E40  16  OFF   1.1    1   0            1.0 

This data comes from the type 74's, as does SYSRPTS(CF), so I don't 
understand your statement:
"I am seeing the TYPE70 records showing the ICF as 100% busy (z/OS 1.9) 
and the RMF Reports Coupling Facility reports showing the same thing."

>From RMF on SYSRPTS:

CF | NOCF
Specifies the Coupling Facility Activity report.    To obtain an entire 
Coupling 
Facility Activity report, ensure that you supply the Postprocessor with a 
complete set of SMF 74 subtype 4 records from all systems in the sysplex

Regards,
Art Gutowski
Ford Motor Company

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to