z/OS is only using about half the subchannels that you defined (to mitigate
path busy conditions). I don't think you have a subchannel issue. Your sync
times are very nice. Your async times are horrific. That is most likely the
problem. Async completion time is influenced by such things as
-MAIN
Subject: Re: CF REPORT
Subchannel activity (report 2) includes all (roughly 18 million) requests from
the indicated source system to the CF, whereas structure activity (report 3)
only includes the (roughly 8 million) requests targeted to the indicated
structure. 12 million delayed out of a
>But but there are other causes for delay (such as dump serialization) that
>could be factors.
Apart from dump serialization, what else? CPU constraints in the CF? CF
internal serialization?
--
Peter Hunkeler
--
For IBM-MAIN s
Subchannel activity (report 2) includes all (roughly 18 million) requests from
the indicated source system to the CF, whereas structure activity (report 3)
only includes the (roughly 8 million) requests targeted to the indicated
structure. 12 million delayed out of all 18 million requests to t
Hi all
Below is our three CF reports at the same time.
Report 1. CFSYS from RMF MONIII
The Coupling Facility Systems (CF Systems) report (CFSYS) gives you information
about the distribution of coupling facility requests
among the systems and about the activities in the subchannels and paths
