I recommend to customers to have 3 transport classes: 1k/8k/20k (default to 20k). The big problem with XCF is if it has to resize messages. You can see that in RMF Post Processor Reports for each link from one System to every other for each transport you will see Fit, Small, Big numbers. Fit is good, lots of Big is not. You should see less than 20% of all messages being resized. If there is a lot of resizing, XCFAS will have a large amount of CPU and will be consuming a large % of your processor (over 30%). Also check RMF for no Buffer numbers. This is bad, too. The number for message specification should be at least 2,000 (not the default). If you don't specify enough, XCF utlimately returns an error to your applications using XCF services. Some applications have major issues when this happens. At Share, usually Joan Kelley (IBM in Pougkipsee) does the state of the art for CFs and includes XCF. She does not post on the Share site lately. I can send my Share presentations that discuss the joys of proper XCF specs, if you'd like. Oh, one other thing, set an auto command for every 15 minutes on every system to issue D XCF,CD,CLASS=ALL. It will show you what message sizes are being used and to where.
Hope this helps. ---------------------------------------------------------------------- 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
