Tivoli Header

Administrator's Guide


Configuring Disk Devices

Tivoli Storage Manager stores data on magnetic disks in two ways:


Task Required Privilege Class
Configuring Random Access Volumes on Disk Devices

Configuring FILE Sequential Volumes on Disk Devices

System

Configuring Random Access Volumes on 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:

  1. Format a random access volume. Use the ANRFMT or ANRFMT2 job. See Using the ANRFMT Job or Using the ANRFMT2 Job.
    Note:
    The server does not support VSAM Extended Format Linear Datasets. The server supports VSAM Linear Datasets that have been defined at 4GB or less.
  2. Define a storage pool that is associated with the DISK device class, or use one of the default storage pools that provides (ARCHIVEPOOL, BACKUPPOOL, and SPACEMGPOOL).

    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 Storage Pools for details.

  3. Define the DISK volumes formatted in step 1 to the storage pool.

    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.

  4. Do one of the following:

Using the ANRFMT Job

Edit the ANRFMT job from the ASAMPLIB data set as follows:

  1. Customize the JOB card parameters for your installation.
  2. In the DEFINE CLUSTER statement:
  3. Enter the name of the new data set in the PARM parameter of the TIVSMFMT EXEC statement.

Figure 4. 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=*
//

Using the ANRFMT2 Job

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:

<name>
The new data set to define for server usage

<mb>
The size in megabytes

<volser>
The volume on which to allocate <name>

Figure 5. 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.

Configuring FILE Sequential Volumes on Disk Devices

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 transfer data for purposes such as electronic vaulting. 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.

To use files as volumes that store data sequentially, do the following:

  1. Define a device class with device type FILE.

    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.

  2. Define a storage pool that is associated with the new FILE device class.

    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 value greater than zero for the number of maximum scratch volumes when you define the device class. If you do set MAXSCRATCH=0 to not allow scratch volumes, you must define each volume to be used in this device class. See Preparing Volumes for Sequential Access Storage Pools for details.

  3. Do one of the following:


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