>How fast can it be if well tuned and configured and with the best >hardware options?
FAST. >If it's not going to be faster than TCPIP, i.e. turn around times of less >than a milliSecond, then it has no advantage over TCPIP and has the >drawback that it doesn't work to non-mainframes. >We need to keep TCPIP to communicate off the mainframe. >Is there any point to having XCF communications between LPARs or would >TCPIP do just as well for that? Most of this was already answered, and as usual the answer is 'it depends'. On your hardware configuration, for instance. On distances between boxes participating in the same sysplex. On XCF message sizes. On how busy any of your participating systems are. There is no canned answer 'it will be faster than TCPIP'. Or 'the time will be longer'. Or 'the time is smaller than a millisecond.' Our average GRS structure response time is less than 0.008ms. But that's GRS (almost no data transfer, cf on the same box as the lpar). The distant lpar connected to the same structure over 25km distance has an average sync response time of about 0.2ms. Asynch response time goes up to 1.1ms. If this application you're talking about is for customers, you can assume that response times will vary greatly, depending on how much hardware is thrown at XCF. Regards, Barbara Nitz -- Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games! http://games.entertainment.gmx.net/de/entertainment/games/free ---------------------------------------------------------------------- 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
