The MERGE control statement is used to merge 1 to 9 existing databases together into one new database. Logic is included to reset generation and tape sequence numbers to eliminate any conflict between the input databases. The output database must be a newly-created, empty database.
Note: The SARPAC tape consolidation utility is required to complete the merge process, therefore, you must have previously installed the Expanded Retention Option (ERO).
The high-level name of the output database must have previously been defined with the NAME control statement (or the PARM parameter of the EXEC JCL statement).
Syntax:
MERGE tape-index driver parameters ARCHCHG=baseyear
where:
Specifies the high-level naming prefix to be set for the TAPEIDX initialization parameter
If omitted, TAPEIDX is set to the high-level name of the output database.
To prevent conflicts with any existing archival tapes, MERGE requires that this high-level naming prefix for tapes be different from those for any tapes defined in the input databases.
Specifies the name of the secondary disk storage driver and must be the same as the DSK2DRVR initialization parameter
Use driver only if you have an optical disk secondary storage driver.
Note: For more information about disk storage, see the chapter "Using the Optical Disk Interface."
Specifies the identifiers for the secondary disk storage driver as defined by the DSK2PARM initialization parameter
Use parameters only if you have an optical disk secondary storage driver. These parameters vary according to type of optical disk driver.
Note: For more information about the proper identifiers, see the chapter "Using the Optical Disk Interface." Parameters are required when you specify a driver name.
Establishes the baseyear designation of the ARCHCHG initialization parameter for the merged database. The baseyear is a four-digit year that can range from 1980 to the present year and must be equal to or earlier than the oldest report in the merged database.
When ARCHCHG baseyear is specified, CA View calculates the GEN number for the report using the number of days from the baseyear to the report date. This initialization parameter is designed for installations that want to change the archival date of a report during collection.
When the ARCHCHG parameter is omitted, the GEN number for reports is initially determined based on the number of days from the earliest report in the merged database. After the merge, CA View increments the GEN number for the reports using the standard method and execution of the started task backup cycle.
Note: This option can only be specified for databases that have the EROOPT=YES initialization parameter setting. Also, the EROPRO initialization parameter will be automatically set to YES as required by the ARCHCHG initialization parameter. For more information about the ARCHCHG, EROOPT, and EROPRO initialization parameters, see the chapter "Initialization Parameters."
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|