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:
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:
Consider the following before dumping the database:
If you can bring the server up, estimate the size by following these steps:
Syntax
>>-DSMSERV DUMPDB----+-DEVclass--=--device_class_name--+--------> '-dump_name-----------------------' .-Scratch--=--Yes-----. >-----+---------------------+-----------------------------------> '-Scratch--=--+-Yes-+-' '-No--' >-----+---------------------------------------+---------------->< | .-,-----------. | | V | | '-VOLumenames--=--+---volume_name--+-+--' '-FILE:file_name---'
Parameters
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:
You can also specify the volume list as an in-stream data set by specifying the data set's DD name with this parameter, and including the data set in the JCL. You must include DD: when you specify this parameter, for example:
volumenames=file:dd:vollist
Examples
Task 1
Dump the TSM database to a tape named DB0001.
Sample JCL:
//DUMPDB JOB ,REGION=128M,TIME=1440,CLASS=A,MSGCLASS=H //ADSMDB EXEC PGM=ANRSERV,PARM='/DUMPDB DEV=CART VOL=DB0001', // DYNAMNBR=300, // TIME=NOLIMIT //STEPLIB DD DSN=EDC.V2R1M0.SEDCLINK,DISP=SHR // DD DSN=SYS1.LINKLIB,DISP=SHR // DD DSN=PLI.SIBMLINK,DISP=SHR // DD DSN=ADSM.LINKLIB,DISP=SHR //OPT DD DSN=ADSM.OPTIONS,DISP=SHR,FREE=CLOSE //DSMAMENG DD DSN=ADSM.ANRMSG(ANRMENU),DISP=SHR //HLPAMENG DD DSN=ADSM.ANRHLP(ANRHENU),DISP=SHR //DSK DD DSN=ADSM.DISKLOG,DISP=SHR
Task 2
Dump the TSM database to a file in the device class named FLAT, which has a device type of FILE.
Sample JCL:
//ADSMSRV0 JOB , // REGION=128M,TIME=1440,CLASS=A,MSGCLASS=H //ADSMSRV0 EXEC PGM=ANRSERV,DYNAMNBR=300,TIME=NOLIMIT, // PARM='/DUMPDB DEVCLASS=FLAT' //STEPLIB DD DSN=EDC.V2R1M0.SEDCLINK,DISP=SHR // DD DSN=PLI.MINI.SIBMLINK,DISP=SHR // DD DSN=SYS1.LINKLIB,DISP=SHR // DD DSN=ADSM.LINKLIB,DISP=SHR //OPT DD DSN=ADSM.OPTIONS,DISP=SHR,FREE=CLOSE //DSMAMENG DD DSN=ADSM.ANRMSG(ANRMENU),DISP=SHR //HLPAMENG DD DSN=ADSM.ANRHLP(ANRHENU),DISP=SHR //DSK DD DSN=ADSM.DISKLOG,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSTERM DD SYSOUT=*
Task 3
Dump the TSM database to tape dataset DBDATA.
Sample JCL:
//DUMPDB JOB ,REGION=128M,TIME=1440,CLASS=A,MSGCLASS=H //ADSMDB EXEC PGM=ANRSERV,PARM='/DUMPDB VOL=FILE:DD:DBDATA', // DYNAMNBR=300, // TIME=NOLIMIT //STEPLIB DD DSN=EDC.V2R1M0.SEDCLINK,DISP=SHR // DD DSN=SYS1.LINKLIB,DISP=SHR // DD DSN=PLI.SIBMLINK,DISP=SHR // DD DSN=ADSM.LINKLIB,DISP=SHR //OPT DD DSN=ADSM.OPTIONS,DISP=SHR,FREE=CLOSE //DSMAMENG DD DSN=ADSM.ANRMSG(ANRMENU),DISP=SHR //HLPAMENG DD DSN=ADSM.ANRHLP(ANRHENU),DISP=SHR //DSK DD DSN=ADSM.DISKLOG,DISP=SHR //* ------------------------------------------------------- //* Dump To Scratch Tapes //* ------------------------------------------------------- //DBDATA DD UNIT=B38,DISP=OLD,LABEL=(,SL),VOL=SER=SCRTCH, // DSN=ADSM.DUMPDB.DATA,DCB=(RECFM=U,LRECL=32760)