|
cb,
It is my opinion that you should do this prior to your upgrade.
There are some additional steps to perform if you move ALL-IN-1 3.0.
I also recommend that you do this around a week before you the upgrade
so that you can the moved environment in production for a while.
Moving ALL-IN-1 and upgrading it the same weekend is asking for trouble.
Attached are the steps to moving ALL-IN-1 to another disk. This is what
I send to customers when they are moving ALL-IN-1. You may know how to
do this already, but I thought I would include it with my response.
Hope this helps,
Paul
MOVING ALL-IN-1 TO ANOTHER DISK
1. PREPARE SYSTEM FOR ALL-IN-1 MOVE.
***GET A GOOD BACKUP (STANDALONE) OF YOUR SYSTEM DISK BEFORE BEGINNING***
If you use disk logicals for your ALL-IN-1 disk, and could set up the logical
on the new disk, it is fairly easy to backup ALL-IN-1 to another disk.
If not, you have to do the following
2. MODIFY A1CONFIG TO REFLECT THE NEW DISK/LOGICAL NAME.
- Log into the ALL-IN-1 Managers account and run shutdown.
- Make a copy of OA$DATA:A1CONFIG.DAT.
$ COPY OA$DATA_SHARE:A1CONFIG.DAT OA$DATA_SHARE:A1CONFIG.BCK
- Enter ALL-IN-1 from a privilged account.
$ALLIN1/USER=MANAGER/OVERRIDE=SHUTDOWN
- Type A1CONFIG at any menu.
- Enter A1BASE in the language field.
- Enter "C" to change.
- Enter the new logical name in the four location fields as well
as the Manager directory field.
- After changes are made enter <CR> twice.
- The language field will be blank.
- Enter ENGLISH in the language field.
- Update the location fields. There should just be two.
- Enter <CR> twice to save changes.
- OA$DATA_SHARE:A1CONFIG.DAT will now contain information for
your new disk. If you have to fall back to your old disk,
all you would have to do is rename A1CONFIG.BCK to A1CONFIG.DAT
and restart ALL-IN-1.
3. REMOVE ALL-IN-1 IMAGES, FORM LIBRARIES, AND TXLS.
- Before backing up the ALL-IN-1 directories to the new
disk, I recommend you make sure the ALL-IN-1 images,
form libraries, and TXLs are not installed. You can
do this two ways.
REBOOT system with A1V24START.COM commented out
of startup, or by doing the following. Attached
are the procedures on how to remove ALL-IN-1 files
that are installed.
The shutdown operation (SDA) is intended to dislodge ALL-IN-1 users
by warning them of the shutdown and eventually forcing image exit.
This operation is intended for housekeeping purposes so that
operations on the ALL-IN-1 system and user file cabinets can be
performed without needing further interlocks or controls on
access. For this reason, the ALL-IN-1 system is left in a state
that allows such housekeeping procedures to run (using the
/OVERRIDE_SHUTDOWN qualifier).
If you wish to dismount the device containing the ALL-IN-1 system,
after ALL-IN-1 has been shutdown, you must perform a number of
additional operations to close open files on the disk. Perform the
following operations:
- Remove the Form Library (FLC) and Message File global
sections using the OA$FBT_REMOVE_LIBRARY function:
$ ALLIN1/NOINIT/OVERRIDE
OA$FBT_REMOVE_LIBRARY OA$LIB:MEMRES
OA$FBT_REMOVE_LIBRARY OA$LIB:OAFORM
OA$FBT_REMOVE_LIBRARY OA$LIB:OAN$FORMS
OA$FBT_REMOVE_LIBRARY OA$LIB:SITEMEMRES
OA$FBT_REMOVE_LIBRARY OA$LIB:SITEOAFORM
OA$FBT_REMOVE_LIBRARY OA$LIB:SITEOAN$FORMS
- Remove the Text Library (TXL) global sections (A1TXL
and CMTXL) using the OA$TXL_REMOVE function:
$ ALLIN1/NOINIT/OVERRIDE
OA$TXL_REMOVE A1TXL
OA$TXL_REMOVE CMTXL
- Remove the image global sections (MAILCOUNT, OA$SUBMIT,
TMSV, OAFCV and OA$MAIN) using the VAX/VMS INSTALL
utility:
$ INSTALL == "$SYS$SYSTEM:INSTALL /COMMAND_MODE"
$ INSTALL
REMOVE OA$LIB:MAILCOUNT
REMOVE OA$LIB:OA$SUBMIT
REMOVE OA$LIB:TMSV
REMOVE OA$LIB:OAFCV
REMOVE OA$LIB:OA$MAIN
- Shut down the background processes using the appropriate
DCL commands:
$ STOP/QUEUE/NEXT OA$FORMATTER
$ STOP TM_SERVER
$ STOP OA$FCV
$ STOP/QUEUE/NEXT OA$MTI_QUEUE !For SENDER/FETCHER
!Also STOP any other batch
!queues used for housekeeping
!jobs
- Shut down MAILBUS processes if installed/running on the
disk (note: All components which are running on your system).
Ex:
$@SYS$MANAGER:MB$CONTROL STOP=(ER,DDS,MRG,TS,MS)
- Shut down print queues which may be accessing formatted
files on the disk.
- Perform similar shutdown operations on each node in the
cluster.
Because this operation needs to be executed for each node in a
cluster, you may wish to construct a command procedure to perform
these commands, then use the VAX/VMS SYSMAN utility to execute the
procedure on all nodes in the cluster, or as an alternative submit the
procedure into batch queues for each node.
4. BACKUP THE ALL-IN-1 DIRECTORY TREE TO THE NEW DISK.
$BACKUP/LOG OLDDISK:[ALLIN1...]*.*.* -
NEWDISK:[ALLIN1...]*.*.*/OWNER=ORIGINAL
5. RESTART ALL-IN-1 AND MODIFY DATA FILES WITH NEW DISK NAME
- You have to restart ALL-IN-1 for the new disk logicals to be
defined.
$@SYS$MANAGER:A1V24START.COM NEWDISK:[ALLIN1.DATA_SHARE]
- You may want to go into ALL-IN-1 and shut it down so that
no users can access ALL-IN-1 until you have finished.
- If the shared directories were on the ALL-IN-1 disk that you
moved, you must update the data files for them.
For Shared directories:
From an ALL-IN-1 menu type
SM_SHARED_DIR_MASTER
- Your cursor will be at the "Shared directory logical" field.
- Enter the find key. This will display all of the shared directories
you have on the system. You must bring each one up and
edit it, replacing the logical value with the new logical.
For SDAFs:
From an ALL-IN-1 menu type
SM_SDAF_MASTER
- Your cursor will be at the "SDAF mail area" field.
- Enter the find key. This will display all of the DAFs that
you have on the system. You must update the SDAF location field
to reflect the new disk logical.
- Run ALL-IN-1 Startup to get the new logical values for the shared
directories and SDAF.
$@SYS$MANAGER:A1V24START NEWDISK:[ALLIN1.DATA_SHARE]
6. UPDATE PROFILE FOR ALL-IN-1 ACCOUNTS
You must update ALL-IN-1 user profiles for MANAGER, IVP, and POSTMASTER
to reflect new disk location.
$ALLIN1/USER=MANAGER
- Enter SM MUA SEL
- Select "MANAGER" and type E to Edit. Enter the new disk location
and enter <CR> twice to save.
- Do the same for IVP and POSTMASTER.
ALL-IN-1 should be able to be accessed by user in its new location.
7. MODIFY HOUSEKEEPING JOBS.
Check your housekeeping jobs. They will probably have to be
deleted and rescheduled.
$SHOW ENTRY/USER=ALLIN1/FULL
You will see that the jobs will be scheduled to run command
procedures that are on your old disk.
8. TEST ALL-IN-1.
- Create mail messages and send them from a non-privileged account.
- If you have message router, send mail off node.
- (optional) Relink ALL-IN-1
|