MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » September 2012

Re: SAVRSTxxx and STRPASTHR



fixed

Rob,

I absolutely agree with you on the change management aspects of the discussion, but that's a management issue not a technical one. Enterprise Extenders is just too easy particularly on a box with LPAR where you use the virtual Ethernet to move things.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 9/18/2012 7:02 AM, rob@xxxxxxxxx wrote:
The fact that you've done this a bazillion times.

As a side, when people move stuff from development to production outside
of the change management system I invariably get a call "I can't delete
this program I restored, can you do it for me?" I believe their
intentions are good, restore it in a test library and test on real
production data instead of a full restore of their production data on the
development machine. (Why, I don't know.) And since they have *ALLOBJ on
the development machine (and I'm not allowed to change that) and they
don't on production they keep stepping on their winkie.


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 http://www.dekko.com From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>, Date: 09/18/2012 07:56 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? 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 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.
--





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

This mailing list archive is Copyright 1997-2014 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