|
Perhaps Pete. Then again, learning all there is to know about Enterprise
Extenders to limp along a dead technology seems like a wasted effort to
me.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Pete Massiello" <pmassiello-ml@xxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 06/06/2010 10:40 AM
Subject: RE: Upgrade to 6.1 or jump to 7.1 ?
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Rob,
While I think this is the right option for you, it
doesn't always work for every customer. Especially those smaller shops who
don't have the talent and resources to make the kind of modifications that
you describe below.
Pete
--
Pete Massiello
iTech Solutions
http://www.itechsol.com
Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutions on LinkedIn:
http://www.linkedin.com/groups?gid=2206093
iTech Solutions because IBM i (AS/400s) didn't come with System
Administrators
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, June 04, 2010 3:05 PM
To: Midrange Systems Technical Discussion
Subject: Re: Upgrade to 6.1 or jump to 7.1 ?
I just didn't care. I ignored Enterprise Extenders and told our team to
come up with TCP/IP replacements for SAVRST, SAVRSTOBJ, SAVRSTLIB. Who
needs STRPASTHR when you have TELNET? SNDNETF can be replaced with FTP.
There are alternatives for SNDNETSPLF. Other than that, who needs it?
SNDDST? Replaced.
Have it buried in your code? That's what the Change Command exit point is
for. We just rooted it out of our code. Used the exit point for awhile
to catch ones we might have missed. Heck, fire up the exit point now if
only to log usage.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Rameez Raza <rameraza@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 06/04/2010 02:51 PM
Subject: Re: Upgrade to 6.1 or jump to 7.1 ?
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Hi ,
Anynet is not supported over IBM i V.7. Here is the note from Memo to user
for V7
*
AnyNet no longer supported
*
Starting in i 7.1, AnyNet® (a method used to run SNA communications
traffic
over IP) is no longer
supported. Users of AnyNet are encouraged to migrate to Enterprise
Extenders
as a replacement. For
information about migrating to Enterprise Extenders from AnyNet, see the
Migrating from AnyNet to
Enterprise Extender topic in the IBM i Information Center.
Regard
Rameez
On Wed, Jun 2, 2010 at 1:48 PM, Luis Rodriguez <luisro58@xxxxxxxxx> wrote:
As I see it, the latest IBM i releases have been quite stable so, ifthere
is not other pressing business concerns (compatibility issues, needednow,
features (like AnyNet), programming changes, etc), Why don't go for the
latest?
Regards,
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
On Wed, Jun 2, 2010 at 1:06 PM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx>wrote:
> I've been pondering an upgrade from v5r4 myself.
Does it make sense to go to 6.1 at this point, or should I go straight
to 7.1?
In my case, I'm not changing hardware at all, just updating the OS. I
know I'll have to run ANZOBJCVN and all that good stuff -- no question
about that.
What I want to know is whether skipping to 7.1 is a good idea right
areor should I be more conservative and go to 6.1?
On 6/2/2010 10:46 AM, Pete Helgren wrote:
I have a customer that I have scheduled for some maintenance. They
pointmoving from 35GB to 70GB drives and I'd like to move them to a more
current OS release. The question is: Should I skip 6.1 at this
storageand just take them to 7.1? They are currently running V5R4M0. They
have a model 520, processor feature 7355. They have a 573D-001
drivescontroller.
The plan is to do a Save 21 (twice). Remove and label the 35GB
strikes),(so they can be re-installed in the correct order if disaster
listlistrestore the Save 21 and then upgrade them to either 6.1 or 7.1.
What else do I need to add to the mix?
Thanks,
Pete
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.