You don't need distribution services since there is no SNA to configure. EE is included with the TCP/IP utilities and object connect. We are only discussing SAVRSTxxx and STRPASTHR, not all the other SNA components. If you need them do it, it's still simple!

You may need the directory entries but most folks have those anyway and if not a reasonably simple CL program can add them for you.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 9/18/2012 8:06 AM, rob@xxxxxxxxx wrote:
Perhaps Jim was thinking of a migration from AnyNet to EE and figured the
above was already configured.

No additional option of SS1? I saw 22 for SAVRST... but isn't EE a
different option?

I did see this:

Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>, Date: 09/18/2012 08:39 AM Subject: Re: SAVRSTxxx and STRPASTHR Sent by: midrange-l-bounces@xxxxxxxxxxxx Larry is the undisputed expert here, but this is what I look for: (V7) 1) Object connect is loaded (5770SS1 option 22) 2) Changes to the network attributes: NODETYPE(*NETNODE), ALWHPRTWR(*YES), and VRTAUTODEV(100) 3) Add an APPC controller (Larry and I always call it ENTERPRISE) link type (*VRTAPPN) 4) Add an APPC controller with linktype (*HPRIP) using the IP address of the remote box 5) Add an APPC device back to the first APPC controller That's the rough outline. There are a couple of details missing but that's the jist of it. Jim Oberholtzer Chief Technical Architect Agile Technology Architects On 9/18/2012 6:58 AM, Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx wrote:
> Care to elaborate on the setup requirements for SAVRSTxxx? I have my
> homegrown tool for this type of thing but I'm interested just in case I
> can get it setup. Then I can retire my tool lol.
> Thanks,
> Tommy Holden
> From: Jim Oberholtzer<midrangel@xxxxxxxxxxxxxxxxx>
> To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>,
> Date: 09/18/2012 06:53 AM
> Subject: SAVRSTxxx and STRPASTHR
> Sentby:midrange-l-bounces@xxxxxxxxxxxx
> A Recent thread about about V5R4 to V7 upgrade brought up the point
> below. While I don't dispute the sentiment of the note with respect to
> leave the old behind and move forward, I'm not sure I agree with the
> drop SAVRSTxxx in favor of Save, FTP, telnet, restore process either.
> Granted I'm not really all that good at networking but it occurs to me
> to set up pass through and SAVRSTxxx takes three (maybe four) changes to
> the network attributes, a controller description, and a device
> description for each node. If I can get it to work then anyone can.
> Since this is all running over TCP/IP, and works quite well over VPN
> connections (I use it every day in that environment), how is this bad?
> I get the get rid of SNA part, but the set up for this seems to me to be
> quite easy, reliable, fast, and gives folks what they want without undue
> systems management. Twenty minutes to set it up, maybe an IPL if
> network attributes need to change, and it's done. If I am wrong, what
> am I missing?
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
> On 9/18/2012 6:38 AM,rob@xxxxxxxxx wrote:
>> > Third option on point 2 (ANYNET). Stop using SNA. We did. The
>> > stuff was getting the last holdouts off of STRPASTHR and on to
>> > nicely wrapped "Tough shirt, try ftp" was given to those fond of
>> > SAVRSTOBJ. Along with an encouragement on our Change Management
>> > We used to have a bunch of SNDNETF's back when we had multiple ERP
>> > machines communicating to a central EDI machine but we had weaned
off of
>> > that long ago.
> --

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page