Thanks, Jim. That's the way I've always done it too. And I will this time
unless someone comes up with reason(s) to do otherwise.

On Mon, Apr 4, 2011 at 4:15 PM, Jim Oberholtzer <midrangel@xxxxxxxxxx>wrote:


I install the client software (with service pack) without doing the
server side and all is well. This of course assumes your workstations
do not connect to i as a managed system.

The method in the MTU has been tested by IBM (and therefore is the IBM
recommended method) for every circumstance that they can think of.

I have connected LAN console with my 64bit Win7 box running V7 i Access
on it to a V5R4 box (in my office) with no problem so I'm not sure if
that's why it's recommended.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 4/4/2011 12:49 PM, Jeff Crosby wrote:

If I read the V7R1 MTU correctly, it suggests to install V7R1 i Access on
the IBM i before installing V7R1 of the OS.

I have always installed the new version of i Access_on all the PC's_
to installing the new version of the OS on the i, but unless my memory is
failing, I don't think I've installed the newer version of i Access on
IBM i prior to the install. Does everybody else do this?

The i Access Installation and Setup guide says I should install all the
following at that time:
5770-SS1 option 12
5770-XE1 base
5770-XW1 base,1

All of the above prior to the OS install. Really? Does that work?


-- Jeff Crosby VP Information Systems UniPro FoodService/Dilgard P.O.
Box 13369 Ft. Wayne, IN 46868-3369 260-422-7531
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].