Re: 6.1 and 7.1

[John McKee <jmmckee@xxxxxxxxxxxxxx>]

Disks are 4326.  Unit 1 67.6 used.  I have been working with 6.1 and
7.1 MTU as well as i5/OS and related software - Installing Upgrading
or deletingi5/OS...

Somewhere in there was an example of the space required for upgrading
from an image catalog.  That example came in at 10GB.  Makes the LS
kind of tight.  If LS is insufficient, the suggested work-around was
STRASPBAL to move dat from unit 1.  Seeing the reference that image
catalog was not spread was only reason I commented.  No media yet.  No
idea, yet, if LS has enough free space.

I run into the same issue with Linux.  All disks are included in
Logical Volume Manager.  Except for a small amount used for boot and
upgrade which can't be included in LVM.  The i makes management of
disks easier, so far, than the LVM tools do.  Just never thought about
the >why< concerning location of image catalog before.  Makes perfect
sense.


There are temp applied PTFs that I will perm apply.  Not sure how much
that will get back on LS.


John McKee

On Fri, Jun 21, 2013 at 6:38 AM,  <rob@xxxxxxxxx> wrote:
> <snip>
> 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.
> </snip>
> Is this a problem?  Yes, if you're running IBM i on just two mirrored 17GB
> drives near capacity (if even possible) then yes that's an issue.  But a
> four drive RAID 5 set of 70GB drives at 70% capacity leaves 15.8gb free.
> If space is an issue, see:
> http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzahc/freeingupspaceintheload-sourcediskunitforanimagecatalog.htm
>
>
> 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:   John McKee <jmmckee@xxxxxxxxxxxxxx>
> To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
> Date:   06/20/2013 11:46 PM
> Subject:        Re: 6.1 and 7.1
> Sent by:        midrange-l-bounces@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.