It's actually pretty easy.
Shut off the server, put in the network card. reboot, and it should find it OK on it's own.
from the command line:
CFGTCP
(note there's probably a shortcut for this but I couldn't come up with it!)
1 for add interface...
here's an example of ours
[red]
Internet address . . . . . . . . . : 10.10.3.2
Subnet mask . . . . . . . . . . . : 255.255.0.0
Line description . . . . . . . . . : ETHLINE
Line type . . . . . . . . . . . . : *ELAN
Associated local interface . . . . : *NONE
Interface status . . . . . . . . . : Active
Type of service . . . . . . . . . : *MAXRLB
Maximum transmission unit . . . . : *LIND
Automatic start . . . . . . . . . : *YES
[/red]
Note that you can also do this using Client Access Express, but since I started on the command line I'm sort of a purist at this point, and there's no turning back!
From there you can configure the services you want to start by going through the various options in "
go network".
At the end all you need to do is
STR TCP. You'll see all the services starting up at that point.
From there you should try to ping a host on the same subnet. If you can ping then you have it set!
Domain information can be done from the CFGTCP menu as well.
More information from the AS/400 information center for configuring with client access.
Hope this helps you! J.R. Juiliano
Information Systems Specialist
Tri-City Emergency Medical Group