Administrator's Reference
Use this 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:
- Issue the DSMSERV FORMAT command to reinitialize the database and recovery
log.
- Issue the DSMSERV LOADDB command to reload the database.
- If necessary, issue the DSMSERV AUDITDB command to locate and correct any
database inconsistencies.
Note: | A message at the end of the output from the DSMSERV LOADDB command indicates
if you must audit the database. If the server was quiesced when it was
halted, the DSMSERV AUDITDB command is not required.
|
Attention: The DSMSERV DUMPDB command supports the use of
manual libraries only (LIBTYPE=MANUAL in the DEFINE LIBRARY command).
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:
- If the server can be restarted, restart the server and issue the BACKUP
DEVCONFIG command.
- If the server cannot be restarted, create the device configuration file
manually with an editor. For information on how to create a device
configuration file manually, see Administrator's Guide.
Consider the following before dumping the database:
Syntax
>>-DSMSERV DUMPDB----DEVclass--=--device_class_name------------->
.-Scratch--=--Yes-----.
>-----+---------------------+----------------------------------->
'-Scratch--=--+-Yes-+-'
'-No--'
>-----+---------------------------------------+----------------><
| .-,-----------. |
| V | |
'-VOLumenames--=--+---volume_name--+-+--'
'-FILE:file_name---'
Parameters
- DEVclass (Required)
- Specifies the device class to which the database information will be
written.
- Scratch
- Specifies whether or not scratch volumes can be used for dumping the
database. The default value is YES.
- Yes
- Scratch volumes can be used. If you include a list of volumes on
the VOLUMENAMES parameter, 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.
- No
- Scratch volumes cannot be used. You must include a list of volumes
on the VOLUMENAMES parameter to contain all of the database data.
- VOLumenames
- Specifies the volumes to use to dump the database. This parameter
is optional, but must be specified if SCRATCH=NO. If you do not specify
this parameter and SCRATCH=YES is specified or assumed, scratch volumes are
used.
TSM 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:
- volume_name
- The names of one or more volumes to use to dump the database.
Specify multiple volumes by separating volume names with commas and no
intervening spaces. You must list the volumes in the order in which you
want the volumes to be used.
- FILE:file_name
- The name of a file that contains a list of the volumes to use to dump the
database. Enter each volume name on a separate line in the file.
List the volumes in the order in which they are to be used.
Examples
Task 1
Dump the TSM database to tapes named DB0001, DB0002, DB0003:
- Halt the server.
- Ensure that the DEVCONFIG option has been specified in the server options
file. The device configuration file must contain the device class,
library, and drive definitions needed for the dump operation.
- Label the tape using the DSMLABEL utility. For example:
dsmlabel -drive=/dev/rmt/0mt
- Issue the DSMSERV DUMPDB command.
- Command:
- dsmserv dumpdb devclass=tapeclass
volumenames=db0001,db0002,db0003
Task 2
Dump the database using tapes listed in a file named
ADSM.VOLLIST.
- Command:
- dsmserv dumpdb devclass=tapeclass
volnames=file:adsm.vollist
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]