Care to elaborate on the setup requirements for SAVRSTxxx? I have my own
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.
From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 09/18/2012 06:53 AM
Subject: SAVRSTxxx and STRPASTHR
Sent by: 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?
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 easy
stuff was getting the last holdouts off of STRPASTHR and on to TELNET. A
nicely wrapped "Tough shirt, try ftp" was given to those fond of
SAVRSTOBJ. Along with an encouragement on our Change Management System.
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.