[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

3707.0. "OA$SMART announcement" by UTRTSC::EISINK (Shadow earth) Wed Dec 29 1993 12:23

	I'm happy to announce OA$SMART. OA$SMART stands for
   
              Shared Mail Area Restruction Tool

   OA$SMART allows you to change the mail areas for both the SDAF and DOCDB 
   files.

   The main purpose is to easily merge several ALL-IN-1 IOS systems. It scans
   the SDAF or DOCB files and replaces the specified mail area for another 
   chosen mail area.

   Now you're able to choose in which mail area the separate mail areas can be
   placed.
   This tools is specially developed to migrate multiple ALL-IN-1 IOS systems 
   into one system. The development is paid for by the customer (two days) and 
   will be used for the migration of five systems into one. This event will 
   take place in late January 1994.

   If time allows I will expand the functionality so more than five ALL-IN-1 IOS
   system can be migrated into one. This will be done by expanding the several
   shared areas. This means that the pfr will allow you to change the range 
   between the lowest and the highest mail area directory into upper ranges.
   This to achieve an easy merge from SDAF'S located in the same mail area.

		regards,
                 Rob Eisink

T.R	Title	User	Personal Name	Date	Lines
3707.1	Ah, but....	GIDDAY::JOYCE	Okay, who moved the goalposts?	`Wed Dec 29 1993 21:56`	16
	Rob, This all sounds like a very neat bit of code but what concerns me is that you appear to be "marketting" it as a total solution. The SDAFs is just the tip of the ice-berg with an IOS merge; what about time management, user accounts, DDS ? And with V3 it gets worse with shared drawer access, groups, partition etc etc. (see note 2513.*). I would hate to think that anyone less familiar with ALL-IN-1 would read your note and think that all they've got to do to merge multiple IOS systems is run your tool (excellent though I'm sure it is!). I would be very interested to know how your customer approachs the rest of the merge (FIVE systems - aaarrrgggghhhh!!!) Andy
3707.2	Yes, not only mail	UTRTSC::EISINK	Shadow earth	`Thu Dec 30 1993 08:59`	68
	Hi Andy, it are 2.3 and 2.4 systems. We've made a plan, usernames are unique. I agree that mail is only a part, but I think the most important. The customer wanted to upgrade all their 2.3 systems (4) to 2.4 and transfer the user with the supplied features of ALL-IN-1. They calculated they should need more than 30 days, 4 users per day. By (in forehand) putting the mail users into seperate areas we're able to backup and restore the users ALL-IN-1 directory, restore the mail in seperate mail areas and so on. I know we've to upgrade the 2.3 profiles to 2.4, we've to merge profile, pending and so on. We make sure that all unread mail, records in pending are moved, to docdb. That can be easily done with newdir to all accounts and pull the record from pending into docdb. Time management, key is username and nbs timestamps so when the usernames are unique (this will be checked) merging so go ok. Multiple usernames like postmaster, manager, ivp etc. are removed. I still have an old copy of Tony's system guide. I analyzed the files on the systems, so it can be done when it is carefully planned. I'm not saying it is easy, but it can be done. I do'nt like to see no to a customer. When we don't do it somebody else (contracter?) will do it and maybe mess things up. Housekeeping procedures are now running on all the systems, converting the system and private files. Also to make sure about the usage counts. After the merge everything is analyzed and again converted, global buffers are calculated, acl and protections are restored. Everything will be done with the tool, scripts and commands files. Testing will be done first, user acceptance tests are done by several users. Oh, one of the reason to chose for multiple areas is also performance and maintenanace. Merging 5 systems into one SDAF, I'm user you've multiple keys and a huge sdaf file. The oa$smart tool reads buffer for buffer, everything is kept in memory and inly the area code is changed. Checks are made if sdaf contains multiple areas. This should not occur but I've seen a system with one different record. In docdb multiple areas are allowed, warnings are given when multiple areas are detected. Also checks are made if file are in the sys$login directory (like PERSONAL.LGP) so these have to picked up during the backup. Lucky enough this is 2.3 and 2.4, no shared drawers like 3.0. But I'm sure we're able to handle that also when it is needed. Device names are scanned for and changed, don't forget we're using ALL-IN-1 so we're able to make our own tools. Get the directory spec from profile, break the symbol and put the new device in it. DDS records are moved from the owning node to the new one. proxy is changed to the correct one. Default_decnet will be removed and the old nodenames are put in mrnodef.dat. This will result in non-delivery messages returned immediatly and not after XX days. Distribution lists and nicknames are scanned and validated against DDS records and automaticly updated. This is only a part of it, but is is fun ! regards Rob
3707.3	Feedback system 1	UTRTSC::EISINK	Shadow earth	`Tue Jan 25 1994 19:26`	15
	Hi some feeback, there is new version availible, thsi to a bug in handling attachments. Last week we used this to convert systems from the E mail area to other areas. Users did not notice anything. After some days the systems we migrated. Meeting, pending, sil files were merged. The day after there were no complains of users that the systems were migrated, We still have some several systems to go, I'll keep you posted, regards Rob