Tivoli Header

Quick Start


Implementing the Tivoli Storage Manager Server Program (First Time Installation)

If you are installing Tivoli Storage Manager for the first time, perform the steps in this section and then continue at Getting Started.

Allocating the Required Server Data Sets

Note:
To help you prepare your Tivoli Storage Manager server, jobs ANRALLO1 and ANRALLO2 are available from the ASAMPLIB dataset. Modify the jobs as necessary.

ANRALLO2 requires that ANRFMT2 be modified as necessary and be placed in a procedure library (for example, SYS1.PROCLIB).

The server does not support VSAM Extended Format Linear Data sets. The server supports VSAM Linear Datasets that have been defined at 4GB or less.

At a minimum, you should allocate and format the following data sets:

TIVSM.DISKLOG
Holds the data set names for the virtual storage access method (VSAM) linear data sets used by the server

TIVSM.RCVRYLOG
Recovery log volume

TIVSM.DB1
Database volume

TIVSM.STORAGE.POOL001
Storage pool volume for backed up files

TIVSM.STORAGE.POOL002
Storage pool volume for archived files

TIVSM.STORAGE.POOL003
Storage pool volume (required only for the space management feature)

TIVSM.ANRSERV.OPTIONS
Server options file

To allocate these data sets (except for the TIVSM.DISKLOG data set) run the ANRALLO1 or ANRALLO2 job after modifying them to meet your needs. The TIVSM.DISKLOG is allocated in the ANRINST job later in the server installation process. See Initializing the Server Database and Recovery Log Volume.

If the SMS address space is not active, you must use the ANRALLO1 job. If the SMS address space is active you can use the ANRALLO2 job, which requires less modification.

Allocating Using the ANRALLO1 Job

Before running this job, modify the JCL statements as follows:

Figure 4 is a modified allocation example for the TSM server data sets. In this example, we allocate and format three storage pool data sets. If you are not implementing the space management feature on the server, you only need to allocate and format two storage pool data sets.

Figure 4. Example of Modified ANRALLO1 Job


//ANRALLO1 JOB ,
//        MSGLEVEL=(1,1),MSGCLASS=H,CLASS=A,REGION=40M,TIME=1440
//*
//*----------------------------------------------------*
//*
//* Allocate TSM server files:
//*      Options file
//*
//*----------------------------------------------------*
//ALLOOPT  EXEC PGM=IEFBR14
//OPTIONS   DD  DSN=TIVSM.ANRSERV.OPTIONS,DISP=(NEW,CATLG),
//        DCB=(RECFM=FB,BLKSIZE=6240,LRECL=80),SPACE=(TRK,(1,1)),
//          UNIT=3390,VOL=SER=TIVSM3
//*----------------------------------------------------*
//*      Recovery log volume:
//*----------------------------------------------------*
//*   allocate TIVSM.RCVRYLOG
//ALLOLOG  EXEC PGM=IDCAMS
//SYSPRINT  DD  SYSOUT=*
//SYSIN     DD  *
  DEFINE CLUSTER( NAME(TIVSM.RCVRYLOG) LINEAR MB(13) VOL(TIVSM1) )
/*
//*   format TIVSM.RCVRYLOG
//FMTLOG   EXEC PGM=DSMFMT,DYNAMNBR=300,COND=(0,NE,ALLOLOG),
//         PARM='/TIVSM.RCVRYLOG'
//DSMAMENG  DD  DSN=TIVSM.SANRMSG(ANRMENU),DISP=SHR
//SYSPRINT  DD  SYSOUT=*
//SYSTERM   DD  SYSOUT=*
//*----------------------------------------------------*
//*      Database volume:
//*----------------------------------------------------*
//*   allocate TIVSM.DB1
//ALLODB1  EXEC PGM=IDCAMS
//SYSPRINT  DD  SYSOUT=*
//SYSIN     DD  *
  DEFINE CLUSTER( NAME(TIVSM.DB1) LINEAR MB(21) VOL(TIVSM2) )
/*
//*   format TIVSM.DB1
//FMTDB1   EXEC PGM=DSMFMT,DYNAMNBR=300,COND=(0,NE,ALLODB1),
//         PARM='/TIVSM.DB1'
//DSMAMENG  DD  DSN=TIVSM.SANRMSG(ANRMENU),DISP=SHR
//SYSPRINT  DD  SYSOUT=*
//SYSTERM   DD  SYSOUT=*
//*----------------------------------------------------*
//*----------------------------------------------------*
//*      Storage pool volumes:
//*----------------------------------------------------*
//*   allocate TIVSM.STORAGE.POOL001
//ALLOPL1  EXEC PGM=IDCAMS
//SYSPRINT  DD  SYSOUT=*
//SYSIN     DD  *
  DEFINE CLUSTER( NAME(TIVSM.STORAGE.POOL001) LINEAR MB(320) VOL(TIVSM3) )
/*
//*   format TIVSM.STORAGE.POOL001
//FMTPL1   EXEC PGM=DSMFMT,DYNAMNBR=300,COND=(0,NE,ALLOPL1),
//         PARM='/TIVSM.STORAGE.POOL001'
//DSMAMENG  DD  DSN=TIVSM.SANRMSG(ANRMENU),DISP=SHR
//SYSPRINT  DD  SYSOUT=*
//SYSTERM   DD  SYSOUT=*
//*
//*
//*   allocate TIVSM.STORAGE.POOL002
//ALLOPL2  EXEC PGM=IDCAMS
//SYSPRINT  DD  SYSOUT=*
//SYSIN     DD  *
  DEFINE CLUSTER( NAME(TIVSM.STORAGE.POOL002) LINEAR MB(100) VOL(TIVSM3) )
/*
//*   format TIVSM.STORAGE.POOL002
//FMTPL2   EXEC PGM=DSMFMT,DYNAMNBR=300,COND=(0,NE,ALLOPL2),
//         PARM='/TIVSM.STORAGE.POOL002'
//DSMAMENG  DD  DSN=TIVSM.SANRMSG(ANRMENU),DISP=SHR
//SYSPRINT  DD  SYSOUT=*
//SYSTERM   DD  SYSOUT=*
//*
//*
//*   allocate TIVSM.STORAGE.POOL003
//ALLOPL3  EXEC PGM=IDCAMS
//SYSPRINT  DD  SYSOUT=*
//SYSIN     DD  *
  DEFINE CLUSTER( NAME(TIVSM.STORAGE.POOL003) LINEAR MB(100) VOL(TIVSM3) )
/*
//*   format TIVSM.STORAGE.POOL003
//FMTPL2   EXEC PGM=DSMFMT,DYNAMNBR=300,COND=(0,NE,ALLOPL3),
//         PARM='/TIVSM.STORAGE.POOL003'
//DSMAMENG  DD  DSN=TIVSM.SANRMSG(ANRMENU),DISP=SHR
//SYSPRINT  DD  SYSOUT=*
//SYSTERM   DD  SYSOUT=*
//

Allocating Using the ANRALLO2 Job

If the SMS address space is active and the ANRFMT2 procedure has been copied to a procedure library, you can use the ANRALLO2 job instead of the ANRALLO1 job to allocate and format the required server data sets. For information about the ANRFMT2 job, see Administrator's Guide. ANRALLO2 requires less modification than ANRALLO1.

Figure 5 is an example of an ANRALLO2 job that allocates and formats the same data sets that are allocated and formatted by the ANRALLO1 job in Figure 4.

Figure 5. Example of Modified ANRALLO2 Job


//ANRALLO2 JOB ,
//         MSGLEVEL=(1,1),MSGCLASS=H,CLASS=A,REGION=40M,TIME=1440
//*
//*----------------------------------------------------*
//*
//* Allocate TSM server files:
//*      Options file
//*
//*----------------------------------------------------*
//ALLOOPT  EXEC PGM=IEFBR14
//OPTIONS   DD  DSN=TIVSM.ANRSERV.OPTIONS,DISP=(NEW,CATLG),
//        DCB=(RECFM=FB,BLKSIZE=6240,LRECL=80),SPACE=(TRK,(1,1)),
//          UNIT=SYSDA,VOL=SER=TIVSM3
//*
//*----------------------------------------------------*
//*      Recovery log volume:
//*----------------------------------------------------*
//*   allocate and format TIVSM.RCVRYLOG
//ALLOLOG  EXEC PROC=ANRFMT2,
//         NAME=TIVSM.RCVRYLOG,MB=13,VOLSER=TIVSM1
//*
//*----------------------------------------------------*
//*      Database volume:
//*----------------------------------------------------*
//*   allocate and format TIVSM.DB1
//ALLODB1  EXEC PROC=ANRFMT2,
//         NAME=TIVSM.DB1,MB=21,VOLSER=TIVSM2
//*
//*----------------------------------------------------*
//*      Storage pool volumes:
//*----------------------------------------------------*
//*   allocate and format TIVSM.STORAGE.POOL001
//ALLOPL1  EXEC PROC=ANRFMT2,
//         NAME=TIVSM.STORAGE.POOL001,MB=320,VOLSER=TIVSM3
//*
//*   allocate and format TIVSM.STORAGE.POOL002
//ALLOPL2  EXEC PROC=ANRFMT2,
//         NAME=TIVSM.STORAGE.POOL002,MB=100,VOLSER=TIVSM3
//*
//*   allocate and format TIVSM.STORAGE.POOL003
//ALLOPL2  EXEC PROC=ANRFMT2,
//         NAME=TIVSM.STORAGE.POOL003,MB=100,VOLSER=TIVSM3

Initializing the Server Database and Recovery Log Volume

In this procedure, TSM prepares the disk log, recovery log, and database for normal use.

Before the TSM server can be started for normal operations, the database and recovery log volumes must be initialized. Use the sample job ANRINST from the ASAMPLIB dataset for this step. Modify ANRINST as necessary.

To indicate that initialization is required, you must specify the FORMAT parameter in the PARM keyword of the EXEC statement. Specify the PARM parameter:

+--------------------------------------------------------------------------------+
|PARM='/FORMAT <recovery log file spec> <data base file spec>'                   |
+--------------------------------------------------------------------------------+

where:

<recovery log file spec> is <number of files ><recovery log file_1 ... recovery log file_n>

and

<data base file spec> is <number of files><data base file_1 ... data base file_n>

The following example specifies one recovery log file (TIVSM.RCVRYLOG) and one database file (TIVSM.DB1):

+--------------------------------------------------------------------------------+
|PARM='/FORMAT 1 TIVSM.RCVRYLOG 1 TIVSM.DB1'                                     |
+--------------------------------------------------------------------------------+

The PARM keyword can be continued on multiple statements by continuing the data in column 16 of each statement. The limit is 100 characters. For example:

+--------------------------------------------------------------------------------+
|//TIVSMINST  EXEC PGM=DSMSERV,DYNAMNBR=300,                                     |
|//       PARM='/FORMAT 1 TIVSM.SRV1.RCVRYLOG 1 TIVSM.SRV1.DB1'                  |
+--------------------------------------------------------------------------------+

Figure 6 is a sample ANRINST job after it has been updated:

Figure 6. Example of Modified ANRINST Job


//ANRINST JOB MSGLEVEL=1,
//          REGION=160M,TIME=10,CLASS=A,MSGCLASS=H
//SERVER  EXEC PGM=DSMSERV,DYNAMNBR=300,
//          PARM='/FORMAT 1 TIVSM.RCVRYLOG 1 TIVSM.DB1'
//OPT      DD DSN=TIVSM.ANRSERV.OPTIONS,DISP=SHR
//DSMAMENG DD DSN=TIVSM.SANRMSG(ANRMENU),DISP=SHR
//*-----------------------------------------------------*
//*  The TSM Disk Log data set is allocated and created as a    */
//*  result of this job. The data sets identified in the PARM   */
//*  field of the EXEC statement WILL be (re-)formatted and     */
//*  if they were previously used, the existing information will*/
//*  be lost.  DO NOT execute this job unless it is absolutely  */
//*  necessary.  It must not be used when upgrading. */
//*-----------------------------------------------------*
//DSK      DD DSN=TIVSM.DISKLOG,DISP=(NEW,CATLG),SPACE=(TRK,(1,1)),
//             UNIT=3390,VOL=SER=TIVSM3,
//             DCB=(RECFM=FB,BLKSIZE=800,LRECL=80)
//SYSPRINT DD SYSOUT=*
//SYSTERM  DD SYSOUT=*

Specifying Server Communication Options

This section describes how to set server communication options. Server options take effect after server is started. For details about these and other options, see Administrator's Reference.

Creating Server Options Data Set

Copy the member ANRSMPOP from the ASAMPLIB dataset to the sequential data set TIVSM.ANRSERV.OPTIONS (created by either ANRALLO1 or ANRALLO2). The options in ANRSMPOP are enough to start the server for the first time. They can be modified at this time or later.

Note:
The server options file must not be a member of a partitioned data set.

Configuring Communication Protocols

Before starting the server, you must update the client/server communication method. You can specify the following communication methods:

Communication Method Server Options
TCP/IP TCPPORT and TCPNAME
3270 or APPC (LU 6.2) LUNAME
IUCV IUCV
TCPaccess ICSPORT and ICSSNAME
TCPaccess HTTP HTTPICSPORT
TCP/IP HTTP HTTPTCPPORT
InfoSpeed PDMNAME and PDMPORT
See Chapter 3, Server and Client Communications for information about configuring server and client communications. After you have completed the client-server communication configuration, go to the next section.

Setting the DEVCONFIG and VOLUMEHISTORY Options

We recommend that you set the DEVCONFIG and VOLUMEHISTORY options at this time. These options are important in the recovery of your database if it is destroyed or unavailable.

The DEVCONFIG option specifies the name of a data set in which TSM stores a backup copy of device configuration information. The VOLUMEHISTORY option specifies the name of a data set in which TSM stores a copy of volume history information. For example, specify TIVSM.DEVCONF1.DATA for the DEVCONFIG option and TIVSM.SERV1.DATA for the VOLUMEHISTORY option. You do not have to allocate the data sets.

You can specify the DEVCONFIG and VOLUMEHISTORY options multiple times to keep more than one backup file of device configuration and volume history information. Each time you specify them, use a different data set name.

For details about the DEVCONFIG and VOLUMEHISTORY options, see Administrator's Reference. For information about TSM database backup and recovery features, see Administrator's Guide.

Starting the Server for Normal Operation

Modify the ANRSTART job from the ASAMPLIB dataset to meet your needs. You can modify:

Figure 7 is an example of a modified ANRSTART job with a STEPLIB DD statement for the runtime library SYS1.SCEERUN and TIVSM.LINKLIB.

Figure 7. Example of Server Startup JCL


 //TIVSM      JOB (999,POK),'TIVSM START',CLASS=A,MSGLEVEL=(1,1),
 //          MSGCLASS=T,REGION=256M,TIME=1440
 //SERVER  EXEC PGM=DSMSERV,DYNAMNBR=300
 //*------------------------------------------------------------------*
 //*                                                                  *
 //*  The STEPLIB ddname is associated with two libraries:            *
 //*          TIVSM.LINKLIB and SCEERUN.                              *
 //*                                                                  *
 //*------------------------------------------------------------------*
 //*
 //STEPLIB   DD DSN=TIVSM.LINKLIB,DISP=SHR
 //          DD DSN=SYS1.SCEERUN,DISP=SHR
 //OPT       DD DSN=TIVSM.ANRSERV.OPTIONS,DISP=MOD
 //DSMAMENG  DD DSN=TIVSM.SANRMSG(ANRMENU),DISP=SHR
 //HLPAMENG  DD DSN=TIVSM.SANRHLP(ANRHENU),DISP=SHR
 //IMAGES    DD DSN=TIVSM.SANRIMG(TIVSMSERV),DISP=SHR
 //DSK       DD DSN=TIVSM.DISKLOG,DISP=SHR
 //SYSPRINT  DD SYSOUT=*
 //SYSPRINT  DD SYSOUT=*

Submit the job to start the server. When operational, the server displays a message saying that initialization is complete, and the TSM prompt displays.

Note:
To start the server as a procedure, update ANRPROC from the ASAMPLIB dataset and install it on a system procedure library (for example, SYS1.PROCLIB).


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