RE: Consolidating multiple iSeries systems...

Hi Mike

You might want to consider having an IASP for each company/system. You'd
still have to solve the duplicate user profile issues but program libraries
with the same name could co-exist in different IASP's.

The SETASPGRP command would allow you to "Switch" between companies although
you'd have to give this some thought.

If having the data and program libraries physically separate at some level
(is useful as opposed to having then logically separated only by library
name) then the IASP approach might work for you.

If you seriously considered the LPAR solution then this indicates the IASP
is well worth considering.

Whichever way you go you're going to do a lot of work with Job descriptions
and user profiles.

Were there communications processes (e.g. DDM, remote data queues) between
the systems ?

Regards
Evan Harris


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Turnidge
Sent: Saturday, 1 March 2008 9:36 a.m.
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