System information

54
AS/400 IBM Network Station: Techniques for Deployment in a WAN
Release 3 boots about as fast as previous releases, even though more
data and function are sent. Much of the data sent is compressed.
Switches, routers and gateways can cause problems. Ensure your
Network Administrator is involved in the implementation.
For 6180 twinax attached Network Stations, best performance is obtained
if all Express Datastream enabled devices are on the same cable,
excluding older, non-Express capable devices.
When Express devices are attached to a single workstation controller, best
performance is obtained by load balancing those devices. That is, half the
devices should be connected to cable ports 0 through 3, and the other half
should be connected to ports 4 through 7.
5250 Application Performance on the AS/400 System
This section provides the 5250 application performance conclusions for the
Network Servers:
In general, the 100, 300 and 1000 all perform equally.
Migrating from LAN attached SNA Client/Access PCs will probably use
more CPU (about 17%) to run the same 5250 applications.
LAN attached TCP/IP Client/Access PCs will use about the same CPU as
IBM Network Stations when running the same 5250 applications.
Local twinax attached NPTs to IBM Network Stations migration will
probably use more CPU (about 27%) to run the same 5250 applications.
Browsers
This section provides the browser conclusions for the Network Servers:
In general, the 100, 300 and 1000 all perform equally.
Poor performance is obtained when both socks and proxy are configured.
Only one should be used.
Never use disk caching.
Java Virtual Machine
This section provides the Java Virtual Machine conclusions for the Network
Servers:
The Series 100 should not be used for Java.
The Series 300 can be used for limited, lightweight Java.
The Series 1000 is for Java; however, since Java hasn't fully matured and
can be used for many, varied applications, customers should insure that
their Java application and the 1000 are compatible.