Re: SAVRSTLIB - how to set up the network over ethernet

[Simon Coulter <shc@xxxxxxxxxxxxxxxxx>]

On Saturday, January 24, 2004, at 05:46  AM, Shea, David wrote:

> I have two AS/400's on my network.  Both with Ethernet.  One is
> 192.168.0.150, the second is at 192.168.0.151.  I want to use SAVRSTLIB
> across the two.  I'm having trouble finding the instructions for 
> setting
> things up.  SAVRSTLIB is asking for a remote location name.  This is 
> where
> I'm getting fuzzy.

The SAVRST series of commands requires an SNA connection. The remote 
location name is the unqualified SNA name for the target system.

If your network cannot handle SNA traffic you will have to enable 
AnyNet support on both systems. Do this with CHGNETA ALWANYNET(*YES). 
There is a small, probably unnoticeable, performance impact. This value 
takes effect without an IPL.

You will have to create APPC controllers and devices at each end. SNA 
is not difficult to configure. Here are sample configurations for your 
environment. Run DSPNETA on each system and note the values for:

        Local network ID
        Local control point name
        Default local location

Life will be easier if both systems have the same value for Local 
network ID. The default is APPN but you can change it as long as all 
*APPC controllers are varied off at the time.

The main tricks to successfully configuring SNA are:
1. Have all systems use the same network ID.
2. Ensure the RMTCPNAME in the controller description matches the 
LCLCPNAME in DSPNETA on the **REMOTE** system.
3. Ensure the RMTLOCNAME in the device description matches the 
LCLLOCNAME in DSPNETA on the **REMOTE** system.

Note that these points are not requirements; they just make things 
easier. It is quite possible to configure SNA between systems with 
disparate network IDs and use control point names and location names 
that are different from what DSPNETA shows by defining the controller 
and device correctly. I expect the following definitions will work fine 
for you. Change the SYSTEM15n values as appropriate for your 
environment.

On SYSTEM150:

CRTCTLAPPC CTLD(SYSTEM151) LINKTYPE(*ANYNETW) ONLINE(*YES) +
           RMTCPNAME(SYSTEM151) TEXT('Link to SYSTEM151')

CRTDEVAPPC DEVD(SYSTEM151) RMTLOCNAME(SYSTEM151) ONLINE(*YES) +
           CTL(SYSTEM(151) TEXT('LU link to SYSTEM151')

On SYSTEM151:

CRTCTLAPPC CTLD(SYSTEM150) LINKTYPE(*ANYNETW) ONLINE(*YES) +
           RMTCPNAME(SYSTEM150) TEXT('PU link to SYSTEM150')

CRTDEVAPPC DEVD(SYSTEM150) RMTLOCNAME(SYSTEM150) ONLINE(*YES) +
           CTL(SYSTEM(150) TEXT('LU link to SYSTEM150')

Vary the controllers and devices on at each system. They should go to 
active status. Verify the connection using STRPASTHR e.g., from 
SYSTEM150 run the command STRPASTHR SYSTEM151. You should a connection 
start and the sign-on screen for the remote system appear. Sign on and 
run ENDPASTHR to return to your original system.

If you cannot connect then error messages will appear in:
        o The job in which you ran STRPASTHR
        o QSYSOPR on the target system
        o QSYSOPR on the local system

Read the messages, follow the recovery, and try again. For example 
check the setting of the QPASTHRSVR system value on the target system, 
verify that the QPASVRP and QPASVRS jobs are active on the target (you 
can use STRCMNSVR to start them if necessary).

The main differences between SNA and TCP are that SNA requires a little 
more configuration effort and that SNA provides much better error 
feedback via the sense code (as long as you have the SNA Formats manual 
handy). TCP is easy to configure but fairly hopeless at telling you why 
things don't work.

I have SNA configured between an AS/400 using Token Ring and an AS/400 
using Ethernet and it works fine using AnyNet as the transport.

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------