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
I did see this:
-- 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 http://www.dekko.com 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 myown
> homegrown tool for this type of thing but I'm interested just in case Ieasy
> can get it setup. Then I can retire my tool lol.
> 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
> 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
TELNET. A>> > stuff was getting the last holdouts off of STRPASTHR and on to
System.>> > nicely wrapped "Tough shirt, try ftp" was given to those fond of
>> > SAVRSTOBJ. Along with an encouragement on our Change Management
off of>> > 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
--> -->> > that long ago.
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact