Re: Consolidating multiple iSeries systems...

["David Turnidge" <daveturnidge@xxxxxxxxx>]

Well, that's been rejected out of hand  because of the hardware costs...

On Fri, Feb 29, 2008 at 2:39 PM, Mike Cunningham <mcunning@xxxxxxx> wrote:

> Run an LPAR for each of your current systems
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
> midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Turnidge
> Sent: Friday, February 29, 2008 3:36 PM
> To: Midrange Systems Technical Discussion
> Subject: Consolidating multiple iSeries systems...
>
> Management has chosen to get off the mid-range and go to .NET based
> systems.
> I have been tasked with finding out what issues there will be to
> consolidate
> each of the iSeries data on one system for historical look-up purposes.
>
> Fortunately, our data libraries are uniquely named, so that shouldn't be a
> problem. Unfortunately, our program libraries are named the same, and
> there
> are programs with the same name but different base source, but I think I
> have a way around that.
>
> So far I have come up with a number of issues, in no particular order:
>
> 1)      Will need to analyze all of our Robot jobs to determine what is
> company specific and still required.
>
> 2)      Will need to set up user profiles for each user and resolve the
> few
> cases of duplication.
>
> a.       Is there a way to automate this?
>
> b.      Will need a way for certain users to go from company to company.
> (Multiple profiles?)
>
> c.       Will need a way for programmers to go from company to company.
> (Software controlled from command line?)
>
> 3)      Need to create device descriptions and resolve duplicate names.
> I'm
> thinking as much as possible the device names should be the same as they
> are
> now.
>
> 4)      What to do with job descriptions in QGPL that have library lists.
> Have multiple QGPLxx libraries and control it by library list? I think
> QGPL
> might hold more issues than are obvious.
>
> 5)      Programs with hard coded library names.
>
> I am looking for any other ideas that you might have. Especially if you
> have
> already had to do this process and can warn of precipices that are ahead
> of
> me...?
>
> Thank you,
>
> Dave
> --
> 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.