1. Utilities such as FDR or ADRDSSU can be used to move a View or Deliver database extent from one volume to another. These would be the most efficient methods to use in terms of time.
- Use of these types of backup/restore utilities to move a database or index extent requires that the track architectures for the OLD and the NEW devices be the same. The old and new device MODEL can be different (i.e. Mod3,9,27,54) but the old and new VOLUMES must all be, for example, DEVICE TYPE 3390, in order for them to have the same track architecture.
- Before backing up or moving any View or Deliver database extents, ensure that ALL associated tasks are DOWN:
* Shut down all View tasks (SARSTC, SARFSS, SARXTD, SARXMS, SAREAS, etc.)
* Using the "/F rmostc,OFF" command, shut down all Deliver RMOSTC tasks that do direct writing to View (RMOPARM ARCHn=DIRECT).
- When moving View database files, ensure that the first INDEX extent of a database (...SARDBASE.I0000001) is not on the same volume as the first DATA extent of that database (...SARDBASE.D0000001).
- This would also hold true for the first extent of a Deliver database (...RMODBASE.D0000001), and the Deliver checkpoint file (...RMODBASE.C0000001).
Other options for getting entire databases or index extents moved to a new pack would include:
2. TAPE to DISK - Execute the SARDBASE UNLOAD function (to tape) - Then execute the SARDBASE ADDDS and LOAD functions to populate the new files on the new DASD.
3. DISK TO DISK - Execute the SARDBASE ADDDS function to allocate new DB files on the new DASD - Then execute the SARDBASE COPY function to do a direct disk-to-disk copy from the target DB to the new DB (Requires shared DASD environment).