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 |
We are working on moving our Treasury customer from their old VAX 11/750 system with VMS V4.5 to a VAX6000 cluster with VMS V5.3-1 to ALL-IN-1 V2.4. See note 3065 in the ALL-IN-1_V24 note file for the background on this customer. We are almost there but we will need to move over the final data files from the old system. I have done several tests movements of ALL-IN-1 system data files and ALL-IN-1 user files and all seems OK in the mail area that is but I want to make sure I have not missed anything before I put together the DCL procedures for the change over. The following ALL-IN-1 data files must be transferred from the old IGVAX system and moved to oa$data_share on the new IGVAX cluster: oa$data: oa$data_share attendee.dat calaccess.dat meeting.dat (on this system) daf.dat ---------------------> oa$data_share:oa$daf_e.dat pending.dat ALL-IN-1 shared directories and files......OA$SHARExxx NOTE: I have made it known that they cannot make any more changes in the profile.dat since I cannot move the V2.2 version profile over to V2.4 without conversion. And since they are on a VAX 11/750 no body really wants to get on it. The following ALL-IN-1 user files must be moved over from the user directories ACTITEM.DAT {user}.a1cal docdb.dat daf.dat nicknames.dat [.msg]........ msg.dir and all files in subdirectories [.doc%]....... all doc%.dir and all files in subdirectories Is it OK to move over WPSDEF.WPL {user}.pst Does this look OK? I was thinking about just doing a backup and restore of all the user files if this won't get me in trouble. Any proplems with this? Reda
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
515.1 | Looks good to me, but what do I know? | BUFFER::VICKERS | If it helps a customer, DO IT | Thu Apr 16 1992 22:30 | 14 |
Reda, The list of files appears complete and should result in having the right things working. Obviously, there could be something that you and I have missed so you need to be prepared to correct any missing elements on the fly. I seriously doubt that there is anything really serious which is missing. It is safe to move the WPSDEF.WPL and the .PST files. The .PST file format hasn't changed in years (decades?) and the WPSDEF.WPL gets upgraded automatically when accessed, I believe. Have fun, don | |||||
515.2 | New DAF logical | AIMTEC::PORTER_T | Terry Porter, ALL-IN-1 Support, Atlanta CSC | Fri Apr 17 1992 15:41 | 17 |
V2.3 introduced new logical names for the SDAF locations, in the form OA$SHARx where x is A thru E, so OA$DATA:DAF.DAT moves to OA$SHARE:OA$DAF_E.DAT. Of course there is no reason why OA$SHARE: should not point to the same location as OA$DATA_SHARE: , in fact this is the default when you upgrade from V2.2 to V2.3. This logical gives the customer the option to locate the SDAFs on different disk drives if the I/O volumes to the OA$DATA drive is excessive. To define the location of the SDAF use the form SM_SDAF_MASTER with a key of the mail area (OA$SHARE in your case). HTH Terry |