View - Database MERGE questions

Products

• Deliver
• View

Issue/Introduction

The client will be merging three View database into one, which will be shared across a three-part JES MAS.

They have the following questions:

1. The Reference Guide mentions to not use SARTDR /TADD on tape from the original database until they have been SARPACed.
    Does a /TADD need to be run?

2. There could be 100 tapes involved in the process.  Is there any way to gauge how long the SARPAC may take to run?

3. Are there any parameters that need to change for a MERGE to take place or for a merged database?

Resolution

The client will be merging three View database into one, which will be shared across a three-part JES MAS.

1. These are the correct processing steps:

. . Run SARDBASE STATUS FULL on each of the databases.
. . List the Generations and Users in use.
. . Run a View backup on each database.
. . Run SARPAC on each database, to lessen the number of tapes in use.
. . Run SARDBASE UNLOAD on the 3 databases.
. . Create a new View database.
. . Run SARDBASE MERGE.
. . Run SARINIT, to verify the parms for the new database.
. . Run SARPAC, for tape consolidation.

2. A SARTDR /TADD should not be run at this time, which would only cause future problems.

3. Suggested to run SARPAC on the databases prior to the MERGE, to lessen the number of tapes involved.
   There is no way to gauge how long the SARPAC would take to run, as there are several environmental factors that could slow things down.

4. There are no parameters that need to change for a MERGE to take place, or would be needed on a merged database.