Manage Learn to apply best practices and optimize your operations.

Connect the dots: Get your iSeries servers talking to one another

Need to transfer information from one iSeries to another? OS/400 has a tool -- Opti-Connect -- built right in that makes transfers easy and fast.

So, you have two iSeries or AS/400 servers (or more) and you need to transfer boatloads of information between the two systems. We have these cool-looking tape drives, but good luck separating your operator from one of those expensive cartridges to transfer programs and data to the second iSeries. Normally the iSeries servers are within a network -- usually a DARN FAST ONE -- so who needs a tape when you can transfer information in seconds between your two systems. It's probably faster then it normally takes to simply format the tape.

Here's how we approach this problem:

  1. Create a save file SOMEPLACE
  2. Save your stuff to the save file
  3. FTP (as long as this server is on) the file to the second iSeries using a Binary Transfer
  4. Restore your stuff

Wow, that sounds like a lot of work. What if I told you since OS/400 Version 3.1 we've had some FREE tools built in to the 400 that do EXACTLY THAT? Where are those tools? In the Opti-Connect product.

Unfortunately, IBM doesn't make the installation of free tools that easy. Here's what you need to do:

Make sure the two servers are communicating using SNA methodologies. WAIT -- we're communicating using TCP/IP. What do we do? First, Anynet support NEEDS to be functioning.

What you need to do is gather information, so perform a DSPNETA (type DSPNETA and ENTER on a command line) on your SOURCE iSeries.

Now do the SAME thing on the corresponding iSeries.

Then perform the following:
CFGTCP[enter] Option 10 ("Work with TCP/IP host table entries") [ENTER]

Now add the following entry to the Host Table for the REMOTE system.

Host Name = Remote Host Name
RMTNETID = Remote Network ID
So -- that would look like this:

Create one on the server you're CURRENTLY SIGNED ON TO pointing at the REMOTE server.

The SNA.IBM.COM is required for the Anynet connection. (This is hard coded. DON'T GET CREATIVE!)

Next, create a Controller for ANYNET…CRTCTLAPPC and hit Enter.


Now the fun bits:

Type WRKCFGL and hit Enter.


The REMOTE location stuff is FROM THE REMOTE DSPNETA. To verify if this is functioning properly, do the following:

Vary ON the APPC controller you've created


and verify that it's on.

NETSTAT option 3, look for APPCove -- or Port 397.

OK, Anynet is there. Now what?

WRKMODD QSOCCT (mode for Object Connect) and hit Enter.

Then perform the following command:


Make sure the QCMN Subsystem is started, then Start the mode description for Object Connect.


Where TARGET name = the name of the target system

Are you exhausted? When you're done you'll get the following commands:

SAVRST -- IFS Save & Restore onto the remote system
SAVRSTOBJ -- Save Restore Objects
SAVRSTLIB -- Save Restore Library
SAVRSTCFG -- Save Restore Configuration
SAVRSTDLO -- Save Restore Document Library Objects
SAVRSTCHG -- Save Restore CHANGED Objects…

It's cool and lazy!

About the author: Andrew Borts is webmaster at United Auto Insurance Group in North Miami, Fla. He is often a frequent speaker at COMMON and is past president of The Southern National Users Group, an iSeries-AS/400 user group based in Deerfield Beach, Fla.


Dig Deeper on Remote Access to iSeries