Use the DSMSERV DUMPDB command as the first step in dumping, reinitializing, and reloading the server database if a catastrophic error occurs (recovery log corruption, for example), and the DSMSERV RESTORE DB command cannot be used. No other server activity is allowed during DSMSERV DUMPDB command processing.
After DSMSERV DUMPDB processing is complete, perform the following steps:
Note: | A message at the end of the output from the DSMSERV LOADDB command indicates whether a DSMSERV AUDITDB command is required. If the server was quiesced when it was halted, the DSMSERV AUDITDB command is not required. |
The DSMSERV DUMPDB command requires a device configuration file. If you specify the DEVCONFIG option in the server options file, ADSM creates and then maintains a device configuration file when you start the server. The device configuration file contains a copy of the device class, library, and drive definitions that exist in your database.
Attention: The DSMSERV DUMPDB command supports the use of manual libraries only (LIBTYPE=MANUAL in the DEFINE LIBRARY command).
Because the DSMSERV DUMPDB command requires a device configuration file, you must specify a device configuration file with the DEVCONFIG option in the server options file. The file specified with the DEVCONFIG option must be available and must contain at least the device class specified for use with this command, along with any necessary library and drive definitions.
Syntax
>>-DSMSERV DUMPDB---DEVclass--=--devclassname-------------------> .-Scratch--=--Yes------. >---+----------------------+------------------------------------> '-Scratch--=--+-Yes-+--' '-No--' >----+-------------------------------------+------------------->< | .-,-------. | | V | | '-VOLumenames--=--+---volname--+---+--' '-FILE:filename--'
Parameters
You must have a device configuration file that includes the definition for this device class, and any libraries and drives needed. You must also specify the name of that device configuration file by using the DEVCONFIG option in your server options file. The device configuration file should be available if you had previously included a DEVCONFIG option in the server options file and then started the server. If the device configuration file has been lost or was never created, do one of the following:
To determine the library type of the library, issue the the QUERY LIBRARY command and specify FORMAT=DETAILED.
If you include a list of volumes on the VOLUMENAMES parameter, then scratch volumes are used only if there is not enough space to dump the database on the volumes specified. If the device type associated with the specified device class is FILE, file names for the scratch volumes are generated based on a time stamp.
ADSM does not record the use of volumes by the DSMSERV DUMPDB command in the volume history file. Therefore, you must record the volume names used and specify them in the exact same order on a future DSMSERV LOADDB command.
Possible values are:
For example, if you want to use the volumes TAPE01, TAPE02, and TAPE03, specify the following:
volumenames=tape01,tape02,tape03
For example, if you want to use the volumes TAPE01, TAPE02, and TAPE03, create a file named VOLLIST that contains these lines:
TAPE01 TAPE02 TAPE03
You can then specify the volumes for the dump command as follows:
volumenames=file:vollist
Usage Notes
Consider the following factors before dumping the database:
If you can bring the server up, you can estimate the size by following these steps:
Examples
Task
Dump the existing ADSM database to an 8mm tape named DB0001.
For this example the following steps are required:
dsmlabel -drive=/dev/mt0