Your data library are all unique, great. For your application library, I
suggest adding a suffix that identify the company (APPLIB001, APPLIB002
...).
You will need to make sure that you alway use the library list to
locate programs or files. If some library name are hard coded, you will
need to change that.
2.a) none that I know of. I suggest using a prefix for each company. we
operate over 200 companies on 7 production partition. Our users are
named U999xxxxxx where 999 is a company number. This way, there can be
no conflict. I suggest changing the profile on the different Iseries
before merging them.
2.b) one usrer profile by company is the easiest way to go. Again,
using the U999xxxxxx naming method, the can be less of a hassle for the
users (U001DROB, U002DROB ...). Also, this minimize any change to your
programs.
If you want to use a single profile, you will need a program to switch
a user from company to company. that means changing the library list.
This is not that hard but there is the security factor (user xxx is
allowed company 1 and 2 but not 3 and 4 ...)
2.c) same as 2.b
3) I am gessing you are talking printer here. Again, the best solution
is to put the company number in the name (Ex: P001xxx).
4) again here, the best solution is to make sure that there are no
duplicate named before the merge. Rename your jobd to incorporate the
company number (Ex: JOBD123)
5) you have to find and change those
Other points to consider
- If you are using Fax on the Iseries. You may have an issue with long
distance call (a specific number was local before the merge but long
distance after)
- If all of your Iseries were not in the same time zone, that will
become an issue also.
Hope this help a little
Good luck
"David Turnidge" <daveturnidge@xxxxxxxxx> 2008-02-29 15:35 >>>
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
midrange.com
