publib.boulder.ibm.compublib.boulder.ibm.com/tividd/td/tsm390n/gc35-0415... · contents...

Tivoli Storage Managerfor OS/390 and z/OSQuick StartVersion 4 Release 2 GC35-0415-01

Note!Before using this information and the product it supports, be sure to read the general information under “Notices” on page 123.

Second Edition (June 2001)

This edition applies to Version 4 Release 2 of Tivoli Storage Manager for OS/390® and z/OS, program 5697–TS9,5698–TSM, and to any subsequent releases until otherwise indicated in new editions or technical newsletters. Makesure you are using the correct edition for the level of the product.

Changes since the last edition are marked with a vertical bar (|) in the left margin. Ensure that you are using the correctedition for the level of the product.

Order publications through your IBM® representative or the IBM branch office serving your locality.

Your feedback is important in helping to provide the most accurate and high-quality information. If you have commentsabout this book or any other Tivoli Storage Manager documentation, please see “Contacting Customer Support” onpage 119.

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

© Copyright International Business Machines Corporation 1993, 2001. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

|||

||

Contents

Summary of Changes for Tivoli Storage Manager Version 4 . . . . . . . . . . . . viiChanges for Version 4 Release 2—June 2001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Changes for Version 4 Release 1—July 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixWhat You Should Know First . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Tivoli Storage Manager Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Conventions Used in This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Types of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Where Tasks Are Performed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Installation and Setup Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Basic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Advanced Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1. Setting Up Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Information Required for Using Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Using ASAMPLIB for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Migrating to Tivoli Storage Manager Version 4.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

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

Allocating the Required Server Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Initializing the Server Database and Recovery Log Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Specifying Server Communication Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Starting the Server for Normal Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Registering an Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Starting an Administrative Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Stopping the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Registering Tivoli Storage Manager Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Registering Backup-Archive Client Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Verifying Your Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 2. Server and Client Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Configuring the Server for APPC (SNALU6.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Key VTAM Statement Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Server Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Configuring the OS/2 Client for APPC (SNALU6.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Key to the Window Abbreviation Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

iiiTivoli Storage Manager for OS/390 and z/OS Quick Start

||

Client Options File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring the Novell Client for APPC (SNALU6.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Key to Window Where Parameters Appear. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Client Options File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Configuring the Server for APPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Connectivity Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

VTAM Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Example of Configuring the MVS Server with APPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Configuring an MVS Server in a Cross-Domain Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configuring an MVS Server in a Single-Domain Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Configuring Tivoli Storage Manager Clients to the MVS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Configuring the OS/2 Client for APPC Using Communication Manager/2. . . . . . . . . . . . . . . . . . . . . 40

Starting the Tivoli Storage Manager Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Considerations for Using OS/2 Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuring Novell NetWare Client for APPC Using NetWare Requester . . . . . . . . . . . . . . . . . . . . . 47


Considerations for Using NetWare for SAA Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Configuring the Server for 3270 Emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50


VTAM Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Configuring the Server for TCP/IP Using IBM TCP/IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51


TCP/IP Communications Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Tivoli Storage Manager Server Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Configuring the Server for TCP/IP Using TCPaccess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53


TCPaccess Communications Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53


Configuring the Server for IUCV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54



Configuring the Server for Web Access with IBM TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring the Server for Web Access with TCPaccess. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Connecting with Tivoli Storage Manager across a Firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring a DOS Client for 3270 Emulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Configuring TSO Administrative Client Using APPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Configuring AIX SNA Server/6000 Clients Using SMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59


iv Version 4 Release 2

||

Considerations for Using the SNA Services/6000 Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Diagnosing Initial Connection Failures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Determining CPI-C Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Analyzing CPI-C Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Gathering Initial Documentation for Level-2 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Obtaining Sense Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Results Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

CM/2 .ndf File for 3174 Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

CM/2 .ndf File for 3172 or 3745 Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

SNA Profile for AIX Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 3. Customizing Your Tivoli Storage Manager System . . . . . . . . . . 83Defining Storage Pool Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Increasing Database and Recovery Log Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Using Tape Devices with Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Adding Tape Devices to Your Tivoli Storage Manager Environment . . . . . . . . . . . . . . . . . . . . . 86

Preparing Tape Volumes for Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Including Tape in the Server Storage Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Verifying the Tape Device Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Creating a New Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Invoking Expiration Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Creating a Client Include-Exclude List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Automating Client Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Automating Administrative Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Protecting Tivoli Storage Manager and Client Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Appendix A. Tivoli Storage Manager Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . 97System-Managed Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Server Storage Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Tivoli Storage Manager Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Storage Devices and Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Automating Client Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Working with a Network of Tivoli Storage Manager Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Appendix B. Using Administrative Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Using the Administrative Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Operation View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

vTivoli Storage Manager for OS/390 and z/OS Quick Start

Network View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Object View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Using the Administrative Client Command-Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Using Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Appendix C. Setting Up the Secure Web Administrator Proxy . . . . . . . . . 109Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Installing the Secure Web Administrator Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Configuring the Secure Web Administrator Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Uninstalling the Secure Web Administrator Proxy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Troubleshooting the Secure Web Administrator Proxy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Appendix D. Tape Processing Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 115Defining Tivoli Storage Manager to Your Tape Management System . . . . . . . . . . . . . . . . . . . . . . . 115

Specifying Permanent Tape Retention. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Setting Up Tape Installation-Wide Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Identifying the Deletion Exit to the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Writing the Deletion Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Registers on Entry to the Deletion Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Deletion Exit Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Registers on Exit from the Deletion Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Appendix E. Where to Look for Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Contacting Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Reporting a Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Tivoli Storage Manager Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Referenced OS/390 and z/OS System Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Related IBM Hardware Products Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Appendix F. Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

vi Version 4 Release 2

Summary of Changes for Tivoli Storage Manager Version 4

Changes for Version 4 Release 2—June 2001The following changes have been made to the product for this edition:

Maximum Size of the Recovery Log IncreasedThe maximum size of the recovery log is increased to 13GB. Significantlyincreasing the size of your recovery log could also significantly increase the timerequired to restart the server, to back up the database, and to restore the database.

Support for Unicode-enabled Client File SpacesFor Windows NT® and Windows® 2000 client systems that are Unicode, the servernow supports storing Unicode file space names, directory names, and file names inUnicode-enabled file spaces. Unicode is a universal character encoding standard thatsupports the interchange, processing, and display of text that is written in any of thelanguages of the modern world. The Unicode-enabled TSM client software must beinstalled on the client systems. New clients that do not yet have any data stored onthe server automatically store data in Unicode-enabled file spaces.

While clients that already have data stored on the server will store any new filespaces as Unicode enabled, these clients do not automatically store their existingdata in Unicode-enabled file spaces. As an administrator, you can migrate theseclients by using the function for automatic file space renaming. TSM renamesexisting file spaces to force the creation of new, Unicode-enabled file spaces. Youcan also allow clients to make the choice about renaming. Once the existing filespaces are renamed on the server, a backup or archive operation causes the filespaces to be created again in server storage, this time as Unicode-enabled filespaces. If you have a large number of clients that are Unicode, or a large amount ofdata on clients that are Unicode, you need to plan the migration.

The addition of support for Unicode may affect the results of some SELECTcommands, because the sorting of information such as file space names is affected.

Using the TSM Client Acceptor to Manage the SchedulerThe client acceptor daemon or service manages the Web backup-archive client. Userscan now select to have the client acceptor also manage the scheduler on the clients.The client acceptor starts the scheduler and the client only when needed to run aTSM schedule. Using the client acceptor to start the scheduler can alleviate problemswith memory consumed by the scheduler. Also, if users are already running theclient acceptor to manage the Web client, they can reduce the number of processesrunning continuously on their machines. See the user’s guide for the appropriateclient.

Improved ANR9999D MessagesBy setting message context reporting on, you get additional information when theserver issues ANR9999D messages. The additional information can help to identifyproblem causes. See the SET CONTEXTMESSAGING command in Administrator’sReference. Also see Messages.

Reclaiming Space in Aggregates During Data MovementYou can specify to have the server reconstruct aggregates during data movement.Reconstruction reclaims empty space that has accumulated as a result of deletion oflogical files from an aggregate.

viiTivoli Storage Manager for OS/390 and z/OS Quick Start

|

|

||||

||||||||

||||||||||

||

|||||||||

|||||

||||

Changes for Version 4 Release 1—July 2000The following changes have been made for Version 4:

Support for Mobile ClientsThis enhancement allows mobile users to back up files and make subsequentbackups to the portion (a subfile) of the file that has changed, rather than the entirefile. This type of backup allows remote or mobile users using modems with limitedbandwidth to reduce connection time, network traffic, and the time it takes to do abackup. This enhancement also uses encryption to protect clients’ data.

LicensingA client is now licensed as a managed system. A managed system can be a client orserver that requires backup services from the TSM server. The following table listschanges to license names:

Table 1. License Name ChangesFormer name Current name Notes

Client Connections Managed System for LAN

Extended Device Support Managed Library

viii Version 4 Release 2

|

Before You Begin

Tivoli Storage Manager provides automated, policy-based storage management for fileservers and workstations. This publication helps you install and configure a practical system.It explains how to:¶ Install the server on OS/390 and z/OS¶ Define the communication network for server and clients¶ Configure Tivoli Storage Manager for your environment

What You Should Know FirstBefore using this publication, you should be familiar with:¶ OS/390 and z/OS operating systems¶ Devices that TSM can use¶ Workstation operating systems on which the clients reside¶ Communication protocols required for the client/server environment¶ Procedures for backing up your workstation

Tivoli Storage Manager Web SiteAll TSM publications are available on the TSM home page on the World Wide Web at thisaddress: http://www.tivoli.com/support/storage_mgr/tivolimain.html

By accessing the TSM home page, you can access subjects that interest you. You can alsokeep up-to-date with the newest TSM product information.

Conventions Used in This BookThis section describes the conventions used in this book.

Types of InformationThe following conventions help you to identify types of information:

Important tips or cautions

Detailed information that is useful, but not essential, in performing a task

Tips to help you avoid or correct problems

Where Tasks Are PerformedThe following conventions identify where to perform the associated tasks:

OS/390 and z/OS MODIFY command

Administrative client command line

ixTivoli Storage Manager for OS/390 and z/OS Quick Start

http://www.tivoli.com/support/storage_mgr/tivolimain.html

Administrative web interface

End user client command line

End user client graphical user interface

Installation and Setup ResultsAfter you complete the tasks in “Setting Up Tivoli Storage Manager” on page 1, the defaultTivoli Storage Manager system will consist of the following:

DatabaseSized for your system

Recovery LogSized for your system

Disk Storage PoolsThree disk storage pools sized for your system:¶ BACKUPPOOL¶ ARCHIVEPOOL¶ SPACEMGPOOL

Standard policyObjects for a default storage policy are defined (all are named STANDARD). Thispolicy specifies the following:¶ When a backed up file is no longer associated with a backup copy group, it

remains in server storage for 30 days.¶ When an archived file is no longer associated with an archive copy group, it

remains in server storage for 365 days.¶ Client files are not space managed.¶ For backup operations:

v Files are backed up to the default disk storage pool, BACKUPPOOL.

v An incremental backup is performed only if the file has changed since thelast backup.

v Files cannot be backed up while they are being modified.

v Up to two backup versions of a file on the client’s system are retained inserver storage. The most recent backup version is retained for as long as theoriginal file is on the client file system. All other versions are retained for upto 30 days.

v One backup version of a file that has been deleted from the client’s system isretained in server storage for 60 days.

¶ For archive operations:

v Files are backed up to the default disk storage pool, ARCHIVEPOOL.

v Files cannot be archived while they are being modified.

v An archive copy is kept for up to 365 days.

x Version 4 Release 2

Basic TasksHere is an overview of the tasks of installing and customizing Tivoli Storage Manager, withpointers to the details of the procedures:

1. Installing the server (see Tivoli Storage Manager Program Directory and “Setting UpTivoli Storage Manager” on page 1)

2. “Registering an Administrator” on page 13

3. “Registering Tivoli Storage Manager Licenses” on page 17

4. “Registering Backup-Archive Client Nodes” on page 18

5. “Verifying Your Server Installation” on page 19

6. “Customizing Your Tivoli Storage Manager System” on page 83

a. “Defining Storage Pool Volumes” on page 83

b. “Increasing Database and Recovery Log Sizes” on page 84

c. “Using Tape Devices with Tivoli Storage Manager” on page 85

d. “Creating a New Policy” on page 88

e. “Automating Client Operations” on page 92

f. “Automating Administrative Commands” on page 94

Advanced TasksTo take full advantage of Tivoli Storage Manager, you may want to perform other tasksdescribed in the Administrator’s Guide, including the following:

Network of serversCreate a network of servers that can:¶ Share object definitions such as storage policies, administrators, and command

scripts¶ Store information in each other’s storage pools¶ Route commands to one or more servers

Server and storage pool protection¶ Mirror your database and recovery log¶ Back up your database and storage pools¶ Recover lost or damaged database and storage pool data

Storage Pools and Volumes¶ Back up your storage pools¶ Move files from one volume to another

Storage Policies¶ Provide clients on some platforms with space management services¶ Provide additional functions to backup and archive services

Security¶ Let clients access Tivoli Storage Manager without requiring passwords¶ Modify the password expiration interval¶ Assign levels of administrator authority¶ Specify the minimum password length¶ Force a client or administrator to change the password

xiTivoli Storage Manager for OS/390 and z/OS Quick Start

Server OperationsMonitor and control:¶ Server processes¶ Client sessions¶ TSM activity log¶ TSM accounting records¶ Logging facilities used to monitor server activity

xii Version 4 Release 2

Setting Up Tivoli Storage Manager

See the Tivoli Storage Manager Program Directory for code installation. This chapterdescribes the following tasks:

Task: Procedure:

Migrate Tivoli Storage Manager from a previous licensedversion to Version 4.2

“Migrating to Tivoli Storage Manager Version 4.2” onpage 3

Setting Up Tivoli Storage Manager for the first time “Implementing the Tivoli Storage Manager ServerProgram (First Time Installation)” on page 5

Set up the server “Getting Started” on page 12

When you install Tivoli Storage Manager, the following are available:¶ Tivoli Storage Manager server¶ One administrative client, named SERVER_CONSOLE

See “Installation and Setup Results” on page x for details about the results of the installation.

For requirements, supported devices, client code, and fixes, go to the TSM Website at http://www.tivoli.com/support/storage_mgr/tivolimain.html

After you have installed Tivoli Storage Manager and before you begin to customizeit for your use, go to the TSM Web site. Download and apply any applicable fixes.

Information Required for Using Tivoli Storage ManagerThis section describes the JCL, data sets, and time coordination used with Tivoli StorageManager.

Using ASAMPLIB for InstallationTivoli Storage Manager provides sample JCL in the ASAMPLIB data set that you canmodify to help you prepare the server. The following members are available:

ANRALLO1Allocates and formats the required server data sets.

ANRALLO2Allocates and formats the required server data sets instead of ANRALLO1 if theSMS address space has been started. ANRALLO2 requires less modification thanANRALLO1.

ANRIDLLoads the TSM database with interface definitions used by the administrative webinterface.

1

1Tivoli Storage Manager for OS/390 and z/OS Quick Start

1.Settin

gUpTivo

liStorag

eMan

ager


ANRINSTInitializes the TSM server database and recovery log.

ANRSMPOPContains a sample server options file.

ANRSTART/ANRPROCStarts and runs the TSM server in normal mode after it has been installed andinitialized.

ASAMPLIB also contains other members that can help you complete other tasks afterinstallation is complete. These members include:

ANRFMTAllocates and formats a new TSM VSAM linear data set. Also extends the databaseand recovery log or creates new storage pool volumes. See Administrator’s Guide fordetails.

ANRFMT2Allocates and formats a new TSM VSAM linear data set instead of ANRFMT if theSMS address space is active. ANRFMT2 requires less modification than ANRFMT.See Administrator’s Guide for details.

ANRLEVELDetermines the level of SVM available on your system.

ANRSIVPContains TSM commands for installation verification. See “Verifying Your ServerInstallation” on page 19.

ANRUSRXAContains assembler DSECT that defines the user exit buffer and the record writtenby the file exit.

ANRUSRXCContains a sample user exit for event logging (written in C).

ANRUSRXHContains a sample C definition of the user exit buffer and the record written by thefile exit.

ANSCLISTContains a sample TSO CLIST for starting a TSO administrative client. See“Configuring TSO Administrative Client Using APPC” on page 56.

ANSPROCContains a sample TSO procedure for starting a TSO administrator client. See“Configuring TSO Administrative Client Using APPC” on page 56.

ANSSMPOPContains a sample TSO administrative client options file. See “Configuring TSOAdministrative Client Using APPC” on page 56.

2 Version 4 Release 2

Migrating to Tivoli Storage Manager Version 4.2If you have previously used Disaster Recovery Manager (DRM) to create a disaster recoveryplan file, that file refers to names that may no longer be valid. After you have installedTivoli Storage Manager, you should back up your storage pools and database and create anew disaster recovery plan file. For the sequence and details of the procedure, see the″Using Tivoli Disaster Recovery Manager″ chapter in the Administrator’s Guide.

Use this procedure if you already have a previous version of Tivoli Storage Managerinstalled and you have:

¶ Database, recovery log, and disk storage pool volumes initialized and defined

¶ One or more administrative clients installed and registered

¶ Backup-archive clients installed and registered

Do the following:

1. Use the BACKUP DB command to dump the contents of the server database to tape.For example:

backup db devclass=cartridge scratch=yes

2. Store the output volumes in a safe location. These volumes will be needed to restoreyour database to the pre-4.2 level of the Tivoli Storage Manager server. If you need torestore the database to the pre-4.2 level of the server, call the IBM support center forassistance.

3. Install Tivoli Storage Manager Version 4.2. Use the Tivoli Storage Manager ProgramDirectory.

4. Update your current server options file if necessary. See Administrator’s Reference forthe Version 4.2 options.

5. Ensure that the REGION parameter on the JCL that is used to start the TSM server(ANRSTART) is set to at least 160MB (REGION=160M).

6. Include or modify the IMAGES DD statement for the administrative web interfaceimage files in the ANRSTART job. For example,

//IMAGES DD DSN=TIVSM.SANRIMG(WEBSERV2),DISP=SHR

7. Upgrade your database to the Tivoli Storage Manager Version 4.2 level. Specify theUPGRADEDB parameter in the EXEC statement of the TSM server startup up jobANRSTART. For example,

//SERVER EXEC PGM=DSMSERV,DYNAMNBR=300,PARM=‘/UPGRADEDB’

8. Start the server by submitting the Tivoli Storage Manager server startup job with theUPGRADEDB parameter.

9. Stop the server using the HALT command:

halt


||||

|||

||||

|

1.Settin

gUpTivo

liStorag

eMan

ager

10. Remove PARM=’/UPGRADEDB’ from the EXEC statement of the server startup job.The upgrade must be done only once.

11. To use the administrative web interface, modify then run the ANRIDL job fromASAMPLIB. Here is an example of an ANRIDL job:

After IDL initialization completes, the server halts.

Note: You must specify either HTTPTCPPORT or HTTPICSPORT in the serveroptions file, TIVSM.ANRSERV.OPTIONS, to use the web interface. For detailssee “Configuring the Server for Web Access with IBM TCP/IP” on page 54 and“Configuring the Server for Web Access with TCPaccess” on page 54.

12. TSM is shipped with sample command scripts that can be loaded into the database andrun from an administrative client or an administrative web interface. They can also beincluded in TSM administrative command schedules. The sample scripts, in theANRSCRPT member of the ASAMPLIB dataset, are primarily SELECT queries, butalso include scripts that define volumes and extend the database and recovery log andthat backup storage pools. To load the sample scripts into the database, run thefollowing job:

Note: The sample scripts may have been loaded when a previous version of ADSM orTSM was installed. Loading the sample scripts again at this point will overlayany existing scripts of the same name and any modifications made to thosescripts will be lost.

13. Restart the server.

//TIVSM JOB MSGLEVEL=(1,1)// REGION=160M,TIME=10,CLASS=A,MSGCLASS=H//*-----------------------------------------------------*//* This sample JOB loads the server database with Interface//* Definitions that are used for the WEB Administrative Interface.//*-----------------------------------------------------*SERVER EXEC PGM=DSMSERV,PARM='/RUNFILE DD:IDL',DYNAMNBR=300//OPT DD DSN=TIVSM.ANRSERV.OPTIONS,DISP=MOD//DSMAMENG DD DSN=TIVSM.SANRMSG(ANRMENU),DISP=SHR//HLPAMENG DD DSN=TIVSM.SANRHLP(ANRHENU),DISP=SHR//IDL DD DSN=TIVSM.SANRIMG(ANRIDL),DISP=SHR//DSK DD DSN=TIVSM.DISKLOG,DISP=SHR//SYSPRINT DD SYSOUT=*//SYSTERM DD SYSOUT=*

Figure 1. Example of Modified ANRIDL Job

//TIVSM JOB MSGLEVEL=(1,1)// REGION=160M,TIME=10,CLASS=A,MSGCLASS=H//*-----------------------------------------------------*//* This sample JOB loads the server database with sample//* server SCRIPTs.//*-----------------------------------------------------*//SERVER EXEC PGM=DSMSERV,PARM='/RUNFILE DD:SCRIPT',DYNAMNBR=300//OPT DD DSN=TIVSM.ANRSERV.OPTIONS,DISP=MOD//DSMAMENG DD DSN=TIVSM.SANRMSG(ANRMENU),DISP=SHR//HLPAMENG DD DSN=TIVSM.SANRHLP(ANRHENU),DISP=SHR//SCRIPT DD DSN=TIVSM.SAMPLIB(ANRSCRPT),DISP=SHR//DSK DD DSN=TIVSM.DISKLOG,DISP=SHR//SYSPRINT DD SYSOUT=*//SYSTERM DD SYSOUT=*


Implementing the Tivoli Storage Manager Server Program (FirstTime Installation)

If you are installing Tivoli Storage Manager for the first time, perform the steps in thissection and then continue at “Getting Started” on page 12.

Allocating the Required Server Data Sets

Note: To help you prepare your Tivoli Storage Manager server, jobs ANRALLO1 andANRALLO2 are available from the ASAMPLIB dataset. Modify the jobs asnecessary.

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

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

TIVSM.DISKLOGHolds the data set names for the virtual storage access method (VSAM) linear datasets used by the server

TIVSM.RCVRYLOGRecovery log volume

TIVSM.DB1Database volume

TIVSM.STORAGE.POOL001Storage pool volume for backed up files

TIVSM.STORAGE.POOL002Storage pool volume for archived files

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

TIVSM.ANRSERV.OPTIONSServer options file

To allocate these data sets (except for the TIVSM.DISKLOG data set) run the ANRALLO1or ANRALLO2 job after modifying them to meet your needs. The TIVSM.DISKLOG isallocated in the ANRINST job later in the server installation process. See “Initializing theServer Database and Recovery Log Volume” on page 9.

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

Allocating Using the ANRALLO1 JobBefore running this job, modify the JCL statements as follows:

¶ Customize the job card for your installation.

¶ For the OPTIONS DD statement, assign a volume for the VOL=SER= parameter.

¶ For each of the VSAM data sets to be allocated (such as TIVSM.RCVRYLOG andTIVSM.DB1), specify the size of the data set with the MB(_) parameter in the DEFINECLUSTER statement.


1.Settin

gUpTivo

liStorag

eMan

ager

You can, as an alternative, use the allocations provided by the ANRALLO1 job. Theseinitial allocations are enough to run the server for the first time. Later, when you start toimplement storage management policies for your client workstations, you can increasethe size of the database, recovery log, and storage pools while the server is running.

¶ For each VSAM data set assign a volume serial in the DEFINE CLUSTER statement.

Figure 2 on page 7 is a modified allocation example for the TSM server data sets. In thisexample, we allocate and format three storage pool data sets. If you are not implementingthe space management feature on the server, you only need to allocate and format twostorage pool data sets.


//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=*

Figure 2. Example of Modified ANRALLO1 Job (Part 1 of 2)


1.Settin

gUpTivo

liStorag

eMan

ager

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

Figure 3 on page 9 is an example of an ANRALLO2 job that allocates and formats the samedata sets that are allocated and formatted by the ANRALLO1 job in Figure 2 on page 7.

//*//*//* 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=*//

Figure 2. Example of Modified ANRALLO1 Job (Part 2 of 2)


Initializing the Server Database and Recovery Log VolumeIn 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 logvolumes must be initialized. Use the sample job ANRINST from the ASAMPLIB dataset forthis step. Modify ANRINST as necessary.

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

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

where:

//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

Figure 3. Example of Modified ANRALLO2 Job


1.Settin

gUpTivo

liStorag

eMan

ager

<recovery log file spec> is <number of files ><recovery log file_1 ... recovery logfile_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 databasefile (TIVSM.DB1):

PARM=‘/FORMAT 1 TIVSM.RCVRYLOG 1 TIVSM.DB1’

The PARM keyword can be continued on multiple statements by continuing the data incolumn 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 4 is a sample ANRINST job after it has been updated:

Specifying Server Communication OptionsThis section describes how to set server communication options. Server options take effectafter server is started. For details about these and other options, see Administrator’sReference.

Creating Server Options Data SetCopy the member ANRSMPOP from the ASAMPLIB dataset to the sequential data setTIVSM.ANRSERV.OPTIONS (created by either ANRALLO1 or ANRALLO2). The optionsin ANRSMPOP are enough to start the server for the first time. They can be modified at thistime or later.

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

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

Figure 4. Example of Modified ANRINST Job


Configuring Communication ProtocolsBefore starting the server, you must update the client/server communication method. You canspecify 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 “Server and Client Communications” on page 25 for information about configuringserver and client communications. After you have completed the client-server communicationconfiguration, go to the next section.

Setting the DEVCONFIG and VOLUMEHISTORY OptionsWe 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 orunavailable.

The DEVCONFIG option specifies the name of a data set in which TSM stores a backupcopy of device configuration information. The VOLUMEHISTORY option specifies thename 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.DATAfor the VOLUMEHISTORY option. You do not have to allocate the data sets.

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

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

Starting the Server for Normal OperationModify the ANRSTART job from the ASAMPLIB dataset to meet your needs. You canmodify:

¶ The job card parameters

¶ Any DD statements necessary to refer to libraries required by Tivoli Storage Manager.

For example, the server requires an LE runtime library to be available at server startup.If the runtime library is not part of your link library list, specify the library on aSTEPLIB DD statement in ANRSTART.

Figure 5 on page 12 is an example of a modified ANRSTART job with a STEPLIB DDstatement for the runtime library SYS1.SCEERUN and TIVSM.LINKLIB.


1.Settin

gUpTivo

liStorag

eMan

ager

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

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

Getting StartedThis section describes the following tasks:

¶ “Registering an Administrator” on page 13

¶ “Starting an Administrative Client” on page 13

¶ “Stopping the Server” on page 16

¶ “Registering Tivoli Storage Manager Licenses” on page 17

¶ “Registering Backup-Archive Client Nodes” on page 18

¶ “Verifying Your Server Installation” on page 19

You can perform most of the tasks mentioned in this section from either anadministrative command line or web interface. See “Using AdministrativeInterfaces” on page 103 for details about each.

All of the administrative commands in this book are shown as issued from an administrativecommand line. The commands can also be issued with the MVS™ MODIFY command as inthe example shown here:

f server,command

server The name of the JOB under which the TSM server is running. For example, TIVSMis the name of the job started in Figure 5.

//TIVSM JOB (999,POK),'TIVSM START',CLASS=A,MSGLEVEL=(1,1),// MSGCLASS=T,REGION=160M,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=*

Figure 5. Example of Server Startup JCL


commandA TSM command.

Registering an AdministratorYou must register an administrator before you can perform the tasks that follow in thissection. Using the MVS MODIFY command, register the administrator ADMIN with thepassword ADMIN. Then give ADMIN the highest authority level, SYSTEM. For detailsabout the other authority levels, see the TSM Administrator’s Reference.

f server,register admin admin adminf server,grant authority admin classes=system

server The name of the JOB under which the TSM server is running. For example, TIVSMis the name of the job started in Figure 5 on page 12.

Changing the Administrative Client PasswordIf you wish, you can change the password of administrator ADMIN at this point. To changethe password to TUCSON, for example, do the following:

update admin admin tucson

OR

1. Select Administrators.

2. Select the desired administrator name.

3. From Operations, select Update an Administrator.

4. Enter the administrator information and Finish.

Refer to TSM Administrator’s Reference for the command syntax and the minimum numberof characters that can be specified.

Starting an Administrative ClientThe TSM server must be running before any client can connect.

Notes:

1. The TSM server must be running before any client can connect.

2. The communications method that an administrative client uses to connect to the TSMserver must be defined in the server options file. See “Specifying Server CommunicationOptions” on page 10.

3. The client options file must be prepared with the appropriate communications methodand related options. Refer to Tivoli Storage Manager Installing the Clients.

This section describes how to start the TSO administrative client and the web interface.Follow the instructions under “Starting the TSO Administrative Client” on page 14 to startthe TSO client and follow the instructions under “Starting the Administrative Web Interface”on page 16 to start the web interface.


1.Settin

gUpTivo

liStorag

eMan

ager

For information on starting all other clients, refer to Tivoli Storage Manager Installing theClients.

When you start the administrative client, you must enter an administrator name andpassword. The administrator ADMIN with a password of ADMIN was defined earlier andshould be used.

Start an administrative client session in command line mode by entering this command onyour workstation:

dsmadmc -id=admin -password=admin

Starting the TSO Administrative ClientThe ANSPROC member of the ASAMPLIB dataset contains a sample TSO logon procedurefor the TSO administrative client. Create or modify this logon procedure and make itavailable to the TSO user ID that will be used to administer Tivoli Storage Manager.Figure 6 is an example of a modified logon procedure.

As an alternative to using the ANSPROC member to start the TSO administrative client, youcan use the ANSCLIST CLIST procedure from the ASAMPLIB dataset by modifying it andadding it to your CLIST library. Figure 7 shows the ANSCLIST CLIST procedure.

TSO Client Option File Setup

The ANSSMPOP member of the ASAMPLIB dataset contains a sample client options file.Allocate a sequential data set and copy ANSSMPOP from the ASAMPLIB dataset to the

//DSMADMC EXEC PGM=IKJEFT01,TIME=1440,REGION=32M,DUNAMNBR=200// PARM=‘SPFPROF’//DSCOPT DD DSN=TIVSM.TSOADMIN.OPTIONS,DISP=SHR//DSCLANG DD DSN=TIVSM.SANSMSG(ANSMENU),DISP=SHR//SYSUADS DD DSN=SYS1.UADS,DISP=SHR//SYSHELP DD DSN=SYS1.HELP,DISP=SHR// DD DSN=SYS1.ISRCLIB,DISP=SHR// DD DSN=SYS1.HELP1,DISP=SHR//SYSPROC DD DSN=SYS1.HRFCLST,DISP=SHR// DD DSN=SYS1.SBLSCLI0,DISP=SHR// DD DSN=SYS1.ISRCLLIB,DISP=SHR

...//SYSPRINT DD TERM=TS//SYSIN DD TERM=TS

Figure 6. Example of Modified TSO Administrative Client Logon Procedure

PROC 0PROFILE PROMPTCONTROL NOLIST NOCONLIST MSG FLUSH PROMPT/* it is important to include the parameter “PROMPT” *//* in the PROFILE and CONTROL statements to allow *//* DSMADMC (TSO Admin Client module) to prompt for *//* input (e.g. PASSWORD). */ALLOC F(DSCOPT) DA(‘TIVSM.TSOADMIN.OPTIONS’) SHR REUSEALLOC F(DSCLANG) DA(‘TIVSM.SANSMSG(ANSMENU)’) SHR REUSECALL ‘SYS1.LINKLIB(DSMADMC)’FREE F(DSCOPT DSCLANG )

Figure 7. Example of ANSCLIST Procedure from ASAMPLIB


allocated data set. The name of the data set must be specified in the DSCOPT DD statement.The options shown here are the only options that you are required to update. For a completelist of client options, refer to Installing the Clients.

The TSO administrative client can communicate with a TSM server in one of fourcommunication methods:

¶ IBM TCP/IP

¶ TCPaccess TCP/IP

¶ IBM APPC/MVS

¶ IBM IUCV

The desired communication method must be specified in the client options file prior tostarting the TSO administrative client. Refer to Administrator’s Reference for a completedescription of the options and the parameters that you can specify.

IBM TCP/IP

COMMMETHOD TCPIPTCPSERVERADDRESS tcp_addressTCPPORT port#

TCPaccess TCP/IP

COMMMETHOD TCPIPICSSNAME ACSSTCPSERVERADDRESS tcp_addressTCPPORT port#

IBM APPC/MVS (SNA LU6.2)

COMMMETHOD SNALU6.2SYMBOLICDESTINATION applid

IBM IUCV

COMMMETHOD IUCVSERVERNAME job_name

If you used the ANSPROC member of the ASAMPLIB dataset for the TSO administrativeclient, enter the following command at the TSO prompt:

dsmadmc

If you used the CLIST procedure and you named it tsmadm, enter the following at the TSOprompt:

tsmadm


1.Settin

gUpTivo

liStorag

eMan

ager

Starting the Administrative Web InterfaceBefore starting the administrative web interface, ensure that you have submitted theANRIDL job from the ASAMPLIB dataset on the server machine. See Figure 1 on page 4for an example of the ANRIDL job. This job loads the web interface definition file.

Note: If you will be using the administrative web interface, your browser must have Java™

1.1.6 support.

To start the web interface, enter the URL on a web browser on your client workstation:

http://server_name:1580

server_nameIs the IP address (name, dotted name, or dotted number - for example, server1 or9.115.2.15) of the Tivoli Storage Manager server you want to contact.

1580 Is the value specified in either the server option HTTPTCPPort or HTTPICSPort.The default is 1580.

To end an administrative client session do one of the following:

quit

OR

From Options, select Log Off

Stopping the ServerYou can stop the server without warning if an unexpected problem occurs. To avoid severelyaffecting administrative and client node activity, stop the server only after currentadministrative and client node sessions have completed or been canceled.

For most tasks in this book, your server must be running. This procedure isexplained here only if an unusual situation requires that you stop the server.

To stop the server, do one of the following:

halt

OR

1. Select Server.

2. Select Server Status.

3. Select Halt Server and then Yes.


This shuts down the server immediately and cancels all client sessions, even if activity hasnot completed.

Registering Tivoli Storage Manager LicensesThe base Tivoli Storage Manager license includes an unlimited number of administrativeclients and one backup-archive client. When you install Tivoli Storage Manager, each serverlicense you order must be specified with a LICENSE option in the server options file. Forexample, to license Tivoli Disaster Recovery Manager and 25 backup-archive clients, addingthe following options to the server options file:license drmlicense managedsyslan number=25

Note: TSM requires one Managed System for LAN license for each Tivoli Data Protectionclient.

The licensed option keywords are:

SPACEMGMTTivoli Space Manager (HSM clients)

DRM Tivoli Disaster Recovery Manager

MANAGEDSYSLANTo license Managed System for LAN. TSM requires this license for each managedsystem (client) that moves data to and from storage over a LAN.

ORACLEAPPLTo license each managed system that uses Tivoli Data Protection for Oracle.

MSSQLAPPLTo license each managed system that uses Tivoli Data Protection for MS SQLServer.

MSEXCHANGEAPPLTo license each managed system that uses Tivoli Data Protection for MS Exchange.

LOTUSNOTESAPPLTo license each managed system that uses Tivoli Data Protection for Lotus® Notes™.

DOMINOAPPLTo license each managed system that uses Tivoli Data Protection for LotusDomino™.

INFORMIXAPPLTo license each managed system that uses Tivoli Data Protection for Informix.

R3APPLTo license each managed system that uses Tivoli Data Protection for R/3.

ESSAPPLTo license each managed system that uses Tivoli Data Protection for ESS.

ESSR3APPLTo license each managed system that uses Tivoli Data Protection for ESS R/3.

EMCSYMMETRIXR3APPLTo license each managed system that uses Tivoli Data Protection for EMCSymmetrix R/3.


1.Settin

gUpTivo

liStorag

eMan

ager

AFSDFSTo license each managed system that uses AFS/DFS Support. TSM also requires aManaged System for LAN license.

The REGISTER LICENSE command dynamically adds license statements to the serveroptions file. The OPT DD card in the server start-up JCL must include the DISP=MODparameter.

Note: The server options file must be a physical sequential (PS) data set.

See TSM Administrator’s Guide and TSM Administrator’s Reference for additional licenseinformation.

You can register licenses by specifying them directly in the server options file. TheREGISTER LICENSE command adds a license statement to the end of the server optionsfile if the options file is specified in the OPT DD statement of the server startup JCL with aDISP=MOD parameter. For example, use the following command to register spacemanagement for use on the MVS server:

register license spacemgt

OR

1. Select Server.

2. Select License Information.

3. From Operations, select Register License.

4. Enter the required information and Finish.

To license features on the server using the web interface:

Registering Backup-Archive Client NodesYou are now ready to register backup-archive clients. For example, to register a node namedMERCEDES with the password MONTANA, do the following:

register node mercedes montana

OR

1. Select Clients.

2. Select Client Nodes.

3. From Operations, select Register a New Node.

4. Enter the node information and Finish.

Two commands, DEFINE CLOPTSET and DEFINE CLIENTOPT, let you defineclient options affecting backup, archive, restore, and retrieval operations. See TSMAdministrator’s Guide and Installing the Clients for details.


Verifying Your Server InstallationThis section describes how to verify the initial configuration by backing up and restoringclient data. The section also describes how to archive and retrieve client data.

Note: The example shown in this section is for a Windows 32–bit backup-archive client.

You can use the ANRSIVP member in the ASAMPLIB dataset as a checklist to verify thatyou have completed all the steps necessary to successfully install the server. Perform thisstep from an MVS operator or system console. The following are queries contained in theANRSIVP member and the expected results if you have successfully completed all therequired installation steps.

Q OPTIONDisplays information about your server options.

Q STATUSDisplays information about your server parameters.

Q STGPOOLDisplays information about your backup and archive storage pools.

Q VOLUMEDisplays information about your storage pool volumes.

Q DB Displays allocation information about the TSM database.

Q DBVDisplays information about database volumes.

Q LICENSEDisplays licensing information.

Q LOGDisplays allocation information about the recovery log.

Q LOGVOLUMEDisplays information about the recovery log volumes.

Q DOMAINDisplays information about policy domains.

Q MGMTCLASSDisplays information about management classes.

Q COPYGROUPDisplays information about backup and archive copy groups.

Before You Perform a BackupBefore you perform a backup, you will need to do the following:

1. Ensure that you have registered your clients and have set up the configuration file.

2. Install the Tivoli Storage Manager client software on each remote workstation.

3. Configure the communications options in the client options file to connect with theserver.


1.Settin

gUpTivo

liStorag

eMan

ager

Backing Up a Client

Using an Include-Exclude Options File to Control ProcessingYou may not want to back up certain files. These files may be core files, local caches ofnetwork file systems, operating system or application files that could be easily recovered byinstalling the program again. This can also apply to any other files that you could easilyrebuild.

You can use the options in the include-exclude options file to exclude certain files frombackup processing. The options apply for both incremental and selective backups. TivoliStorage Manager backs up any file that is not explicitly excluded from backup. You can alsoinclude specific files that are in a directory you have excluded. For more information oncreating an include-exclude options file, see the appropriate Using the Backup-ArchiveClients User’s Guide.

Do the following to backup a client:

1. To start the backup-archive client GUI, click on the client icon:

Enter the registered node name and password.

Use the following steps to backup several files:

2. Click Backup from the TSM window. The Backup window appears.

3. Expand the directory tree. Select the folder icons to display the files in the directory.Choose the selection boxes next to the files or directories you want to back up.

4. Choose the backup type:

¶ For an incremental backup (by either date only or complete), click Incremental.

Note: The first backup of a file is always a full backup, even if you specifyIncremental.

¶ For a selective backup, click Always backup.

5. Click Backup. The Backup Status window displays the backup processing status.

Restoring Tivoli Storage Manager Client FilesThis section explains the procedure used to perform a simple restore of client files. Fordetails and advanced procedures, see the appropriate Using the Backup-Archive ClientsUser’s Guide.

Restoring Files or DirectoriesAn administrator can determine how many backup versions are kept for each file. Keepingmultiple versions of files allows a user to restore an older version if their most recentbackup is damaged.

Tivoli Storage Manager refers to the most recent backup version as the active version. Themost recent backup version is considered an inactive version if the file was deleted orexcluded at the client and an incremental backup was run. Any other backup version is


considered an inactive version. If you try to restore both an active and inactive version of afile at the same time, only the active version is restored.

Every time Tivoli Storage Manager backs up your files, it marks the new backup version asthe active backup. It also changes the previous active backup to an inactive backup. Whenthe maximum number of inactive versions is reached, the oldest inactive version is deleted.

¶ To restore an inactive backup version:

Click Display active/inactive files from the View menu on the TSM window.

¶ To restore an active backup version:

Click Display active files only from the View menu on the TSM window.

Restoring files or subdirectoriesTo restore backup versions of individual files or subdirectories:

1. Click Restore from the TSM window. The Restore window opens.

2. Expand the directory tree. Select the selection boxes next to the files or directories youwant to restore.

3. Click Restore. The Restore Destination window opens.

4. Select the destination in the Restore Destination window.

5. Click Restore. The Restore Status window displays the restore processing status.

Archiving and Retrieving FilesThis section contains procedures to help you perform a simple archive and retrieval of clientfiles. For details and advanced procedures, see the appropriate Using the Backup-ArchiveClients manual.

Note: We recommend that you archive a small file or directory.

To archive files, select the files by name or description, or select them from a directory treein the TSM main window.

Note: A user can assign an archive description for all archived files. The description can beup to 255 characters. If you do not enter a description, TSM assigns a default archivedescription. When you select the archive function from the backup-archive GUI, TSMdisplays a list of all previously used archive descriptions. You can use these displayedarchive descriptions on future archives.

To Archive Files by Name

Note: You can archive a file or a group of files with similar names. Specify the file name orpath in the Find Files window. Assign a unique description for each archive package.

To archive a file:

1. Click the Archive button in the TSM main window. The Archive by Tree window opens.

2. Expand the directory tree.

3. Click the plus sign (+) next to a directory or drive.

4. Highlight the drive or directory that you want.


1.Settin

gUpTivo

liStorag

eMan

ager

5. Click the

Find button on the toolbar.

6. Enter the search criteria in the Find Files window.

7. Click Search. The Matching Files window opens.

8. Click the selection boxes next to the files you want to archive.

9. Click Archive to archive the files. The Archive Status window displays the status progressof the archive.

To Archive Files Using a Directory Tree

Note: You can archive specific files or entire directories from a directory tree. You can alsoassign a unique archive description for each group of files you archive.

To archive your files:

1. Click the Archive button in the TSM main window. The Archive by Tree window opens.


3. Click the plus sign (+) next to a directory or drive.

4. Click the selection boxes next to the files or directories that you want to archive.

5. Click Archive. The Archive Status window opens. The Archive Status window displays thestatus progress of the archive.

Retrieving Archive CopiesYou retrieve a file when you want to return an archive copy of a file or a directory from theTSM server to your workstation. To retrieve archive copies:

1. Click the Retrieve button on the TSM main window. The Retrieve by Tree windowopens.


3. Click the plus (+) sign next to an object that you want to expand. The objects on thetree are grouped by archive package description.

4. Highlight the object in the tree that you want.

5. Click the

Find button on the tool bar. The Find Files window opens.

6. Enter your search information in the Find Files window.

7. Click Search. The Matching Files window opens.

8. Click on the selection boxes next to the files you want to retrieve.

9. Click Retrieve. The Retrieve Destination window opens.

10. Enter the information in the Retrieve Destination window.


11. Click Retrieve. The Retrieve Status window displays the processing results.


1.Settin

gUpTivo

liStorag

eMan

ager

Server and Client Communications

Tivoli Storage Manager supports a number of server/client communication methods. Youmust configure the server and each client workstation. This appendix describes how toconfigure MVS, Tivoli Storage Manager, and the client workstation for each communicationmethod. The appendix also includes a brief description of connection failures and a resultsfile.

This appendix includes the following sections:

¶ APPC

“Configuring the Server for APPC (SNALU6.2)” on page 26

“Configuring the OS/2 Client for APPC (SNALU6.2)” on page 27

“Configuring the Novell Client for APPC (SNALU6.2)” on page 30

“Configuring the Server for APPC” on page 32

“Example of Configuring the MVS Server with APPC” on page 35

“Configuring the OS/2 Client for APPC Using Communication Manager/2” onpage 40

“Configuring Novell NetWare Client for APPC Using NetWare Requester” onpage 47

¶ 3270 Emulation

“Configuring the Server for 3270 Emulation” on page 50

¶ TCP/IP and HTTP

“Configuring the Server for TCP/IP Using IBM TCP/IP” on page 51

“Configuring the Server for TCP/IP Using TCPaccess” on page 53

“Configuring the Server for Web Access with IBM TCP/IP” on page 54

“Configuring the Server for Web Access with TCPaccess” on page 54

“Connecting with Tivoli Storage Manager across a Firewall” on page 54

¶ IUCV

“Configuring the Server for IUCV” on page 54

¶ “Diagnosing Initial Connection Failures” on page 68

¶ “Software Requirements” on page 74

¶ “Results Files” on page 74

2


|

2.Server

andClien

tCommunicatio

ns

Configuring the Server for APPC (SNALU6.2)Use Table 2 to help you configure the server for the APPC (SNALU6.2) communicationmethod to allow a Novell NetWare or OS/2® client to connect to the server. You should firstreview the installation procedures for the server and for the Novell NetWare and OS/2clients. This section provides the information you will need for those procedures.

See the following documentation for the installation procedures:¶ “Setting Up Tivoli Storage Manager” on page 1¶ Installing the Clients¶ “Configuring the OS/2 Client for APPC Using Communication Manager/2” on page 40¶ “Configuring Novell NetWare Client for APPC Using NetWare Requester” on page 47

The following is an explanation of the items on the worksheet. You must have thisinformation before you begin configuring the server for APPC (SNALU6.2):

Partner DescriptionThe description this item is normally known by

Mode DescriptionThe description of the Logon Mode Table and Logon Mode Table Entry Name

Novell Local DescriptionThe description of the Novell logical unit (LU)

OS/2 Local DescriptionThe description of the OS/2 LU

Reference ParameterA reference that can be used to trace information to the partner node and back

VTAM® ParameterThe name the parameter is known by VTAM

VTAM ExampleThe example name as used in this book

VTAM StatementThe part of the VTAM statement where the partner is located

Your DataThe space to write in your data. This is your data which corresponds to the datashown in the examples in this book.

Table 2. Worksheet for COMMMETHOD SNALU6.2(APPC) for MVS

Reference Parameter

VTAMParameterName Example

VTAMStatement Your Data

PARTNERDescription

Network ID s_netid Network name DEIBMFD VSUL

Partner LU nameor ACB name

partner_lu ACBNAME DSMSERV1 VAPPL

Application ID applid Applid DSMSERV1 VAPPL

MODEDescription


Table 2. Worksheet for COMMMETHOD SNALU6.2(APPC) for MVS (continued)

Reference Parameter

VTAMParameterName Example

VTAMStatement Your Data

Logon ModeTable name

MODETAB ISTINCLM VAPPL

Logon ModeName

logmode DLOGMOD #BATCH VAPPL

Logon ModeName

logmode LOGMODE #BATCH MODEENT

NOVELLLOCALDescription

IDBLK vtam_xid IDBLK 05D VBUILD vtam_xid

IDNUM IDNUM F333C VBUILD

Local node name c_independentlu LU F13833C0 VBUILD

PU name c_pu PU F13833C VBUILD

OS/2 LOCALDescription

IDBLK vtam_xid IDBLK 05D VBUILD

IDNUM vtam_xid IDNUM F333B VBUILD

Local node name c_independentlu LU F13833B0 VBUILD

PU name c_pu PU F13833B VBUILD

Note: Enter your data in uppercase to ensure correct acceptance by MVS

Key VTAM Statement ColumnHere are the full names of the abbreviations in the VTAM Statement column of theworksheet:

VSUL VTAM Setup List

VAPPLVTAM APPLID Statement

VBUILDSwitched Major Node Definition

Server OptionInclude the following option in the server options file for APPC (SNALU6.2)communications. You can write value you want to use in the blank space:

luname dsmserv1 ______________

Configuring the OS/2 Client for APPC (SNALU6.2)Use Table 3 on page 28 to help configure your OS/2 client for the APPC (SNALU6.2)communication method. You should first review the instructions for installing the server andthe OS/2 client. Then use this section to find the information for your configuration. See thefollowing documentation for the installation instructions:


2.Server

andClien

tCommunicatio

ns

¶ “Setting Up Tivoli Storage Manager” on page 1¶ Installing the Clients

The following is an explanation of the data items on the worksheet. You must have thisinformation before you begin the installation:

Local DescriptionThe description this data item is normally known by

Partner DescriptionThe description this data item is normally known by


Client Workstation ParameterThe name of the fields used on the windows in Communications Manager/2 (CM/2)

Client Installation ExampleThe name used in the examples

Window AbbreviationThe abbreviations of the windows used in CM/2. A list of the abbreviations and theircorresponding full names follow the worksheet.


Table 3. Worksheet for COMMMETHOD SNALU6.2(APPC) for OS/2Reference Parameter Client

WorkstationParameterName

ClientInstallationExample

WindowAbbreviation

YourData

LOCAL Description

Configuration Name Configuration TSMAPPC OC

Network ID ofWorkstation

c_netid C&SM LAN ID/ Network ID /Partner networkID

DEIBMFD TRAP LNCCTAH

Independent LU c_independentlu Local NodeName / LocalPU name

F13833B0 LNC CTAH

IDBLK & IDNUM vtam_xid Local node ID /Node ID

05D F333B LNC CTAH

Link name Link Name toHost

HOST0001 CL CTAH

Token Ring Address dest_addr LAN destinationaddress

400010000002 CTAH

Partner Node Name Partner nodename

OS2A CTAH

PARTNER Description

Network ID ofApplication

s_netid Network ID DEIBMFD PL


Table 3. Worksheet for COMMMETHOD SNALU6.2(APPC) for OS/2 (continued)Reference Parameter Client

WorkstationParameterName


WindowAbbreviation

YourData

Application ID & Alias partner_lu LU Name &Alias

DSMSERV1OS2NODEA

PL

Fully qualified PartnerLU - Network ID

s_netid.partner_lu Partner LU -Fully qualifiedname

DEIBMFD.DSMSERV1

CCSI

Server Program Name applid Partner TP - TPName

DSMSERV1 CCSI

Logon Mode name logmode Mode name #BATCH SFI CCSI

CPI CommunicationsSide Information -Symbolic destinationname

Symbolicdestination name

MVSTIVSM CCSI ++

Note: ++ case sensitive - enter as specified by administrator

Key to the Window Abbreviation ColumnHere are the full names of the abbreviations in the Window Abbreviation column.¶ OC - Open Configuration¶ TRAP - Token Ring or Other LAN Types DLC Adapter Parameters¶ LNC - Local Node Characteristics¶ SFI - SNA Features List¶ CCSI - CPI Communications Side Information¶ CL - Connections List¶ AL - Adapter List¶ CTAH - Connection to a Host

Client Options FileThe following are the communication options that you must enter in the client options file(dsm.opt). The COMMMETHOD option value for APPC must always be SNALU6.2. Thevalues listed for the other options are the values used in the examples for configuring theOS/2 client as discussed in “Configuring the OS/2 Client for APPC Using CommunicationManager/2” on page 40. Blank spaces are provided for you to write in the values you usedwhen you configured your OS/2 client for communications. Enter these options in the clientoptions file.

commmethod snalu6.2symbolicdestination ________ (for example, MVSTIVSM from side information

panel information)

-OR-

partnerluname _________ (for example, DEIBMFD.DSMSERV1)tpname _________ (for example, DSMSERV1)cpicmodename _________ (for example, #BATCH)


2.Server

andClien

tCommunicatio

ns

Configuring the Novell Client for APPC (SNALU6.2)Use Table 4 to help you in configuring your Novell NetWare client for the APPC(SNALU6.2) communication method in order to connect to the TSM server. Before startingyour configuration, you should first review the instructions for installing the server and forinstalling the Novell NetWare client. Then, use the examples in these instructions as areference to obtain the information needed for your configuration. See the followingdocumentation for the installation instructions:¶ “Setting Up Tivoli Storage Manager” on page 1¶ Installing the Clients

The following is an explanation of the data items on the worksheet. You must have thefollowing information from the worksheet before you begin the configuration:

Local DescriptionThe description this data item is normally known by

Partner DescriptionThe description this data item is normally known by


Client Workstation ParameterThe name of the fields used on the windows in CSCON/SIUTIL

Client Installation ExampleThe name used in the examples

Window AbbreviationThe abbreviations of the windows used in CSCON/SIUTIL. A list of theabbreviations and their corresponding full names follow the worksheet.


Table 4. WORKSHEET for COMMMETHOD SNALU6.2(APPC) for Novell

Reference Parameter

ClientWorkstationParameterName


WindowAbbreviation Your Data

LOCALDescription

2.1 ServiceProfile

New ProfileName

APPCPRO SSP

Network IDwhereworkstationresides

c_netid SNA NetworkID

DEIBMFD HCC

Network IDwhereapplicationresides

s_netid Network Name DEIBMFD LLCD


Table 4. WORKSHEET for COMMMETHOD SNALU6.2(APPC) for Novell (continued)

Reference Parameter

ClientWorkstationParameterName


WindowAbbreviation Your Data

Independent LUName or LocalLU Name

c_independentlu Peripheral NodeControl PointName / LUname

F13833C0 HCC LLCD

IDBLK IDNUMor Vtam XID

vtam_xid Block ID andPUID for TokenRing Connection

05D F333C STRC

Logical AdapterName

Logical AdapterName

TOKENSAA STRC

Local PU name c_pu PU name F138833C LLCD

Side Information- Symbolicdestination name

Side InformationRecord Name

MVSTIVSMMVSTIVSM.CPI

LLCD ++

PARTNERDescription

Application IDor Partner LUName

partner_lu LU Name DSMSERV1 PLCD

Token RingAdapter addressof workstation

dest_addr Network AdapterAddress

400010000003 PLCD

Local ProgramName

Local ProgramName

DSMC PLCD

Server ProgramName

applid Remote ProgramName

DSMSERV1 PLCD

Logon ModeName

logmode Mode Name #BATCH MCD

Side Information- Symbolicdestination name

Side InformationRecord Name

MVSTIVSM PLCD MCD ++

CSCON profilename

SAA® ServiceProfile Name

APPCPRO MCD

Note: ++ case sensitive - enter as specified by administrator

Key to Window Where Parameters AppearThe following lists the full names of the abbreviations in the Window Abbreviation columnof the above worksheet.¶ SSP - Select Service Profile¶ HCC - Host Connection Configuration¶ STRC - SNA Token Ring Configuration¶ LLCD - Local LU Configuration Data¶ PLCD - Partner LU Configuration Data¶ MCD - Mode Configuration Data


2.Server

andClien

tCommunicatio

ns

Client Options FileThe following are the communication options that you must enter in the client options file(dsm.opt). The COMMMETHOD option value for APPC must always be SNALU6.2. Thevalues listed for the other options are the values used in the examples for configuring theNovell NetWare client . Blank spaces are provided for you to write in the values you usedwhen you configured your Novell NetWare client for communications. Enter these options inthe client options file. Refer to Installing the Clients.

commmethod snalu6.2symbolicdestination _________ (for example, MVSTIVSM from side information

panel information)

Configuring the Server for APPCAPPC lets two partner programs communicate through a defined protocol. The interface tothe protocol mechanisms on each side is called a logical unit (LU). To allowprogram-to-program communication, these LUs must be of type 6.2 (LU6.2). APPCprotocols are more complex to implement than other protocols. However, the APPCprotocols provide better performance and reliability, and they should be considered aspreferred protocol for use with TSM. This particularly applies when TSM supports LANserver clients such as OS/2 LAN servers or Novell NetWare servers.

Connectivity SupportTSM implements Independent LUs. SNA PU type 2.1 support is required in VTAM, theSNA gateway, and in Tivoli Storage Manager client communications software. In an MVSenvironment, PU 2.1 support is provided as a combination of communications gatewaysoftware and VTAM levels.

For the supported communications gateways, the requirements are the following:

¶ 3745 Communications Controller

PU 2.1 support requires the following software levels:

v NCP Version 5 Release 2, or higher

v VTAM Version 3 Release 2 (VTAM/XA; 5665-289), or higher

¶ 3172 Interconnect Controller


v Interconnect Controller Program Version 2, or higher

v VTAM Version 3 Release 4 (VTAM/ESA; 5685-085), or higher

¶ 3174 Workstation Controller


v 3174 Licensed Internal Code, Configuration C Release 1, or higher

OR

v 3174 Licensed Internal Code, Configuration B with RPQ#8Q0800, Typw 2.1 PassthruFunction

v VTAM Version 3 Release 4 (VTAM/ESA; 5685-085), or higher


VTAM SetupYour VTAM system administrator or systems programmer defines a new application toVTAM through the use of an access control block (ACB). An ACB defined for TSM, whenadded to the VTAM configuration, provides an application ID which the client referenceswhen it wants to connect to the TSM server. When the TSM application ID is referenced, alogon procedure is begun which ultimately tells the server where to look for the TSM client.

The VTAM APPL StatementYou define the ACB in the VTAM APPL statement. The following is an example of theAPPL statement that the VTAM systems programmer should add to your VTAMconfiguration:

TIVSM VBUILD TYPE=APPLDSMSERV1 APPL ACBNAME=DSMSERV1,EAS=30,AUTH=(ACQ,PASS,VPACE), X

HAVAIL=YES,APPC=YES,PARSESS=YES,SONSCIP=YES, XVPACING=5,MODETAB=ISTINCLM,DLOGMOD=#BATCH,

DSMSERV1 is the application ID (applid) that the TSM client references when it wants toconnect to the server. The way in which the client references this name is discussed later inthis installation guide where we cover client connectivity. If you are installing the OS/2client and you prefer to review that section now, you can find it in “Configuring the OS/2Client for APPC Using Communication Manager/2” on page 40. If you are installing theNovell NetWare client and you prefer to review that section now, you can find it in“Configuring Novell NetWare Client for APPC Using NetWare Requester” on page 47.

The Logon Mode DefinitionWhen the client references the application ID for the TSM server (DSMSERV1), theMODETAB=ISTINCLM and DLOGMOD=#BATCH parameters reference a logon modedefinition which establishes the connection and the characteristics of the session. Thesecharacteristics include the maximum number of sessions allowed, the maximum number ofconversations allowed, and other control information. MODETAB references the table inwhich the logon mode definition entry is found. In this example, the table referenced is theIBM supplied VTAM default table (ISTINCLM). DLOGMOD references the table entryitself which is the logon mode definition #BATCH. We recommend that you use the#BATCH mode entry in the VTAM default logon mode table (ISTINCLM) initially toestablish the APPC connection. Depending on your VTAM level, this mode might not bepre-defined in the default logon mode table. You should verify this with your VTAM systemprogrammer. If this mode is needed, add it to the default logon mode table as shown below:

TITLE ‘#BATCH’#BATCH MODEENT LOGMODE=#BATCH, X

ENCR=B'0000',SSNDPAC=8, XSRCVPAC=8,PSNDPAC=8

After you have the APPC connection established and would like to create a new mode forperformance tuning, you can create it in your current logon mode table, compile, and thenlink-edit the member into the VTAM library.

In VTAM, a response unit (RU) is a message unit that acknowledges a request. Since theRU size is negotiated between VTAM and the workstations, you do not have to specify asize in the #BATCH logon mode definition. However, if you specify a size, it should be atleast 4K.


2.Server

andClien

tCommunicatio

ns

The Switched Major Node DefinitionEach workstation connected to the network must be represented on the network as physicalunit (PU). A PU can have one or more logical units (LUs). However, only one LU on a PUcan be an independent LU. An independent LU can activate a session directly with theserver LU without asking for services from the VTAM system services control point (SSCP).A dependent LU, however, must request services from the SSCP in order to activate asession with server LU. The LU provides the end user application with the ability to accessand communicate with server.

The PUs and their associated LUs for the TSM clients are defined and linked togetherthrough a VTAM switched major node definition. A switched major node is the majorbuilding block of VTAM through which all the PUs and LUs for a given application such asTSM are linked together so that they can communicate with the server. The APPCconnection for an TSM client must be made through an independent LU.

You define a switched major node through the VTAM build statement (VBUILD). Thefollowing VBUILD statement (Figure 8 on page 35) defines the PUs and LUs for threeworkstations. F13833B0, F13833C0, F13833D0 are the independent LUs. Based on yourTSM client configuration, you must define a similar VBUILD statement.


TSM Server SetupEnter the ACBNAME (DSMSERV1) from VTAM APPL statement in the server optionsfile’s LUNAME option. Refer to “The VTAM APPL Statement” on page 33. The entry takesthe following format:

luname dsmserv1

The ACBNAME identifies the TSM server to VTAM as the application to which the clientcan connect.

Example of Configuring the MVS Server with APPCYou can use this section as a reference when configuring MVS and the TSM server forAPPC communications. It also provides scenarios for configuring the following clients forAPPC communications:¶ TSO administrative client

* SWITCHED MAJOR NODE **

VBUILD TYPE=SWNET,MAXGRP=1, XMAXNO=1

*F13833B PU ADDR=C5, X

IDBLK=05D,IDNUM=F333B, XISTATUS=ACTIVE, XPUTYPE=2,MAXOUT=8,MAXDATA=4105,MAXPATH=1, XVPACING=8,PACING=8,DISCNT=NO, XUSSTAB=USSSNAM,SSCPFM=USSSCS, XMODETAB=MTD1SERH,DLOGMOD=QUERY X

F13833B0 LU LOCADDR=0,MODETAB=ISTINCLM,DLOGMOD=#BATCH, XVPACING=8,PACING=8

F13833B1 LU LOCADDR=2F13833B2 LU LOCADDR=3F13833B3 LU LOCADDR=4F13833B4 LU LOCADDR=5F13833B5 LU LOCADDR=6,MODETAB=WI3820,PACING=0,VPACING=0, X

DLOGMOD=IBM3820T*F13833C PU ADDR=C5, X

IDBLK=05D,IDNUM=F333C, XISTATUS=ACTIVE, XPUTYPE=2,MAXOUT=8,MAXDATA=4105,MAXPATH=1, XVPACING=8,PACING=8,DISCNT=NO, XUSSTAB=USSSNAM,SSCPFM=USSSCS, XMODETAB=MTD1SERH,DLOGMOD=QUERY X

F13833C0 LU LOCADDR=0,MODETAB=ISTINCLM,DLOGMOD=#BATCH, XVPACING=8,PACING=8

*F13833D PU ADDR=C5, X

IDBLK=05D,IDNUM=F333D, XISTATUS=ACTIVE, XPUTYPE=2,MAXOUT=8,MAXDATA=4105,MAXPATH=1, XVPACING=8,PACING=8,DISCNT=NO, XUSSTAB=USSSNAM,SSCPFM=USSSCS, XMODETAB=MTD1SERH,DLOGMOD=QUERY X

F13833D0 LU LOCADDR=0,MODETAB=ISTINCLM,DLOGMOD=#BATCH, XVPACING=8,PACING=8

Figure 8. SWNET Major Node


2.Server

andClien

tCommunicatio

ns

¶ OS/2 backup-archive and administrative clients¶ Novell NetWare backup-archive client¶ AIX® backup-archive and administrative clients

This section also provides help in diagnosing initial client/server connection failures.

Configuring an MVS Server in a Cross-Domain NetworkThe following configurations were done in a cross-domain environment. All the workstationsare generated to the 3745 in the DEIBMFD network with the SSCPNAME as FDW. The3745 is channel-attached to an MVS host machine in the DEIBMA4 network. This MVSmachine is connected to another MVS host machine where the TSM server application,named A4V, is running.

Note: MVS/APPC must be started to run TSO administrative client. For other clients, theLU6.2 is sufficient.

VTAM/NCP SetupThe following VTAM definitions must be made on the adjacent SSCP. The MVS hostmachine is channel-attached to the 3745 in this environment.

1. We recommend that you use the #BATCH mode in the VTAM default logon mode table(ISTINCLM) initially to establish the APPC connection. See Figure 9. Depending onyour VTAM level, this mode might not be pre-defined in the default logon mode table.You should verify this with your VTAM system programmer. If this mode is needed, addit to the logon mode table, compile, and then link-edit the member into a VTAM library.

If desired, you can create a new mode for performance tuning after the APPC connectionis established. To do this, create it in your current logon mode table, compile it, and thenlink-edit the member into a VTAM library.

Since the RU size is negotiated between VTAM and the workstations, we recommendthat you define a dummy mode table entry (see below). However, if you are going tospecify an RU size, you should use a block size of at least 4KB.

TSMAPPC MODEENT LOGMODE=TSMAPPC

2. Define a physical unit (PU) and an independent logical unit (LU) in the SWNET MajorNode. An independent LU is denoted by locaddr=0. In the following example, the PU isdefined as F13833B and the independent LU is defined as F13833B0. See Figure 10 onpage 37.

TITLE '#BATCH'#BATCH MODEENT LOGMODE=#BATCH, X

ENCR=B‘0000’,SSNDPAC=8, XSRCVPAC=8,PSNDPAC=8,TYPE=0

Figure 9. #BATCH mode entry


This makes it much easier to implement Advanced Peer-to-Peer Network (APPN). TheCPNAME has to be the same as the independent LU name. In the above example, useCPNAME=F13833B0 instead of IDBLK and IDNUM.

MVS VTAM SetupThe following steps must be completed on an MVS host machine where the serverapplication is executed. In this environment, the MVS host machine name is A4V.

1. Define an APPL statement for the TSM MVS application in VTAM. See Figure 11.

*------------** SWITCHED MAJOR NODE **------------**

VBUILD TYPE=SWNET,MAXGRP=1, XMAXNO=1

*F13833B PU ADDR=C5, X

IDBLK=05D,IDNUM=F333B, <==== see explanation below XISTATUS=ACTIVE, XPUTYPE=2,MAXOUT=8,MAXDATA=4105,MAXPATH=1, XVPACING=8,PACING=8,DISCNT=NO, XUSSTAB=USSSNAM,SSCPFM=USSSCS, XMODETAB=MTD1SERH,DLOGMOD=QUERY X

F13833B0 LU LOCADDR=0,MODETAB=ISTINCLM,DLOGMOD=#BATCH, XVPACING=8,PACING=8

F13833B1 LU LOCADDR=2F13833B2 LU LOCADDR=3F13833B3 LU LOCADDR=4F13833B4 LU LOCADDR=5F13833B5 LU LOCADDR=6,MODETAB=WI3820,PACING=0,VPACING=0, X

DLOGMOD=IBM3820T*F13833C PU ADDR=C5, X

IDBLK=05D,IDNUM=F333C, XISTATUS=ACTIVE, XPUTYPE=2,MAXOUT=8,MAXDATA=4105,MAXPATH=1, XVPACING=8,PACING=8,DISCNT=NO, XUSSTAB=USSSNAM,SSCPFM=USSSCS, XMODETAB=MTD1SERH,DLOGMOD=QUERY X

F13833C0 LU LOCADDR=0,MODETAB=ISTINCLM,DLOGMOD=#BATCH, XVPACING=8,PACING=8

*F13833D PU ADDR=C5, X

IDBLK=05D,IDNUM=F333D, XISTATUS=ACTIVE, XPUTYPE=2,MAXOUT=8,MAXDATA=4105,MAXPATH=1, XVPACING=8,PACING=8,DISCNT=NO, XUSSTAB=USSSNAM,SSCPFM=USSSCS, XMODETAB=MTD1SERH,DLOGMOD=QUERY X

F13833D0 LU LOCADDR=0,MODETAB=ISTINCLM,DLOGMOD=#BATCH, XVPACING=8,PACING=8

Figure 10. SWNET Major Node

A4VBTSM VBUILD TYPE=APPLA4VTSM2 APPL ACBNAME=A4VTSM2,EAS=30,AUTH=(ACQ,PASS,VPACE), X

HAVAIL=YES,APPC=YES,PARSESS=YES,SONSCIP=YES, XVPACING=5,MODETAB=ISTINCLM,DLOGMOD=#BATCH,DSESLIM=4

Figure 11. Sample APPL Statement


2.Server

andClien

tCommunicatio

ns

In this example, the ACBNAME parameter, known as the LU name by the TSM server,is the partner LU that the clients see. MODETAB is the logon mode table entry name.DLOGMOD is the default logon mode entry name.

The DSESLIM parameter has been coded to handle two concurrent sessions from eachLU; for example, when you run the administrative client and the backup client from thesame workstation. You can increase this value if necessary.

Note: For more information about the APPL parameters, see the VTAM ResourceDefinition Reference.

2. In the server options file, use the name specified with the ACBNAME keyword of theVTAM APPL statement. For example:

luname A4VTSM2

3. Ensure the VTAMLIB contains the load module for the mode entry table that has the logmode defined. This load module is also loaded in the 3745-NCP.

Configuring an MVS Server in a Single-Domain NetworkThe steps in “Configuring an MVS Server in a Cross-Domain Network” on page 36 can beapplied to the single network environment. A single network ID is used throughout all of theclients’ configuration files.

Depending on where the control unit is attached, the setup for the server can be simplified.In the example environment, the control unit is not channel-attached to the same hostmachine where TSM is running. Therefore, you have two VTAMs to deal with. The logmode that you defined on the NCP must also exist on the second host machine where theapplication is running. However, define the independent LUs only on the host machinewhere the control unit is attached. The host machine is the owning SSCP.

In the case where the control unit is attached to the same application host machine, you onlydeal with one VTAM.

Configuring the 3172 Communication ControllerConfiguration of the 3172 control unit environment is similar to the configuration of the3745 control unit environment except for the single domain network. In most cases, thecontrol unit is channel-attached to the same host machine that TSM is running on.

Configuring the 3174 Communication ControllerFigure 12 on page 39 contains sample 3174 PU and LU definitions for use with TSM.


The following is a list of recommendations and requirements from the 3174 support group:

¶ If you use the APPN® Feature Code, which we recommend, you must implement APPNto support TSM. You should define the 3174 as an NN (network node). We alsorecommend that the workstations using TSM be configured as EN (end nodes).

¶ The APPN Feature requires 4MB of RAM on the 3174. For performance enhancement,we recommend that the 3174 have 6MB of RAM.

For more information on configuring the 3174 for APPN connectivity see manuals: 3174APPN Implementation Guide (GG24-3702) and IBM 3174 Establishment ControllerInstallation Guide (GG24-3061).

¶ Code DYNAMLU=YES on the 3174 PU macro to utilize VTAM cross-domainresources. This eliminates the need for coding the independent LU LOCADDR=0

¶ The mode used for TSM communication must be specified in the 3174 MODE/COSCorrelation panel during the APPN feature customization.

Note: See the software requirements for the 3174 in “Software Requirements” on page 74.

Configuring Tivoli Storage Manager Clients to the MVS Server

Note: See the worksheets (“Configuring the Server for APPC (SNALU6.2)” on page 26,“Configuring the OS/2 Client for APPC (SNALU6.2)” on page 27, and “Configuringthe Novell Client for APPC (SNALU6.2)” on page 30) and Installing the Clients foradditional information.

Before configuring the clients, obtain the following information from the VTAMadministrator and the MVS system administrator:

CLIENT REQUIREMENTS

c_netidNetwork ID of the network where the client workstation’s PU and LU are defined.In this network topology, it is the 3745.

c_independentluIndependent LU name defined in the 3745 VTAMLST where locaddr=0.

DSM3174 VBUILD TYPE=LOCAL*PU3174 PU CUADDR=2A0, X

DISCNT=NO, XDELAY=0, XISTATUS=ACTIVE, XMAXBFRU=9, XPACING=7, XPUTYPE=2, XVPACING=7, XXID=YES, XSECNET=NO

* INDEPENDENT LUSPS21ILU LU LOCADDR=0,ISTATUS=ACTIVEBORNEO LU LOCADDR=0,ISTATUS=ACTIVEIMAGOS2I LU LOCADDR=0,ISTATUS=ACTIVEIMAGNOVI LU LOCADDR=0,ISTATUS=ACTIVE

Figure 12. VTAM Definition for 3174 Token Ring LAN Gateway


2.Server

andClien

tCommunicatio

ns

c_pu PU name defined in the 3745 VTAMLST. This parameter is required for theNetWare client, but is not required for the other clients.

vtam_xidIDBLK and IDNUM defined in the 3745 VTAMLST for the PU. This is required forthe host link definition.

logmodeLOGMODE name defined in the mode table entry in the 3745 VTAMLST.

SERVER REQUIREMENTS

s_netidNetwork ID of the network where the server application resides.

dest_addrToken ring adapter address of the adjacent SSCP. In this network topology, it is thelocally administered address to the 3745.

partner_luServer’s LU to be used as client’s Partner LU. This is the ACBNAME in the APPLstatement.

Configuring the OS/2 Client for APPC Using CommunicationManager/2

The example configuration that follows uses Communication Manager/2 (CM/2) level 1.0.To begin the configuration process for CM/2, follow these steps:

1. From the OS/2 Desktop, double click on the Communication Manager/2 icon.

2. Double click on the Communication Manager Setup icon. The CommunicationManager Setup window appears.

3. Press the Setup button. The Open Configuration window appears. See Figure 13 onpage 41.


4. Enter a new name in the Configuration field. If you want a description, enter it in theDescription field.

5. Press the OK button. Answer Yes to any messages that appear.

6. On the Communications Manager Configuration Definition - APPC window, selectToken-ring or other LAN types for the Workstation Connection Type.

7. Select CPI Communications for the Feature or Application.

8. Press the Configure... button.

After you have followed the previous steps, the Communication Manager Profile ListSheet window is displayed. All of the profiles listed need to be configured. The profiles are:

DLC - Token-ring or other LAN typesSNA local node characteristicsSNA connectionsSNA features

The following sections show you the CM/2 windows and the information that you need tofill in.

Note: See “CM/2 .ndf File for 3172 or 3745 Gateways” on page 77 for the sample .ndf filethat would be created by completing the following procedure.

In the Communications Manager Profile List Sheet window, double click on DLC -Token-ring or other LAN types. The Token Ring or Other LAN Types DLC AdapterParameters window appears. See Figure 14 on page 42.

Figure 13. Open Configuration Window


2.Server

andClien

tCommunicatio

ns

1. Enter the c_netid in the C&SM LAN ID field.

2. Press the OK button.

In the Communications Manager Profile List Sheet window, double click on SNA localnode characteristics. The Local Node Characteristics window appears. See Figure 15.

1. Enter the c_netid in the Network ID field.

2. Enter the c_independentlu in the Local node name field.

3. Select End node - no network node server for the Node type. You need to select Endnode to network node server if you are connecting to an APPN network node server.

4. Enter the vtam_xid in the Local node ID fields. These values can be left with zeros ifCPNAME is used in the VTAMLST.

5. Press the OK button to return to the Communications Manager Profile List Sheetwindow.

Figure 14. Token Ring or Other LAN Types DLC Adapter Parameters Window

Figure 15. Local Node Characteristics Window


In the Communications Manager Profile List Sheet window, double click on SNAconnections. The Connections List window appears. See Figure 16.

1. Select To host in the Partner type group box.

2. Press the Create... button.

When you press the Create... button in the Connections List window, the Adapter Listwindow appears. See Figure 17.

1. Select Token-ring or other LAN types if you are using token ring.

2. Press the Continue... button.

Figure 16. Connections List Window

Figure 17. Adapter List Window


2.Server

andClien

tCommunicatio

ns

When you press the Continue... button in the Adapter List window, the Create aConnection to a Host window appears. See Figure 18.

1. Enter the dest_addr in the LAN destination address field.

2. Enter the c_netid in the Partner network ID field. This is the network identificationnumber of the adjacent CP (3745-NCP) that the client workstation is generated to. In thisexample, it is the client’s network ID.

3. Enter a value in the Partner node name field. This is the SSCPNAME in VTAMLIST.For the OS/2 client, this can be any value you want. BCTSO is used in this example.

4. Enter the vtam_xid in the Node ID fields. These values are required for the host linkconnection definition. It could be zeros if CPNAME is used in the VTAMLST.

5. Press the Define Partner LUs... button.

When you press the Define Partner LUs... button in the Create a Connection to a Hostwindow, the Create Partner LUs window appears. See Figure 19 on page 45. DefiningPartner LUs generates the DEFINE_PARTNER_LU_LOCATION statement. This ensuresthat the FQ_OWNING_CP_NAME parameter is in the .ndf file.

Figure 18. Create a Connection to a Host


1. Enter the partner_lu in the LU Name field.

2. Enter a value in the Alias field. The Partner LU alias can be any value you want.

3. Press the Add button to add the Partner LU to the list.

4. Press the OK button to return to the Connections List window.

5. Press the Close button to return to the Communications Manager Profile List Sheetwindow.

In the Communications Manager Profile List Sheet window, double click on SNAfeatures. The SNA Features List window appears.

1. Select Partner LUs in the Features list.

2. Select the Partner LU you previously defined in the far right list. In this example, thePartner LU name is A4VTSM2.

3. Press the Change... button.

When you press the Change... button in the SNA Features List window, the Change aPartner LU window appears.

1. Update the Partner LU network ID if it is different from the client’s network ID(s_netid).

Note: This updates the FQ_PARTNER_LU_NAME parameter in theDEFINE_PARTNER_LU statement. This is important if the client and server areon different networks.

2. Press the OK button to return to the SNA Features List window.

If you decide to create a new mode instead of using the predefined one (#BATCH), youneed to complete the following steps:

Figure 19. Create Partner LUs


2.Server

andClien

tCommunicatio

ns

1. In the SNA Features List window, select Modes from the Features list.

2. Press the Create... button to create a new mode. The Create a Mode Definition windowappears.

3. Enter logmode in the Mode Name field.

Note: The mode name must match the VTAM’s log mode defined in the mode tableentry.

4. Press the OK button to return to the SNA Features List window.

Note: You should use the #BATCH mode for TSM.

1. In the SNA Features List window, select CPI Communications side information fromthe Features list.

2. Press the Create... button. The Create CPI Communications Side Information windowappears. See Figure 20. Use this window to create a symbolic destination name if youwant to use one in the options file (dsm.opt).

3. Enter a value in the Symbolic destination name field. You can enter anything. Thevalue that you enter here should also be the symbolic destination name in the client’sdsm.opt file.

4. Enter the Fully qualified name (s_netid and partner_lu) of the partner LU, or use theAlias.

5. Enter the server program name in the TP name field. This can be any value you want.

6. Select Same or None for the Security type.

7. Select the mode you just created from the Mode name field. Select #BATCH if you didnot define one.

8. Press the OK button.

Figure 20. Create CPI Communications Side Information Window


Notes:

1. If the same OS/2 client wants to have access to another host server, such as a VM orMVS server, via the same gateway, you need to define another partner LU, a CPIC sideinformation record, and a new mode if it is using a different mode name. You canquickly add the following statements to the .ndf file for the new server:

DEFINE_PARTNER_LUDEFINE_PARTNER_LU_LOCATIONDEFINE_PARTNER_MODEDEFINE_CPIC_SIDE_INFO

2. The VTAM SWNET Major Node defined the independent LU with MODETAB andDLOGMODE for the first server. This should not have any effect if the second server isusing a different MODETAB and DLOGMODE. When the client establishes aconnection to the server, the mode that is defined on the client overrides the modedefined in the VTAM SWNET Major Node definition.

Starting the Tivoli Storage Manager Client1. Edit the dsm.opt file, giving the symbolic destination a value of MVSTIVSM. For

example:

commmethod snalu6.2symbolicdestination mvstivsm

2. Ensure that CM/2 is started.

3. Start the TSM program

Considerations for Using OS/2 ClientsTSM does not allow the user to choose the local LU for the client program. If CM/2supports other applications that use independent LUs, you need to specify a default LU forTSM by adding the following statement to your .ndf file:

DEFINE_DEFAULTS DEFAULT_LOCAL_LU_ALIAS (<local LU alias>)

After adding this statement you need to run CMVERIFY /E to verify your changes anddynamically update the SNA information in CM/2.

Note: You must manually add this statement to the .ndf file. The Communication ManagerSetup program provides no means for doing so.

Configuring Novell NetWare Client for APPC Using NetWareRequester

In the NetWare configuration that follows, the SNA profile is created using DOS requestor.

Creating the CSCON Configuration Profile

1. Go to the SYSTEM/CSCON directory and invoke CSCON service.

2. Select Configure Communication Services.

3. Select NetWare for SAA.

4. Create a 2.1 type service profile called appcpro (TSM requires a type 2.1 serviceprofile).


2.Server

andClien

tCommunicatio

ns

5. Select the newly created profile to create a host connection.

Creating a Host Connection

When you select Configure Host Connection from the Configure SAA Service Profilewindow, the Host Connection Configuration window appears.

1. Enter c_netid for the SNA network ID.

2. Enter c_independentlu for the Control Point Name.

3. Enter the number of licenses you have for NetWare SAA for the Number IndependentSessions Supported.

4. Place the cursor in the Host Attachment field and press the Insert key. Then select thetype of LAN to be configured. We’re selecting Token Ring in this example.

Configuring the SNA Token-Ring

After you select SNA Token Ring, the SNA Token Ring Configuration window appears.

1. Enter 04 for Token Ring Source Service Access Point.

2. Enter Primary for Token Ring Adapter Type.

3. Enter vtam_xid for the Block ID and PUID for Token Ring Connection fields. IfCPNAME is used in the VTAMLST, leave the default values for these two fields.

4. Enter the logical adapter name from the IPX bind statement in the autoexec.ncf file. Forexample, in bind ipx to TOKENSAA net=ABCD, TOKENSAA is the logical adaptername.

5. Exit CSCON.

Creating a Side Information File

1. Go to the SYSTEM\NWSAA\CPIC directory and invoke the SIUTIL service.

Note: The SIUTIL help facility clearly explains all of the fields.

2. Select Create New Side Information File.

3. Call the file MVSTIVSM.CPI.

4. Select Add A Side Information Record.

5. Call the record MVSTIVSM. This is the name to be used as symbolic destination in theclient’s dsm.opt file. Beware of case sensitive fields because certain levels of SIUTIL donot automatically change entries to uppercase letters, but TSM changes the symbolicdestination to uppercase letters.

Defining Local LU Configuration

When you select Add a Side Information Record from the Side Information RecordsCommand Menu window, the Local LU Configuration Data window appears.

1. Enter the following:a. LU name: c_independentlub. PU name: c_puc. Detach PU Type: 1d. Security Type: 0


e. LU Local Address: 0f. LU Session Limit: 8g. Network Name: c_netid

2. Press Ctrl PgDn to go to the PLU Record.

Defining Partner LU Configuration

When you press Ctrl PgDn from the Local LU Configuration Data window, the PartnerLU Configuration Data window appears.

1. Enter the following:a. LU name: partner_lu (This is the Partner LU)b. Data Link Control Name: ITRNc. Network Adapter Number: 0d. Network Adapter Address: dest_addre. LU Session Limit: 8f. Max Logical Record Size: 0g. Character Set: 0h. Local Program name: DSMCi. Remote Program Name: DSMSERV

2. Press Ctrl PgDn to go to the Mode Record.

Defining the Mode Configuration Data

When you press Ctrl PgDn from the Partner LU Configuration Data window, the ModeConfiguration Data window appears.

1. Enter the following:a. Mode name: logmodeb. Max Negotiable Session Limit: 8c. Automatic Activate Session Limit: 8d. Min Contention Winners Source: 0e. Min Contention Winners Target: 0f. Pacing size: 8g. Max RU size: 2048h. Min RU size: 256i. CNOS Flags: 6j. CNOS Termination Set: 4k. SAA Service Profile Name: appcpro (CSCON profile name)

2. Press Enter to save your changes.

3. Exit SITUIL.

Starting the Tivoli Storage Manager Client1. Edit the dsm.opt file, giving the symbolic destination a value of MVSTIVSM. For

example:

commmethod snalu6.2symbolicdestination mvstivsm

2. At the NetWare server console prompt, enter the following commands:LOAD COMMEXEC


2.Server

andClien

tCommunicatio

ns

CSLOAD APPCPROLOAD CPIC_SAA SYS:\SYSTEM\NWSAA\CPIC\MVSTIVSM.CPILOAD SYS:\TIVSM\DSMC

Note: Use CSUNLOAD APPCPRO to unload the appcpro profile.

Considerations for Using NetWare for SAA ClientsYou can support two different service profiles on the NetWare for SAA client. For example,you could have a type 2.0 service profile for 3270 emulation and a type 2.1 service profilefor TSM. There are two ways to accomplish this:

1. Use two separate, physical LAN boards on the NetWare server.

The advantage of using a separate board for the LU6.2 traffic is performance.

2. Using the same physical board.

NetWare for SAA can service a type 2.0 service profile and a type 2.1 service profileusing the same physical board. For this to work, the SOURCE SAP (Service AccessPoint) for the 2.0 service profile should be changed to ‘08’ and the 2.1 service profileshould use a SOURCE SAP of ‘04’.

Note: Using the same physical board does not work using SOURCE SAP ’04’ for the2.0 service profile and SOURCE SAP ’08’ for the 2.1 service profile. TheSOURCE SAP for the SNA connections are configured using CSCON.

Configuring the Server for 3270 EmulationMany large enterprises using MVS hosts already make wide use of 3270 emulation. AnTSM client simply generates a sequence of keystrokes that results in a connection beingestablished with the server.

OS/2, DOS, or Windows TSM clients can connect to an MVS server using 3270 emulation.

Connectivity SupportThe IBM VTAM product is required to run the 3270 communication method on the TSMserver.

VTAM SetupYour VTAM system administrator or systems programmer defines a new application toVTAM through the use of an access control block (ACB). An ACB defined for TSM, whenadded to the VTAM configuration, provides an application ID that the TSM client referenceswhen it wants to connect to the server. When the TSM application ID is referenced, a logonprocedure is begun which ultimately tells the TSM server where to look for the client.

The VTAM APPL StatementYou define the ACB in the VTAM APPL statement. The following is an example of theAPPL statement that the VTAM systems programmer should add to your VTAMconfiguration:

TIVSM VBUILD TYPE=APPLDSMAPPL APPL ACBNAME=DSMLU, x

MODETAB=ISTINCLM,DLOGMOD=#BATCH


DSMLU is the application ID that the client references when it wants to connect to theserver. The way in which the client references this name is discussed later in this installationguide where we cover client connectivity.

The Logon Mode DefinitionWhen the client references the application ID for the server (DSMLU), theMODETAB=ISTINCLM and DLOGMOD=#BATCH parameters reference a logon modedefinition which establishes the connection and the characteristics of the session. Thesecharacteristics include the maximum number of sessions allowed, the maximum number ofconversations allowed, and other control information. MODETAB references the table inwhich the logon mode definition entry is found. In this example, the table referenced is theIBM supplied VTAM default table (ISTINCLM). DLOGMOD references the table entryitself which is the default logon mode definition #BATCH.

We recommend that you use the #BATCH mode entry in the VTAM default logon modetable (ISTINCLM) initially to establish the 3279 emulation connection. Depending on yourVTAM level, this mode might not be pre-defined in the default logon mode table. Youshould verify this with your VTAM system programmer. If this mode is needed, add it to thedefault logon mode table as shown below:

TITLE 'BATCH'BATCH MODEENT LOGMODE=#BATCH, X

ENCR=B'0000',SSNDPAC=8, XSRCVPAC=8,PSNDPAC=8

After you have the 3270 emulation connection established and would like to create a newmode for performance tuning, you can create it in your current logon mode table, compile,and then link-edit the member into the VTAM library.

Tivoli Storage Manager Server SetupEnter the ACBNAME (DSMLU) from the above VTAM definition example in theLUNAME parameter of the server options file. The entry takes the following format:

luname dsmlu

The ACBNAME identifies the Tivoli Storage Manager server to VTAM as the application towhich the client can connect.

Configuring the Server for TCP/IP Using IBM TCP/IPTCP/IP provides a reliable protocol and can be easily configured for the TSM server.

Connectivity SupportTCP/IP Communications Server (CS) for OS/39 is required to run the TCP/IPcommunication method on the TSM server.

In addition, TCP/IP communications requires a suitable communications gateway such as thefollowing:¶ 3745 Communications Controller¶ 3172 Interconnect Controller¶ Channel attached RISC System/6000


||

2.Server

andClien

tCommunicatio

ns

TCP/IP Communications SetupBefore starting the Tivoli Storage Manager server, make sure that the following TCP/IP job,which includes the TCP/IP address space, has been started: TCPIP

The following TCP/IP jobs must be started if IUCV is available on your system and theIUCV communication method will be used:

VMCFTNF

These are the names of the jobs as distributed with the TCP/IP product. If the names werechanged during installation, you must determine the new names and make sure the jobs havebeen started.

The Tivoli Storage Manager will use UNIX® System Services (USS) sockets API whenOS/390 is Release 5 or higher. This may require a change to the BPXPRMxx PARMLIBmember for your installation (xx is a unique set of characters set by your systemsprogramer). In the BPXPRMxx member you will find statements similar to the following:

FILESYSTYPE TYPE(INET) ENTRYPONT(EZBPFINI)NETWORK DOMAINNAME(AF_INET)

DOMAINNUMBER(2)MAXSOCKETS(200)TYPE(INET)

or the following:

FILESYSTYPE TYPE(CINET) ENTRYPOINT(BPXTCINT)NETWORK DOMAINNAME(AF_INET)

DOMAINNUMBER(2)MAXSOCKETS(200)TYPE (CINET)

The value specified with the MAXSOCKETS keyword must be greater than the valuespecified with the Tivoli Storage Manager server option MAXSESSIONS.

Tivoli Storage Manager Server SetupEnter the following in the server options file:¶ The name of the TCP/IP address space in the TCPNAME option¶ The TCP/IP port address in the TCPPORT option

You can find the name of the TCP/IP address space in the TCPIP.TCPIP.DATA data set.TCP/IP uses this data set to specify configuration information required by TCP/IP clientprograms. The following example displays the first part of the TCPIP.TCPIP.DATA set whichidentifies TCPIP as the name of the TCPIP address space.

*TCPIPJOBNAME specified the name of the started procedure which was*used to start the TCPIP address space. TCPIP is the default.*TCPIPJOBNAME TCPIPTCPIPUSERID TCPIP

You can obtain your TCP/IP port address from your network administrator. TCP/IP, wheninstalled, comes with a number of predefined ports. Your network administrator can tell you


||||

||||||

|

||||||

||

which one has been assigned to the TSM server. The number of the port is associated withthe job name or the started task name for the server.

For example, if TCPIP is the name of your TCP/IP address space and TCP/IP port 1500 hasbeen assigned to the job name of the server, make the following entries in the server optionsfile.

tcpname tcpiptcpport 1500

Configuring the Server for TCP/IP Using TCPaccessSterling software offers TCPaccess for implementing TCP/IP on MVS. Tivoli StorageManager supports TCPaccess protocols.

Connectivity SupportTCPaccess V4.1 or later is required to run the TCPaccess protocol on the server.

Consult TCPaccess documentation for specifics on TCPaccess communication hardwarerequirements.

TCPaccess Communications SetupBefore starting the TSM server, make sure that TCPaccess is started. If TCPaccess is notstarted, the server attempts to establish contact with TCPaccess every minute. As a result,you do not have to stop and restart the server to establish contact but only start TCPaccess.

The server displays the ANR5092E message after each of the first seven unsuccessfulattempts to contact TCPaccess, advising you that contact has not been made. After theseventh attempt, the message is suppressed.

Tivoli Storage Manager Server SetupEnter the following in the server options file:¶ The TCPaccess subsystem name in the ICSSNAME option¶ The TCP/IP port address in the ICSPORT option

You can find the TCPaccess subsystem name specified in the SSN parameter in theTCPaccess startup JCL. The default subsystem name is ACSS. You can find the TCPaccessstartup JCL in SYS1.PROCLIB. The TCPaccess subsystem name can be no longer than fourcharacters.

You can obtain your TCP/IP port address from your network administrator. TCPaccess, wheninstalled, comes with a number of predefined ports. Your network administrator can tell youwhich one has been assigned to the TSM server.

For example, if ACSS is the TCPaccess subsystem name and TCP/IP port 1500 has beenassigned to the TSM server, make the following entries in the server options file.

icssname acssicsport 1500


2.Server

andClien

tCommunicatio

ns

Configuring the Server for IUCVTSM can use Inter-User Communication Vehicle (IUCV) to communicate with the TSOadministrative client. However, it is recommended that either TCP/IP or APPC be used forTSO administrative client communications.

Connectivity SupportEnsure that IUCV is available on your system before trying to use it as a communicationmethod for the TSO administrative client.

Tivoli Storage Manager Server SetupEnter the following in the server options file:

iucv start

Configuring the Server for Web Access with IBM TCP/IPTCP/IP must be active before you can use the administrative web interface. Ensure that theANRIDL job was run on the TSM server. See Figure 1 on page 4.

Enter a port number in the server options file:

httptcpport 1580

The default is 1580.

Configuring the Server for Web Access with TCPaccessTCPaccess communications must be active before you can use the administrative webinterface. Also, ensure that the ANRIDL job was run on the TSM server (see Figure 1 onpage 4).

Enter a port number in the server options file:

httpicsport 1580

The default is 1580.

Connecting with Tivoli Storage Manager across a FirewallThe Tivoli Storage Manager server and clients can work across a firewall in most cases. Youmust configure the firewall to open up the ports that the server and clients need. Becausefirewalls differ in how you open the ports, you must follow the instructions thataccompanied the firewall software or hardware that you are using. If you need help withopening ports, contact the supplier of your firewall.

The following operations require that you open ports on the firewall:

¶ To allow clients to communicate with a server across a firewall, you must open the portthat is the TCP/IP port for the server (the TCPPORT option in the server options file).The default TCP/IP port is 1500.


||

|

|

|||||

|

|||

¶ To use the administrative Web interface for a server across a firewall, you must open theport that is the HTTP port for the server (the HTTPPORT option in the server optionsfile). The default HTTP port is 1580.

We strongly recommend that you use the Tivoli Storage Manager Secure WebAdministrator Proxy for Web administration of the Tivoli Storage Manager server in anenterprise environment. Install the proxy on a web server that sits on the firewall, so thatthe web server can access resources on both sides of the firewall (this is sometimescalled the ″demilitarized zone″). Once you set up the proxy, you can use it to administerany TSM server at Version 3.7 or higher. For more information on how to install anduse the proxy, see the appendix about the Web proxy in Quick Start. You can alsoincrease security in this environment by enabling HTTPS services (also called securesocket layer, or SSL) on the web server where you install the proxy. Check theinformation for your web server for how to set this up.

¶ To use the Web backup-archive client to connect to a client across a firewall, you mustuse the client at Version 4.1.2 or later. You must open three ports on the firewall. Theports are:

v The HTTP port for the client (the HTTPPORT option in the client options file). Thedefault client HTTP port is 1581.

v The two ports specified with the WEBPORTS option in the client options file. Bydefault, Web ports are assigned randomly, which does not work across a firewall. Youmust specify this option with non-zero values for the two ports, then open these portson the firewall.

Currently the following operations are known to have problems when a firewall is in place:

¶ The backup-archive Web client at a version earlier than Version 4.1.2 does not workwhen the client system or server that it connects to is across a firewall.

¶ The client scheduler operating in prompted mode does not work when the server isacross a firewall. The client scheduler does work when operating in polling mode.

¶ The server cannot log events to a Tivoli Enterprise™ Console (T/EC) server across afirewall.

Configuring a DOS Client for 3270 EmulationThe following communications software is required in order to run the DOS TSM clientusing 3270 emulation:

¶ IBM Personal Communications/3270 3.0 (42G0452) or laterOR

¶ Attachmate EXTRA! emulation product

To configure the DOS client for communications, you must first create the client options file(dsm.opt) and then, modify it with the minimum required settings.

1. To create the client options file, type the following at the command prompt and pressEnter:

copy dsm.smp dsm.opt


|||

||||||||||

|||

||

||||

|

||

||

||

|

2.Server

andClien

tCommunicatio

ns

2. Modify the NODENAME option so that it corresponds with the name assigned to theclient node when it was registered through the administrator command interface. See“Registering Backup-Archive Client Nodes” on page 18.

For example, if the node name assigned during registration was client1, make the entryas follows:

nodename client1

3. Modify the 3270HOSTCOMMAND option with a command string that includes a logoncommand that will connect the 3270 terminal to the Tivoli Storage Manager server. Thelogon command takes the form LOGON APPLID(), where the application id specifiedwithin the parenthesis is the name defined for the TSM server during VTAM setup. Forexample, in “The VTAM APPL Statement” on page 50, the name defined for the serveris DSMLU.

The command string can also contain any sequence of keystrokes such as clearing a logoand perhaps switching to a particular VTAM panel. For example, the following stringclears the screen, gets the VTAM applications panel up, and logs on to the TSM server:

@C IBMVAMP@E LOGON APPLID(DSMLU)@E

DSMLU is the application id defined by the systems programmer as discussed earlier in“VTAM Setup” on page 50. The letters preceded by the @ are action keystrokes, likeclear or enter. These are explained in Installing the Clients.

4. Close all your applications and reboot your system in order for the modifications to takeeffect.

You are now ready to verify the adequacy of the server installation by starting up the DOSClient.

Configuring TSO Administrative Client Using APPC1. In the SYS1.PARMLIB dataset, create the APPC/MVS configuration members,

APPCPMxx and ASCHPMxx. See Figure 21 through Figure 25.

Note that APPCPMxx does not need to define the LU of the server application nor doesit require a transaction program (TP) in the MVS APPCTP repository. This is becauseTSM uses the VTAM record level API rather than the APPC/MVS.

Figure 21 on page 57 shows the APPCPMxx statements used to define an APPC/MVSconfiguration.


Figure 22 shows the sample IDCAMS job to create the dataset SYS1.APPCTP.

Figure 23 shows the sample IDCAMS job to create the dataset SYS1.APPCSI.

Figure 24 on page 58 shows the VTAM LU definitions defined for an APPC/MVSconfiguration.

/*** ***//* This is an example using APPCPMxx statements to define an *//* APPC/MVS configuration. *//* *//* APPCPMxx parmlib members contain startup, default, and *//* customization values for APPC/MVS. They also contain *//* information indicating the correspondence between *//* logical unit(LU) names and transaction schedulers. *//* *//* This member illustrates the use of the LUADD, LUDEL, and *//* SIDEINFO statement types, in context. *//*** ***/

LUADD ACBNAME(A4VAPPC) /* SPECIFY THE NAME OF THE LU TO BE *//* added - generic LU. */

BASE /* This is the default LU for *//* outbound requests. */

TPDATA(SYS1.APPCTP)/* Specify the TP profile repository. *//* */

TPLEVEL(SYSTEM) /* TPLEVEL(SYSTEM) is the default. *//* OTHER VALUES COULD BE SPECIFIED. */

SIDEINFO /* Specify that VSAM data set */DATASET(SYS1.APPCSI)/* SYS1.APPCSI is the permanent */

/* repository for the side information.*/

Figure 21. APPCPMxx Parmlib Member

//APPCTP EXEC PGM=IDCAMS//SYSPRINT DD SYSOUT=*//SYSIN DD *

DEFINE CLUSTER -(NAME(SYS1.APPCTP) -VOLUMES(JTFASH) -INDEXED REUSE -SHAREOPTIONS(3 3) -RECORDSIZE(3824 7024) -KEYS(112 0) -RECORDS(300 150))

Figure 22. Sample JCL for TP Create (SYS1.APPCTP)

//APPCSI EXEC PGM=IDCAMS//SYSPRINT DD SYSOUT=*//SYSIN DD *

DEFINE CLUSTER -(NAME(SYS1.APPCSI) -VOLUMES(JTFASH) -INDEXED REUSE -SHAREOPTIONS(3 3) -RECORDSIZE(248 248) -KEYS(112 0) -RECORDS(50 25))

Figure 23. Sample JCL for SI Create (SYS1.APPCSI)


2.Server

andClien

tCommunicatio

ns

Figure 25 shows the ASCHPMxx statements used to define an APPC/MVS configuration.

2. Create a job for the server’s side information record in SYS1.APPCSI. See Figure 26.

3. Insert the following lines into your TSO administrative client’s option file:

//************* MVSAPPC - VTAM LU DEFINITIONS FOR APPC/MVS ****//***********MVSAPPL VBUILD TYPE=APPLA4VAPPC APPL APPC=YES, X

ABCNAME=A4VAPPC, XAUTOSES=0, XDDRAINL=NALLOW, XDRESPL=NALLOW, XEAS=32, XMODETAB=TPOMODE, XSECACPT=CONV, XSRBEXIT=YES, XVERIFY=NONE

Figure 24. Generic VTAM LU definition for APPC/MVS

CLASSADD CLASSNAME(A)MAX(6)MIN(2)RESPGOAL(0.5)MSGLIMIT(500)

CLASSADD CLASSNAME(FAST)MAX(6)MIN(2)RESPGOAL(0.02)MSGLIMIT(500)

CLASSADD CLASSNAME(SLOW)OPTIONS DEFAULT(SLOW)

SUBSYS(JES2)TPDEFAULT REGION(4M)

TIME(10,30)MSGLEVEL(1,1)OUTCLASS(X)

Figure 25. ASCHPMxx Parmlib Member

//TSOUSER JOB ,TSOUSER,MSGCLASS=X,// PRTY=5//TPINFO EXEC PGM=ATBSDFMU//SYSPRINT DD SYSOUT=*//SYSSDOUT DD SYSOUT=*//SYSSDLIB DD DISP=SHR,DSN=SYS1.APPCSI//SYSIN DD *SIDELETE

DESTNAME(TOTIVSM2) <=== ensure it is not there yetSIADD

DESTNAME(TOTIVSM2) <=== symbolic destination name in dsm.optTPNAME(DUMMY) <=== any name you wishMODENAME(TSMAPPC) <=== mode namePARTNER_LU(A4VTSM2) <=== Partner LU

SIRETRIEVEDESTNAME(TOTIVSM2)

Figure 26. Sample Job


commmethod snalu6.2symbolicdestination totivsm2 <== the name defined in MVS SI record

4. Create a CLIST to start the TSM TSO administrative client and name the CLISTANSADM. See Figure 27.

5. Ensure APPC/MVS is available before starting the TSM TSO administrative client. Then,enter the following commands:

S APPC,SUB=MSTRS ASCH,SUB=MSTR

6. To start the TSO administrative client, enter the TSO command EX (ANSADM) orDSMADMC. For DSMADMC to execute properly, the ANSPROC procedure must haveexecuted at TSO logon. See “Starting the TSO Administrative Client” on page 14 forinformation about ANSPROC.

Configuring AIX SNA Server/6000 Clients Using SMITDefine the Data Link Control (DLC)1. Select Devices.2. Select Communication.3. Select Token Ring Adapter.4. Select Services.5. Select Data Link Controls.6. Select Add a Token Ring Data Link Control.

Getting to SNA Server/6000 via SMIT1. Select Communications Application and Services.2. Select SNA Server/6000.3. Select Configure SNA Profiles.

Creating the Initial Node Definition

To create the initial node definition, follow these steps:

1. From the Configure SNA Profiles window, select Initial Node Setup.

2. Select token_ring for this configuration. The Initial Node Setup screen appears. SeeFigure 28 on page 60.

PROC 0PROFILE PROMPTCONTROL NOLIST NOCONLIST MSG FLUSH PROMPT/* it is important to include the parameter “PROMPT” *//* in the PROFILE and CONTROL statements to allow *//* DSMADMC (TSO Admin Client module) to prompt for *//* input (e.g. PASSWORD). */ALLOC F(DSCOPT) DA(‘TIVSM.TSOADMIN.OPTIONS’) SHR REUSEALLOC F(DSCLANG) DA(‘TIVSM.SANSMSG(ANSMENU)’) SHR REUSECALL ‘SYS1.LINKLIB(DSMADMC)’FREE F(DSCOPT DSCLANG )

Figure 27. Sample CLIST


2.Server

andClien

tCommunicatio

ns

3. Enter c_independentlu for the Control Point name.

4. Select appn_end_node for the Control Point type.

5. Enter c_netid for the Local Network Name.

6. Enter vtam_xid for the XID node ID. This is the IDBLK and IDNUM defined in the3745 VTAMLST. This node id is essential in a cross-domain environment where theserver application host machine is not the same as the host machine that the workstationis generated to.

7. The rest of the fields can be left with the defaults.

8. Press Enter to save your input.

9. Press PF3 to return to the Configure SNA Profiles window.

Note: The Initial Node setup is similar to OS/2 CM/2 define Local Node Characteristics.This can also be done in SMIT under the Advanced Configuration/ControlPoint window.

Creating the Link/Mode/Side Information

1. Select Advanced Configuration.

2. Select Links.

3. Select Token Ring from the Token Ring Physical Units window.

Note: The screens in Figure 29 on page 61 and Figure 30 on page 63 are actually compositescreens. You need to use Page Down and Page Up to view all of the parameters. Thevalues that you need to change are shown in bold print.

Initial Node Setup

Type or select values in entry fields.Press Enter AFTER making all desired changes.

[Entry Fields]Control Point name token_ring + [F13833D0]Control Point type appn_end_node +Local network name [DEIBMFD]XID node ID [05df333d]

Optional link station information:

Link station type token_ringLink station name []

* Calling link station? yes +Link address [] X

F1=Help F2=Refresh F3=Cancel F4=ListEsc+5=Undo F6=Command F7=Edit F8=ImageF9=Shell F10=Exit Enter=Do

Figure 28. Initial Node Setup Screen


Token Ring SNA DLC

1. Select Add a profile.

2. Enter a name for the profile. For example, tok0.00001.

3. Enter c_independentlu for the Local Link Name.

4. Under Dynamic Link Activation Parameters:a. Change Solicit SSCP sessions to yes.b. Change CP-CP sessions Supported to no.

Add Token Ring SNA DLC Profile


[TOP] [Entry Fields]Profile name [tok0.00001]Data link device name [tok0] +Force disconnect time-out (1-600 seconds) [120] #User-defined maximum I-Field size? yes +

...

Receive window count (1-127) [8] #Ring access priority 0 +Inactivity time-out (1-120 seconds) [48] #Response time-out (1-40, 500 msec intervals) [4] #Acknowledge time-out (1-40, 500 msec intervals) [1] #Local link name [F13833D0]Local SAP address (04-ec) [04] XTrace base listening link station? no +

If yes, Trace format long +Dynamic link stations supported? yes +

Link Recovery Parameters...

Dynamic Link Activation ParametersSolicit SSCP sessions? yes +CP-CP sessions supported? no +Partner required to support CP-CP sessions? no +

Dynamic Link TG COS Characteristics...

Dynamic Link TG COS Characteristics...

Comments [][BOTTOM]


Figure 29. Add Token Ring SNA DLC Profile Screen


2.Server

andClien

tCommunicatio

ns

5. Press Enter to save the profile.

6. Press PF3 to return to the Token Ring Physical Units window.

Token Ring Link Station

1. From the Token Ring Physical Units window, select Token Ring Link Station.

2. Select Add a Profile. There is one link-station defined per server. Use most of thedefault parameters.

3. Enter a name for the profile. This value can be anything and the server name can be theprofile name. BCTSO is the name of the profile in this example.

4. Press Enter to create the profile. The Add Token Ring Link Station Profile windowappears. See Figure 30 on page 63.


5. Place the cursor in the SNA DLC Profile name field and press PF4. Select the TokenRing SNA DLC that was created above. It is tok0.00001 in this example.

6. Under Adjacent Node Address Parameters, enter dest_addr for the Remote linkaddress

7. Under Link Activation Parameters, do the following:a. Change Solicit SSCP sessions to yes.b. Change Initiate call when link station is activated to yes. This denotes that this is a

calling link station.c. Change Activate link station at SNA start up to yes.d. Change CP-CP sessions Supported to no.

Add Token Ring Link Station Profile


[TOP] [Entry Fields]Profile name [BCTSO]Use APPN Control Point’s XID node ID? yes +

* SNA DLC Profile name [tok0.00001] +...

Adjacent Node Address ParametersAccess routing link_address +If link_name, Remote link name yes []If link_address,

Remote link address [400010000002] XRemote SAP address (04-ec) [04] X

Adjacent Node Identification Parameters...

Link Activation ParametersSolicit SSCP sessions? yes +Initiate call when link station is activated? yes +Activate link station at SNA start up? yes +Activate on demand? no +CP-CP sessions supported? no +...

Restart Parameters...

Transmission Group COS Characteristics...

Comments [][BOTTOM]


Figure 30. Add Token Ring Link Station Profile Window


2.Server

andClien

tCommunicatio

ns


9. Press PF3 until you return to the Advanced Configuration window.

Defining LU 6.2 Session

1. Select Sessions.

2. Select LU 6.2.

LU 6.2 Mode

1. Select LU 6.2 Mode.

2. Select Add a Profile.

3. Enter the profile name. You can use the same name as the mode name in the next step.See Figure 31.

4. Enter logmode for the Mode name This is the client’s LOGMODE.

Note: This must match the VTAM’s logmode defined in the mode table entry.


6. Press PF3 to return to the LU 6.2 window.

Partner LU6.2 Profile

1. From the LU 6.2 window, select LU 6.2 Partner LU.


Add LU 6.2 Mode Profile


[Entry Fields]* Profile name [TSMAPPC]

Mode name [TSMAPPC]Maximum number of sessions (1-5000) [8] #Minimum contention winners (0-5000) [4] #Minimum contention losers (0-5000) [0] #Auto activate limit (0-500) [0] #Upper bound for adaptive receive pacing window [16] #Receive pacing window (0-63) [7] #Maximum RU size (128,...,32768: multiples of 32) [1024] #Minimum RU size (128,...,32768: multiples of 32) [256] #Class of Service (COS) name [#CONNECT]

Comments []


Figure 31. Add LU 6.2 Mode Profile Window


3. Enter the profile name. This name can be any value. BCTSO is used in this example.See Figure 32.

4. Enter the s_netid.partner_lu for the Fully qualified partner LU name.

5. Enter the Partner LU Alias. This value can be anything.


7. Press PF3 to return to the LU 6.2 window.

Partner LU 6.2 Location

1. Select Partner LU 6.2 Location. This is the same as theDEFINE_PARTNER_LU_LOCATION statement in CM/2. It is required for anycross-domain environment.


3. Enter the profile name. This name can be any value. BCTSO is used in this example.

Add LU 6.2 Partner LU Profile


[Entry Fields]* Profile name [BCTSO]

Fully qualified partner LU name [DEIBMA4.A4VTSM2]Partner LU alias [A4VTSM2]Parallel sessions supported? yes +Session security supported? no +Conversation security level none +

Comments []


Figure 32. Add LU 6.2 Partner LU Profile


2.Server

andClien

tCommunicatio

ns

4. Enter s_netid.partner_lu for the Fully qualified partner LU name.

5. Enter c_netid.cp_name for the Fully qualified owning Control Point (CP) name.cp_name must be the SSCPNAME of the workstation’s network. In this environment,the SSCPNAME is FDW.


7. Press PF3 until you return to the LU 6.2 window.

Side Information

1. Select LU 6.2 Side Information.

2. Enter any name for the profile. The name that you enter here must also be the symbolicdestination specified in the client’s dsm.opt file. BCTSO is used in this example.

Add Partner LU 6.2 Location Profile



Fully qualified partner LU name [DEIBMA4.A4VTSM2]Fully qualified owning Control Point (CP) name [DEIBMFD.FDW]Local node is network server for LEN node? no +Fully qualified network node server name []

Comments []


Figure 33. Add Partner LU 6.2 Location Profile Window


3. Enter c_independentlu for the Local LU or Control Point alias. This can be selectedfrom the PF4 list.

4. Enter s_netid.partner_lu for the Fully qualified partner LU name or select the PartnerLU Alias name.

5. Select the Mode name from the PF4 list. This is the mode you have just created.

6. Enter the Remote transaction program name (RTPN). This can be any name.ANYTHING is used in this example.


8. Press PF3 until you return to the Advanced Configuration window.

Verify Configuration Profiles

1. Select Verify Configuration Profiles from the Advanced Configuration window. Thiscan also be done from any window that has the verify option.

Add LU 6.2 Side Information Profile



Local LU or Control Point alias [F13833D0] +Provide only one of the following:

Partner LU alias [] +Fully qualified partner LU name [DEIBMA4.A4VTSM2]

Mode name [TSMAPPC] +Remote transaction program name (RTPN) [ANYTHING]RTPN in hexadecimal? no +

Comments []


Figure 34. Add LU 6.2 Side Information Profile Window


2.Server

andClien

tCommunicatio

ns

Starting the Tivoli Storage Manager Client1. Edit the dsm.sys file, giving the symbolic destination a value of BCTSO. For example:

servername bctsocommmethod snalu6.2

symbolicdestination bctso

2. Ensure that SNA/6000 is started. This can be done by using the ‘sna -start sna’ commandor via SMIT under the Manage SNA Resources window.

3. Start the TSM program.

Considerations for Using the SNA Services/6000 ClientThe SNA Services/6000 setup is the same as the SNA Server/6000 setup except for oneimportant difference–the partnerluname in the dsm.sys file specifies the “ConnectionProfile” name of the file that has the partner LU definition and not the actual partner LUname. This difference is attributed to the way that SNA Services/6000 implements thepartner LU.

Diagnosing Initial Connection FailuresAll TSM clients that use APPC issue standard CPI-C calls to communicate. A standard set ofreturn codes apply to all clients and can be useful in diagnosing initial connection failures.The CPI-C return codes are prefixed by CM. For example, CM_PARAMETER_ERROR.

Determining CPI-C Return CodesTSM does not write the base CPI-C return code to the TSM error log. To determine theCPI-C return code, you must run a TSM trace. To run a trace, add the following statementsto the client options file (dsm.opt):

Advanced Configuration

Move cursor to desired item and press Enter.

LinksSessionsSNA System DefaultsControl PointGateway DefinitionsSecurityVerify Configuration ProfilesExport Configuration ProfilesImport Configuration ProfilesMigrate Configuration Profiles

F1=Help F2=Refresh F3=Cancel F8=ImageF9=Shell F10=Exit Enter=Do

Figure 35. Advanced Configuration Window


traceflags commtracefile trace.out

An example of the trace file is shown in Figure 36.

Note: Tivoli Storage Manager clients write the CPI-C return information directly to thedsmerror.log file, eliminating the need to run the COMM trace.

Analyzing CPI-C Return CodesHere is a list of common CPI-C errors encountered when trying to configure APPCcommunications for TSM. A complete list of the CPI-C return codes is documented inCommon Programming Interface Communications Specifications (SC31-6180)

CM_ALLOCATE_FAILURE_NO_RETRY

The conversation cannot be allocated on a session because of a condition that is nottemporary. Likely causes are:

v A 3174 controller is being used which does not support independent LU traffic.

v TSM is using a dependent LU. If an independent LU is defined on the workstation,ensure that the default_local_lu_alias points to an independent LU.

It is usually useful to get the sense information for these failures (see “Obtaining SenseInformation” on page 71).

CM_ALLOCATE_FAILURE_RETRY

The conversation cannot be allocated on a session because of a condition that might betemporary. Likely causes are:

v An APPN feature has not been configured correctly on the 3174.

v TSM was unable to find the partner LU location.

It is usually useful to get the sense information for these failures (see “Obtaining SenseInformation” on page 71).

CM_TP_NOT_AVAILALBE_NO_RETRY

The remote system rejected the allocation request because the local program specified aremote program that the remote system recognizes but cannot start. Likely causes are:

v The TSO administrative client session has not been prepared for prompting correctly.To ensure that password prompting works correctly, issue PROFILE PROMPT beforeinvoking the client program.

CM_PARAMETER_ERROR

Tracing is active to file ‘trace.out’,----------------------------------------------------------------06/20/1998 10:59:32 - Trace begun.commcpic.c(3895): ConvInit set protocol stack to OS/2SAA rc: 0commcpic.c(3929): ConvInit: Error initializing conversation to sym_dest_name SPIKEcommcpic.c(3231): CpicOpen: Error initializing conversation, rc: 24commcpic.c(4172): CastCpicRc: Entry rc: CM_PROGRAM_PARAMETER_CHECK (24),

Figure 36. Sample Trace File


2.Server

andClien

tCommunicatio

ns

The local program issued a call specifying a parameter containing an invalid argument.Likely causes are:

v The local program attempted to use the mode named SNASVCMG or CPSVCMG.

v The partner LU alias refers to an undefined partner LU name.

v For NetWare for SAA clients, the CSCON.NLM or CPIC_SAA program has not beenloaded.

CM_PROGRAM_PARAMETER_CHECK

The local program issued a call in which a programming error has been found in one ormore parameters. Ensure that the following are correct:

v Syntax of APPC options in the dsm.opt file

v Syntax of parameters in APPC configuration

Gathering Initial Documentation for Level-2 SupportIf you need to contact the support center for help, collect the following information:

¶ VTAM PU/LU definition for the workstation and independent LU

¶ VTAM mode table

¶ Client dsm.opt file

¶ Client workstation APPC definitions (see Table 5)

Table 5. Obtaining Client Configuration DefinitionsProduct Where to Look...

OS/2 CommunicationsManager 2 (CM/2)

CM/2 writes configuration definitions to a file with the extension of .ndf.This file can be found in the -CMLIB subdirectory.

OS/2 ExtendedServices®

Extended Services writes configuration definitions to a file with theextension of .ndf. This file can be found in the -CMLIB-APPNsubdirectory.

SNA/6000 SNA/6000 allows the user to export SMIT SNA/6000 configurationdefinitions to a .jfs file. To export the definitions:¶ Type SMIT SNA from a AIX command line¶ Select Configure SNA Profiles¶ Select Advanced Configuration¶ Select Export Configuration Profiles¶ Enter a filename for the export output

NetWare SAA NetWare SAA does not provide a mechanism to export SIUTIL definitionsto a file. Screen captures from SIUTIL must be obtained. From the SIUTILexec, view the side information file and capture the three main SIUTILscreens:¶ Local LU Configuration Data¶ Partner LU Configuration Data¶ Node Configuration Data

Also obtain the PU 2.1 service profile being used by the TSM sideinformation record.


Obtaining Sense InformationOften it is useful to obtain the sense information to pinpoint an error. In some specific cases,such as CM_ALLOCATE_FAILURE_NO_RETRY, it is necessary. Each platform offers aunique trace facility to capture this information. The following sections discuss eachplatform in detail.

OS/2 CM/2There are two ways to obtain sense information in an OS/2 environment.¶ Running CM/2 Trace Services¶ Issuing CMTRACE at the command line

Running CM/2 Trace ServicesTo run CM/2 Problem Determination Aids - Trace Services, double click on the ProblemDetermination Aids - Trace icon in the CM/2 folder. The Problem Determination Aids -Trace Services window appears.

To start the trace, follow these steps:

1. Select APPC under the APIs column.

2. Select the DLC which your computer is using. IBMTRNET is used in this example.

3. Select all Events that begin with APPC_.

4. Press the Start button.

To view the trace, follow these steps:

1. Press the Stop all button to stop the trace.

2. Press the Save button.

3. Select a filename and press the OK button.

4. Select Format trace file... from the File pull-down menu.

5. Check the Output file format - Detail box. Let all other options assume their defaultvalues.

Issuing CMTRACE CommandsTo use CMTRACE commands to create a trace file, do the following:

1. From an OS/2 command prompt, run the APPNT.CMD command file shown inFigure 37 on page 72. This starts CMTRACE.


2.Server

andClien

tCommunicatio

ns

2. Run the TSM command or operation you want to trace.

3. From an OS/2 command prompt, run the APPNF.CMD command file shown inFigure 38. This stops CMTRACE and formats the trace file.

Reading the Trace FileIf you used Trace Services, a detailed trace file was created with the same prefix that waschosen when the file was saved, but with an extension of .det. If you used CMTRACE atthe command line, the trace file that you specified was created.

In the trace file, look for the CM_ALLOCATE_FAILURE_NO_RETRY message. Pagingup from this error code reveals the sense data. For example, Sense data = 0xFFFE0113.

NetWare for SAAThe PBTRACE program is NetWare’s equivalent to the CM/2 trace facility. It can be used todetermine the Primary and Secondary APPC return codes for NetWare for SAA clients.

Running PBTRACETo run PBTRACE, follow these steps:

1. Make sure COMMEXEC is loaded by issuing the LOAD COMMEXEC command fromthe NetWare console.

Note: All of the commands shown in this section should be issued from the NetWareconsole.

@ECHO OFFREM ** Start traces after resetting the trace bufferREM ** Trace APPC and services verbs, Token ring Data andREM ** APPC events 1 2 3 4 5 and 12REM ** event 1 = internal DLC interfaceREM ** event 2 = APPC verbsREM ** event 3 = internal APPC flowsREM ** event 4 = APPC send and receiveREM ** event 5 = XID flowsREM ** event 12 = Utility verbs such as error log entriesREM ** storage 3 uses up to three 64K segments for tracesREM ** For other options in tracing enter "CMTRACE ?"ECHO ONCMTRACE START -reset -api appc services -data ibmtrnet -event 1 2 3 4 5 12-storage 3

Figure 37. APPNT.CMD Command File

@ECHO OFFREM ** Stop traces (trace data remains in storage)REM ** Copy TRACE from storage to disk file in the current directoryREM ** File name is specified as a parameter and the extension isREM ** .TRC for the full trace,REM ** .DET for the detailed trace andREM ** .SUM for the trace summaryREM ** For other options in trace formatting enter FMTTRACE ?REM ** If you want tracing to continue with the same type, then removeREM ** the CMTRACE STOP line.ECHO ONCMTRACE STOPCMTRACE copy %1.trcFMTTRACE -DS %1

Figure 38. APPNF.CMD Command File


2. Issue the LOAD PB_NWSAA command.

3. Issue the CSLOAD APPCPRO to load the 2.1 service profile.

4. Issue the LOAD PBTRACE command.

Answer yes (“Y”) to the two prompts that follow.

5. Issue the LOAD CPIC_SAA SYS:\SYSTEM\NWSAA\CPIC\MVSTIVSM.CPIcommand to load the side information file.

6. Issue the LOAD SYS:\TIVSM\DSMC command.

Note: To stop the trace, reissue the LOAD PBTRACE command, but answer no (“N”) tothe two prompts that follow.

Reading the Trace FileAfter completing the previous steps, the trace information is written to a file calledSYS:\SYSTEM\OUTPUT.PC.

The service profile log found in the SYS:SYSTEM directory should also be obtained alongwith the trace. For some errors the SUBTYPE field will contain the sense code from theerror.

Contact Novell or IBM support to help read the trace information.

SNA Server/6000Sense information can be found in the SNA Server/6000 failure logs. For more informationabout SNA Server/6000 trace facilities, see AIX SNA Server/6000: Diagnosis Guide andMessages

Obtaining Failure Log InformationTo obtain failure log information, follow these steps:

1. Direct the SNA Server/6000 failure log to a file by issuing the following command:

sna -setlogs -f /var/sna/tivsm

This directs failure messages to /var/sna/tivsm.1.

2. Recreate the failure.

3. Close the current set of logs with the command:

sna -setlogs -t

This closes the file /var/sna/tivsm.1 and directs failure messages to /var/sna/tivsm.2

4. Format the failure log by issuing the following command:

trcrpt -d 27B /var/sna/tivsm.1 > /var/sna/tivsm.out

This formats the data and writes it to a file called /var/sna/tivsm.out.

Note: To issue commands you must be running as root or as part of group system.


2.Server

andClien

tCommunicatio

ns

Reading the Formatted Failure LogUse “vi” or any other system editor to view the log information. Look for the string SenseCode:.

Software RequirementsUsing APPC, you can establish communications between an MVS server and OS/2, NovellNetWare, AIX/6000, and TSO clients. Table 6 lists the software requirements for usingAPPC with any of the above mentioned configurations.

Note: Hardware adapter options are not listed since they are transparent as long as they aresupported by the operating system.

Table 6. APPC Software RequirementsSoftware Requirements

MVS Server Communications Server (CS) for OS/390

IBM OS/2 or IBMOS/2 DBCS Clients

One of the following:

¶ IBM Communications Manager/2 Version 1.0 or later

¶ IBM OS/2 Extended Services Version 1.0 or later

¶ IBM SAA Networking Services/2

Novell NetWareClients

NetWare for SAA level 1.3.52 or later (COMMEXEC level 1.3.45 or later)

AIX/6000® ClientsVersion 3.2 and above

SNA Services/6000 Version 1.2

Version 3.2.3 and aboveSNA Server/6000 Version 2.1

TSO Administrativeclients

Communications Server (CS) for OS/390

3174CommunicationController

Communications Server (CS) for OS/390

LAN Type:¶ Token Ring (one of the following):v 3174 LIC-B with T2.1 Passthru Support (RPQ 8Q0800)v 3174 LIC-C3 and APPN Feature Codev 3174 LIC-C5 which includes APPN Feature Code (recommended)

¶ Ethernet (one of the following):v 3174 LIC-C4 and APPN Feature Codev 3174 LIC-C5 which includes APPN Feature Code (recommended)

Results FilesThis section displays the following results files:¶ CM/2 .ndf File for 3174 Gateway (Figure 39 on page 75)¶ CM/2 .ndf File for 3172 or 3745 Gateways (“CM/2 .ndf File for 3172 or 3745

Gateways” on page 77)¶ SNA Profile for AIX Clients (“SNA Profile for AIX Clients” on page 79)


CM/2 .ndf File for 3174 Gateway

DEFINE_LOCAL_CP FQ_CP_NAME(PELNET01.IMAGOS2I) <== c_netid.c_independentluDESCRIPTION(ps/2 mod 95 s/n HD256) <== Any ValueCP_ALIAS(imagos2i)NAU_ADDRESS(INDEPENDENT_LU)NODE_TYPE(EN)NW_FP_SUPPORT(NONE)HOST_FP_SUPPORT(YES)MAX_COMP_LEVEL(NONE)MAX_COMP_TOKENS(0);

DEFINE_CONNECTION_NETWORK FQ_CN_NAME(PELNET01.LAN2AE ) <== c_netid.cp_nameADAPTER_INFO( DLC_NAME(IBMTRNET)

ADAPTER_NUMBER(0));DEFINE_LOGICAL_LINK LINK_NAME(LINK3174)

DESCRIPTION(Link to MVS TSM server via 3174-21L s/n KN671)ADJACENT_NODE_TYPE(NN)PREFERRED_NN_SERVER(YES)DLC_NAME(IBMTRNET)ADAPTER_NUMBER(0)DESTINATION_ADDRESS(X'400031740671') <== dest_addrETHERNET_FORMAT(NO)CP_CP_SESSION_SUPPORT(YES)SOLICIT_SSCP_SESSION(YES)NODE_ID(X'05D00000') <== vtam_xidACTIVATE_AT_STARTUP(YES)USE_PUNAME_AS_CPNAME(NO)LIMITED_RESOURCE(NO)LINK_STATION_ROLE(USE_ADAPTER_DEFINITION)MAX_ACTIVATION_ATTEMPTS(USE_ADAPTER_DEFINITION)EFFECTIVE_CAPACITY(USE_ADAPTER_DEFINITION)COST_PER_CONNECT_TIME(USE_ADAPTER_DEFINITION)COST_PER_BYTE(USE_ADAPTER_DEFINITION)SECURITY(USE_ADAPTER_DEFINITION)PROPAGATION_DELAY(USE_ADAPTER_DEFINITION)USER_DEFINED_1(USE_ADAPTER_DEFINITION)USER_DEFINED_2(USE_ADAPTER_DEFINITION)USER_DEFINED_3(USE_ADAPTER_DEFINITION);

DEFINE_PARTNER_LU FQ_PARTNER_LU_NAME(PELNET01.DFDSMLU2) <== s_netid.partner_luDESCRIPTION(TSM server on MVS)PARTNER_LU_ALIAS(DFDSM) <== Partner LU AliasPARTNER_LU_UNINTERPRETED_NAME(DFDSMLU2) <== partner_luMAX_MC_LL_SEND_SIZE(32767)CONV_SECURITY_VERIFICATION(NO)PARALLEL_SESSION_SUPPORT(YES);

Figure 39. Sample .ndf File for 3174 Gateway (Part 1 of 2)


2.Server

andClien

tCommunicatio

ns

Note: This example uses a different TSM server than does the rest of this document. SeeFigure 12 on page 39 for the LU definition.

DEFINE_MODE MODE_NAME(TSMAPPC) <== logmodeDESCRIPTION(APPC mode name on MVS)COS_NAME(#BATCH)DEFAULT_RU_SIZE(NO)MAX_RU_SIZE_UPPER_BOUND(4096)RECEIVE_PACING_WINDOW(63) <== CM/2 runs on an 80486 - use 63MAX_NEGOTIABLE_SESSION_LIMIT(32767)PLU_MODE_SESSION_LIMIT(16)MIN_CONWINNERS_SOURCE(2)COMPRESSION_NEED(PROHIBITED)PLU_SLU_COMPRESSION(NONE)SLU_PLU_COMPRESSION(NONE);

DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES)DEFAULT_MODE_NAME(BLANK)MAX_MC_LL_SEND_SIZE(32767)DIRECTORY_FOR_INBOUND_ATTACHES(*)DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED)DEFAULT_TP_PROGRAM_TYPE(BACKGROUND)DEFAULT_TP_CONV_SECURITY_RQD(NO)MAX_HELD_ALERTS(10);

DEFINE_CPIC_SIDE_INFO SYMBOLIC_DESTINATION_NAME(DFDSM ) <== Sybolic Destination.DESCRIPTION(Req’d by DSM/OS2 for APPC comm w/MVS)FQ_PARTNER_LU_NAME(PELNET01.DFDSMLU2) <== s_netid.partner_luMODE_NAME(OS2APPC ) <== logmodeTP_NAME(DFDSMLU2); <== TP Name

START_ATTACH_MANAGER;

Figure 39. Sample .ndf File for 3174 Gateway (Part 2 of 2)


CM/2 .ndf File for 3172 or 3745 Gateways

DEFINE_LOCAL_CP FQ_CP_NAME(DEIBMFD.F13833B0) <== c_netid.c_independentluDESCRIPTION(Local Node LU definition) <== Any ValueCP_ALIAS(F13833B0)NAU_ADDRESS(INDEPENDENT_LU)NODE_TYPE(EN)NODE_ID(X'05DF333B') <== vtam_xidHOST_FP_SUPPORT(NO);

DEFINE_LOGICAL_LINK LINK_NAME(HOST0001)DESCRIPTION(Link to adjacent SSCP-3745, partner node can be anythingFQ_ADJACENT_CP_NAME(DEIBMFD.BCTSO) <== c_netid.cp_nameADJACENT_NODE_TYPE(LEN)DLC_NAME(IBMTRNET)ADAPTER_NUMBER(0)DESTINATION_ADDRESS(X'400010000002') <== dest_addrCP_CP_SESSION_SUPPORT(NO)ACTIVATE_AT_STARTUP(NO)LIMITED_RESOURCE(USE_ADAPTER_DEFINITION)LINK_STATION_ROLE(USE_ADAPTER_DEFINITION)SOLICIT_SSCP_SESSION(YES)NODE_ID(X'05DF333B') <== vtam_xidEFFECTIVE_CAPACITY(USE_ADAPTER_DEFINITION)COST_PER_CONNECT_TIME(USE_ADAPTER_DEFINITION)COST_PER_BYTE(USE_ADAPTER_DEFINITION)SECURITY(USE_ADAPTER_DEFINITION)PROPAGATION_DELAY(USE_ADAPTER_DEFINITION)USER_DEFINED_1(USE_ADAPTER_DEFINITION)USER_DEFINED_2(USE_ADAPTER_DEFINITION)USER_DEFINED_3(USE_ADAPTER_DEFINITION);

DEFINE_PARTNER_LU FQ_PARTNER_LU_NAME(DEIBMA4.A4VTSM2) <== s_netid.partner_luDESCRIPTION(MVS TSM Server Partner LU on A4V network)PARTNER_LU_ALIAS(A4VTSM2) <== Partner LU AliasPARTNER_LU_UNINTERPRETED_NAME(A4VTSM2) <== partner_luMAX_MC_LL_SEND_SIZE(32767)CONV_SECURITY_VERIFICATION(NO)PARALLEL_SESSION_SUPPORT(YES);

Figure 40. Sample .ndf File for 3172 or 3745 Gateways (Part 1 of 2)


2.Server

andClien

tCommunicatio

ns

DEFINE_PARTNER_LU_LOCATION FQ_PARTNER_LU_NAME(DEIBMA4.A4VTSM2) <==s_netid.partner_luDESCRIPTION(MVS TSM Server Partner LU on A4V networkWILDCARD_ENTRY(NO)FQ_OWNING_CP_NAME(DEIBMFD.BCTSO) <== c_netid.cp_nameLOCAL_NODE_NN_SERVER(NO);

DEFINE_MODE MODE_NAME(TSMAPPC) <== logmodeDESCRIPTION(TIVSM mode for TSMAPPC, max RU size 2048)COS_NAME(#BATCH)DEFAULT_RU_SIZE(NO)MAX_RU_SIZE_UPPER_BOUND(4096)RECEIVE_PACING_WINDOW(7) <== CM/2 runs on an 80386 - use 7MAX_NEGOTIABLE_SESSION_LIMIT(16)PLU_MODE_SESSION_LIMIT(8)MIN_CONWINNERS_SOURCE(4);

DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES)DEFAULT_MODE_NAME(BLANK)MAX_MC_LL_SEND_SIZE(32767)DIRECTORY_FOR_INBOUND_ATTACHES(*)DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED)DEFAULT_TP_PROGRAM_TYPE(BACKGROUND)DEFAULT_TP_CONV_SECURITY_RQD(NO)MAX_HELD_ALERTS(10);

DEFINE_CPIC_SIDE_INFO SYMBOLIC_DESTINATION_NAME(MVSTIVSM) <== Symbolic Destination.DESCRIPTION(Side info for MVS TSM server on A4V network)PARTNER_LU_ALIAS(A4VTSM2) <== Partner LUMODE_NAME(#BATCH) <== logmodeTP_NAME(DSMSERV); <== TP Name

START_ATTACH_MANAGER;

Figure 40. Sample .ndf File for 3172 or 3745 Gateways (Part 2 of 2)


SNA Profile for AIX Clients

sna:;prof_name = “sna”;max_sessions = 200;max_conversations = 200;restart_action = once;rrm_enabled = no;dynamic_inbound_partner_lu_definitions_allowed = yes;standard_output_device = “/dev/console”;standard_error_device = “/var/sna/sna.stderr”;nmvt_action_when_no_nmvt_process = reject;comments = “”control_pt:;prof_name = “node_cp”;xid_node_id = 0x05df333D <== vtam_xid;network_name = “DEIBMFD” <== c_netid;control_pt_name_alias = “F13833D0”;control_pt_name = “F13833D0” <== c_independentlu;control_pt_node_type = appn_end_node;max_cached_trees = 500;max_nodes_in_topology_database = 500;route_addition_resistance = 128;comments = “”partner_lu6.2:;prof_name = “BCTSO” <== <adjacent cp_name>;fq_partner_lu_name = “DEIBMA4.A4VTSM2” <== s_netid.partner_lu;partner_lu_alias = “A4VTSM2” <== Partner LU Alias;session_security_supp = no;parallel_session_supp = yes;conversation_security_level = none;comments = “”partner_lu6.2_location:;prof_name = “BCTSO”;fq_partner_lu_name = “DEIBMA4.A4VTSM2” <== s_netid.partner_lu;fq_partner_owning_cp_name = “DEIBMFD.FDW” <== c netid<sscp_name>;local_node_is_network_server_for_len_node = no;fq_node_server_name = “”;comments = “”

Figure 41. Sample SNA Profile (Part 1 of 4)


2.Server

andClien

tCommunicatio

ns

side_info:;prof_name = “BCTSO” <== Symbolic Destination;local_lu_or_control_pt_alias = “F13833D0” <== Partner LU Alias;partner_lu_alias = “A4VTSM2”;fq_partner_lu_name = “”;mode_name = “TSMAPPC” <== logmode;remote_tp_name_in_hex = no;remote_tp_name = “ANYTHING” <== TP Name;comments = “”link_station_token_ring:prof_name = “BCTSO”use_control_pt_xid = yesxid_node_id = “*”sna_dlc_profile_name = “tok0.00001”stop_on_inactivity = notime_out_value = 0LU_registration_supported = noLU_registration_profile_name = “”link_tracing = notrace_format = longaccess_routing_type = link_addressremote_link_name = “”remote_link_address = 0x400010000002 <== dest_addrremote_sap = 0x04verify_adjacent_node = nonet_id_of_adjacent_node = “”cp_name_of_adjacent_node = “”xid_node_id_of_adjacent_node = “*”node_type_of_adjacent_node = learnsolicit_sscp_sessions = yescall_out_on_activation = yesactivate_link_during_system_init = yesactivate_link_on_demand = nocp_cp_sessions_supported = nocp_cp_session_support_required = noadjacent_node_is_preferred_server = noinitial_tg_number = 0restart_on_normal_deactivation = norestart_on_abnormal_deactivation = norestart_on_activation = no



TG_effective_capacity = 4300800TG_connect_cost_per_time = 0TG_cost_per_byte = 0TG_security = nonsecureTG_propagation_delay = lanTG_user_defined_1 = 128TG_user_defined_2 = 128TG_user_defined_3 = 128comments = “’sna_dlc_token_ring:

prof_name = “tok0.00001”datalink_device_name = “tok0”force_timeout = 120user_defined_max_i_field = nomax_i_field_length = 30729max_active_link_stations = 255num_reserved_inbound_activation = 8num_reserved_outbound_activation = 8transmit_window_count = 16dynamic_window_increment = 1retransmit_count = 8receive_window_count = 8priority = 0inact_timeout = 48response_timeout = 4acknowledgement_timeout = 1link_name = “F13833D0” <== c_independentlulocal_sap = 0x04retry_interval = 60retry_limit = 20dynamic_link_station_supported = notrace_base_listen_link_station = notrace_base_listen_link_station_format = shortdynamic_lnk_solicit_sscp_sessions = yesdynamic_lnk_cp_cp_sessions_supported = nodynamic_lnk_cp_cp_session_support_required = nodynamic_lnk_TG_effective_capacity = 4300800dynamic_lnk_TG_connect_cost_per_time = 0dynamic_lnk_TG_cost_per_byte = 0dynamic_lnk_TG_security = nonsecuredynamic_lnk_TG_propagation_delay = landynamic_lnk_TG_user_defined_1 = 128dynamic_lnk_TG_user_defined_2 = 128dynamic_lnk_TG_user_defined_3 = 128comments = “”


mode:prof_name = “TSMAPPC”mode_name = “TSMAPPC” <== logmodemax_sessions = 255min_conwinner_sessions = 8min_conloser_sessions = 8auto_activate_limit = 0max_adaptive_receive_pacing_window = 16receive_pacing_window = 7max_ru_size = 4096min_ru_size = 256class_of_service_name = “#BATCH”comments = “”



2.Server

andClien

tCommunicatio

ns

Customizing Your Tivoli Storage ManagerSystem

This chapter describes customizing Tivoli Storage Manager by doing the following:

¶ “Defining Storage Pool Volumes”

¶ “Increasing Database and Recovery Log Sizes” on page 84

¶ “Using Tape Devices with Tivoli Storage Manager” on page 85

¶ “Creating a New Policy” on page 88

¶ “Automating Client Operations” on page 92

¶ “Automating Administrative Commands” on page 94

The customization described here does not include all TSM functions. However, it doesprovide a flexible, powerful system that can meet most customers’ needs. If the server thatyou have just installed will be part of a network of Tivoli Storage Manager servers, yourcustomization tasks may be affected. For example, your server may receive configurationinformation from a TSM server that is designated as a configuration manager. Thisinformation could include objects such as administrator definitions, policy definitions, andserver definitions. On the other hand, your server may be the configuration manager, andyour definitions will be provided to a network of managed servers. In addition, you mayhave to define one or more other servers to your server. For details, see Administrator’sGuide.

The server must be running to perform the tasks described here. Start the server ifit is not running.

In the examples performed on the administrative Web interface, the first step for allprocedures is to expand Object view.

Defining Storage Pool VolumesBefore a client can back up, archive, or migrate files, you must define data sets as storagepool volumes. These are the data sets that you allocated and formatted when you ran theANRALLO1 or ANRALLO2 job (see “Allocating the Required Server Data Sets” onpage 5). Do the following to assign the data sets as volumes to the default storage pools:

3


3.Custo

mizin

gYo

urTivo

liStorag

eMan

ager

System

define volume backuppool tivsm.storage.pool001define volume archivepool tivsm.storage.pool002define volume spacemgpool tivsm.storage.pool003

OR

1. Expand Server Storage.

2. Select Storage Pools.

3. Select Disk Storage Pools.

4. Select Volumes.

5. Select Define Disk Volume.


Repeat these steps for each storage pool.

You can define additional storage pool volumes to TSM after you have allocated andformatted them with either ANRFMT or ANRFMT2.

Increasing Database and Recovery Log SizesWhen you installed TSM, you initialized disk volumes for the database and recovery log. Aspart of that process, TSM defines the first database volume and first recovery log volume. Atany time, you can increase the size of the database or recovery log by adding more volumes.

Before you define new volumes, allocate and format them using the ANRFMT job orthe ANRFMT2 job from the ASAMPLIB dataset. See “Allocating the Required ServerData Sets” on page 5 and Administrator’s Guide for details.

To increase the size of the database and recovery log, for example, VOLA and VOLB, doone of the following:

define dbvolume voladefine logvolume volb

extend db 13extend log 9

OR

Define and extend the database volume:

1. Expand Database.

2. Select Database Volumes.

3. From Operations, select Define Database Volume.



5. Return to Database and from Operations, select Extend.


Define and extend the recovery log volume:

1. Select Recovery Log.

2. Select Recovery Log Volumes.

3. Select Define Recovery Log Volumes.


5. Return to Recovery Log and select Extend.


Using Tape Devices with Tivoli Storage ManagerThis section shows you how to use tape devices with your TSM system. After adding thetape devices to TSM, you can migrate data from disk storage pools to tape storage pools.This section describes the following tasks:

¶ “Adding Tape Devices to Your Tivoli Storage Manager Environment” on page 86

¶ “Preparing Tape Volumes for Use” on page 87

¶ “Creating a New Policy” on page 88

¶ “Creating a Client Include-Exclude List” on page 91

¶ “Verifying the Tape Device Environment” on page 87

If you want to use a tape management system with TSM see the Administrator’s Guide fordetails.

Here are some concepts that can help you to set up your tape environment:

Storage pool migration

To prevent disk storage pools from becoming filled with client data, you can specify that client databe automatically migrated to the tape storage pool.

A disk’s high migration threshold (default value: 90%) determines when data is migrated. The lowmigration threshold (default value: 70%) determines when migration stops. Thus data migration fromthe default backup disk storage pool begins when the pool is 90% full and continues until it is at 70%full or less.

Another default is to cache data (leave the data on the storage pool) even after the data has beenmigrated. Cached data stays on disk for quick access until the space is needed for new data.

See Administrator’s Guide for details.Mount limit

Mount limit (the number of drives available in a device class) has a default value of 1. The mountlimit should be equal to the number of drives of the same type in that library.


3.Custo

mizin

gYo

urTivo

liStorag

eMan

ager

System

Here are some concepts that can help you to set up your tape environment:

Scratch volumes

A scratch volume is a volume that is available for use. The volume is labeled, is either blank orcontains no valid data, and is not defined to . You can specify the number of scratch volumes that canrequest for this pool (MAXSCRATCH parameter in the command or the Maximum scratch volumesfield in the GUI). If you do not specify a value, no scratch volumes can be requested, and you mustdefine each volume to be used.Collocation

Collocation is turned off by default. Once clients begin storing data in a storage pool with collocationoff, you cannot easily change the data in the storage pool so that it is collocated. To understand theadvantages and disadvantages of collocation, see the Administrator’s Guide.

Adding Tape Devices to Your Tivoli Storage Manager EnvironmentThe following scenario shows how to include two IBM 3490 tape devices into the TSMenvironment. You must assign a device class for the type of tape devices you have andassociate that device class with a storage pool:

1. Classify the devices by device type. It is helpful to choose a device class name thatidentifies the type of device for which it is intended (in this example, TAPECLASS).

define devclass tapeclass devtype=cartridge -format=3490e mountlimit=2

OR

a. Expand Device Classes.

b. Select CARTRIDGE Device Classes.

c. From Operations, select Define Device Class.

d. Enter the device class information and Finish.

2. Define a storage pool named TAPEPOOL for the device class.

define stgpool tapepool tapeclass -maxscratch=100 collocate=no

OR

a. Expand Storage Pools.

b. Select Sequential Access Storage Pools.

c. From Operations, select Define Sequential Access Storage Pool.

d. Enter the storage pool information and Finish.


Preparing Tape Volumes for UseAll tape volumes must have standard tape labels before TSM can use them. You can usetapes as scratch volumes, up to the number of scratch volumes you specified for the storagepool. Using scratch volumes allows TSM to acquire volumes as needed.

You can also use private volumes in a storage pool. You must define any private volumes toTSM, assigning each to a specific storage pool. However, if a storage pool contains onlyprivate volumes and runs out of them, storage operations to that pool stop until morevolumes are defined. Prepare tape volumes as follows:

1. Label your volumes with standard labels according to your local procedures.

2. Define any volumes that are to be used as private volumes. For example, define volumeDSM001, which has standard labels:

define volume tapepool dsm001

OR

a. Expand Storage Pools.

b. Select Sequential Access Storage Pools.

c. Select the storage pool you want.

d. Select Volumes.

e. Select Define Sequential Access Volume.

f. Enter the volume information and Finish.

Including Tape in the Server Storage HierarchyNow that TSM can use your tape devices, you can update your disk storage pools so thatclient data can be migrated to tape. This section describes how to change BACKUPPOOLand ARCHIVEPOOL so that data migrates to TAPEPOOL.

update stgpool backuppool nextstgpool=tapepoolupdate stgpool archivepool nextstgpool=tapepool

OR

1. Expand Storage Pools.

2. Select Sequential Access Storage Pools.

3. Select the pool to be updated.

4. Select Update Sequential Access Storage Pool.

5. Enter the storage pool information and Finish.

Verifying the Tape Device EnvironmentTo verify that the tape media have been integrated into your TSM system, migrate data froma disk storage pool. Migration from a storage pool requires tape mounts. The mount


3.Custo

mizin

gYo

urTivo

liStorag

eMan

ager

System

messages are directed to the console message queue and to any administrative client that hasbeen started with either the mount mode or console mode option.

Trigger migration from a disk storage pool (BACKUPPOOL, for example) by setting thehigh and low migration thresholds to 0:

update stgpool backuppool highmig=0 lowmig=0

After migration occurs, reset the thresholds to their original settings:

update stgpool backuppool highmig=90 lowmig=70

OR

To migrate data from a disk storage pool and, after migration occurs, to reset the thresholdsto their original settings, update the storage pool:

1. Expand Storage Pools.

2. Select Sequential Access Storage Pools.

3. Select the pool to be updated.

4. Select Update Sequential Access Storage Pool.

5. Enter the storage pool information and Finish.

Controlling when migration occurs

To migrate from a disk storage pool to a tape storage pool, devices must beallocated and tapes must be mounted. For these reasons, you may want to ensurethat migration occurs at a time that is best for your situation. You can control whenmigration occurs by leaving the high migration threshold set to 100 most of thetime, and lowering it when you want migration to occur.

In the preceding step, you lowered both migration thresholds to 0 to verify thatmigration occurred. You may not want to empty the disk storage pool by settingthe low migration threshold to 0 every time you want migration to occur. Normally,you may want to keep the low threshold at 40%, and vary the high threshold fromas high as 90% to as low as 50%. See Administrator’s Guide for details.

Creating a New PolicyThe TSM default policy specifies how TSM manages client files. For example, it specifiesthat TSM retains up to two backup versions of any file that exists on the client (see“Installation and Setup Results” on page x for details). Two versions may be enough formost clients. However, if some clients need the last ten versions to be kept, you can doeither of the following:

¶ Create a new policy domain and assign these clients to that domain (described in thissection).

¶ Create a new management class within the default policy domain. Then theinclude-exclude lists for all the affected clients must be updated.


Storing Directly to Tape

Under the default policy, client files are stored directly to disk. You can also definepolicies for storing client files directly to tape. In a copy group, simply name a tapepool as the destination. Note, however, that if you store directly to tape, the numberof available tape drives limits the number of client nodes that can store data at thesame time.

To create a new policy, you can start by copying the policy domain, STANDARD. Thisoperation also copies the associated policy set, management class, and copy groups. Youthen assign clients to the new domain.

1. Copy the default policy domain, STANDARD, to the new policy domain,NEWDOMAIN.

copy domain standard newdomain

OR

a. Select Policy Domains.

b. Select STANDARD domain.

c. From Operations, select Copy Policy Domain.

d. Enter the domain information and Finish.

This operation copies the policy domain, and all associated policy sets, managementclasses, and copy groups. Within the policy domain named NEWDOMAIN and thepolicy set named STANDARD, you have:¶ Management class named STANDARD¶ Backup copy group named STANDARD¶ Archive copy group named STANDARD

For our example, you update only the backup copy group.

2. Update the backup copy group by specifying that ten versions of backed up files are tobe kept.

update copygroup newdomain standard standard standard -type=backup verexists=10

OR

a. Expand Policy Domains, Policy Sets, and then Management Classes.

b. Select Backup Copy Groups.

c. Select the NEWDOMAIN STANDARD STANDARD STANDARD copy group.

d. From Operations, select Update Copy Group.


3.Custo

mizin

gYo

urTivo

liStorag

eMan

ager

System

e. Enter the copy group information and Finish.

3. Validate and activate the STANDARD policy set in NEWDOMAIN.

validate policyset newdomain standardactivate policyset newdomain standard

OR

a. Expand Policy Domains and then select Policy Sets.

b. Select NEWDOMAIN STANDARD policy set.

c. From Operations, select Validate Policy Set and then Finish.

d. From Operations, select Activate Policy Set and then Finish.

The following conditions result in warning messages during validation:

¶ A destination storage pool is not a defined storage pool.

¶ The default management class does not contain a backup or archive copygroup.

¶ The current ACTIVE policy set names a management class that is not definedin the policy set being validated.

¶ The current ACTIVE policy set contains copy groups that are not defined in thenamed policy set.

¶ A management class specifies that a backup version must exist before a file canbe migrated from a client node, but the management class does not contain abackup copy group.

4. Assign client nodes to the NEWDOMAIN policy domain by either updating existingclient nodes or registering new nodes. For example, to update client node mercedes, doeither of the following:

update node mercedes domain=newdomain

OR

a. Expand Clients.

b. Select Client Nodes.

c. Select the desired node.

d. From Operations, select Update this Node.

e. Enter the node information and Finish.

TSM will now keep up to ten versions of backed up files for client node mercedesbecause it is assigned to the NEWDOMAIN policy domain.


Invoking Expiration ProcessingExpired files are not deleted from server storage until expiration processing occurs. You caninvoke expiration processing in a number of ways:

¶ The expiration interval server option can specify that processing be invoked at a setinterval from the time the server is started. The default is a 24 hour interval.

¶ You can issue the EXPIRE INVENTORY command manually whenever you wish (seethe following example).

¶ You can schedule the EXPIRE INVENTORY command to be issued regularly at aspecific time (see “Automating Administrative Commands” on page 94). If you scheduleexpiration processing, set the expiration interval server option to 0.

expire inventory quiet=yes wait=no

OR

1. Select Server.

2. Select Server Status.

3. From Operations, select Expire Inventory.

4. Select any desired options and Finish.

Creating a Client Include-Exclude ListAny client can exclude some files from some policy operations and include other files inother operations. This is done with statements in an include-exclude list or, on UNIX clients,in an include-exclude file. For example, an include-exclude file should exclude system filesthat, if recovered, could corrupt the operating system. TSM server and client directoriesshould also be excluded. See the appropriate TSM client user’s guide for details.

You can define include-exclude statements for your installation. Users can add thesestatements in their client options file (dsm.opt). You can also enter the statements in a set ofoptions and assign that set to client nodes when you register or update the nodes. For detailsabout the DEFINE CLOPTSET and DEFINE CLIENTOPT commands, see Administrator’sGuide and Administrator’s Reference.

Here are a few examples of include-exclude statements:

¶ A user wants all *.sct and *.drw files in the d:\eng\spec\ directory included for backupbut all other files in that directory excluded. The user adds the following include-excludestatements:

exclude d:\eng\spec\*.*include d:\eng\spec\*.drwinclude d:\eng\spec\*.sct


3.Custo

mizin

gYo

urTivo

liStorag

eMan

ager

System

TSM reads the statements from the bottom up until a match is found. In thepreceding example, no match would be found on the include statements for the filed:\eng\spec\proto.obj. TSM reads the exclude statement, finds a match, andexcludes the file.

¶ For a file or group of files, the user can also override the default management class:

exclude d:\eng\spec\*.*include d:\eng\spec\*.drw monthlyinclude d:\eng\spec\*.sct

In this example,

v *.sct files are bound to the default management class.

v *.drw files are bound to the management class monthly.

v All other files in the spec directory are excluded from backup or archive.

Automating Client OperationsYou can schedule most client operations, such as backup, to begin automatically. You canschedule the following on most clients:¶ TSM backup, archive, restore, and retrieve operations¶ Operating system commands¶ Macros (files that can contain operating system and TSM commands)

This section guides you through scheduling client backups for three registered client nodesassigned to the STANDARD policy domain: bill, mark, and mercedes.

1. Schedule an incremental backup and associate the schedule with the clients. Theschedule, named DAILY_INCR, is for the TSM default policy domain, namedSTANDARD. The default specifies backup to the disk storage pool BACKUPPOOL.This schedule calls for a schedule window that:¶ Begins on the date the schedule is defined (the default) at 11:00 p.m.¶ Lasts for 1 hour (the default)¶ Is repeated daily (the default)¶ Stays in effect indefinitely (the default)

define schedule standard daily_incr action=incremental -starttime=23:00

define association standard daily_incr bill,mark,mercedes

OR

a. Expand Automation.

b. Select Client Schedules.

c. From Operations, select Define Schedule.

d. Enter the schedule information and Finish.


e. Return to Client Schedules.

f. Select the desired schedule.

g. From Operations, select Define Associations.

h. Enter the association information and Finish.

2. Start the client scheduler. For the schedules to become active for a workstation, a usermust start the scheduler from the node.

dsmc schedule

To help ensure that the scheduler is running on the clients, clients can include theSCHEDULE command in their system start-up commands.

The include-exclude list (file on UNIX clients) on each client also affects whichfiles are backed up or archived by the two schedules defined in the preceding steps.For example, if a file is excluded from backup with an EXCLUDE statement, thefile will not be backed up when the DAILY_INCR schedule runs.

3. Because the DAILY_INCR schedule is to run daily, you can verify that it is working asit should on the day after you define the schedule and associate it with clients. If theschedule has run successfully, the status will be Completed.

query event standard daily_incr begindate=today-1

OR

a. Expand Automation.

b. Select Client Schedules.

c. Select the desired schedule name.

d. From Operations, select Query Client Events.

e. Enter the required information and Finish.

You can limit the query of events to display only schedules that did not run asexpected. For example, you can use the following command daily to see whichclients did not run the DAILY_INCR schedule the previous day:

query event standard daily_incr begindate=today-1 -exceptionsonly=yes

Schedules that did not complete successfully have a status of Failed, Missed, orSevered.

4. Check the results of the schedule DAILY_INCR on one of the clients that was associatedwith that schedule. For most clients, including OS/2 clients, information about whathappens when a schedule runs is stored in the file dsmsched.log.


3.Custo

mizin

gYo

urTivo

liStorag

eMan

ager

System

Automating Administrative CommandsYou can automate TSM administrative tasks by scheduling administrative commands. Forexample, you can automate commands that need to be run regularly or that requiresignificant processing or other system resources. In this section, you define a schedule to runexpiration processing.

1. Define a schedule named EXPPROC that invokes expiration processing every night at2:00 a.m.

This schedule calls for a schedule window that:¶ Begins on the date the schedule is defined (the default) at 2:00 a.m.¶ Lasts for 1 hour (the default)¶ Is repeated every day¶ Takes effect immediately¶ Stays in effect indefinitely (the default)

define schedule expproc type=administrative -cmd='expire inventory' active=yes starttime=02:00

OR

a. Select Automation.

b. Select Administrative Command Schedules.

c. From Operations, select Define Schedule.

d. Enter the schedule information and Finish.

2. Because the EXPPROC schedule is to run daily, you can verify that the automation isworking as it should on the day after you define the schedule. If the schedule has runsuccessfully, the status will be Completed.

query event expproc type=administrative begindate=today-1

OR

a. Select Automation.

b. Expand Administrative Command Schedules.

c. Select Query Administrative Events.

d. Enter the required information and Finish.

Protecting Tivoli Storage Manager and Client DataThe database, recovery log, and storage pools are critical to the operation of the server. Ifthe database or recovery log is unusable, the entire server is unavailable. If a database is lostand cannot be recovered, the backup, archive, and space-managed data for that server is lost.If a storage pool volume is lost and cannot be recovered, the data on the volume is also lost.


Tivoli Storage Manager provides a number of ways to protect your data, including backingup your storage pools and database. For example, you can define schedules so that thefollowing operations occur:

¶ After the initial full backup of your storage pools, incremental storage pool backups aredone nightly.

¶ Full database backups are done weekly.

¶ Incremental database backups are done nightly.

In addition, Tivoli Disaster Recovery Manager (DRM), an optional feature of TSM, canassist you in many of the tasks associated with protecting and recovering your data. See theAdministrator’s Guide for details.


3.Custo

mizin

gYo

urTivo

liStorag

eMan

ager

System

Tivoli Storage Manager Concepts

This appendix describes basic Tivoli Storage Manager concepts, such as customizing yourstorage media and automating operations. Because Tivoli Storage Manager manages yourstorage media based on a set of policies, you can customize it for different data types anduser groups. You can also automate some operations like client backups and server databasebackups. Tivoli Storage Manager can increase your productivity and eliminate error-prone,repetitive tasks.

System-Managed StorageTivoli Storage Manager includes the following components:

ServerProvides storage management for client workstations and maintains a database ofinformation.

You can set up servers in a network to allow you to manage them centrally and tobalance storage resources.

Server StorageContains files that are backed up, archived, and migrated from workstations. Serverstorage consists of pools of random and sequential access media.

Administrative clientProvides an interface to the server.

Backup-archive clientProvides backup and archive services to workstations.

Tivoli Space Manager (HSM) clientProvides space management services for workstations on some platforms.

Application ClientsProvides backup-restore for selected databases. Application clients are available forSQL, Exchange, Oracle, and Lotus Domino databases.

Server Storage MigrationTo use your storage resources efficiently, you can arrange server storage into a hierarchy.You can then define when data is migrated from faster, more expensive storage pools (disk,for example) to slower, less expensive storage pools (tape, for example). You can also storedata on another TSM system See Administrator’s Guide for details.

Tivoli Storage Manager PolicyTSM lets users on workstations do the following tasks:

A


A.Tivo

liStorag

eMan

ager

Concep

ts

BackupCopy files to server storage to prevent loss of data. Copies of multiple versions of afile can be stored.

ArchivingCopy files to server storage for long-term storage.

Hierarchical Storage ManagementFree storage space by moving data to server storage. The original file is replacedwith a pointer to the location of the original in server storage. This function is alsocalled space management or migration.

Administrators define policy in the following policy objects: policy domains, policy sets,management classes, and backup and archive copy groups.

The following figure shows how TSM stores client data.

�1� A client backs up, archives, or migrates a file. The file is bound to either the defaultmanagement class or a management class specified in the client’s include-exclude list.

�2� If, according to the management class, the file is eligible for backup, archive, orspace management, the client sends the file and file information to the server.

�3� The server checks the management class or copy group to determine where in serverstorage to store the file initially.

Figure 42. How TSM Controls Backup, Archive, and Space Management


If enough space is not available in the initial storage pool, the server examines the nextpool in the hierarchy and places the file there if space is available.

�4� The server stores the file in the appropriate storage pool and stores informationabout the file in the database.

When files in server storage are migrated from one pool to another, the server updatesthe file information in the database.

ExpirationA file remains in server storage until it expires and expiration processing occurs. A fileexpires based on criteria set in TSM policy. For example, backup policy may specify that upto two backup versions of a file can be kept in server storage. If a third backup version of afile is created, the oldest version in server storage expires. Backup policy may also specifythat if a file is deleted from a client file system, it expires after 60 days.

During expiration processing, TSM deletes from the database those files that have expired.

Storage Devices and MediaTSM represents physical storage devices and media with the following administrator-definedobjects:

Device ClassEach device is associated with a device class that specifies the device type and howthe device manages its media. TSM has a predefined device class (DISK) forrandom access devices.

Storage Pools and VolumesA storage pool is a named collection of storage volumes of the same media type. Astorage pool is associated with a device class. For example, a 3490 tape storage poolcontains only 3490 tape volumes. A storage pool volume is associated with aspecific storage pool.

Figure 43 on page 100 summarizes the relationships among the physical device environment,TSM storage objects, and TSM clients. The numbers below correspond to the numbers in thefigure.

�1� When clients are registered, they are associated with a policy domain. The otherTSM policy objects are within the policy domain.

�2�, �3�When a file is backed up, archived, or migrated from a client, it is bound to amanagement class. A management class and the backup and archive copy groupswithin it specify where files are stored and how they are managed when they arebacked up, archived, or migrated from a client (space-managed files).

�4�, �5�Storage pools are the destinations for backed up, archived, or space-managed files.Copy groups specify storage pools for backed up or archived files. Managementclasses specify storage pools for space-managed files.

Storage pools are mapped to device classes, which represent devices. The storagepool contains volumes as indicated in the device type associated with the deviceclass. For example, a storage pool that is mapped to a device class with a devicetype of CARTRIDGE contains only cartridge tapes.


A.Tivo

liStorag

eMan

ager

Concep

ts

All devices require a device class that specifies a device type.

�6� Files that are initially stored on disk storage pools can migrate to tape storage poolsif the pools are set up in a storage hierarchy.

Automating Client OperationsYou can automate client operations, such as backup and archive. Figure 44 on page 101shows the TSM objects that may be involved in automated client operations. They are listedbelow:

Figure 43. Putting it All Together


Include-exclude criteria on each TSM clientDetermines which files are backed up, archived, or space-managed, and binds filesto management classes

Management classDetermines where client files are stored and how they are managed

ScheduleDetermines when client operations such as backup occur

Association defined between client and scheduleDetermines which schedules are run for a client

The client can specify a management class for a file or set of files, or can use the defaultmanagement class for the policy domain. The client specifies a management class by usingan INCLUDE option in the client’s include-exclude list or file. See �A� in Figure 44.

Figure 44. Automating Client Operations


A.Tivo

liStorag

eMan

ager

Concep

ts

The management class contains information that determines how TSM handles files thatclients backup, archive, or migrate. For example, the management class contains the backupcopy group and the archive copy group. Each copy group points to a destination, which is astorage pool where files are stored when they are backed up or archived. See �E� inFigure 44 on page 101.

Clients are assigned to a policy domain when they are registered. Schedules that canautomate client operations are also associated with a policy domain. See �C� in Figure 44 onpage 101. To automate client operations, you define schedules for a domain. You then defineassociations between schedules and clients in the same domain. See �B� in Figure 44 onpage 101.

For a schedule to work on a particular client, the client machine must be turned on and theclient scheduler must be running.

The scheduled client operations are called events, and information about events are stored inthe TSM database. See �D� in Figure 44 on page 101. For example, you can query the serverto determine which scheduled events completed successfully and which failed.

Working with a Network of Tivoli Storage Manager ServersTo store data from clients more efficiently, you may find that having Tivoli Storage Managerservers located close to your clients is the best way to manage network bandwidthlimitations. As a result, you may have servers at many locations. TSM provides functions tohelp you configure, manage, and monitor the servers connected to a network consistentlyand efficiently.

TSM provides a number of functions to help you manage a network of servers. You can:

¶ Maintain and distribute server configuration information such as policy from a singleconfiguration manager to many managed servers

¶ Monitor many servers and clients from a single server

¶ Issue commands on one server to other servers and groups of servers

¶ Use the storage on one server for data from another server

Use of these functions requires licensing for the optional features, Enterprise Administration,Network, and Server-to-server virtual volumes.


Using Administrative Interfaces

This appendix contains the following sections that describe how to use the Tivoli StorageManager administrative interfaces:¶ “Using the Administrative Web Interface”¶ “Using the Administrative Client Command-Line Interface” on page 108

Using the Administrative Web InterfaceYou can issue Tivoli Storage Manager commands, view server administration data, andperform all administrative tasks directly from the Web interface. For details about startingthe Web interface, see “Starting an Administrative Client” on page 13. To end a Webinterface session, select Log Off, from the Options pull down menu.

Note: If you want to use the administrative Web interface, your browser must have Java1.1.6 support. We recommend that you use Netscape 4.06 or higher or InternetExplorer 4.01 or higher.

Tivoli Storage Manager Server Administration has four major views:

¶ “Operation View” on page 104

¶ “Network View” on page 106

¶ “Configuration View” on page 106

¶ “Object View” on page 107

The following sections contain details about each view.

Figure 45 on page 104 shows the four major views of the Web interface with the Operationview partially expanded.

B


B.Usin

gAdministrative

Interfaces

By default, the time-out interval for an administrative Web interface session is 10minutes. After the interval elapses, you must reenter your administrator name andpassword. To change the interval, do the following from the Web interface:

1. Expand the Operation View.

2. Expand Manage Security.

3. Click Set web authentication time out.

Specify an interval from 0 to 9999 minutes. A value of 0 means that the sessionis never timed out.

Operation View

Work withadministrators

Add, update, and remove an administratorGrant and revoke administrative privilegesGrant or revoke administrator privileges

Work with clientnodes

Add, update, remove a client node

Automate clientoperations

Define, update, delete a client scheduleAssociate, client nodes with a scheduleRemove client nodes from a scheduleReport on scheduled eventsTune scheduling settings

Figure 45. Administrative Web Interface Tree


|

||

Manage the databaseand recovery log

View database detailsAdd a volume to the databaseExtend, reduce database sizeRemove a volume from the databaseAdd a copy volume to the databaseWork with the database space triggerWork with the database backup triggerBack up a database

View recovery log detailsAdd, remove a volume to the recovery logExtend, reduce recovery log sizeAdd a copy volume to the recovery logWork with the recovery log space triggerSet the recovery log mode

Manage serverstorage

Query storage poolsQuery storage pool volumesWork with disk storage pools:

View disk storage poolsDefine, update, delete a disk storage poolBack up, restore a storage poolDefine, update, delete a disk storage pool volumeMove data on a storage pool volumeVary a disk volume online, offlineRestore a disk storage pool volume

Work with sequential access storage pools:View all sequential storage poolsDefine, update, delete a sequential access storage poolBack Up, restore a sequential access storage poolDefine, update, delete a sequential access volumeMove data on a storage pool volumeRestore sequential access storage pool volume

Work with copy storage pools:View all copy storage poolsDefine, update, delete a copy storage poolDefine, update, delete a sequential access volumeMove data on a storage pool volume

Automate operations Define, update, activate, deactivate, delete an administrative command scheduleView events for administrative schedulesDefine, update, rename, copy, delete, run a command script

Monitor operations Query the server activity logQuery client schedule event recordsView database detailsView commands issued by administratorsView sessions currently accessing the serverView processes running on the server

Manage security Set server authenticationOpen registration settingsEnable client sessionsDisable client sessionsSet password expiration, invalid sign-on limit, minimum password lengthSet web authentication time outLock, unlock a node from server accessLock, unlock an administrator


B.Usin

gAdministrative

Interfaces

Performance tuning Tune client files sent by transactionTune files, bytes moved by transactionTune the database buffer pool

Central Configuration Define/update settings for this serverConfiguration manager operationsEstablish this server as a configuration managerWork with configuration profilesNotify subscribers of changes

Managed serveroperations

Define the configuration manager serverSet configuration refresh frequencyView profiles available for subscriptionPrepare to subscribe to server informationPrepare to subscribe to policy informationWork with profile subscriptions

Network View

Other servers Define, update, delete, export, import other servers

Client Nodes Register, update, remove, export, import client nodes

Server groups Define, delete, update, rename server groupsDefine, delete, move server group membersRoute commands to multiple servers

Route a command tomultiple servers

Route commands to multiple servers

Configuration View

Define/update settingsfor this server

Define and update server settings (for example, name, password, address)

Configurationmanager operations

Establish this server as a configuration managerWork with configuration profilesNotify subscribers of changes

Managed serveroperations

Define the configuration manager serverSet configuration refresh frequencyView profiles available for subscriptionPrepare to subscribe to server informationPrepare to subscribe to policy informationWork with profile subscriptions

Configuration Objects Configuration settingsConfiguration profilesManaged administratorsManaged policy domainsManaged command schedulesManaged scriptsManaged option setsManaged server definitionsManaged server groupsSubscribersProfile subscriptions


Object View

Administrators Register, update, remove, rename, export, import, lock, unlock administratorsGrant, revoke administrator authoritiesGrant, revoke client authorities

Clients Client NodesFile SpacesBackup SetsClient Option SetsClient OptionsFile SpacesBackup Sets

Server Server StatusServer OptionsLicense InformationActivity LogProcessesSessionsRestartable Restore SessionsVolume HistoryQuery, backup, delete, update volume historyOther ServersServer GroupsServer Group Members

Database Database VolumesBackup TriggerDatabase Space Trigger

Recovery Log Recovery Log VolumesRecovery Log Space Trigger

Automation Server Command ScriptsAdministrative command schedulesQuery administrative eventsDelete eventsClient schedulesAssociationsQuery Client EventsDelete eventsImmediate Actions SchedulesQuery Client EventsDelete events

Policy Domains Policy SetsManagement ClassesBackup Copy GroupsArchive Copy GroupsClient NodesFile SpacesBackup SetsClient schedulesAssociationsQuery Client EventsDelete events


B.Usin

gAdministrative

Interfaces

Server Storage Storage PoolsDisk storage poolsVolumesSequential Access Storage PoolsVolumesCopy Storage PoolsVolumesQuery storage poolsQuery storage pool volumesDevice ClassesLibraries and Drives

Disaster RecoveryManager

DRM StatusDRM MachineDRM MachineDRM Machine Node AssociationDRM Recovery MediaDRM Recovery Media Machine AssociationDRM Offsite Recovery MediaDRM Recovery Plan FileCreate, query recovery plan files

Storage Agents Define, update, delete drive mappings

Using the Administrative Client Command-Line InterfaceThe administrative client command-line interface lets administrators control and monitor theserver through administrative commands. For more information on installing and using thecommand-line interface, see Administrator’s Reference.

Using Interactive ModeTo enter a series of administrative commands, start the administrative client in interactivemode by entering:

dsmadmc

You are then prompted to enter your user ID and password. If you do not want to beprompted for that information, you can enter your user ID and password with theDSMADMC command by using the -ID and -PASSWORD options. For example, enter:

dsmadmc -id=smith -password=secret

To end an administrative client session in interactive mode, use the QUIT command:

quit


Setting Up the Secure Web AdministratorProxy

The Tivoli Storage Manager Secure Web Administrator Proxy provides a secure method forthe TSM administrative Web interface to retrieve Web pages without affecting theperformance of the server. A Web proxy on a separate Web server machine, not the TivoliStorage Manager server, fills requests from the administrative Web interface for images andHTML pages. A single Web server can handle requests for multiple Tivoli Storage Managerservers on different platforms as shown in Figure 46.

In a typical Web proxy setup, you would perform the following tasks:

1. Install a Web server. The Web server can be on the following platforms: AIX, HP-UX,Sun Solaris, or Windows NT/2000. The Web server can provide services to TivoliStorage Manager servers on AIX, HP-UX, Sun Solaris, Windows NT/2000, and MVS.

Note: You should not install the Web server and Tivoli Storage Manager server on thesame machine. To do so would be to lose the performance advantage of using theWeb proxy.

2. Install the Web proxy and help files (GIF images and HTML files).

Figure 46. Tivoli Storage Manager and the Web Proxy

C


C.Settin

gUptheSecu

reWeb

Administrato

rProxy

3. Specify a URL that includes the Common Gateway Interface (CGI) directory for yourWeb server to access the administrative Web interface.

The Web proxy connects to Tivoli Storage Manager as a client, secures the connection, andretrieves Web pages or submits forms. The TSM server responds with the requested HTMLpages and redirects the URLs in the page to the Web proxy. When the Web proxy receivesthe response, it passes the information to the Web server. The Web server’s Secure SocketLayer (SSL) package encrypts the information and returns it to the Web browser.

PrerequisitesTo install, configure, and use the Web proxy, you need the following:

¶ A Web server with the following:

v At least 20MB of space to install the base package and the English-language versionof the Web proxy help files. If you install other languages, you will need more space.

Note: The setup and configuration wizard does not check for available disk space.

v Secure socket layer (SSL) set up.

v Support for Common Gateway Interface (CGI) 1.0 or later.

v Support for Java Development Toolkit (JDK) or Java Runtime Environment (JRE)1.1.6 or later. To get JDK or JRE, go to http://www.javasoft.com.

¶ A registered Tivoli Storage Manager administrator that has no authority.

¶ The communication methods set to TCP/IP and HTTP in the Tivoli Storage Managerserver options file.

Note: The HTTPS communication method, which was required for SSL support underADSM Version 3, is not required for the Web proxy and is not supported byTivoli Storage Manager.

Installing the Secure Web Administrator ProxyThe Web proxy files are in the swap directory on a separate CD-ROM, named Tivoli StorageManager Secure Web Administrator Proxy. This CD-ROM is shipped with Tivoli StorageManager. The CD-ROM also includes HTML versions of all Tivoli Storage Manager serverand client publications in a self-extracting zip file.

Follow this procedure to install and configure the Web proxy:

1. Set a case-sensitive environment variable that is named JAVA_HOME to point to thebase directory of your Java installation. For example

¶ On Windows NT or 2000:set JAVA_HOME=c:\jdk116

¶ On UNIX:export JAVA_HOME=/usr/jdk_base

2. If you are getting the Web proxy files from the FTP site, download them into anydirectory on your Web server.

3. Change directories to the location of the files.

4. Click on the Setup file or enter Setup from a command line.


http://www.javasoft.com

5. When the wizard begins, simply enter the information as requested:

¶ You need to know the path to your cgi-bin directory and html directory for your Webserver. For example, the root directory of the Web server is e:\web and contains twodirectories cgi-bin and html. When the wizard prompts you for directory names, entere:\web\cgi-bin and e:\web\html.

Note: The cgi-bin and html directories can be mapped to other locations by usingsymbolic links. The Web proxy will resolve the symbolic links.

¶ You will be asked for the ID and password of a Tivoli Storage Manageradministrator that is dedicated to the Web proxy. For security reasons, you shouldnot grant this administrator any authority. You can register this administrator beforeor after you configure the Web proxy.

¶ If the Web proxy will be serving only one Tivoli Storage Manager server, werecommend that you specify as a default the TCP/IP address and port number of thatserver. If the Web proxy will serve an Enterprise Administration server network,consider specifying the TCP/IP address and port number of the configurationmanager as the default.

Configuring the Secure Web Administrator ProxyAfter you have installed the Web proxy, do the following from each Tivoli Storage Managerserver to be connected to the Web server:

1. Ensure that the administrator ID and password that you specified in the wizard (see step5 on page 111) is registered with the Tivoli Storage Manager server. For example, toregister administrator PROXY with the password of PROXY, do the following:

register admin proxy proxy

Note: Do not grant any authority to the administrator. If you do, the security of yourTivoli Storage Manager system could be compromised.

2. Set the high level and low level addresses of the Tivoli Storage Manager server. Forexample, to set the high level address to TSM.TUCSON.XYZ.COM and the low leveladdress to 1500, do the following:

set serverhladdress tsm.tucson.xyz.comset serverlladdress 1500

3. Invoke the proxy by entering the URL that you specified to the wizard (see step 5 onpage 111). For example:http://web/cgi-bin/dsmproxy

If you have set the high and low level server addresses (see 2 on page 111), the loginscreen of the administrative Web interface is displayed. If you have not specified theaddresses, a form is displayed asking for a location.


C.Settin

gUptheSecu

reWeb

Administrato

rProxy

Uninstalling the Secure Web Administrator ProxyThe Web proxy installation puts the uninstall wizard in the same directory as the supportfile. These support files are located in your HTML directory in the tivoli/tsm/swap/ directory.For example, if your Web server is located at e:\www\html, the uninstall wizard will belocated in e:\www\html\tivoli\tsm\swap. To start the uninstall wizard, enter the followingcase-sensitive command:Uninstall

If you issue this command from the tivoli/tsm/swap/ directory, the wizard begins removingthe files. If you issue this command from any other directory, the wizard prompts you forthe location of your HTML directory. The wizard then determines what files were installedand how the Web proxy should be removed.

Troubleshooting the Secure Web Administrator Proxy¶ Broken images appear, or requests for help files return a page that states that the

page was not found.

1. Check the permission of the files. The default permission on UNIX is 644, whichgives to the owner read-write authority and to all others read-only authority.

2. Check the Web server error log and verify that the file location is correct. If the fileis not at that location, consider adding an Alias to your Web server configurationfile. For example, on the Apache Web server the tivoli/tsm/swap/ directory is in/www/tivoli/tsm/swap/. You could fix the problem by adding the following line tohttpd.conf:Alias /StorageFiles "/www/StorageFiles"

¶ An initial request returns two errors stating that the Web proxy had an errorwhile connecting to xxx: On your Tivoli Storage Manager console set the server highlevel and low level addresses. See step 2 on page 111.

¶ The Web proxy states that the password or ID is invalid: Verify that the Web proxyadministrator’s ID and password have been set on the server. You can update thepassword on the Web proxy using the ?configure option. To use this option, append?configure to the end of the dsmproxy URL. For example:http://webserver.tucson.ibm.com/cgi-bin/dsmproxy?configure

¶ ?configure or the Web administrative intertface links do not work: Set the proxy’sCGI URL to your Web server’s CGI URL. For example:dsmproxy -cgiURL=http://webserver.tucson.ibm.com/cgi-bin

¶ To get to a server other than the default server: Append ?jump to the URL. Forexample:http://webserver.tucson.ibm.com/cgi-bin/dsmproxy?jump

¶ The Web proxy states that the administrator ID is locked: Unlock the administrator’sID using the UNLOCK ADMIN command.

¶ The Web proxy reports an internal error: To turn on tracing on the Web proxy, doone of the following:

v Append the FORCETRACE option to the Web request. For example, here is asample Web request:http://webserver.tucson.ibm.com/cgi-bin/dsmproxy?SERVER=tsm:1500&URL=1500


To turn tracing on for this request enter FORCETRACE before the server:http://webserver.tucson.ibm.com/cgi-bin/dsmproxy?FORCETRACE&SERVER=tsm:1500&URL=1500

The trace information will be placed into a file named proxytrace.txt, which islocated in cgi-bin directory of the Web server.

v From the command line, issue the following command in the Web server cgi-bindirectory where the dsmproxy was installed:dsmproxy -trace=proxytrc.txt

The proxy would then append trace information to the proxytrc.txt file. The trace filename can be any name you choose.

¶ ?configure reports an error when updating the configuration through the Web: Thisproblem typically occurs on UNIX systems due to file permission errors. On UNIX ,update the permissions of the file, /etc/dsmproxy.cfg. On Windows NT or 2000, theoptions are stored in the registry.


C.Settin

gUptheSecu

reWeb

Administrato

rProxy

Tape Processing Considerations

This chapter contains Product-sensitive Programming Interface and Associated GuidanceInformation.

This chapter provides information about setting Tivoli Storage Manager to use scratch tapesfrom the scratch pool controlled by your tape management system. Tape managementsystems vary, but you should use the same procedure for all:

1. Define Tivoli Storage Manager to the tape management system as an external datamanager, if applicable.

2. Specify to the tape management system that a TSM volume must be permanentlyretained.

3. Set up tape installation-wide exits

Here is a typical scenario when TSM requires a new scratch volume and requests a privatemount:

1. The tape management system can then give TSM a volume from the scratch pool.However, in most installations, the operator selects the scratch volume from a listprovided by the tape management system.

2. The tape management system verifies that the volume mounted is a scratch volume.

3. Tivoli Storage Manager uses the volser of this tape to define the volume to the storagepool.

4. The tape label is rewritten with the expiration date from the device class (if specified)and the data set name.

5. When the tape volume becomes empty, usually due to reclamation, it is deleted fromTSM. During the deletion process, the tape deletion exit is called and notifies the tapemanagement system that it can return the tape to the scratch pool.

Defining Tivoli Storage Manager to Your Tape Management SystemIf you are using the IBM DFSMSrmm™ or DFRMM tape management system products, youdo not have to define Tivoli Storage Manager to either of them. The Removable MediaManager supports all tape data sets, including those created by Tivoli Storage Manager andDFSMShsm™.

If you are using a different tape management system product, refer to the productdocumentation. Defining TSM to tape management systems varies by product.

D


D.Tap

eProcessin

gConsid

erations

If your tape management system uses program names to identify External Data Managers,the TSM program name is ANRSERV.

Specifying Permanent Tape RetentionYou might need to tell your tape management system that a volume needs to be permanentlyretained.

If you are using IBM’s DFSMSrmm or DFRMM tape management system products, youshould define policies (vital record specifications) to cover the TSM tape data sets. A singlepolicy specifying the TSM high level qualifier includes all TSM tape data sets.

You can retain all DFSMShsm tapes that require no movement, with the exception of tapeswritten by ABARS, by specifying the RMM TSO subcommands shown in followingexample:

RMM ADDVRS DSNAME('mprefix.**') COUNT(99999) OWNER(owner)RMM ADDVRS DSNAME('bprefix.**') COUNT(99999) OWNER(owner)RMM ADDVRS DSNAME('authid.**') COUNT(99999) OWNER(owner)

where:

mprefixSpecifies the DFSMShsm-defined migrated data set prefix.

bprefixSpecifies the DFSMShsm-defined backup and dump data set prefix.

authidSpecifies the DFSMShsm prefix used for control data set backups.

COUNT(99999)Specifies to retain all data sets that match the filter mask.

owner Specifies the user ID of the individual responsible for these definitions.

For more information on defining policies, see DFSMS/MVS DFSMSrmm Implementationand Customization Guide. For more information on vital record specifications, seeDFSMSrmm Guide and Reference.

If you are using a different tape management system, one of the most commonly used waysto specify permanent tape retention is by setting up the expiration date in the device classdefinition within TSM. Be aware of the following when setting up the expiration date:

¶ The storage group to which your tape volumes belong must have this device class.

¶ An expiration date of 2099365 is most often used to indicate permanent retention.

¶ Other values can be used as long as the tape management system understands that thevalue used means permanent retention.

Here is an example of how to update the cartridge device class for permanent retentionusing the expiration date of 2099365 (December 31, 2099):

update devclass cartridge expiration=2099365


|||

|

|

||

||

|

Setting Up Tape Installation-Wide ExitsYou must use the deletion installation-wide exit to notify your tape management system thatthe Tivoli Storage Manager server has deleted a tape from its database. This exit can providea tape management system with the information required to maintain an accurate inventoryof TSM tapes. However, you do not have to use this exit to use tapes with TSM.

The deletion exit is called when the TSM server is returning a tape to scratch because it nolonger contains valid files, and when the DELETE VOLUME command is used to delete avolume from the database. The tape volume is deleted from the TSM server database beforethe deletion exit is called.

The deletion exit allows your tape management system to accurately reflect the server tapeusage. You need to use the tape management system facilities to notify itself that the serverhas deleted the tape from its database.

After the deletion exit notifies the tape management system, it returns control to the server.Tape deletions cannot be cancelled.

If you are using DFSMSrmm or DFRMM, the vital record specification policy is used todetermine the management of the volume. If you are using a different tape managementsystem, it should recognize that the volume is being managed by an external data manager(EDM). It should then ensure that only TSM has access until the volume is returned to thetape management system.

Identifying the Deletion Exit to the ServerTo use the deletion exit, specify the module in the DELETIONEXIT option in the serveroptions file. If you are using a tape management system, specify the module name of thedeletion exit provided by the tape management system. For example, if you are using theDFSMShsm ARCTVEXT module, specify:

deletionexit arctvext

EDGTVEXT, which replaced ARCTVEXT by DFSMS™ 1.4, can be used as the deletionexit.

Writing the Deletion ExitIf you are using the DFSMShsm ARCTVEXT exit, the DFSMSrmm EDGTVEXT, or adeletion exit supplied with a tape management system, include the coding required for theTSM deletion exit in your existing exit. The coding considerations for this exit are the sameas those for the DFSMShsm ARCTVEXT exit and the DFSMSrmm EDGTVEXT, includingentry and exit linkage. A non-zero return code or abend in the exit results in an errormessage, but has no other effect on TSM processing.

The deletion exit must be reentrant and can run in either 24-bit or 31-bit addressing mode.

Registers on Entry to the Deletion ExitThe registers contain the following information on entry to the deletion exit:

RegisterDescription

1 The address of the parameter list passed to the exit.


D.Tap

eProcessin

gConsid

erations

13 The address of a 72-byte standard MVS save area.

14 The address to which the exit must return control.

15 The address of the deletion exit.

0, 2–12These registers contain nothing of use to the exit.

Deletion Exit Parameter ListTable 7 shows the parameter list passed to the tape deletion exit. Register 1 contains theaddress of this parameter list.

Table 7. Deletion Exit Parameter ListOffset Length

(bytes)Data Type Description

0 (X'00') 4 Address of the data area Pointer to an 8-byte data area containing informationabout the volume the server has deleted from itsdatabase. Table 8 shows the format of the data area.

4 (X'04') 4 Address of the return code The address of a full word containing the return codethat the exit must set after completing processing. Thereturn code is binary, and should be 0 if processing issuccessful, or any other number if processing isunsuccessful. TSM generates an error message ifprocessing is unsuccessful. The high order bit of thereturn code address is set to 1.

Table 8 shows the format of the data area pointed to by the deletion exit parameter list.

Table 8. Deletion Exit Data AreaOffset Length Data Type or Bit Pattern Description

0 (X'00') 6 Character The volume serial number of the tape volume deletedfrom the database

6 (X'06') 2 Binary Informational flags

1... .... .... .... The tape volume is purged from the server’s database.

.1.. .... .... .... The server has protected the files on the volume withexpiration dates. This information is determined from thedevice class associated with the volume.Note: If the expiration or retention information on thedevice class has changed after the volume was first used,this informational flag may be incorrect.

.... .... 1... .... The DFSMShsm SCRATCHTAPE option was used onthe SETSYS TAPEDELETION command for this tapecategory.

.... .... .... ..1. This is a backup tape.

Registers on Exit from the Deletion ExitWhen you return control to the server, restore the registers to the values they had on entry.


Where to Look for Information

This appendix describes the service that IBM provides for Tivoli Storage Manager and tellsyou where to look for more information about Tivoli Storage Manager.

Contacting Customer SupportFor support for this or any Tivoli product, you can contact Tivoli Customer Support in oneof the following ways:

¶ Visit the Tivoli Storage Manager technical support Web site athttp://www.tivoli.com/support/storage_mgr/tivolimain.html.

¶ Submit a problem management record (PMR) electronically at IBMSERV/IBMLINK.You can access IBMLINK at http://www2.ibmlink.ibm.com.

¶ Submit a problem management record (PMR) electronically athttp://www.tivoli.com/support. See “Reporting a Problem” on page 120 for details.

¶ Send e-mail to [email protected].

Customers in the United States can also call 1-800-TIVOLI8 (1-800-848-6548). For productnumbers 5697-TS9, 5697-DRS or 5697-DPM call 1-800-237-5511.

International customers should consult the Web site for customer support telephone numbers.

You can also review the Customer Support Handbook, which is available on our Web site athttp://www.tivoli.com/support/handbook/.

When you contact Tivoli Customer Support, be prepared to provide identificationinformation for your company so that support personnel can readily assist you. Companyidentification information may also be needed to access various online services available onthe Web site.

The support Web site offers extensive information, including a guide to support services (theCustomer Support Handbook); frequently asked questions (FAQs); and documentation for allTivoli products, including Release Notes, Redbooks, and Whitepapers. The documentationfor some product releases is available in both PDF and HTML formats. Translateddocuments are also available for some product releases.

You can order documentation by e-mail at [email protected]. Please provide the publicationnumber, part number, or order number of the desired document. Alternatively, you canprovide the document title, version number, and date of publication.

E


E.Where

toLookfor

Inform

ation


http://www2.ibmlink.ibm.com

http://www.tivoli.com/support

http://www.tivoli.com/support/handbook/

We are very interested in hearing about your experience with Tivoli products anddocumentation. We also welcome your suggestions for improvements. If you have commentsor suggestions about our documentation, please contact us in one of the following ways:

¶ Send e-mail to [email protected].

¶ Complete our customer feedback survey at http://www.tivoli.com/support/feedback/.

Reporting a ProblemPlease have the following information ready when you report a problem:

¶ The Tivoli Storage Manager server version, release, modification, and service levelnumber. You can get this information by entering the QUERY STATUS command at theTSM command line.

¶ The Tivoli Storage Manager client version, release, modification, and service levelnumber. You can get this information by entering dsmc at the command line.

¶ The communication protocol (for example, TCP/IP), version, and release number you areusing.

¶ The activity you were doing when the problem occurred, listing the steps you followedbefore the problem occurred.

¶ The exact text of any error messages.

InternetYou can get additional information through an anonymous FTP server,ftp://ftp.software.ibm.com. Tivoli Storage Manager information is in the/storage/tivoli-storage-management directory.

A newsgroup, [email protected], is implemented by a third party. IBM supports thisnewsgroup on a best-effort basis only.

Tivoli Storage Manager PublicationsThe following table lists TSM server publications.

Publication Title Order Number

Tivoli Storage Manager Messages GC35-0405

Tivoli Storage Manager, S/390 Edition Licensed Program Specifications GI10-4543

Tivoli Disaster Recovery Manager, S/390 Edition Licensed ProgramSpecifications

GI10-4544

Tivoli Storage Manager for OS/390 and z/OS Quick Start GC35-0415

Tivoli Storage Manager for OS/390 and z/OS Administrator’s Guide GC35-0416

Tivoli Storage Manager for OS/390 and z/OS Administrator’s Reference GC35-0417

The following table lists the TSM client publications.


Tivoli Space Manager for UNIX Using the Hierarchical StorageManagement Clients

SH26-4115

Tivoli Storage Manager for Macintosh Using the Backup-Archive Client SH26-4120


http://www.tivoli.com/support/feedback/

ftp://ftp.software.ibm.com


Tivoli Storage Manager for UNIX Using the Backup-Archive Clients SH26-4122

Tivoli Storage Manager for NetWare Using the Backup-Archive Client SH26-4116

Tivoli Storage Manager for Windows Using the Backup-Archive Clients SH26-4117

Tivoli Storage Manager Installing the Clients SH26-4119

Tivoli Storage Manager Quick Reference for the Backup-Archive Clients SH26-4118

Tivoli Storage Manager Trace Facility Guide SH26-4121

Tivoli Storage Manager Using the Application Programming Interface SH26-4123

The following table lists Tivoli Data Protection publications.


Tivoli Data Protection for Informix Installation and User’s Guide SH26-4095

Tivoli Data Protection for Lotus Domino, S/390 Edition Licensed ProgramSpecifications

GC26-7305

Tivoli Data Protection for Lotus Domino for UNIX Installation and User’s Guide SH26-4088

Tivoli Data Protection for Lotus Domino for Windows NT Installation GC26-7320

Tivoli Data Protection for Lotus Notes on AIX Installation and User’s Guide SH26-4067

Tivoli Data Protection for Lotus Notes on Windows NT Installation and User’sGuide

SH26-4065

Tivoli Data Protection for Microsoft Exchange Server Installation and User’s Guide SH26-4110

Tivoli Data Protection for Microsoft SQL Server Installation and User’s Guide SH26-4111

Tivoli Data Protection for Oracle for UNIX Installation and User’s Guide SH26-4112

Tivoli Data Protection for Oracle for Windows NT Installation and User’s Guide SH26-4113

Tivoli Data Protection for R/3 Version 2.7 Installation and User’s Guide SC33-6388

Tivoli Data Protection for Workgroups for Windows NT User’s Guide GC35-0359

Tivoli Data Protection for Workgroups for NetWare User’s Guide GC32-0444

Referenced OS/390 and z/OS System PublicationsThe following table lists referenced OS/390 and z/OS publications.


OS/390 Security Server (RACF) Security Administrator’s Guide SC28-1915

DFSMS/MVS DFSMSrmm Implementation and Customization Guide SC26-4932

DFSMS/MVS DFSMSrmm Guide and Reference SC26-4931

Related IBM Hardware Products PublicationsThe following table lists related IBM hardware products publications.

Title Order Number

IBM 3490 Magnetic Tape Subsystem Enhanced Capability Models E01 andE11 User’s Guide

GA32-0298

Magstar 3494 Tape Library Operator Guide GA32-0280


E.Where

toLookfor

Inform

ation

Title Order Number

Magstar 3494 Tape Library Introduction and Planning Guide GA32-0279

IBM Magstar 3590 Tape Subsystem Operator’s Guide GA32-0330

IBM 3495 Tape Library Dataserver Models L20, L30, L40, and L50Operator’s Guide

GA32-0235

IBM RedbooksThe International Technical Support Center (ITSC) publishes redbooks, which are books onspecialized topics, such as, Using TSM to Back Up Databases. You can order publicationsthrough your IBM representative or the IBM branch office serving your locality. You canalso search for and order books of interest to you by visiting the IBM Redbooks home pageon the World Wide Web at this address: http://www.redbooks.ibm.com.

TranslationsSelected TSM publications have been translated into languages other than American English.Contact your IBM representative for more information about the translated publications andthe availability of these translations in your country.


http://www.redbooks.ibm.com

Notices

This information was developed for products and services offered in the U.S.A. IBM maynot offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currentlyavailable in your area. Any reference to an IBM product, program, or service is not intendedto state or imply that only that IBM product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe any IBMintellectual property right may be used instead. However, it is the user’s responsibility toevaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described inthis document. The furnishing of this document does not give you any license to thesepatents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM IntellectualProperty Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other countrywhere such provisions are inconsistent with local law: INTERNATIONAL BUSINESSMACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUTNOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do notallow disclaimer of express or implied warranties in certain transactions, therefore, thisstatement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes areperiodically made to the information herein; these changes will be incorporated in neweditions of the publication. IBM may make improvements and/or changes in the product(s)and/or the program(s) described in this publication at any time without notice.

F


F.Notices

Any references in this information to non-IBM Web sites are provided for convenience onlyand do not in any manner serve as an endorsement of those Web sites. The materials atthose Web sites are not part of the materials for this IBM product and use of those Web sitesis at your own risk.

IBM may use or distribute any of the information you supply in any way it believesappropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose ofenabling: (i) the exchange of information between independently created programs and otherprograms (including this one) and (ii) the mutual use of the information which has beenexchanged, should contact:

IBM CorporationInformation Enabling RequestsDept. M135600 Cottle RoadSan Jose CA 95193-0001U.S.A.

Such information may be available, subject to appropriate terms and conditions, including insome cases, payment of a fee.

The licensed program described in this information and all licensed material available for itare provided by IBM under terms of the IBM Customer Agreement, IBM InternationalProgram License Agreement, or any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of thoseproducts, their published announcements or other publicly available sources. IBM has nottested those products and cannot confirm the accuracy of performance, compatibility or anyother claims related to non-IBM products. Questions on the capabilities of non-IBM productsshould be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. Toillustrate them as completely as possible, the examples include the names of individuals,companies, brands, and products. All of these names are fictitious and any similarity to thenames and addresses used by an actual business enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations may notappear.


TrademarksThe following terms are trademarks of the International Business Machines Corporation inthe United States or other countries or both:

ACF/VTAMAD/CycleAdvanced Peer-to-Peer NetworkingAFSAIXApplication System/400APPNAS/400ATC/370Common User AccessCUADATABASE 2DB2DFDSMDFSDFSMS/MVSDFSMS/VMDFSMSdssDFSMShsmDFSMSrmmES/9000ESCON

Extended ServicesIBMIBMLinkMVS/ESAMVS/SPOpenEditionOperating System/2Operating System/400OS/2OS/390OS/400POWERparallelRACFRISC System/6000RS/6000SPSystem/370System/390SystemViewVM/ESAVTAMXT

Lotus, Lotus 1–2–3, Lotus Approach, Lotus Domino and Lotus Notes are trademarks ofLotus Development Corporation in the United States and/or other countries.

Tivoli and Tivoli ADSM are trademarks of Tivoli Systems Inc. in the United States and/orother countries.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of MicrosoftCorporation in the United States and/or other countries.

UNIX is a registered trademark of the Open Group in the United States and/or othercountries.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. inthe United States and/or other countries.

Intel is a registered trademark of the Intel Corporation in the United States and/or othercountries.

Other company, product, and service names may be trademarks or service marks of others.


F.Notices

Glossary

A

absoluteA value for the backup copy group mode indicating that a file is considered for incremental backup even if thefile has not changed since the last backup. See also mode. Contrast with modified.

access modeAn attribute of a storage pool or a storage volume attribute that specifies whether TSM can write to or read fromthe storage pool or storage volume. The access mode can be read/write, read-only, or unavailable. Volumes inprimary storage pools can also have an access mode of destroyed. Volumes in copy storage pools can also havean access mode of offsite.

accounting facilityA facility that records statistics about client session activity.

accounting recordsFiles that record session resource usage at the end of each client session.

activateThe process of validating the contents of a policy set and copying the policy set to the ACTIVE policy set.

active policy setThe policy set that contains the policy rules currently in use by all client nodes assigned to the policy domain.The active policy set is the policy set that was most recently activated for the policy domain. See policy set.

active versionThe most recent backup copy of a file stored by TSM. Such a file is not eligible for deletion until a backupprocess detects that the user has either replaced the file with a newer version, or has deleted the file from theworkstation. Contrast with inactive version.

activity logA log that records normal activity messages generated by the server. These messages include information aboutserver and client operations, such as the start time of sessions or device I/O errors. Each message includes amessage ID, date and time stamp, and a text description. The number of days to retain messages in the activitylog can be specified.

administrative clientA program that runs on a file server, workstation, or mainframe that allows administrators to control and monitorthe server through administrator commands. Contrast with backup-archive client.

administrative command scheduleA database record that describes the planned processing of an administrative command during a specific timeperiod. See also client schedule.

The terms in this glossary are defined as they pertain to the Tivoli Storage Manager library. If you do not find the term you need,refer to the IBM Software Glossary on the Web at this URL: www.ibm.com/ibm/terminology/. You can also refer to IBM Dictionaryof Computing, New York: McGraw-Hill, 1994.

This glossary may include terms and definitions from:

¶ The American National Standard Dictionary for Information Systems, ANSI X3.172-1990, copyright (ANSI). Copies may bepurchased from the American National Standards Institute, 11 West 42nd Street, New York 10036.

¶ The Information Technology Vocabulary, developed by Subcommittee 1, Joint Technical Committee 1, of the InternationalOrganization for Standardization and the International Electrotechnical Commission (ISO/IEC JTC2/SC1).


Glossary

http://www.ibm.com/ibm/terminology

administrative privilege classA level of authority granted to an administrator of TSM. The privilege class determines which TSMadministrative tasks the administrator can perform. For example, an administrator with system privilege class canperform any administrative task. See system privilege class, policy privilege class, storage privilege class,operator privilege class, and analyst privilege class.

administrative sessionA period of time in which an administrator user ID communicates with a server to perform administrative tasks.Contrast with client node session.

administratorA user who has been registered to the server. Administrators can be authorized to one or more of the followingadministrative privilege classes: system, policy, storage, operator, or analyst. Administrators can use theadministrative commands and queries allowed by their privileges.

Advanced Interactive Executive (AIX)An operating system used in the RISC System/6000® computers. The AIX operating system is the IBMimplementation of the UNIX operating system.

Advanced Peer-to-Peer Networking® (APPN)An extension to the LU6.2 peer orientation for end-user services. See SNA LU6.2 and Systems NetworkArchitecture.

Advanced Program-to-Program Communication (APPC)An implementation of the SNA/SDLC LU6.2 protocol that allows interconnected systems to communicate andshare the processing of programs. See SNA LU6.2, Systems Network Architecture, and Common ProgrammingInterface Communications.

AFSAndrew file system.

aggregate fileA file, stored in one or more storage pools, consisting of a group of logical files packaged together. See logicalfile and physical file.

AIXAdvanced Interactive Executive.

analyst privilege classAn administrative privilege class that allows an administrator to reset statistics.

Andrew file system (AFS)A distributed file system developed for UNIX operating systems.

APIApplication program interface.

APPCAdvanced Program-to-Program Communication.

application clientOne of the Tivoli Data Protection for application programs installed on a system. The Tivoli Storage Managerserver provides backup services to these clients.

application program interfaceA set of functions that applications running on a client platform can call to store, query, and retrieve objects fromTSM storage.

APPNAdvanced Peer-to-Peer Networking.


archiveA function that allows users to copy one or more files to a storage pool for long-term storage. Archive copiesmay be accompanied by descriptive information and may be retrieved by archive date, by file name, or bydescription. Contrast with retrieve.

archive copyA user file that has been archived to a TSM storage pool.

archive copy groupA policy object containing attributes that control the generation, destination, and expiration of archive files. Anarchive copy group belongs to a management class.

archive retention grace periodThe number of days that TSM retains an archive copy when the server is unable to rebind the file to anappropriate management class.

AS/400®

Application System/400®.

assigned capacityThe portion of available space that can be used to store database or recovery log information. See also availablespace.

association(1) The defined relationship between a client node and a client schedule. An association identifies the name of aschedule, the name of the policy domain to which the schedule belongs, and the name of a client node thatperforms scheduled operations. (2) On a configuration manager, the defined relationship between a profile and anobject such as a policy domain. Profile associations define the configuration information that will be distributedto managed servers when they subscribe to the profile.

auditThe process of checking for logical inconsistencies between information that the server has and the actualcondition of the system. TSM has processes for auditing volumes, the database, libraries, and licenses. Forexample, in auditing a volume TSM checks for inconsistencies between information about backed up or archivedfiles stored in the database and actual data associated with each backup version or archive copy in server storage.

authenticationThe process of checking a user’s password before allowing that user access to the server. Authentication can beturned on or off by an administrator with system privilege.

authorityThe right granted to a user to perform tasks with TSM servers and clients. See administrative privilege class.

autochangerA small multislot tape device that has a mechanism that automatically puts tape cartridges into the tape drive ordrives. Also called medium or media changer, or a library.

availability managementManaging recovery from relatively common computer system outages such as a disk drive head crash. Recoveryis often accomplished by using disk mirroring and other forms of RAID technology, or by maintaining onsitebackup copies of data.

available spaceThe amount of space, in megabytes, that is available to the database and recovery log. This space can be used toextend the capacity of the database or recovery log, or to provide sufficient free space before a volume is deletedfrom the database or recovery log.

awkIn AIX, a pattern-matching program for processing text files. With the DRM product, you can use an awk scriptto break up the disaster recovery plan file into usable parts.


Glossary

B

background processA server process that runs in the background, allowing the administrative session to be used for other work.

backupThe process of copying information for safekeeping. TSM has processes for backing up user files, the TSMdatabase, and storage pools. For example, users can back up one or more files to a storage pool to ensure againstloss of data. Contrast with restore. See also database backup series and incremental backup.

backup-archive clientA program that runs on a workstation or file server and provides a means for users to back up, archive, restore,and retrieve files. Contrast with administrative client.

backup copyA user file that has been backed up to a TSM storage pool.

backup copy groupA policy object containing attributes that control the generation, destination, and expiration of backup files. Abackup copy group belongs to a management class.

backup retention grace periodThe number of days that TSM retains a backup version after the server is unable to rebind the file to anappropriate management class.

backup seriesSee database backup series.

backup setA portable, consolidated group of active backup files for a single client. Generation of a backup set is possiblefor selected backup-archive clients that obtain services from a server at the latest software level.

backup versionA file, directory, or file space that a user has backed up, which resides in TSM server storage. There may bemore than one backup version of a file in the storage pool, but at most only one is an active backup version. Seeactive version and inactive version.

bindingThe process of associating a file with a management class name. See rebinding.

boot mediaMedia that contains operating system and other files essential to running a workstation or server.

bufferStorage used to compensate for differences in the data rate flow, when transferring data from one device toanother.

buffer poolTemporary space used by the server to hold database or recovery log pages. See database buffer pool andrecovery log buffer pool.

C

cacheThe process of leaving a duplicate copy on random access media when the server migrates a file to anotherstorage pool in the hierarchy.

CARTRIDGEOn TSM servers that support it, a device class that is used to categorize tape devices that support tape cartridges,such as the 3490 Magnetic Tape Subsystem.


cartridge system tape (CST)The base tape cartridge media used with 3480 or 3490 Magnetic Tape Subsystems. When specified as a mediatype in TSM, CST identifies standard length tape. Contrast with enhanced capacity cartridge system tape.

central schedulerA function that allows an administrator to schedule client operations and administrative commands. Theoperations can be scheduled to occur periodically or on a specific date. See client schedule and administrativecommand schedule.

CIDConfiguration Installation and Distribution.

clientA program running on a PC, workstation, file server, LAN server, or mainframe that requests services of anotherprogram, called the server. The following types of clients can obtain services from a TSM server: administrativeclient, application client, API client, backup-archive client, HSM client (also known as space manager client), andhost server.

Client Access™/400®

A software product that supports advanced program-to-program communications (APPC) in the DOS, OS/2, andMicrosoft® Windows environments and provides a set of end user services.

client domainThe set of drives, file systems, or volumes selected by a backup-archive client user during a backup or archiveoperation.

client migrationThe process of copying a file from a client node to TSM storage and replacing the file with a stub file on theclient node. The process is controlled by the user and by space management attributes in the management class.See also space management.

client nodeA file server or workstation on which the backup-archive client program has been installed, which has beenregistered to the server.

client node sessionA period of time in which a user communicates with a server to perform backup, restore, archive, retrieve,migrate, or recall requests. Contrast with administrative session.

client options fileA file that a client can change, containing a set of processing options that identify the server, communicationmethod, and options for backup, archive, hierarchical storage management, and scheduling. Also called thedsm.opt file.

client polling scheduling modeA client/server communication technique where the client queries the server for work.

client scheduleA database record that describes the planned processing of a client operation during a specific time period. Theclient operation can be a backup, archive, restore, or retrieve operation, a client operating system command, or amacro. See also administrative command schedule.

client/serverA system architecture in which one or more programs (clients) request computing or data services from anotherprogram (server).

client system options fileA file, used on UNIX clients, containing a set of processing options that identify the TSM servers to be contactedfor services. This file also specifies communication methods and options for backup, archive, hierarchical storagemanagement, and scheduling. Also called the dsm.sys file. See also client user options file.


Glossary

client user options fileA user-created file, used on UNIX clients, containing a set of processing options that identify the server,communication method, backup and archive options, space management options, and scheduling options. Alsocalled the dsm.opt file. See also client system options file.

closed registrationA registration process in which an administrator must register workstations as client nodes with the server.Contrast with open registration.

clusterIn a Microsoft environment, a set of independent computer systems, called nodes, that are set up to work togetheras a single system. The cluster helps ensure that critical applications and resources remain available.

collocationA process that attempts to keep all data belonging to a single client node or a single client file space on aminimal number of sequential access media volumes within a storage pool. Collocation can reduce the number ofvolumes that must be accessed when a large amount of data must be restored.

code pageAn assignment of graphic characters and control function meanings to all code points; for example, assignment ofcharacters and meanings to 256 code points for an 8-bit code, assignment of characters and meanings to 128 codepoints for a 7-bit code. Describes how binary values are mapped to human-readable characters.

commitTo make changes permanent in the database. Changes made to the database files are not permanent until they arecommitted.

Common Programming Interface Communications (CPI-C)A programming interface that allows program-to-program communication using SNA LU6.2. See also SystemsNetwork Architecture.

Common User Access® (CUA®)Guidelines for the dialog between a human and a workstation or terminal. One of the three Systems ApplicationArchitecture areas.

communication managerA component of OS/2 that allows a workstation to connect to a host computer and use the host resources as wellas the resources of other personal computers to which the workstation is attached, either directly or through ahost.

communication methodThe method used by a client and server for exchanging information.

communication protocolA set of defined interfaces that allow computers to communicate with each other.

compressionThe process of saving storage space by eliminating empty fields or unnecessary data in a file. In TSM,compression can occur at a workstation before files are backed up or archived to server storage. On some typesof tape drives, hardware compression can be used.

Configuration Installation and Distribution (CID)The term used to describe the capability of IBM products for automated installation. CID-enabled products arecapable of unattended, remote installation.

configuration managerOne TSM server that distributes configuration information to other TSM servers (called managed servers) viaprofiles. Configuration information can include policy and schedules. See managed server and profile.

copy groupA policy object that contains attributes that control the generation, destination, and expiration of backup andarchive files. There are two kinds of copy groups: backup and archive. Copy groups belong to managementclasses. See also frequency, destination, mode, serialization, retention, and version.


|||

||||

copy statusThe status of volume copies defined to the database or recovery log. The copy status can be synchronized, stale,off-line, or undefined.

copy storage poolA named set of volumes that contains copies of files that reside in primary storage pools. Copy storage pools areused only to back up the data stored in primary storage pools. A copy storage pool cannot be a destination for abackup copy group, an archive copy group, or a management class (for space-managed files). See primarystorage pool and destination.

CPI-CCommon Programming Interface Communications.

CSTCartridge system tape.

CUACommon User Access.

D

daemonIn the AIX operating system, a program that runs unattended to perform a standard service. Some daemons aretriggered automatically to perform their tasks; others operate periodically.

daemon processIn the AIX operating system, a process begun by the root user or by the root shell that can be stopped only bythe root user. Daemon processes generally provide services that must be available at all times, such as sendingdata to a printer.

damaged fileA physical file for which TSM has detected read errors.

DASDDirect access storage device.

databaseA collection of information about all objects managed by the server, including policy management objects, usersand administrators, and client nodes.

database auditA utility that checks for and optionally corrects inconsistent database references.

database backup seriesOne full backup of the database, plus up to 32 incremental backups made since that full backup. Each fullbackup that is run starts a new database backup series. A backup series is identified with a number.

database backup triggerA set of criteria that defines when and how database backups are run automatically. The criteria determine howoften the backup is run, whether the backup is a full or incremental backup, and where the backup is stored.

database buffer poolStorage that is used as a cache to allow database pages to remain in memory for long periods of time, so that theserver can make continuous updates to pages without requiring input or output (I/O) operations from externalstorage.

database dumpThe action performed by the DSMSERV DUMPDB utility (DMPADSM command on AS/400), which copiesTSM database entries to media for later reload in case a catastrophic error occurs.

database loadThe action performed by the DSMSERV LOADDB utility (LODADSM command on AS/400), which copiesTSM database entries from media to a newly installed database.


Glossary

database snapshotA function of TSM that backs up the entire TSM database to media that can be taken off-site. The databasesnapshot does not interrupt any database backup series and cannot have incremental database backups associatedwith it. Contrast with full backup.

database volumeA volume that has been assigned to the TSM database.

dataserverSee Tape Library Dataserver.

data setSee linear data set.

DDMDistributed Data Management.

default management classA management class assigned to a policy set, which is used to govern backed up or archived files when a userdoes not specify a management class for a file.

deletion exitFor MVS or VM, an installation-wide exit that informs a tape management system or operator that the server hasdeleted a sequential access media volume from its database.

delimiter(1) A character used to indicate the beginning and end of a character string. (2) A character that groups orseparates words or values in a line of input.

desktop clientThe group of backup-archive clients supported by TSM that includes clients on OS/2, DOS, Windows, Apple,and Novell NetWare operating systems.

destinationA copy group or management class attribute that specifies the primary storage pool to which a client file will bebacked up, archived, or migrated.

device classA named group of storage devices with common characteristics. Each device class has a unique name andrepresents a device type of disk, file, optical disk, or tape.

device configuration fileA file that contains information about defined device classes, and, on some TSM servers, defined libraries anddrives. The file can be created by using a TSM command or by using an option in the server options file. Theinformation is a copy of the device configuration information in the TSM database.

device driverA collection of subroutines that control the interface between I/O device adapters and the processor.

device typeA category of storage device. Each device class is categorized with one of the supported device types, forexample, DISK or CARTRIDGE.

direct access storage device (DASD)A device in which access time is effectively independent of the location of the data.

disaster recoveryRecovery from catastrophic interruptions of computer systems, such as loss of the system location because ofnatural events. Backup data is kept offsite to protect against such catastrophes.

Disaster Recovery ManagerSee Tivoli Disaster Recovery Manager.


disaster recovery planA document that contains information about how to recover computer systems if a disaster occurs. The TivoliDisaster Recovery Manager (DRM) product allows you to create the plan for a TSM server. The plan is a filethat contains information about the software and hardware used by the TSM server, and the location of recoverymedia.

DISKA device class that is defined by TSM at installation. It is used to categorize disk drives, such as internal diskdrives or 3390 DASD.

disk operating system (DOS)An operating system used in IBM PC, PS/2, and compatible computers.

Distributed Data Management (DDM)A feature of the System Support Program Product that allows an application program (client) to use serverprogram functions to work on files that reside in a remote system.

DLLDynamic link library.

DLTDigital linear tape.

domainSee policy domain or client domain.

DOSDisk operating system.

driveA device used to read and write data on a medium such as a magnetic disk, optical disk, or tape.

DRMA short name for Tivoli Disaster Recovery Manager.

drive mappingThe correlation of drive names between a TSM server and a TSM storage agent.

dsm.opt fileSee client options file and client user options file.

dsmserv.optSee server options file.

dsm.sys fileSee client system options file.

dynamicA copy group serialization value that specifies that TSM accepts the first attempt to back up or archive a fileregardless of whether the file is modified during the backup or archive process. See also serialization. Contrastwith shared dynamic, shared static, and static.

dynamic link libraryA file containing executable code and data bound to a program at load time or run time, rather than duringlinking. The code and data in a dynamic link library can be shared by several applications simultaneously.

E

ECCSTEnhanced capacity cartridge system tape.

enhanced capacity cartridge system tape (ECCST)Cartridge system tape with increased capacity that can only be used with 3490E tape subsystems. Contrast withcartridge system tape.


Glossary

enterprise configurationA capability that allows the administrator to distribute the configuration of one TSM server to other servers usingserver-to-server communication. See configuration manager, managed server, profile, and subscription.

enterprise loggingThe sending of events from TSM servers to a designated event server. The event server routes the events todesignated receivers, such as to a user exit. See also event.

error logA character file written on random access media that contains information about errors detected by the server orclient.

estimated capacityThe available space, in megabytes, of a storage pool.

EthernetA data link protocol and LAN that interconnects personal computers and workstations via coaxial cable.

event(1) An administrative command or a client operation that is scheduled to be run using TSM scheduling. (2) Amessage that a TSM server or client issues. Messages can be logged using TSM event logging.

event recordA database record that describes actual status and results for events.

event serverA server to which other servers can send events for logging. The event server routes the events to any receiversthat are enabled for the sending server’s events.

excludeThe process of identifying files or directories in an include-exclude list to prevent these objects from beingbacked up whenever a user or schedule issues an incremental or selective backup operation, or to prevent theseobjects from being migrated off the client node via Tivoli Space Manager space management.

exclude-include listSee include-exclude list.

exitTo execute an instruction within a portion of a computer program in order to terminate the execution of thatportion.

exit machineOn a VM server, a virtual machine that runs the mount and deletion installation-wide exits on VM systems.

expirationThe process by which files are identified for deletion because their expiration date or retention period has passed.Backed up or archived files are marked expired by TSM based on the criteria defined in the backup or archivecopy group.

expiration dateOn MVS, VM, and VSE servers, a device class attribute used to notify tape management systems of the datewhen TSM no longer needs a tape volume. The date is placed in the tape label so that the tape managementsystem does not overwrite the information on the tape volume before the expiration date.

exportThe process of copying administrator definitions, client node definitions, policy definitions, server controlinformation or file data to external media.

export/import facilitySee import/export facility.

extendThe process of increasing the portion of available space that can be used to store database or recovery loginformation. Contrast with reduce.


F

failoverFor a Microsoft cluster configuration, the process that occurs when one resource, for example a server, fails andoperations are automatically taken over by another resource in the cluster.

file record extentThe extent of the file enumerated in number of records.

file spaceA logical space in a client’s storage that can contain a group of files. For clients on Windows systems, a filespace is a logical partition that is identified by a volume label. For clients on systems such as AIX and UNIX, afile space can consist of any subset of directories and subdirectories stemming from a virtual mount point. Clientscan restore, retrieve, or delete their file spaces from TSM server storage. TSM does not necessarily store all thefiles from a single file space together, but can identify all the files in server storage that came from a single filespace.

File Transfer Protocol (FTP)In TCP/IP, the protocol that makes it possible to transfer data among hosts and to use foreign hosts indirectly.

formatA device class attribute that specifies the recording format used to read or write to sequential access media suchas tape.

frequencyA copy group attribute that specifies the minimum interval, in days, between incremental backups.

FSIDFile space ID. A unique numeric identifier that the server assigns to a file space when it is stored in serverstorage.

FTPFile Transfer Protocol.

full backupA function of TSM that copies the entire database. A full backup begins a new database backup series. Contrastwith incremental backup and database snapshot. See database backup series.

fuzzy copyA backup version or archive copy of a file that might not accurately reflect what is currently in the file becauseTSM backed up or archived the file while the file was being modified.

G

GUIGraphical user interface.

H

HDAHead-disk assembly.

head-disk assembly (HDA)A field replaceable unit in a direct access storage device containing the disks and actuators.

hierarchical storage management (HSM) clientThe Tivoli Space Manager program that runs on workstations to allow users to maintain free space on theirworkstations by migrating and recalling files to and from Tivoli Storage Manager storage. Synonymous withspace manager client.


|||

||||||

|||

Glossary

high migration thresholdA percentage of the storage pool capacity that identifies when TSM can start migrating files to the next availablestorage pool in the hierarchy. Contrast with low migration threshold. See server migration.

host serverThe name for the system on which the Tivoli Data Protection for Workgroups program runs. The host serverobtains scheduling services from Tivoli Storage Manager.

HP-UXHewlett-Packard UNIX operating system.

HSM clientHierarchical storage management client. Also known as the space manager client.

I

importThe process of copying exported administrator definitions, client node definitions, policy definitions, servercontrol information or file data from external media to a target server.

import/export facilityThe facility that allows system administrators to copy definitions and file data from a source server to externalmedia to move or copy information between servers. A subset of information can be imported to a target serverfrom the external media.

inactive versionA backup version of a file for which a more recently backed-up version exists. Inactive backup versions areeligible for expiration processing according to the management class assigned to the file. Contrast with activeversion.

include-exclude fileOn UNIX and Windows clients, a file containing statements that TSM uses to determine whether to back up ormigrate certain files, and to determine the associated management classes to use for backup, archive, and spacemanagement. See include-exclude list.

include-exclude listA group of include and exclude option statements that TSM uses. The exclude options identify files that shouldnot be backed up or migrated off the client node. The include options identify files that are exempt from theexclusion rules, or assign a management class to a file or group of files for backup, archive, or spacemanagement services. The include-exclude list for a client may include option statements from theinclude-exclude file (for UNIX clients) or the client options file (for other clients), and from a client option seton the server.

incremental backup(1) A function that allows users to back up files or directories that are new or have changed since the lastincremental backup. With this function, users can back up files or directories from a client domain that are notexcluded in the include-exclude list and that meet the requirements for frequency, mode, and serialization asdefined in the backup copy group of the management class assigned to the files. Contrast with selective backup.(2) A function of TSM that copies only the pages in the database that are new or changed since the last full orincremental backup of the database. Contrast with full backup. See database backup series.

internal mounting facilityOn a VM server, a VM facility that allows the server to request tape mounts by sending a message to a mountoperator. The message is repeated until the tape is mounted or until the mount wait time is exceeded.

inter-user communication vehicle (IUCV) facilityOn a VM server, a VM communication method used to pass data between virtual machines and VM components.

IPX/SPXInternetwork Packet Exchange/Sequenced Packet Exchange. IPX/SPX is Novell NetWare’s communicationprotocol.


|||

||||||

IUCVInter-user communication vehicle.

K

KBKilobyte.

kernelThe part of an operating system that performs basic functions such as allocating hardware resources.

kernel extensionA program that modifies parts of the kernel that can be customized to provide additional services and calls. Seekernel.

kilobyte (KB)1024 bytes.

L

LANLocal area network.

LAN-free data transferThe movement of client data directly from a client to a storage device over a SAN, rather than over the LAN.

lengthA device class attribute that specifies the length of cartridge tape by specifying one of the following media types:CST for standard length tape or ECCST for double length tape.

library(1) A repository for demountable recorded media, such as magnetic tapes. (2) For TSM, a collection of one ormore drives, and possibly robotic devices (depending on the library type), which can be used to access storagevolumes. (3) In the AS/400 system, a system object that serves as a directory to other objects. A library groupsrelated objects, and allows the user to find objects by name.

library clientA TSM server that uses server-to-server communications when multiple TSM servers share a storage device tocontact a library manager and request device services.

library managerA TSM server that controls device operations when multiple TSM servers share a storage device. Theseoperations include mount, dismount, volume ownership, and library inventory.

linear data setA type of MVS data set that TSM uses for the database, the recovery log, and storage pools. The data set mustbe preallocated using VSAM IDCAMS and formatted by TSM for its use.

loadSee mount.

local area network (LAN)A network in which a set of devices are connected to one another for communication and that can be connectedto a larger network.

logical fileA client file stored in one or more server storage pools, either by itself or as part of an aggregate file. See alsoaggregate file and physical file.

logical occupancyThe space required for the storage of logical files in a storage pool. Because logical occupancy does not includethe unused space created when logical files are deleted from aggregates, it may be less than physical occupancy.See also physical file and logical file.


Glossary

logical volume(1) A portion of a physical volume that contains a filesystem. (2) For the TSM server, the combined space fromall volumes defined to either the database or the recovery log. The database is one logical volume and therecovery log is one logical volume.

log pool sizeThe size of an area in memory used to store recovery log pages.

low migration thresholdA percentage of the storage pool capacity that specifies when TSM can stop the migration of files to the nextstorage pool. Contrast with high migration threshold. See server migration.

M

machine informationDetails about the machine on which a client node resides.

macro fileA file that contains one or more administrative commands and that is run from an administrative client. Contrastwith TSM command script.

managed objectA definition in the TSM database of a managed server that was distributed to the managed server by aconfiguration manager. In general, the definition cannot be modified locally on the managed server. When amanaged server subscribes to a profile, all objects associated with that profile become managed objects in thedatabase of the managed server. Objects can include policy, schedules, client options sets, server scripts,administrator registrations, and server and server group definitions.

managed serverA TSM server that receives configuration information from a configuration manager via subscription to one ormore profiles. Configuration information can include definitions of objects such as policy and schedules. Seeconfiguration manager, subscription, and profile.

managed systemA client or server that requests services from the Tivoli Storage Manager server.

management classA policy object that users can bind to each file to specify how the server manages the file. The management classcan contain a backup copy group, an archive copy group, and space management attributes. The copy groupsdetermine how the TSM server manages backup versions or archive copies of files. The space managementattributes determine whether files are eligible for migration from space manager client nodes to TSM storage, andunder what conditions. See also copy group, binding and rebinding.

maskA pattern of characters that controls the keeping, deleting, or testing of positions of another pattern of charactersor bits.

maximum extensionSpecifies the maximum amount of storage space, in megabytes, that you can extend the database or recovery log.

maximum reductionSpecifies the maximum amount of storage space, in megabytes, that you can reduce the database or recovery log.

maximum utilizationThe highest percentage of assigned capacity used by the database or recovery log.

MBMegabyte.

megabyte (MB)(1) For processor storage and real and virtual memory, 220 or 1 048 576 bytes. (2) For disk storage capacity andtransmission rates, 1 000 000 bytes.


migrate(1) To move data from one storage pool to the storage pool specified as the next pool in the hierarchy. Theprocess is controlled by the high and low migration thresholds for the first storage pool. See high migrationthreshold and low migration threshold. (2) To copy a file from a Tivoli Space Manager client node to TSMstorage. Tivoli Space Manager replaces the file with a stub file on the client node. The process is controlled bythe include-exclude list and by space management attributes in management classes.

migrationThe process of moving data from one storage location to another. See client migration and server migration.

minidiskA logical subdivision of a VM physical disk that provides storage on contiguous cylinders of DASD. On a VMserver, a minidisk can be defined as a disk volume that can be used by the database, recovery log, or a storagepool.

mirroringA feature that protects against data loss within the database or recovery log by writing the same data to multipledisks at the same time. Mirroring supports up to three exact copies of each database or recovery log volume.

mmMillimeter.

modeA copy group attribute that specifies whether to back up a file that has not been modified since the last time thefile was backed up. See modified and absolute.

modifiedA backup copy group mode value indicating that a file is considered for incremental backup only if it haschanged since the last backup. A file is considered changed if the date, size, owner, or permissions have changed.See mode. Contrast with absolute.

MotifA graphical user interface that performs window management and contains a high level toolkit for applicationprogram development. It provides an icon view of the UNIX file system. Also known as X-Windows/Motif orMotif X—Toolkit.

mountTo place a data medium (such as a tape cartridge) on a drive in a position to operate.

mount exitOn a VM server, an installation-wide exit (DSMMOUNT EXEC) that requests tape mounts on behalf of theserver on VM systems.

mount limitA device class attribute specifying the maximum number of volumes that can be simultaneously accessed fromthe same device class, that is, the maximum number of mount points. See mount point.

mount operatorOn a VM server, a VM user ID that can receive tape mount messages from the server.

mount pointA logical drive through which TSM accesses volumes in a sequential access device class. For a device class witha removable media device type (for example, CARTRIDGE), a mount point is a logical drive associated with aphysical drive. For a device class with the device type of FILE, a mount point is a logical drive associated withan I/O stream. The number of mount points for a device class is determined by the mount limit for that class.See mount limit.

mount requestA server request to mount a sequential access media volume so that data can be read from or written to thesequential access media.

mount retention periodA device class attribute that specifies the maximum number of minutes that the server retains a mountedsequential access media volume that is not being used before it dismounts the sequential access media volume.


Glossary

mount wait periodA device class attribute that specifies the maximum number of minutes that the server waits for a sequentialaccess volume mount request to be satisfied before canceling the request.

MSCSMicrosoft Cluster Server.

Multiple Virtual Storage (MVS)One of the family of IBM operating systems for the System/370™ or System/390® processor, such asMVS/ESA™.

MVSMultiple Virtual Storage.

N

Named PipesA communication protocol that is built into the Windows NT or OS/2 operating system. It can be used toestablish communications between the TSM server and any TSM clients on the same system.

NetBIOSNetwork Basic Input/Output System.

network adapterA physical device, and its associated software, that enables a processor or controller to be connected to anetwork.

Network Basic Input/Output System (NetBIOS)An operating system interface for application programs used on IBM personal computers that are attached to theIBM Token-Ring Network.

Network File System (NFS)A protocol defined by Sun Microsystems that extends TCP/IP network file services. NFS permits remote nodefiles to appear as though they are stored on a local workstation.

Networking Services/DOS (NS/DOS)A software product that supports advanced program-to-program communications (APPC) in the DOS andMicrosoft Windows 3.1 environments. With NS/DOS, communications applications on your workstation “talk to”partner applications on other systems that support APPC.

NFSNetwork File System.

node(1) A unique name used to identify a workstation to the server. See also client node. (2) In a Microsoft clusterconfiguration, one of the computer systems that make up the cluster. See cluster.

node privilege classAn administrative privilege class that allows a user to remotely access a Web backup-archive client with anadministrative user ID and password. A user with node privilege can have client owner or client access authorityfor a specific client node or for all clients in a policy domain.

notify operatorA VM user ID that specifies an operator who receives messages about severe errors and abnormal conditions.

O

objectA collection of data managed as a single entity.


||

||

offsite recovery mediaMedia that is kept at a different location to ensure its safety if a disaster occurs at the primary location of thecomputer system. The media contains data necessary to recover the TSM server and clients. The offsite recoverymedia manager, which is part of DRM, identifies recovery media to be moved offsite and back onsite, and tracksmedia status.

offsite volumeA removable media volume that is at a location where it cannot be mounted for use.

open registrationA registration process in which users can register their own workstations as client nodes with the server. Contrastwith closed registration.

Operating System/2® (OS/2)An operating system used in IBM PC AT®, PS/2, and compatible computers.

operator privilege classAn administrative privilege class that allows an administrator to issue commands that control the operation of theserver. This privilege class allows disabling or halting the server to perform maintenance, enabling the server,canceling server processes, and managing tape.

optical libraryA storage device that houses optical disk drives and optical disks, and contains a mechanism for moving opticaldisks between a storage area and optical disk drives.

OS/2Operating System/2.

OS/390Operating System/390.

OS/400®

Operating System/400®.

ownerThe owner of backup-archive files sent from a multiuser client node, such as AIX.

P

page(1) A block of instructions, data, or both. (2) In TSM, a unit of space allocation within database volumes. (3) In avirtual storage system, a fixed block that has a virtual address and is transferred as a unit between real storageand auxiliary storage.

paging(1) The action of transferring instructions, data, or both, between real storage and external page storage. (2)Moving data between memory and a mass storage device as the data is needed.

pattern-matching expressionA string expression that uses wildcard characters to specify one or more TSM objects. See also wildcardcharacter.

physical fileA file, stored in one or more storage pools, consisting of either a single logical file, or a group of logical filespackaged together (an aggregate file). See also aggregate file and logical file.

physical occupancyThe occupancy of physical files in a storage pool. This is the actual space required for the storage of physicalfiles, including the unused space created when logical files are deleted from aggregates. See also physical file,logical file, and logical occupancy.

platformThe operating system environment in which a program runs.


Glossary

policy domainA policy object that contains policy sets, management classes, and copy groups that are used by a group of clientnodes. See policy set, management class, and copy group.

policy privilege classAn administrative privilege class that allows an administrator to manage policy objects, register client nodes, andschedule client operations (such as backup services) for client nodes. Administrators can be authorized withunrestricted or restricted policy privilege.

policy setA policy object that contains a group of management class definitions that exist for a policy domain. At any onetime there can be many policy sets within a policy domain but only one policy set can be active. Seemanagement class and active policy set.

premigrationFor an HSM client, the process of copying files that are eligible for migration to TSM storage, but leaving theoriginal file intact on the local system.

primary storage poolA named set of volumes that TSM uses to store backup versions of files, archive copies of files, and filesmigrated from HSM client nodes. A primary storage pool may be backed up to a copy storage pool. Seedestination and copy storage pool.

privilege classA level of authority granted to an administrator of TSM . The privilege class determines which TSMadministrative tasks the administrator can perform. For example, an administrator with system privilege class canperform any administrative task. See system privilege class, policy privilege class, storage privilege class,operator privilege class, andanalyst privilege class.

profileA named group of configuration information that can be distributed from a configuration manager when amanaged server subscribes. Configuration information can include registered administrators, policy, clientschedules, client option sets, administrative schedules, server command macros, server definitions, and servergroup definitions. See configuration manager and managed server.

protection statusA device class attribute that specifies whether to update the RACF® profile to identify which users have accessto cartridge tapes associated with this device class on MVS servers.

Q

QICQuarter-inch cartridge (a type of magnetic tape media).

R

random access mediaAny volume accessed in a nonsequential manner. In TSM, volumes are accessed in a nonsequential manner ifthey reside in the DISK device class.

randomizationThe percentage of the startup window that the server can use to randomize start times for different client nodesassociated with a schedule.

rebindingThe process of associating a file with a backed-up file with a new management class name. For example,rebinding occurs when the management class associated with a file is deleted. See binding.

recallA function that allows users to access files that have been migrated from their workstations to TSM storage viathe Tivoli Space Manager (HSM client). Contrast with migrate.


receiverA server repository that contains a log of server messages and most client messages as events. For example, areceiver can be file and user exits, or the TSM server console and activity log. See also event.

reclamationA process of consolidating the remaining data from many sequential access volumes onto fewer new sequentialaccess volumes.

reclamation thresholdThe percentage of reclaimable space that a sequential access media volume must have before the server canreclaim the volume. Space becomes reclaimable when files are expired or are deleted. The percentage is set for astorage pool.

recovery logA log of updates that are about to be written to the database. The log can be used to recover from system andmedia failures.

recovery log buffer poolUsed to hold new transactions records until they can be written to the recovery log.

recovery mediaMedia that contains data necessary to recover the TSM server and clients.

reduceThe process of freeing up enough space to allow you to delete a volume from the database or recovery log.Contrast with extend.

REELOn TSM servers that support it, a device class that is used to categorize tape devices that support tape reels, suchas the 3420 9-track tape device.

register(1) Define a client node or administrator who can access the server. See registration. (2) Specify licenses thathave been purchased for the server.

registrationThe process of identifying a client node or administrator to the server.

reply operatorOn a VM server, a VM user ID that specifies an operator who will reply to tape mount requests by the server.

restoreThe process of returning a backup copy to an active storage location for use. TSM has processes for restoring itsdatabase, storage pools, storage pool volumes, and users’ backed-up files. For example, users can copy a backupversion of a file from the storage pool to the workstation. The backup version in the storage pool is not affected.Contrast with backup.

retentionThe amount of time, in days, that inactive backed up or archived files are kept in the storage pool before they aredeleted. Copy group attributes and default retention grace periods for the domain define retention.

retention periodOn an MVS server, a device class attribute that specifies how long files are retained on sequential access media.When used, TSM passes this information to the MVS operating system to ensure that other tape managementsystems do not overwrite tape volumes that contain retained data.

retrieveA function that allows users to copy an archive copy from the storage pool to the workstation. The archive copyin the storage pool is not affected. Contrast with archive.

rollbackTo remove changes that were made to database files since the last commit point.


Glossary

root userIn the AIX and UNIX environments, a user who has superuser authority. The user can log in and executerestricted commands, shut down the system, and edit or delete protected files.

S

SANStorage area network.

scheduleA database record that describes scheduled client operations or administrative commands. See administrativecommand schedule and client schedule.

scheduling modeThe type of scheduling operation set for the server and client. TSM supports two scheduling modes for clientoperations: client-polling and server-prompted.

scratch volumeA volume that is available for TSM use. The volume is labeled, is either blank or contains no valid data, and isnot defined to TSM.

scriptSee TSM command script.

SCSISmall computer system interface.

selective backupA function that allows users to back up specific files or directories from a client domain. With this function,users can back up files or directories that are not excluded in the include-exclude list and that meet therequirement for serialization as defined in the backup copy group of the management class assigned to the files.Contrast with incremental backup.

sequential access mediaAny volume that is accessed in a sequential manner, as opposed to a random manner. In TSM, volumes areaccessed sequentially if they reside in a device class other than DISK.

serializationA copy group attribute that specifies what TSM does if files are modified during back up or archive processing.The value of this attribute determines whether processing continues, is retried, or is stopped. See static, dynamic,shared static, and shared dynamic.

serverThe program that provides backup, archive, space management, and administrative services to clients. The serverprogram must be at the necessary level to provide all of these services.

server migrationThe process of moving data from one storage pool to the next storage pool as controlled by the high and lowmigration thresholds. See high migration threshold and low migration threshold.

server options fileA file that contains settings that control various server operations. These settings, or options, affect such things ascommunications, devices, and performance.

server-prompted scheduling modeA client/server communication technique where the server contacts the client when a scheduled operation needsto be done.

server storageThe primary and copy storage pools used by the server to store users’ files: backup versions, archive copies, andfiles migrated from Tivoli Space Manager client nodes (space-managed files). See primary storage pool, copystorage pool, storage pool volume, and volume.


session resource usageThe amount of wait time, CPU time, and space used or retrieved during a client session.

shared dynamicA copy group serialization value that specifies that a file must not be modified during a backup or archiveoperation. TSM attempts to retry the backup or archive operation a number of times; if the file is in use duringeach attempt, TSM will back up or archive the file on its last try even though the file is in use. See alsoserialization. Contrast with dynamic, shared static, and static.

shared libraryA library device that is shared among multiple Tivoli Storage Manager servers.

shared staticA copy group serialization value that specifies that the file must not be modified during backup or archive. TSMwill retry the backup or archive operation a number of times; if the file is in use during each attempt, TSM willnot back up or archive the file. See also serialization. Contrast with dynamic, shared dynamic, and static.

shellIn the AIX and UNIX environments, a software interface between a user and the operating system of a computer.Shell programs interpret commands and user interactions on devices such as keyboards, pointing devices, andtouch-sensitive screens and communicate them to the operating system.

SMITSystem Management Interface Tool.

SNA LU6.2Systems Network Architecture Logical Unit 6.2.

snapshotSee database snapshot.

socket(1) An endpoint for communication between processes or applications. (2) A pair consisting of TCP port and IPaddress, or UDP port and IP address.

source serverA server that can send data, in the form of virtual volumes, to another server. Contrast with target server.

space-managed fileA file that is migrated from and recalled to a client node via Tivoli Space Manager (HSM client).

space managementThe process performed by Tivoli Space Manager to keep sufficient free storage space available on a client nodeby migrating files to Tivoli Storage Manager storage. The files are migrated based on criteria defined inmanagement classes to which files are bound, and the include-exclude list. Synonymous with hierarchical storagemanagement. See also migration.

space manager clientSynonym for hierarchical storage management (HSM) client.

stale copy statusSpecifies that a volume copy is not available to the database or recovery log.

stanzaA group of lines in a file that together have a common function or define a part of the system. Stanzas areusually separated by blank lines or colons, and each stanza has a name.

startup windowA time period during which a schedule must be initiated.

staticA copy group serialization value that specifies that the file must not be modified during backup or archive. If thefile is modified during the attempt, TSM will not back up or archive the file. See also serialization. Contrast withdynamic, shared dynamic, and shared static.


Glossary

storage area network (SAN)A high-speed communications network optimized for storage.

storage agentA program that enables Tivoli Storage Manager to back up and restore client data directly to and fromSAN-attached storage.

storage hierarchyA logical ordering of primary storage pools, as defined by an administrator with system privilege. Generally, theordering is based on the speed and capacity of the devices that the storage pools use. In TSM, the storagehierarchy is defined by identifying the next storage pool in a storage pool definition. See storage pool.

storage management servicesA component that allows a central system to act as a file backup, archive, and space management server for localarea network file servers and workstations.

storage poolA named set of storage volumes that TSM uses to store client data. A storage pool is either a primary storagepool or a copy storage pool. See primary storage pool and copy storage pool.

storage pool volumeA volume that has been assigned to a TSM storage pool. See volume, copy storage pool, and primary storagepool.

storage privilege classAn administrative privilege class that allows an administrator to control the allocation and use of storageresources for the server, such as monitoring the database, recovery log, and server storage. Administrators can beauthorized with unrestricted or restricted storage privilege.

stub fileA file that replaces the original file on a client node when the file is migrated from the client node to TSMstorage.

subscriptionThe method by which a managed server requests that it receive configuration information associated with aparticular profile on a configuration manager. See managed server, configuration manager, and profile.

superuserSee root user.

synchronized copy statusSpecifies that the volume is the only volume copy or is synchronized with other volume copies in the database orrecovery log. When synchronized, mirroring has started.

system privilege classAn administrative privilege class that allows an administrator to issue all server commands.

Systems Application Architecture (SAA)Software interfaces, conventions, and protocols that provide a framework for designing and developingapplications that are consistent across systems.

Systems Network Architecture (SNA)A set of rules for data to be transmitted in a network. Application programs communicate with each other using alayer of SNA called advanced program-to-program communications (APPC).

T

tape library(1) A term used to refer to a collection of tape cartridges. (2) An automated device that performs tape cartridgemounts and demounts without operator intervention.


Tape Library DataserverAn automated tape library consisting of mechanical components, cartridge storage frames, IBM tape subsystems,and controlling hardware and software. The tape library dataserver performs tape cartridge mounts and demountswithout operator intervention.

tape volume prefixA device class attribute that is the high-level-qualifier of the file name or the data set name in the standard tapelabel.

target serverA server that can receive data sent from another server. Contrast with source server. See also virtual volumes.

TCP/IPTransmission Control Protocol/Internet Protocol.

TelnetIn TCP/IP, the protocol that opens the connection to the system.

Tivoli Disaster Recovery Manager (DRM)A product that works with TSM to assist in preparing and later using a disaster recovery plan for the TSM server.

Tivoli Storage Manager (TSM)A client/server program that provides storage management to customers in a multivendor computer environment.

Transmission Control Protocol/Internet Protocol (TCP/IP)A set of communication protocols that support peer-to-peer connectivity functions for both local and wide areanetworks.

trusted communication agentA program that performs communication tasks on behalf of the client or server, and ensures the security of thecommunications.

TSMTivoli Storage Manager.

TSM application program interface (API)A set of functions that applications running on a client platform can call to store, query, and retrieve objects fromTSM storage.

TSM command scriptA sequence of TSM administrative commands that are stored in the TSM database. The script can includesubstitution for command parameters and conditional logic. You can run the script from any interface to theserver.

U

UCS-2An ISO/IEC 10646 encoding form, Universal Character Set coded in 2 octets. The TSM client on Windows NTand Windows 2000 uses the UCS-2 code page when the client is enabled for Unicode.

Unicode StandardA universal character encoding standard that supports the interchange, processing, and display of text that iswritten in any of the languages of the modern world. It can also support many classical and historical texts and iscontinually being expanded. The Unicode Standard is compatible with ISO/IEC 10646. For more information, seehttp://www.unicode.org.

unit nameOn an MVS server, a device class attribute that specifies a group of tape devices used with the MVS server. Aunit name can be a generic device type, an esoteric unit name, or a physical device.

UNIX System ServicesMVS/ESA services that support an environment within which operating systems, servers, distributed systems, andworkstations share common interfaces. UNIX System Services supports standard application development across


|||

||||

Glossary

multivendor systems and is required to create and use applications that conform to the POSIX standard. UNIXSystem Services was formerly known as OpenEdition® MVS.

UTF-8Unicode transformation format - 8. A byte-oriented encoding form specified by the Unicode Standard.

utilizationThe percent of assigned capacity used by the database or recovery log at a specific point of time.

V

validateThe process of ensuring that the active policy set contains a default management class and reporting on copygroup definition errors.

versionA backup copy of a file stored in server storage. The most recent backup copy of a file is the active version.Earlier copies of the same file are inactive versions. The number of versions retained by the server is determinedby the copy group attributes in the management class.

Virtual Machine (VM)One of the family of IBM operating systems for the System/390 processor, including VM/ESA®.

virtual serverIn a Microsoft cluster configuration, an MSCS cluster group that appears to be a single Windows server. Thevirtual server has a network name, an IP address, one or more physical disks, and a service.

Virtual Storage Extended (VSE)One of the family of IBM operating systems for the System/390 processor, including VSE/ESA™.

virtual volumeA volume that appears to be a sequential media volume on a source server but that is actually stored as anarchive file on a target server.

VMVirtual Machine.

volumeThe basic unit of storage for the TSM database, recovery log, and storage pools. A volume can be an LVMlogical volume, a standard file system file, a tape cartridge, or an optical cartridge. Each volume is identified bya unique volume identifier. See database volume, scratch volume, and storage pool volume.

volume history fileA file that contains information about: volumes used for database backups and database dumps; volumes used forexport of administrator, node, policy, or server data; and sequential access storage pool volumes that have beenadded, reused, or deleted. The information is a copy of the same types of volume information in the TSMdatabase.

VSEVirtual Storage Extended.

W

wildcard characterA special character such as an asterisk (*) or a question mark (?) that can be used to represent one or morecharacters. Any character or set of characters can replace a wildcard character. Also called pattern-matchingcharacter.

WORMA type of optical media that can only be written to and cannot be erased.


||

|||

|||

|||

X

X WindowsA network transparent windowing system developed by MIT. It is the basis for other products, such as EnhancedX Windows which runs on the AIX operating system.

Z

z/OSAn IBM operating system based on the 64–bit z/Architecture.


|

|

||

Glossary

Index

Numerics3172 Communication Controller 383174 Communication Controller 38

AACTIVATE POLICYSET command 90activating

policy set 90administrative client

description 97ending 16starting 13, 14Web interface 4, 54, 103

administrative client optionsstarting 14

administrative command-line interface 103administrative commands

ACTIVATE POLICYSET 90COPY DOMAIN 89DEFINE ASSOCIATION 92DEFINE DBCOPY 84DEFINE DEVCLASS 86DEFINE LOGCOPY 84DEFINE SCHEDULE 92, 94DEFINE STGPOOL 86DEFINE VOLUME 83, 84, 87EXPIRE INVENTORY 91, 94HALT 16QUERY EVENT 93, 94REGISTER NODE 18UPDATE ADMIN 13UPDATE COPYGROUP 89UPDATE STGPOOL 87VALIDATE POLICYSET 90

ADSM.SAMPLIB jobs 1advanced tasks xiallocate datasets 5ANRIDL job for web interface 4ANRINST startup job 9archive

description x, 19, 97to tape 85, 87, 88

archive copy group x, 89associating

clients with policy domains 89clients with schedules 92

automatingadministrative commands 94client operations 92, 100

Bbackup

copy group x, 89description x, 12, 19, 97, 98selective 20to tape 85, 87, 88

backup-archive clientdescription 97register 18

CCARTRIDGE device class 86client

configuring to the MVS server 39client node, TSM

description 12, 19registration 18

command-line interfaceOS/2 16

command-line interface, administrativeinteractive mode 108quitting 108starting 108using 108

command scripts 4commands, administrative

ACTIVATE POLICYSET 90COPY DOMAIN 89DEFINE ASSOCIATION 92DEFINE DBCOPY 84DEFINE DEVCLASS 86DEFINE LOGCOPY 84DEFINE SCHEDULE 92, 94DEFINE STGPOOL 86DEFINE VOLUME 83, 84, 87EXPIRE INVENTORY 91, 94HALT 16QUERY EVENT 93, 94REGISTER NODE 18UPDATE ADMIN 13UPDATE COPYGROUP 89UPDATE STGPOOL 87VALIDATE POLICYSET 90

commands, clientQUIT 16SELECTIVE 20

communication methodsHTTPICS 54HTTPTCP 54

configuringAIX SNA Server/6000 clients using SMIT 50


Index

configuring (continued)cross-domain network 36for 3270 Emulation 11for APPC 51for interlink SNS/TCPACCESS 54for IUCV 54for TCP/IP 35, 54network clients 19OS/2 clients using communication manager/2

defining partner LU configuration 47SNA connections 47SNA features 47SNA local node characteristics 42

server communications 10single-domain network 38TSO administrative clients 40

connection failuresdiagnosing 68

connectivity support 32, 50continuation characters 12conventions used in this book ixCOPY DOMAIN command 89CPI-C

analyzing return codes 69determining return codes 68level-2 support 70sense information 71

Ddata set allocation 5data storage 5database

formatting 10default

disk storage pool volume 83management class 89

DEFINE ASSOCIATION command 92DEFINE DBCOPY command 84DEFINE DEVCLASS command 86DEFINE LOGCOPY command 84DEFINE SCHEDULE command 92, 94DEFINE STGPOOL command 86DEFINE VOLUME command 83, 84, 87defining

archive copy group 89backup copy group 89client node 18database volume 84management class 89policy 88, 89policy domain 89policy set 89storage pool 86storage pool volume 83

device classCARTRIDGE 86default 86defining 86

device class description 99disaster, protecting against 3, 94disaster recovery

disk storage pool volumes 84mirror volumes 84recovery log volumes 84

disk space for installation 1disk storage pools

default volume size 83defining initial volume 84

documentation, TSM 119dsmsched.log 93

Eending the administrative client 16expiration

description 99interval (server option) 91processing 94, 99server option 91

EXPIRE INVENTORY command 91, 94

Ffirewall 54format database 10format recovery log 10

Ggraphical user interface

client 16

HHALT command 16halting the server 16HX command 16

IIBM Redbooks 122include-exclude list 91incremental backup 19initial configuration wizards 19initializing

server 9tape volumes 87


installingover a previous version

prerequisites 5procedure 1, 5

remote clients 19interfaces, administrative

administrative Web interface 103command line 108

JJCL 12

Llabel, tape 87license, TSM 17

Mmanagement class

default 90, 92description 98

migrate to version 3 3migrating to tape 85, 87, 88migration

hierarchy 85, 87server storage 97thresholds 87

mount limit, description 85MVS

setup 37

Nnetwork client 19network environment 19Novell Netware

configuring netware 47creating CSCON configuration profile 47defining local LU configuration 48

Ooptions file

servercreating 10

OS/2considerations for using OS/2 clients 47DSMADMC 16

OS/2 (continued)starting the administrative client 16

Ppassword, administrative client

changing 13policy

description 97using 88, 90

policy domainassociating a client with 89defining 89

policy setactivating 90validating 90

protecting data 94

QQUERY EVENT command 93, 94querying

events 93, 94

Rrecovery log

formatting 10redbooks 122REGISTER NODE command 18registering

client node 18remote client 19results files 74runfile command 4

Sscheduling

administrative commands 94client operations 92

scratch volumesdescription 86

scripts, TSM command 4Secure Web Administrator Proxy

CD-ROM 110description 109FTP site 110installing and configuring 110prerequisites 110troubleshooting 112uninstalling 112


Index

selective backup 12, 19server, TSM

basic install and setup 1changing options 91configuring for 3270 Emulation 11configuring for APPC 51configuring for interlink SNS/TCPACCESS 54configuring for IUCV 54configuring for TCP/IP 35, 54defining storage pool volumes 84description 97halting 16initialization 2normal operation 11options 91stopping 16storage 97storage migration 85, 87, 99verifying configuration 19

server/client communicationsconfiguring 10

server optionscreating file 9

SNA LU6.2profile for AIX clients 75

software requirements using APPC 74space management (HSM)

description 97storage pool size 97

standard label 87starting

administrative client 13, 14client scheduler 93OS/2 administrative client 13, 16

startup job ANRINST 9stopping

client 16server 16

storage poolARCHIVEPOOL 83, 85, 87, 88BACKUPPOOL 83, 85, 87, 88default 88description 12, 19, 97, 98, 99disk 83SPACEMGPOOL 83, 85, 88volumes 99

storage volumes 83

Ttape

devices 85, 86volumes, initializing 87volumes, labeling 87

TAPE command 87tape installation-wide exits 115tape management system 85TCP/IP

configuring the server 35, 54

threshold, migration 87Tivoli Disaster Recovery Manager (DRM) 3TSM concepts 97TSO administrative client 14

UUPDATE ADMIN command 13UPDATE COPYGROUP command 89UPDATE STGPOOL command 87updating

copy group 89storage pool 87

upgrade to version 3 3

VVALIDATE POLICYSET command 90validating a policy set 90version 3 upgrade 3volume

defining 84, 87private 87

VTAMNCP 36setup 33, 50

Wweb server 109


Program Number: 5698–TSM5697–TS9

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC35-0415-01

Spin

ein

form

atio

n:

TivoliStorageManager

forOS/39

0andz/OS

Qui

ckSt

art,

Vers

ion

4R

elea

se2

publib.boulder.ibm.compublib.boulder.ibm.com/tividd/td/tsm390n/gc35-0415... · contents...

Documents