Tivoli Header

Administrator's Reference

DSMSERV LOADDB (Reload the Database)

Use this command to reload a dumped Tivoli Storage Manager database in optimal order. No other server activity is allowed while reloading the database. Perform the applicable steps in this order:

  1. When recovering from a failure reinstall Tivoli Storage Manager using the DSMSERV LOADFORMAT and create a new database and recovery log. This keeps the original database and log volumes intact in case you must repeat the dump and load. Run a modified version of the install job (PGM=ANRSERV,PARM='/LOADFORMAT') to reinitialize the recovery log and database datasets. A sample job named ANRINST is provided in the ASAMPLIB dataset.

    Attention: Do not reinitialize DISK storage pool volumes.

  2. Save the current sequential volume history to a file. The load process regresses the sequential volume history information. The saved copy should be printed or copied to a safe location. The information in the dataset will be needed after the database is reloaded. If the data is not printed or copied, key information may be lost when the server is restarted after loading the database.
  3. The DSMSERV LOADDB utility specifies a device class to be used when reading the database information. Ensure that a device configuration file that includes the definitions for this device class and for any required libraries and drives is available.

  4. Run the DSMSERV LOADDB utility.
  5. A message at the end of the output from the DSMSERV LOADDB indicates if you must audit the database. If the server was halted with the HALT command with the quiesce parameter and allowed to end normally before running the DSMSERV DUMPDB utility, an AUDITDB utility will not normally be required when the database is loaded using the DSMSERV LOADDB utility. Otherwise, run the DSMSERV AUDITDB utility to ensure that the database is returned to a synchronized state after it is reloaded. If there was any storage pool volume activity after the dump, audit the volumes by using the AUDIT VOLUME command. (The AUDIT VOLUME command is run from the command prompt with the server running in normal mode.)
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 LOADDB--dump_name-------------------------------------------------------.
>>-+---------------------------------------------------------------------------------+-><
   |                                                             .-,-----------.     |
   |                                                             V             |     |
   '-DSMSERV LOADDB--DEVclass--=--classname----VOLumenames--=--+---volume_name-+-+---'
                                                               +-FILE:file_name--+
                                                               '-FILE:DD:ddname--'
 
 

Parameters

dump_name
Identifies the location of the dumped database. Specify a dataset name or a DD name.

The dataset name can be specified with or without single quotes. When the name is enclosed within single quotes then a fully qualified name is assumed and is used as specified. Otherwise, the user ID associated with the job that is running the server where this command was issued, is appended to the beginning of the name to create a complete dataset name.

The location of the dataset can also be identified with DD:ddname where ddname is the name of a DD statement in the server job. The DD statement will have the dataset name of the dumped database.

When this parameter is specified, no other parameters may be specified.

DEVclass
Specifies the device class to be used when reading the database information.

classname
Specifies the name of the device class that describes the type of volume(s) that will be used as input to DSMSERV LOADDB.

When this parameter is specified, the dump_name parameter must not be specified. Also, the volumenames parameter must be specified when DEVCLASS is specified.

VOLumenames
Specifies the volumes needed to load the database. Possible values are:

volume_name
Specifies one or more names of volumes that contain the dumped database. These volumes will be used to load the database. When more than one volume needs to be specified, a comma must be used to separate the names, there should be no blanks. The volumes must be listed in the order that they must be used for loading the database.

FILE:file_name
Identifies the name of a dataset containing a list of volume names exist. The lines or records of the dataset must contain only one volume name per line or record and the lines or records must be in the order that they must be used for loading the database.

The dataset name can be specified with or without single quotes. When the name is enclosed within single quotes then a fully qualified name is assumed and is used as specified. Otherwise, the user ID associated with the job executing the DSMSERV LOADDB utility is appended to the beginning of the name to create a complete dataset name.

FILE:DD:ddname
Specifies the name of the DD statement that defines the location of a dataset containing the list of volume names. The lines or records of the dataset must contain only one volume name per line or record and the lines or records must be in the order that they must be used for loading the database.
Note:
The dataset identified through the FILE:file_name or the FILE:DD:ddname must be a sequential dataset 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 will be 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. See the examples below for further information.

Examples

Task 1

Load the database from the DB0001 tape.

Sample JCL:

//LOADDB  JOB  ,REGION=256M,TIME=1440,CLASS=A,MSGCLASS=H
//TIVSMDB  EXEC PGM=ANRSERV,PARM='/LOADDB 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

Load the database from the file ARIZONA.S0303570.DLD, in the device class named FLAT.

Sample JCL:

//LOADDB  JOB  ,
//         REGION=256M,TIME=1440,CLASS=A,MSGCLASS=H
//TIVSMDB  EXEC PGM=ANRSERV,DYNAMNBR=300,TIME=NOLIMIT,
//  PARM='/LOADDB DEVCLASS=FLAT VOL=ARIZONA.S0303570.DLD'
//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

Load the database from volumes that are listed in a dataset that is defined by the DBDATA DD statement

Sample JCL:

  //LOADDB  JOB  ,REGION=256M,TIME=1440,CLASS=A,MSGCLASS=H
  //TIVSMDB  EXEC PGM=ANRSERV,PARM='/LOADDB 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
  //* -------------------------------------------------------
  //* LOAD The Database from tape
  //* -------------------------------------------------------
  //DBDATA   DD  *
    TAP001
    TAP002
    TAP003
    TAP004
  /* 
  //         


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]