Optical Disk Database Maintenance
The UNLOAD and MERGE functions of the CA View database maintenance utility (SARDBASE) contain parameters to support optical disk storage. For more information about these functions, see .
The UNLOAD and MERGE functions of the CA View database maintenance utility (SARDBASE) contain parameters to support optical disk storage. For more information about these functions, see
Maintain the Database (SARDBASE).
Only MERGE Moves Optical Disk Data
The MERGE function should be used for reloading the actual SYSOUT data from secondary disk storage. The COPY and LOAD functions copy the index information about the SYSOUT groups on secondary disk storage. In other words, COPY and LOAD merely transfer ownership of the secondary disk storage data that is already archived, while the MERGE actually reloads the data to another optical disk data set.
In addition to merging multiple databases together, you can use the merge function to replace one type of secondary disk device with another, to consolidate the archived secondary disk storage, and to replace secondary disk storage with primary disk.
MERGE Statement Prerequisite
When performing a MERGE function with an input database that contains any SYSOUT groups archived to secondary disk storage, the contents of the secondary disk SYSOUT groups must have been unloaded with SECOND specified on the UNLOAD control statement. The MERGE function will then reload the SYSOUT groups based upon the secondary disk operands on the MERGE command.
UNLOAD Control Statement
The UNLOAD control statement allows for unloading the SYSOUT data for SYSOUT groups archived to secondary disk storage.
- SECONDDoes not unload the SYSOUT data for SYSOUT archived to secondary disk storage.
- NO SECONDDoes not unload the SYSOUT data for SYSOUT archived to secondary disk storage.
The SECOND/NOSECOND parameter has a default value of NOSECOND. Specifying SECOND can substantially increase the time required to perform the UNLOAD function.
Whether or not you specify SECOND when unloading, the LOAD function never reloads the SYSOUT data for SYSOUT groups archived to secondary disk storage. The LOAD function merely transfers ownership of the secondary disk storage that is already archived.
You must specify SECOND when unloading the databases if you are going to use the MERGE function, because the MERGE function always reloads the SYSOUT data, either to primary or secondary disk.
MERGE Control Statement
The syntax of the MERGE control statement is as follows:
MERGE tape-index driver parameters
- tape-indexSpecifies the high-level naming prefix to be set for the TAPEIDX initialization parameter.If omitted, TAPEIDX is set to the name of the output database.
- driverSpecifies the required name of the secondary disk storage driver.This name must be the same as the one specified by the DSK2DRVR initialization parameter. Specify SARD2D0x for the optical disk driver you have purchased. Replace the x with the driver number described in Driver Names and Types inOptical Disk Interface.
- parametersSpecifies the required unit name and volume serial number range for the secondary disk storage driver as defined by the DSK2PARM initialization parameter.The parameters are required when you specify a driver name.
- For the Kodak Optistar Report-Level Driver, the format of this operand is: unit/volser1/volser2.For more information about these identifiers, see the section DSK2PARM: Kodak Optistar Report-Level Driver inConfigure the Optical Disk Interface.
- For the Kodak Optistar Page-Level Driver, the format of this operand is: unit/volser1/volser2/ssid.For more information about these identifiers, see the section DSK2PARM: IBM Page-Level Driver for Models 131, 132, 133 inConfigure the Optical Disk Interface.
- For the IBM DASD Emulation Optical Driver, the format of this operand is: index/unit/blksize.For more information about these identifiers, see the section DSK2PARM: IBM Page Level Driver for Models 131, 132, 133 inConfigure the Optical Disk Interface.
MERGE Command Operand Restrictions
Since the operands for the MERGE command are positional, specify an asterisk to indicate the omission of the
tape-indexoperand when you code the
To prevent conflicts with any existing archive tapes, MERGE requires that the high-level naming prefix for tapes be different from those for any other tapes defined in the input databases.
To Reload from Optical Disk to the Database
If you omit the
driveroperand, you must also omit the
parametersoperand. When the
parametersoperands are omitted, at MERGE time any SYSOUT groups unloaded from the optical disk are reloaded to the primary disk CA View database.