Re: Check List / Documents on Data Migration Between Iseries

We've consolidated 15 iSeries on to one.  We still have 4 others for 
special purpose.  The library names for the user data on all the machines 
were different.  This allowed us to bring a copy onto the development 
machine and not worry about conflicts.  Thus that concern when 
consolidating was not an issue.
At that time we started naming our printers different.  Instead of P1, P2 
and the like, we started naming them P##x##
first ## was the company number, x was kind of like a printer type, ## was 
a printer number for that company.
We always had central control of user profiles, thus there were no 
duplicates.  We just had to make sure that they were all on the big box.
Don't forget the stuff in WRKFLR or the stuff in WRKLNK '/*'.  Many 
people, having come over on the Mayflower, assume that if the data is not 
in a library, in a pf or a lf, then it's expendable.
You could use SNADS and SNDNETSPLF to duplicate spool files to the target. 
 Or you could use this as an opportune time to clean those up.

If you have lots of objects you may run into a problem in which there is a 
limit to the number of objects one person may own.  For example, all of 
your data may be owned by one group profile.  We ran into this problem. 
Also, we decided that each division should have their own group profile 
for security reasons.  The number of object issue just gave spark to get 
the security implemented.  That started us having issues with users who 
access multiple databases.  But the number of them, (not counting systems) 
could probably be counted on one hand.  Thus they might have a ROB13, 
ROB23, ... user profile in which the ## is the division number.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




KSI <ksiwebsphere@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/25/2003 01:50 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     midrange-l@xxxxxxxxxxxx
        cc: 
        Fax to: 
        Subject:        Check List / Documents on Data Migration Between 
Iseries


Hello Everybody,

Shortly, I'm carrying out Data Migration between
multiple iSeries servers to a single iSeries server. 
Is there any checklist/document available (strictly
for iSeries) for carrying out the data migration
successfully so that i'll not miss anything in the due
process.  Please mail me the checklist/document
available or send me the URL so that i can download
the documents from there.

Any help on this will be highly appreciated.

Also, wanted to let you know that this group is
amazing.

LOL
ksi

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/
_______________________________________________
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.