Re: 6.1 and 7.1 -- MIDRANGE-L

My apologies for lack of detail. This is in IBMi Memo to Users 7.1.
Chapter 1 Read this first. Section: Plan for your Operations Console
installation or upgrade
Specifically this:

Prerequisite information for LAN attached Operations Console users
upgrading to, or installing, i 7.1:
You must comply with the following before upgrading or installing your
software (operating system,
Licensed Internal Code) to i 7.1:
1. For all upgrades and installations, you need to establish a
connection between the system and
Operations Console PC using the 11111111 (eight 1's) service tools
user ID. The default password for
this user ID is 11111111; however, this password might have been
changed following a previous
installation. This default user ID ensures a successful
reauthentication of the client connection to the
system. When you receive the operating system release upgrade, the
shipped service tools user IDs (except 11111111) are expired. To
reauthenticate the client connection to the system, enter the service
tools user ID of 11111111 (eight 1's) and either the default password
of eight 1's or the password you
might have previously created for this user ID. This is especially
important for automatic installations.
2. It is recommended that you update IBM i Access for Windows to i 7.1
before you upgrade the
operating system. For more information, see the Installing IBM i
Access for Windows topic in the
IBM i Information Center.
Note: Failure to comply with the above actions might prevent the
console from working correctly during
the upgrade or installation.

Says that shipped service tool ids are expired. Since we use a
locally created id, my thinking is that it isn't an issue. But, I
wanted to be sure I understood the implication. I believe upgrading
Client Access first bypasses problems, and that may have already been
a topic on the list. Or, at least was in a post. If so, I apologize
for not doing a better search.

John McKee

On Fri, Jun 21, 2013 at 6:44 AM, <rob@xxxxxxxxx> wrote:

John,

Where did you read
<snip>
"1) We have a pc running CA over hospital network as console. I read
that the connection would have to be revalidated. I am unclear as to
what that means."
</snip>
Context really matters. If you read it in the IBM i Access for Windows
Administrators Guide that will have a whole different meaning than if you
read it in "System 34 audit instructions upgraded to AS/400 by my big
three accounting firm" or the HIPAA Guide for IT Administrators.

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: "TheBorg" <sjl_abc@xxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx,
Date: 06/21/2013 01:24 AM
Subject: Re: 6.1 and 7.1
Sent by: midrange-l-bounces@xxxxxxxxxxxx

"Validation" means that the regulating or certifying authority (perhaps
the
FDA) requires that you have a test script which "validates" hardware and
software systems, and that it has passed the validation test. If you
don't
have a test script, one will need to be created, old test scripts may need

to be revised for additional testing, depending on what changed on the IBM
i
side.

More importantly than your console, however, your hospital applications
could require revalidation if any significant changes occur because of an
IBM i version upgrade.

For example, if you had to install a newer/different version of an
application you would probably required to revalidate that application,
and
if any of its interfaces to other applications were modified those
applications would need validation as well.

-sjl

"John McKee" wrote in message
news:mailman.1179.1371786364.9013.midrange-l@xxxxxxxxxxxx...

My boss initially felt one vendor would not work at 7.1, since 6.1 was
all that he saw on their website. He is following up on this. From
what I have read in the 7.1 and 6.1 MTUs, I don't see issues.

Maybe ill-informed questions, but I am unsure how to research this:

1) We have a pc running CA over hospital network as console. I read
that the connection would have to be revalidated. I am unclear as to
what that means.

2) Image catalog appears to be only created on the LS. Thus LS has to
have sufficient space for all DVD images. I thought that was
interesting.

John McKee

On Thu, Jun 20, 2013 at 10:05 PM, Pete Massiello - ML
<pmassiello-ml@xxxxxxxxxxxx> wrote:

How about versions of domino unsupported, AnyNet supported at 6.1 but

not

at 7.1, Different versions of Java supported for 6.1 & 7.1 with removal

of

option 10 at 7.1, Websphere 6.0 not supported at 7.1, but supported at
6.1. Operations Direct Console supported at 6.1 & not at 7.1, should I
continue?

Depending on which hardware you have, if it is old it could support 6.1,

but not 7.1.

I would highly recommend going to 7.1 in every upgrade, but there are
reasons to upgrade just to 6.1 if any of the above will cause you an
issue. This is why we have Memo to Users and the Upgrade roadmap. There

is more of a difference between 6.1 & 7.1 than just the DVD labels.

Pete

--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Thursday, June 20, 2013 3:06 PM
To: Midrange Systems Technical Discussion
Subject: 6.1 and 7.1

Object conversion at 6.1. What could possibly be a hurdle at 7.1? I
didn't want to hijack the thread where an upgrade from a v level is

being

discussed.

John McKee
--
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.