Tivoli Header
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 LOADFORMAT 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.
You must have a device configuration file that includes the definition for
this device class. 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:
- Note:
- When a database is loaded or restored, the server-to-server communication
verification token is changed. The verification token is an attribute
of the database and is not stored in the database itself. Part of the
token is the install date and time for the database. For servers that
have been defined for server-to-server communications, you must issue an
UPDATE SERVER command with FORCESYNC=YES.
Syntax
>>-DSMSERV DUMPDB--+-DEVclass--=--device_class_name--| A |-+---><
'-dump_name-----------------------------'
A
.-Scratch--=--Yes-----.
|--+---------------------+-------------------------------------->
'-Scratch--=--+-Yes-+-'
'-No--'
>--+-------------------------------------+----------------------|
| .-,-----------. |
| V | |
'-VOLumenames--=--+---volume_name-+-+-'
+-FILE:file_name--+
'-FILE:DD:ddname--'
Parameters
- DEVclass
- Specifies the name of the device class associated with the volumes to
which the database dump will be written. Specify either this parameter
or dump_name.
- dump_name
- Specifies the name of the storage location for the dumped database.
Specify either this parameter or the DEVCLASS parameter. Use one of the
the following for the dump name:
- dataset name
- When enclosed in single quotation marks ('), specifies the fully
qualified dataset name. Without quotation marks, the complete dataset
name is assumed to be the user ID associated with the job that is running the
server from which the command is issued followed by the specified name.
- DD:ddname
- Specifies the output file where the database is to be stored. A
ddname is the 1-8 character data definition name that is assigned to the
JCL DD statement.
- Scratch
- Specifies whether or not scratch volumes can be used for dumping the
database. You can specify this parameter only if you specify the
DEVCLASS parameter. 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.
Tivoli Storage Manager 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. The volumes will be used in the order in which they
are listed.
- 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. When
enclosed in single quotation marks ('), specifies the fully qualified
dataset name. Without quotation marks, the complete dataset name is
assumed to be the user ID associated with the job that is running the server
from which the command is issued followed by the specified name.
- FILE:DD:ddname
- Specifies the name of the DD statement that defines the location of a
dataset containing the list of volumes names. Enter each volume name on
a separate line in the file. List the volumes in the order in which
they are to be used.
- Note:
- Datasets identified by the FILE:file_name or the
FILE:DD:ddname must be sequential datasets with one volume serial
number per record or line. No other text or punctuation characters
should be on the line and the lines or records must not be sequence
numbered. Leading and trailing blanks are acceptable and are ignored
during processing. The dataset RECFM may be F, FB, V, or VB. The
dataset LRECL and BLKSIZE are not critical as long as reasonable values are
used, for example DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120) or
DCB=(DSORG=PS,RECFM=VB,LRECL=255,BLKSIZE=19069). If the dataset is
specified using the FILE:file_name parameter, then the dataset must be
cataloged. If the dataset is specified with the
FILE:DD:ddname parameter, the ddname can identify an inline
spooled dataset.
Examples
Task 1
Dump the Tivoli Storage Manager database to a tape named DB0001.
- 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
definition needed for the dump operation.
- Start the DSMSERV DUMPDB utility.
Sample JCL:
//DUMPDB JOB ,REGION=256M,TIME=1440,CLASS=A,MSGCLASS=H
//TIVSMDB EXEC PGM=ANRSERV,PARM='/DUMPDB DEV=CART VOL=DB0001',
// DYNAMNBR=300,
// TIME=NOLIMIT
//OPT DD DSN=TIVSM.OPTIONS,DISP=SHR,FREE=CLOSE
//DSMAMENG DD DSN=TIVSM.ANRMSG(ANRMENU),DISP=SHR
//HLPAMENG DD DSN=TIVSM.ANRHLP(ANRHENU),DISP=SHR
//DSK DD DSN=TIVSM.DISKLOG,DISP=SHR
Task 2
Dump the Tivoli Storage Manager database to a file in the device class
named FLAT, which has a device type of FILE.
- 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
definition needed for the dump operation.
- Start the DSMSERV DUMPDB utility.
Sample JCL:
//TIVSM JOB ,
// REGION=256M,TIME=1440,CLASS=A,MSGCLASS=H
//TIVSM EXEC PGM=ANRSERV,DYNAMNBR=300,TIME=NOLIMIT,
// PARM='/DUMPDB DEVCLASS=FLAT'
//OPT DD DSN=TIVSM.OPTIONS,DISP=SHR,FREE=CLOSE
//DSMAMENG DD DSN=TIVSM.ANRMSG(ANRMENU),DISP=SHR
//HLPAMENG DD DSN=TIVSM.ANRHLP(ANRHENU),DISP=SHR
//DSK DD DSN=TIVSM.DISKLOG,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSTERM DD SYSOUT=*
Task 3
Dump the Tivoli Storage Manager database to tape dataset identified by DD
statement DBDATA.
- Halt the server.
- Start the DSMSERV DUMPDB utility.
Sample JCL:
//DUMPDB JOB ,REGION=256M,TIME=1440,CLASS=A,MSGCLASS=H
//TIVSMDB EXEC PGM=ANRSERV,PARM='/DUMPDB VOL=FILE:DD:DBDATA',
// DYNAMNBR=300,
// TIME=NOLIMIT
//OPT DD DSN=TIVSM.OPTIONS,DISP=SHR,FREE=CLOSE
//DSMAMENG DD DSN=TIVSM.ANRMSG(ANRMENU),DISP=SHR
//HLPAMENG DD DSN=TIVSM.ANRHLP(ANRHENU),DISP=SHR
//DSK DD DSN=TIVSM.DISKLOG,DISP=SHR
//* -------------------------------------------------------
//* Dump To Scratch Tapes
//* -------------------------------------------------------
//DBDATA DD UNIT=B38,DISP=OLD,VOL=SER=TIVO01,
// DSN=TIVSM.DUMPDB.DATA
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]