|
You might ask IBM. You might also see if you can find your SSA Sizing Questionairre and see if anything significant has changed since the last time you updated it. It is my understanding that a 5250 data screen whether on emulation or dumb terminal, can handle up to 2k of information sent and received vs. the screen, but the main issue is heads down keying. Many of our users have INV300 SFC300 just sitting there, not rapidly refreshing the info so no drain on the comm line. The speed of remote printers might be a consideration. Since you have a line right now that you plan to upgrade, take a look at IBM's performance measurement such as GO PM400 to see what kind of overloads you might have. Many years ago remote users complained to our CEO about performance, when we were on S/36. He asked me how significant it would improve with a faster comm line. I showed him the performance statistics ... stuff got slowed down only 10% of the time for us due to comm overload, so a faster comm line would be throwing money away with no appreciable improvement. The killer in the performance data was disk access arms, and it effected all users, HQ as well as remote. It only stands to reason with very few arms and very many users that would be a potential bottleneck. I explained CACHE to him and the bottom line was that he went along with my suggestion that we get more memory, and performance did dramatically improve for everyone. We used to be leased line but are now on simulated leased line through frame relay, where one line handles 400, PC, voice, and fax traffic, saving us a bundle on long distance costs between our sites. >Dear all, > >We're on v.6.1 MM. We are in the process of upgrading the leased line >between the AS/400 and a remote site. Are there any figures from any >parties, say SSA, telling the required bandwidth for each 5250 emulation >session and clien/server session conecting to BPCS? > >Regards, >Eric Tam - Al Macintyre (macwheel99@sigecom.net via Eudora)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.