Tivoli Storage Manager stores data on magnetic disks in two ways:
For disk devices, Tivoli Storage Manager provides a defined DISK device class that is used with all disk devices.
Do the following to use random access volumes on a disk device:
For example, enter the following command on the command line of an administrative client:
define stgpool engback1 disk maxsize=5m highmig=85 lowmig=40
This command defines storage pool ENGBACK1.
See Example: Defining a Storage Pool Hierarchy for details.
For example, enter the following command on the command line of an administrative client:
define volume engback1 vol1
This command defines volume VOL1 in storage pool ENGBACK1.
See Defining Storage Pool Volumes for details.
Edit the ANRFMT job from the ASAMPLIB data set as follows:
Figure 8. ANRFMT Job from ASAMPLIB
//ANRFMT JOB MSGLEVEL=(1,1), // MSGCLASS=H,CLASS=A,REGION=7M,TIME=1440 //* //****************************************************************** //* //* ANRFMT Use ANRFMT to extend the recovery log, database or a //* storage pool if SMS is not active on your system. If //* SMS is active, you might choose to use ANRFMT2 as a //* PROC. //* //* Dependency: none //* //* Function: //* - allocate a VSAM linear dataset //* - pre-format the dataset for use by the server //* //* Usage: //* - customize the job card //* //* - modify: //* step parameter value //* -------- -------- --------------------------------------- //* ALLOCAT NAME name of the VSAM dataset to allocate //* and pre-format //* MB size of the dataset in megabytes //* VOL volume serial for the VSAM dataset //* //* TIVSMFMT PARM= dataset name here must match the NAME //* field of the preceding allocation step //* //****************************************************************** //****************************************************************** //* //* Allocate the VSAM data set //* //****************************************************************** //ALLOCAT EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DEFINE CLUSTER( NAME(TIVSM.DATASET.NAME) LINEAR MB(100) VOL(VOLL01) ) /* //* //* //****************************************************************** //* //* Pre-format the data set before defining it to the server //* Note: this step will not be executed if the ALLOCAT //* step fails //* //****************************************************************** //TIVSMFMT EXEC PGM=DSMFMT,DYNAMNBR=300,COND=(0,NE,ALLOCAT), // PARM='/TIVSM.DATASET.NAME' //OPT DD DSN=TIVSM.ANRSERV.OPTIONS,DISP=SHR //DSMAMENG DD DSN=TIVSM.ANRMSG(ANRMENU),DISP=SHR //SYSPRINT DD SYSOUT=* //SYSTERM DD SYSOUT=* // |
If you install ANRFMT2 as a procedure on an appropriate library (for example, SYS1.PROCLIB), you can invoke the allocation and pre-formatting of a data set by entering the following at the system console:
s anrfmt2,name=<name>,mb=<mb>,volser=<volser>
where:
Figure 9. ANRFMT2 Job from ASAMPLIB
//ANRFMT2 PROC NAME=,MB=,VOLSER= //* //****************************************************************** //* //* ANRFMT2 Use ANRFMT2 to extend the recovery log, database or a //* storage pool. //* ANRFMT2 is a proc: if installed in an appropriate //* library, it may be started from the system console. //* //* Dependency: SMS must be active; the data set does not have to //* be system-managed //* //* Function: //* - allocate a VSAM linear data set //* - pre-format the data set for use by the server //* //* Usage: //* - invoke via JCL (see ANRALLO2 for examples) //* //* - OR, issue on the system console: //* s anrfmt2,name=<name>,mb=<mb>,volser=<volser> //* //* where: //* <name> is the new data set to define for server usage //* <mb> is the size in megabytes //* <volser> is the volume on which to allocate <name> //* //****************************************************************** //****************************************************************** //* allocate a new data set //****************************************************************** //ALLOCVOL EXEC PGM=IEFBR14 //DSMVOL DD DSN=&NAME, // DISP=(NEW,CATLG),RECORG=LS,AVGREC=M, // SPACE=(&MB,(1)),UNIT=SYSDA,VOL=SER=&VOLSER //* //* //*************************************************************** //* pre-format the data set before defining it to the server //* Note: this step will not be executed if the ALLOCVOL //* step fails //*************************************************************** //DSMFMT EXEC PGM=DSMFMT,DYNAMNBR=300,COND=(0,NE,ALLOCVOL), // TIME=1440,PARM='/&NAME' //OPT DD DSN=TIVSM.ANRSERV.OPTIONS,DISP=SHR //DSMAMENG DD DSN=TIVSM.ANRMSG(ANRMENU),DISP=SHR //SYSPRINT DD SYSOUT=* //SYSTERM DD SYSOUT=* // |
After you have allocated space to disk volumes, you can add them to the database or recovery log as described in Increasing the Size of the Database or Recovery Log.
Another way to use magnetic disk storage is to use files as volumes that store data sequentially (as on tape volumes). You can use FILE sequential volumes to ship data electronically. For example, you can send the results of an export operation or a database backup operation to another location. At the receiving site, the files can be placed on tape or disk. You can define a device class with a device type of FILE.
Do the following to use the FILE device class:
For example, enter the following command on the command line of an administrative client:
define devclass fileclass devtype=file mountlimit=2
This command defines device class FILECLASS with a device type of FILE.
See Defining FILE Device Classes.
To store database backups or exports on FILE volumes, this step is all you need to do to prepare the volumes. For more information, see Defining Device Classes for Backups and Planning for Sequential Media Used to Export Data.
For example, enter the following command on the command line of an administrative client:
define stgpool engback2 fileclass maxscratch=100 mountlimit=2
This command defines storage pool ENGBACK2 with device class FILECLASS.
See Defining or Updating Primary Storage Pools for details.
To allow Tivoli Storage Manager to use scratch volumes for this device class, specify a number greater than zero for the number of maximum scratch volumes when you define the device class. If you set MAXSCRATCH=0 to not allow scratch volumes, you must define each volume to be used in this device class. See Defining Storage Pool Volumes for details.
Tivoli Storage Manager automatically creates the files to be used as sequential access volumes. Volume names can be defined using the DEFINE VOLUME command, or they can default to scratch.