DSM/Tape Catalog User’s Guide Abstract This user’s guide describes the Distributed Systems Management/Tape Catalog (DSM/TC) software product, which lets users organize, manage, and track tape volumes. This guide describes the components of DSM/TC and provides instructions and examples on how to configure, run, and maintain the DSM/TC system. Product Version DSM/TC H01 Supported Release Version Updates (RVUs) This manual supports G06.23 and all subsequent G-series RVUs, H06.
Document History Part Number Product Version Published 520233-003 DSM/TC G06 April 2004 520233-004 DSM/TC G06 June 2004 520233-005 DSM/TC G06 January 2007 520233-006 DSM/TC H01 February 2008 520233-008 DSM/TC H01 February 2013
Legal Notices Copyright 2013 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
DSM/Tape Catalog User’s Guide Index Tables Legal Notices What’s New in This Manual vii Manual Information vii New and Changed Information vii About This Manual ix Audience ix Manual Organization ix Related Publications x Notation Conventions x 1.
Contents 2. Tape File Concepts 2. Tape File Concepts File Generations 2-1 Absolute Generations 2-3 Relative Generations 2-3 Tape File Version 2-5 File Retention Period 2-6 Sources of Retention Period and Expiration Date 2-6 Expiration Date for an Incomplete Tape File 2-8 Tape File Expiration 2-10 Manual Tape File Expiration 2-10 SQL Warning Message 6008 2-11 3.
Contents 6. Using TAPECATALOG DEFINE Attributes Task 4. Start $ZSVR 5-2 Task 5. Install DSM/TC Catalog Manager (MEDIADBM) 5-3 Task 6. Create File Catalogs, Volume Catalogs, and Pools 5-3 Creating File Catalogs 5-3 Creating Volume Catalogs 5-4 Creating Pools 5-5 Task 7.
Contents 8.
Contents 9. Database Design of DSM/TC Nonretryable Errors 8-9 9.
Contents B. CLASS TAPECATALOG DEFINE Syntax Summary B. CLASS TAPECATALOG DEFINE Syntax Summary C. CLASS TAPECATALOG DEFINE Consistency Checks D. CLASS TAPE DEFINE to CLASS TAPECATALOG DEFINE Conversion E. CLASS TAPE/TAPECATALOG DEFINE Equivalent Attributes Index Tables Table 3-1. Table 4-1. Table 6-1. Table 6-2. Table C-1. Table E-1.
What’s New in This Manual Manual Information DSM/Tape Catalog User’s Guide Abstract This user’s guide describes the Distributed Systems Management/Tape Catalog (DSM/TC) software product, which lets users organize, manage, and track tape volumes. This guide describes the components of DSM/TC and provides instructions and examples on how to configure, run, and maintain the DSM/TC system. Product Version DSM/TC H01 Supported Release Version Updates (RVUs) This manual supports G06.
What’s New in This Manual Changes in the H06.13 RVU: Updated the section Setting the System Defaults on page A-1. Changes in the H06.13 RVU: Updated the description on page 1-11 to specify the default number of disk files as 20,000, and added a caution on 1-11. Updated the description on 1-15 to specify that cataloging can be requested only for the disk file name of the output volume set with user-defined catalogfiles number, and added a caution on page 1-15.
About This Manual This manual is a guide to the basic concepts and functions of the Distributed Systems Management/Tape Catalog (DSM/TC) product. It provides introductory and conceptual information, and configuration and usage guidelines for users who are responsible for configuring, managing, and maintaining the DSM/TC software system. Audience The primary audience is system administrators who are responsible for configuring a tape management system.
About This Manual Related Publications Section Description Appendix B, CLASS TAPECATALOG DEFINE Syntax Summary Provides a complete CLASS TAPECATALOG DEFINE syntax summary. Appendix C, CLASS TAPECATALOG DEFINE Consistency Checks Contains a table of CLASS TAPECATALOG DEFINE consistency checks. Appendix D, CLASS TAPE DEFINE to CLASS TAPECATALOG DEFINE Conversion Shows how to convert from a CLASS TAPE DEFINE to a CLASS TAPECATALOG DEFINE.
About This Manual General Syntax Notation lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.c italic computer type.
About This Manual General Syntax Notation An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char…" Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.
About This Manual Notation for Messages !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum , [ filename:maxlen ] ) ; !i !o:i Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text. Bold text in an example indicates user input typed at the terminal.
About This Manual Notation for Management Programming Interfaces either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line.
About This Manual Change Bar Notation Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
About This Manual Change Bar Notation DSM/Tape Catalog User’s Guide — 520233-008 xvi
1 Introduction to DSM/TC Distributed Systems Management/Tape Catalog (DSM/TC) is a software system that manages tape files and labeled magnetic tapes (open reel and cartridge) in a NonStop Kernel environment. Using this system: A tape file can be accessed by name only. You need not know the name of the tape containing the tape file. Tape files are protected from being accidentally overwritten.
Introduction to DSM/TC Operational Characteristics The automatic revision of a tape’s status by DSM/TC as the tape cycles through the process of being a scratch tape, of having data written to it, and of becoming a scratch tape again For more information on TAPECATALOG DEFINE attributes, see: Section 6, Using TAPECATALOG DEFINE Attributes Appendix B, CLASS TAPECATALOG DEFINE Syntax Summary Appendix C, CLASS TAPECATALOG DEFINE Consistency Checks Appendix D, CLASS TAPE DEFINE to CLASS TAPECA
Introduction to DSM/TC The MEDIACOM Interface and Its Commands The MEDIACOM Interface and Its Commands MEDIACOM is an operator interface for labeled-tape operations. MEDIACOM is also the operator interface to the DSM/TC system. This interactive program can be run from any node in a DSM/TC system. MEDIACOM commands executed during a session take effect immediately on the DSM/TC node specified. (Command syntax lets you specify the node.
Introduction to DSM/TC Volume Catalog Volume catalog entries stay in the catalog indefinitely. They do not have expiration dates. These entries represent a magnetic tape in the DSM/TC system for as long as the tape is usable. During a tape’s usable lifetime, it alternates between being a scratch tape and a tape containing one or more files. When a tape is no longer usable (it is damaged, lost, permanently removed, or discarded), its volume catalog entry is removed with a DELETE TAPEVOLUME command.
Introduction to DSM/TC Volume Catalog In the second stage (selected as an output tape), two states are possible: Selected DSM/TC selected the tape as an output tape to satisfy the request of a TAPECATALOG DEFINE. This status is brief, indicating that the tape is reserved for use and should be mounted on a tape drive in the next few minutes. It also protects the tape from being requested by another application prior to being mounted on the drive.
Introduction to DSM/TC Tape Pools Use of multiple volume catalogs can improve Media Catalog performance. Tape Pools Tape pools are arbitrary divisions of a volume catalog used to group tapes by physical characteristics, by their owners, by their users, and so on. A volume catalog can have as many pools as you need, but it must have at least one. Each pool name in a volume catalog must be unique.
Introduction to DSM/TC Append Capable Pools Manual: Change status to FULL to prevent the tape from being used as an assigned tape until some future time. Change the status to BAD to prevent the tape from being used as a scratch tape. Usually pools are defined with an AUTOSCRATCH value that permits immediate use of their tapes after the tapes’ files expire. However, for special cases, pools can be defined so that tapes with expired files receive a status of released.
Introduction to DSM/TC Tape Volumes HP recommends using APPEND ON only for tapes of label type BACKUP. APPEND is not supported on 517x tape drives. The APPEND pool attribute can be turned ON or OFF (default) at pool creation. For a description of the MEDIACOM, ADD POOL command, see the DSM/Tape Catalog Operator Interface (MEDIACOM) Manual. If a pool is created with APPEND ON, all tape volumes of label type BACKUP added to the pool are eligible for multiple tape files per volume set.
Introduction to DSM/TC Tape Volumes ALTER TAPEVOLUME command, see the DSM/Tape Catalog Operator Interface (MEDIACOM) Manual. These rules apply: When a tape volume of label type BACKUP that resides within an append capable pool is altered from ASSIGNED to FULL, it is no longer available for use until it is either returned to ASSIGNED or has been expired.
Introduction to DSM/TC Tape Files Tape Files The MEDIACOM ADDTAPEFILE directive is not supported for append capable pools. All TAPEFILEs associated with a volume set must be cataloged in the same file catalog. TAPEFILE deletion and expiration are much the same as with ANSI and IBM label types that contain multiple FILESEQUENCE tape file sets.
Introduction to DSM/TC File Catalog Tracked Information Tape File Entry Disk File Entry Comment text specified in the DEFINE request X Names of the tape media that contain the file X X Name of the tape’s volume catalog and pool X X Order the tapes were used if the file spans two or more tapes X X Order the file was written if more than one file was written to a volume set X X Tape file entry that owns the disk file entry X Names of the tape media in a multitape volume set that contains
Introduction to DSM/TC The CLASS TAPECATALOG DEFINE created and then reach the end of their retention period. For more information on retention periods, see File Retention Period on page 2-6. As the entries expire, they are marked invalid. Instead of being removed at the next clean-up run, they stay in the catalog until the last tape file on the volume set expires. They are all deleted at the next clean-up run.
Introduction to DSM/TC The CLASS TAPECATALOG DEFINE Access tape files that were previously cataloged A DEFINE request specifies all the necessary information about the chosen tape file or scratch tape by using a series of attributes. When an application opens a file requiring an input or output tape, the information in the DEFINE is sent to $ZSVR, the operating system tape server process.
Introduction to DSM/TC CATALOGFILES Option of BACKUP and BACKCOPY Note. Unless otherwise stated, this manual discusses a TAPECATALOG DEFINE with the assumption that the DEFINE is being used to access DSM/TC. To access DSM/TC, the DEFINE specifies the CATALOG attribute as ON or does not use the CATALOG attribute, in which case CATALOG defaults to ON. CATALOGFILES Option of BACKUP and BACKCOPY Backing up data is an essential task at most installations.
Introduction to DSM/TC CATALOGFILES Option of BACKUP and BACKCOPY File-Mode Backup Cataloging the copied disk files when you run the BACKUP utility in file mode, DSM/TC tracks which disk file entry belongs to which tape. Needed tape volumes can be automatically selected when restoring. This makes individual file recovery more efficient than without using CATALOGFILES. CATALOGFILES does not apply to Backup Restore 2.0 BACKUP.
Introduction to DSM/TC 7> 7> 7> 7> 7> 8> & & & & & DSM/TC System Terms LABELS BACKUP,& POOL OPERATIONS_TAPES,& VOLUME SCRATCH,& FILEID WEEKLY_PAYROLL,& GEN 4 BACKCOPY =COPY_IN, =COPY_OUT, *.*.
Introduction to DSM/TC System Search Space Example If you have three nodes in your DSM/TC system (named \SKY, \STAR, and \SEA), after the DSM/TC software is installed, you must issue three ALTER MEDIADEFS commands to create a system search list on each node. These examples show partial syntax of the commands: MC> ALTER MEDIADEFS \SKY ... SSLIST (\SKY, \STAR, \SEA) ... MC> ALTER MEDIADEFS \STAR ... SSLIST (\STAR, \SKY, \SEA) ... MC> ALTER MEDIADEFS \SEA ... SSLIST (\SEA, \SKY, \STAR) ...
Introduction to DSM/TC To perform a variety of tasks for DSM/TC on both nodes, but issue MEDIACOM commands only from \ROSE: 18> MC> MC> MC> MC> MC> MC> MC> MC> MC> Current Default Node MEDIACOM (MEDIACOM will run on \ROSE.) (Commands affect \ROSE until VOLUME command.) ALTER POOL TEST_TAPES, VOLCAT TAPE_CAT, DENSITY 6250 . . VOLUME \TREE (All commands now affect \TREE.) ALTER POOL OPS_TAPES, VOLCAT TAPE_CAT, RESET TYPE . .
Introduction to DSM/TC Role-based flexibility in handling MEDIACOM commands Role-based flexibility in handling MEDIACOM commands The authority to execute the sensitive MEDIACOM commands DELETE TAPEFILE, ALTER TAPEFILE, and ALTER MEDIADEFS is restricted, by default, only to the super group. However, from H06.26/J06.15 RVU onwards, support for role-based flexibility enables you to authorize non-super group users to execute these MEDIACOM commands.
Introduction to DSM/TC Role-based flexibility in handling MEDIACOM commands DSM/Tape Catalog User’s Guide — 520233-008 1 - 20
2 Tape File Concepts DSM/TC manages tape files based on the information in their tape file entries. Some data stored in the catalog is also stored in the label of a tape, but tape label information is always secondary to DSM/TC information. If there is a conflict between the tape label data and the DSM/TC database, DSM/TC satisfies or rejects a tape request based on the information in its database.
Tape File Concepts File Generations Example Assume that every Monday an application runs that requests the latest generation of MASTER_ACCT with this DEFINE: 90> 90> 90> 90> ADD & & & DEFINE =IN, CLASS TAPECATALOG,& USE IN,& FILEID MASTER_ACCT,& GEN -1 When running the application at the fifth week on March 2, the =IN DEFINE retrieves generation 4 of MASTER_ACCT on tape T00155 as the input file, and the new output file is cataloged as generation 5 on tape T00188: Tape File Name Tape Name Generatio
Tape File Concepts Absolute Generations Absolute Generations Every generation of a tape file entry has an absolute generation number, which is the number it was given when the entry was created (1, 2, 3, and so on). When you want a particular generation of a tape file, you can use an absolute generation number in the GEN attribute of the TAPECATALOG DEFINE. Example For example, assume a special report is required from the data in generation 3 of MASTER_ACCT.
Tape File Concepts Relative Generations Example This example shows four generations of CALIF_ACCOUNTS in a file catalog as of January 27: Tape File Name Tape Name Absolute Generation Relative Generation Date Created CALIF_ACCOUNTS X00015 1 -4 January 6 CALIF_ACCOUNTS X00025 2 -3 January 13 CALIF_ACCOUNTS X00032 3 -2 January 20 CALIF_ACCOUNTS X00045 4 -1 January 27 On January 27, a special report is needed from the data in the second generation of CALIF_ACCOUNTS on tape X00025.
Tape File Concepts Tape File Version Tape File Version A version of a tape file can be viewed as a subdivision of a generation. Usually, there is only one version of a tape file entry. But if there is any problem with the existing tape file, you could instruct the operator to revise the output tape DEFINE before rerunning the application so that a new version is made instead of a new generation. DSM/TC lets only one version in a generation be valid—the latest version entered in the file catalog.
Tape File Concepts File Retention Period three versions, if MASTER_OUT is the only file in the volume set, version 0 and 1 of generation 3 will have expired and been deleted.) File Retention Period When a tape file is created, it is given an expiration date to define how long to retain the tape file past its creation date. This date is stored in the file’s tape file entry.
Tape File Concepts Sources of Retention Period and Expiration Date using a MEDIACOM ALTER TAPEFILE command. When that date is reached, the entry expires. The DSM/TC default value for retention period When you do not specify the EXPIRATION or RETENTION attributes in a DEFINE, a default retention period is converted to an expiration date for you. To set a default retention period, use a MEDIACOM ALTER MEDIADEFS command for each node in the DSM/TC system.
Tape File Concepts Expiration Date for an Incomplete Tape File The tape file entry for YEAR_END_REPORT stays in the catalog until an operator removes it with a MEDIACOM DELETE TAPEFILE command or until it reaches an expiration date assigned later with an ALTER TAPEFILE command. Expiration Date for an Incomplete Tape File An application that comes to an abnormal end could produce a tape file that is somehow incomplete and probably should not be used as input.
Tape File Concepts Expiration Date for an Incomplete Tape File the job, the application would request the incomplete file as the current generation to read. Another advantage is that this procedure does not leave gaps in the absolute generation numbers. This procedure is also effective when your application uses the same tape file names for input and output tape files. Immediately deleting the incomplete tape file entry prevents another application from requesting it.
Tape File Concepts Tape File Expiration Generation 3 has two versions of MASTER_OUT. Because DSM/TC allows only one valid version in a generation, it marks the most current entry for generation 3 the valid one, which is the file created from the rerun. Tape File Expiration File catalog entries with a status of invalid stay in the file catalog until the next run of the clean-up process.
Tape File Concepts SQL Warning Message 6008 SQL Warning Message 6008 Under certain conditions, for example, when a large amount of data is added to a DSM database in a time period before the automatic file expiration process has run, this SQL warning message can be output to the console that is executing a MEDIACOM session: 6008 STATISTICS OR PARTITIONS FOR A TABLE WERE NOT AVAILABLE SO THE ACCESS PATH CHOSEN MIGHT NOT BE THE BEST AVAILABLE.
Tape File Concepts SQL Warning Message 6008 DSM/Tape Catalog User’s Guide — 520233-008 2 - 12
3 DSM/TC Tape Processing This section addresses various aspects of selecting and using magnetic tapes: Topic Page Levels of Tape Processing Support 3-1 Labeled Tapes 3-2 Volume Set 3-2 DSM/TC Interaction With $ZSVR 3-9 Status Changes in a Volume Catalog Entry 3-11 Premounted Output Tapes 3-12 Substituting Scratch Tapes 3-13 Levels of Tape Processing Support To configure a NonStop Kernel node for a specific level of tape support, use the LEVEL option of the MEDIACOM ALTER MEDIADEFS command.
DSM/TC Tape Processing Labeled Tapes emergency with the hardware at a site. If some processing is still necessary during an emergency, you can switch to the COMPATIBLE tape support level to use TAPE DEFINEs for tape requests. Labeled Tapes DSM/TC is designed to manage files stored on labeled magnetic tapes. It does not support unlabeled tapes and their files. Some of the information about a tape and a tape file is written in the tape’s label, and that information is duplicated in the catalog system.
DSM/TC Tape Processing Copying a Volume Set Created by the BACKUP Utility For example, this table shows two volume sets. The first volume set is one tape with two files. The second volume set is three tapes with four files.
DSM/TC Tape Processing Copying a Volume Set Created by the BACKUP Utility You can check the value of the logical copy using one of the following: MEDIACOM command: info tapefile ,detail SQLCI command from the volume where the tapefile is present: select * from tapefile For example, assume that system \A contains a file id Test1 with gen 1.
DSM/TC Tape Processing Copying a Volume Set Created by the BACKUP Utility 3> & 3> & 3> & POOL OPERATIONS_TAPES,& VOLUME SCRATCH,& FILEID PAYROLL_BACKUP 4> 4> 4> 4> 4> 4> DEFINE =OUT2, CLASS TAPECATALOG,& USE OUT,& LABELS BACKUP,& POOL OPERATIONS_TAPES,& VOLUME SCRATCH,& FILEID PAYROLL_BACKUP ADD & & & & & 5> BACKUP (=OUT1, =OUT2), $PAY.*.*, LISTALL, CATALOGFILES You cannot use the same DEFINE twice, even if they are identical as in this example.
DSM/TC Tape Processing 9> & 9> & 10> 10> 10> 10> 10> 10> 10> Copying a Volume Set Created by the BACKUP Utility FILEID PAYROLL_BACKUP,& GEN 1 ADD & & & & & & DEFINE =OUT2, CLASS TAPECATALOG,& USE OUT,& LABELS BACKUP,& POOL OPERATIONS_TAPES,& VOLUME SCRATCH,& FILEID PAYROLL_BACKUP,& GEN 1 11> BACKCOPY =IN, (=OUT1, =OUT2), *.*.
DSM/TC Tape Processing 13> & 13> & Copying a Volume Set Created by the BACKUP Utility FILEID PAYROLL_BACKUP,& GEN 1 14> BACKCOPY =IN, =OUT3, *.*.*, CATALOGFILES 15> 15> 15> 15> ADD & & & DEFINE =IN, CLASS TAPECATALOG,& USE IN,& LABELS BACKUP,& FILEID PAYROLL_BACKUP 16> 16> 16> 16> 16> 16> 16> ADD & & & & & & DEFINE =OUT4, CLASS TAPECATALOG,& USE OUT,& LABELS BACKUP,& POOL OPERATIONS_TAPES,& VOLUME SCRATCH,& FILEID PAYROLL_BACKUP,& GEN 1 17> BACKCOPY =IN, =OUT4, *.*.
DSM/TC Tape Processing Copying a Volume Set Created by the BACKUP Utility When converting your site to DSM/TC, you need to catalog a backup volume set that was created before DSM/TC was in use, but not its disk files: MC> ADD TAPEFILE OPR_MONDAY_BACKUP,& >>> MODE BACKFILE,& >>> EXPIRATION OCT 15 1993 DSM/Tape Catalog User’s Guide — 520233-008 3-8
DSM/TC Tape Processing Copying Volume Sets Not Created by BACKUP or BACKCOPY When converting your site to DSM/TC and you need to catalog a backup volume set that was created before DSM/TC was in use, including all its disk files, you must copy the backup tape with the BACKCOPY utility, using the CATALOGFILES option: 12> 12> 12> 12> 12> ADD & & & & DEFINE =IN, CLASS TAPE,& USE IN,& LABELS BACKUP,& FILEID OPS_BACKUP,& VOLUME (A00020) 13> 13> 13> 13> 13> 13> ADD & & & & & DEFINE =OUT, CLASS TAPEC
DSM/TC Tape Processing DSM/TC Interaction With $ZSVR replacement tapes during audit dump restoration if multiple parallel or serial audit dumps were performed, use the MEDIACOM ALTER TAPEMOUNT request. DSM/TC Interaction With $ZSVR To use MEDIACOM commands effectively, you should understand how the NonStop Kernel tape server process, $ZSVR, and DSM/TC interact with each other.
DSM/TC Tape Processing How $ZSVR Manages Tape Requests b. $ZSVR sends a mount message to the event message collector and any terminal acting as the tape console. The message tells the operator which tape to mount on a tape drive. c. After the operator mounts the tape, $ZSVR uses AVR to find the drive on which the tape is mounted and to make sure the tape name is the same as the one in the mount message. d. When $ZSVR locates the correct tape drive, it connects it to the application so it can use the tape.
DSM/TC Tape Processing Status Changes in a Volume Catalog Entry Status Changes in a Volume Catalog Entry The availability of a tape for a read or write operation is determined solely by the status of its volume catalog entry. With the exception of bad, the entry’s status is changed by DSM/TC in real time to reflect what is happening to the tape after it is requested by a DEFINE. Status Changes for an Input Tape Tapes used for input already contain one or more files.
DSM/TC Tape Processing Premounted Output Tapes Example This DEFINE requests a scratch tape by its name: 5> 5> 5> 5> 5> 5> ADD DEFINE =OUTFILE, CLASS TAPECATALOG,& & LABELS ANSI,& & FILEID TEST_DATA_12,& & VOLUME TAP046,& & POOL TEST_TAPES,& & USE OUT 6> FUP COPY $DATA.OPER.RECDS, =OUTFILE To satisfy this request, these actions take place after $ZSVR receives the DEFINE information. Each step also describes the status changes as they occur in the volume catalog entry for TAP046: 1.
DSM/TC Tape Processing Substituting Scratch Tapes Substituting Scratch Tapes To request scratch tapes, use a DEFINE request with the VOLUME attribute. You can request them generically with VOLUME SCRATCH or specifically by their names, such as VOLUME (B34, B59, C60). In some cases, DSM/TC or an operator substitutes a different scratch tape for the one originally requested. A tape can be a scratch tape or, if the label type is BACKUP, a partially filled appended tape. Table 3-1.
DSM/TC Tape Processing 10> & 10> & 10> & Using VOLUME (Tape Name) USE OUT,& POOL TEST_MISC,& FILEID SALES_REPORT_LOCAL When your application opens the output file, $ZSVR takes the usual steps to obtain the name of a scratch tape from DSM/TC. $ZSVR receives the name TAP15 and issues a mount message for it: ...
DSM/TC Tape Processing Using VOLUME (Tape Name) pool designated in the DEFINE and reserves it. If another tape name is in the list and passes verification, it is reserved. 2. $ZSVR issues a mount message for the substituted tape name received from DSM/TC and then connects the tape drive to the application after it determines which drive the tape is on. Note. When scratch tapes are named by the VOLUME attribute, the operator must mount the tape named in the mount message.
DSM/TC Tape Processing Using VOLUME (Tape Name) This example illustrates an automatic substitution by DSM/TC and a substitution by the operator. This DEFINE names three scratch tapes for an output tape file: 32> 32> 32> 32> 32> 32> ADD & & & & & DEFINE =WRITE_LARGE_FILE, CLASS TAPECATALOG,& USE OUT,& POOL MIS_TAPES,& LABELS ANSI,& FILEID MONTH_END_SUMMARY,& VOLUME (B01120, B01121, B01122) In this example, tape B01120 passes verification, and the operator is asked to mount the tape: ...
DSM/TC Tape Processing Using VOLUME (Tape Name) DSM/Tape Catalog User’s Guide — 520233-008 3 - 18
4 Role-based flexibility The authority to execute the sensitive MEDIACOM commands DELETE TAPEFILE, ALTER TAPEFILE, and ALTER MEDIADEFS is restricted only to the super group. H06.26/J06.15 RVU onwards, support for role-based flexibility enables you to authorize non-super group users to execute these MEDIACOM commands. With this support, you can also deny permissions to specific users to execute these commands.
Role-based flexibility Guidelines This command provides all the permissions to the users of the group 121,*. The security levels can be altered by specifying R, W, E, P, C, or O. Note. If the SECURITY-MEDIA-ADMIN group is frozen, then the users having both O and E permissions are only permitted to execute these MEDIACOM commands. For more information on ADD GROUP, ALTER GROUP, or ADD USER, see Safeguard Reference Manual.
Role-based flexibility Troubleshooting The user is a member of the Safeguard SECURITY-MEDIA-ADMIN group. If the user is a member of SECURITY-MEDIA-ADMIN group, then check whether the user has sufficient permissions to execute the MEDIACOM commands. DENY ACL is not set for the user in the SECURITY-MEDIA-ADMIN group. The SECURITY-MEDIA-ADMIN group exists, and the user is a member of the group with required permissions. If these conditions are met, check whether the group is FROZEN.
Role-based flexibility Troubleshooting Verify if any member of the super group is added explicitly to the SECURITYMEDIA-ADMIN group. The MEDIACOM SPR is the latest, and the requisite standard security and Safeguard SPRs are installed on the system. Scenario 5: System is configured to allow only a non-super user to execute the MEDIACOM commands listed in Table 4-1, but the super user is also able to execute these commands.
5 Configuring DSM/TC This section describes how to configure DSM/TC: Topic Page Task 1. Enable Labeled Tape Processing 5-1 Task 2. Enable TMF Database Protection 5-2 Task 3. Create an SQL/MP System Catalog 5-2 Task 4. Start $ZSVR 5-2 Task 5. Install DSM/TC Catalog Manager (MEDIADBM) 5-3 Task 6. Create File Catalogs, Volume Catalogs, and Pools 5-3 Task 7.
Configuring DSM/TC Task 2. Enable TMF Database Protection Task 2. Enable TMF Database Protection DSM/TC catalogs and configuration tables are audited and therefore protected by TMF. HP highly recommends that you use full (rollforward) TMF protection. For DSM/TC installation and configuration, you must have TMF running. For more information on enabling TMF protection, see the TMF Reference Manual. Task 3.
Configuring DSM/TC Task 5. Install DSM/TC Catalog Manager (MEDIADBM) Example This is an example of an OBEY file to start ZSERVER using the three AUTOEXPIRE parameters: param AUTOEXPIRE^DISABLE param AUTOEXPIRE^UPDATE^STATS param AUTOEXPIRE^TIME FALSE TRUE 18:30 ZSERVER/name $ZSVR, cpu 2, nowait/1 Task 5. Install DSM/TC Catalog Manager (MEDIADBM) 1. To use another catalog beside the system catalog to store configuration tables: a. Create a user catalog using CREATE CATALOG. b.
Configuring DSM/TC Creating Volume Catalogs Examples To create a file catalog on the current default node (if there is no NonStop SQL/MP database in the subvolume, DSM/TC creates one): MC> CREATE FILECAT FILE_CATALOG_SKY,& >>> SUBVOL $V101.CATALOG,& >>> SECURE “NG-O”,& >>> OWNER 5,149 To create a file catalog on a different node: MC> CREATE FILECAT \SEA.FILE_CATALOG_OPS_SEA,& >>> SUBVOL \SEA.$SYS01.
Configuring DSM/TC Creating Pools To create a file and volume catalog on the same subvolume of the current default node (the catalogs have the same logical names; this is required when the file and volume catalog are on the same subvolume): MC> CREATE FILECAT TAPE_CATALOG,& >>> SUBVOL $IRIS.TAPECAT,& >>> SECURE “NC-O”,& >>> OWNER 5,149 MC> CREATE VOLCAT TAPE_CATALOG,& >>> SUBVOL $IRIS.
Configuring DSM/TC Task 7. Define DSM/TC Defaults Using MEDIACOM To create a pool of cartridge tapes physically stored and used in a tape library: MC> ADD POOL ACS_TAPES,& >>> VOLCAT MASTER_TAPE_CATALOG,& >>> LABELS ANSI,& >>> TYPE CART3480 Task 7. Define DSM/TC Defaults Using MEDIACOM To establish DSM/TC default values, use the DSM/TC operator interface, MEDIACOM.
Configuring DSM/TC Default File Catalog option Description (page 2 of 2) UNLABELED Permits only unlabeled tape processing. TAPE DEFINEs and TAPECATALOG DEFINEs are not permitted. This level is equivalent to the SYSGEN option TAPE_LABEL_PROCESSING DISABLED. INTEGRATED A third-party tape management system is used in parallel with DSM/TC. The only DEFINEs that work are TAPECATALOG DEFINEs with CATALOG ON. Labeled tape processing is allowed only if the third-party tape management system is running.
Configuring DSM/TC Default Retention Three retention mechanisms are supported: Time-based retention Time-based retention instructs the file catalog to retain the file generation until a specified period of time has passed. Time-based retention is specified in number of days. The default retention value is 30 days. Date-based retention Date-based retention instructs the file catalog to retain the tape file until a specified date.
Configuring DSM/TC Default Abend Retention Default Abend Retention Abend retention is the number of days past the creation date to keep a catalog entry for an incomplete tape file. (An incomplete tape file is created when an application abnormally ends while writing data to a tape.) The default value is 1 day. To change the default: > MEDIACOM ALTER MEDIADEFS, ABENDRETENTION HP recommends that you set the same abend retention, support level, and retention period values on all nodes.
Configuring DSM/TC Data Compression The tape drive configured default compression setting (set using the SCF ALTER TAPE command) For drives that support a hardware override, the hardware setting takes precedence over any software setting. The default hardware setting is to use the software setting. The tape drive is reset to the default hardware setting prior to each tape media use. Therefore, if you want a hardware override, you must manually apply it before each use.
Configuring DSM/TC Data Compression To set compression off by default: MC> ALTER MEDIADEFS, COMPRESSION OFF Using DEFINEs to Override the System Compression Default After you set the system compression default, the drive always writes using the default setting. You can override the default specification for a specific job by using a TAPECATALOG DEFINE with the COMPRESSION attribute. The COMPRESSION attribute lets you override the system default specification on a job-by-job basis.
Configuring DSM/TC Automatic Selection and Mounting of Tapes This example for an unlabeled tape shows a BACKUP command that does not use a DEFINE. In this case, the drive writes data using the system default specification: 1>BACKUP $TAPE, $DATA.*.* Note. Applications specifying a TAPE DEFINE always use the system default specification because no COMPRESSION attribute exists for a TAPE DEFINE.
Configuring DSM/TC Default NL and BLP Behavior BLPCHECK When BLPCHECK is set to ON and a BLP request is made by an application, this message appears on the tape console and is sent to EMS: ... REQUEST TO USE $tape WITH NO LABEL PROTECTION To respond to this request, use the ACCEPT TAPEMOUNT or REJECT TAPEMOUNT command. When BLPCHECK is set to OFF and a BLP request is made by an application, processing occurs with no user intervention.
Configuring DSM/TC Setting Defaults Using ALTER MEDIADEFS Part of your tape inventory consists of Model 3480 cartridge tapes stored in a tape library that has only one Library Storage Module (LSM). The LSM has two tape drives.
Configuring DSM/TC Adding Tape Volumes to Pools, or Preexisting Tape Files 2. Use the ALTER MEDIADEFS command to change the tape level support on all three nodes to MEDIACAT: MC> ALTER MEDIADEFS, LEVEL MEDIACAT MC> ALTER MEDIADEFS \SEA, LEVEL MEDIACAT MC> ALTER MEDIADEFS \STAR, LEVEL MEDIACAT Because \SKY is the default node, you need not include its name in the first ALTER MEDIADEFS command.
Configuring DSM/TC >>> >>> >>> Adding Preexisting Tape Files LABELS IBM,& TYPE CART5120,& STATUS RELEASED Adding Preexisting Tape Files To manually catalog a tape file from a tape created by BACKUP, BACKCOPY, or other processes, use the ADD TAPEFILE command. BACKCOPY is a standard Backup Restore utility. The tape must belong to a pool and volume catalog before you execute ADD TAPEFILE. Otherwise, you must add it to a pool using the ADD TAPEVOLUME command, specifying the tape’s status as scratch.
Configuring DSM/TC Adding Preexisting Tape Files BACKUP. Because it is not cataloged, use a TAPE DEFINE to describe the input backup tape. 6> 6> 6> 7> 7> 7> 7> 8> 8> ADD DEFINE =COPY_IN, CLASS TAPE,& & VOLUME (BCK065),& & LABELS BACKUP ADD DEFINE =COPY_OUT, CLASS TAPECATALOG,& & USE OUT,& & LABELS BACKUP,& & FILEID MONDAY_BACKUP BACKCOPY =COPY_IN, =COPY_OUT, *.*.
Configuring DSM/TC Adding Preexisting Tape Files DSM/Tape Catalog User’s Guide — 520233-008 5 - 18
6 Using TAPECATALOG DEFINE Attributes An application requests DSM/TC services through CLASS TAPECATALOG DEFINEs. Use a TAPECATALOG DEFINE to request scratch tapes for new tape files, request cataloging of new tape files, and access cataloged tape files.
Using TAPECATALOG DEFINE Attributes TAPECATALOG DEFINE Attribute Summary TAPECATALOG DEFINE Attribute Summary Table 6-1 lists the attributes used for input tapes. Table 6-2 on page 6-2 lists the attributes used for output tapes. In both tables: The left column lists the required attributes that must be used because they do not have default values. The middle columns list required attributes that have default values. You do not have to use them if their default values are what you want.
Using TAPECATALOG DEFINE Attributes TAPECATALOG DEFINE Attribute Descriptions TAPECATALOG DEFINE Attribute Descriptions AUTOMATED { ON | OFF } determines the maximum number of times an attempt is made to automatically select and mount a DSM/TC or TMF cataloged scratch tape into a tape drive in a tape library: If ON, $ZSVR requests DSM/TC or the TMF catalog to select a scratch tape in a tape library to satisfy a mount message for a maximum of ten times.
Using TAPECATALOG DEFINE Attributes TAPECATALOG DEFINE Attribute Descriptions If OFF, tape requests do not go through DSM/TC and no cataloging takes place. CATALOG OFF causes the TAPECATALOG DEFINE to function as a TAPE DEFINE. If CATALOG OFF is specified, the FILECAT, VOLCAT, POOL, COMMENT, PHYSICAL, and LOGICAL attributes are ignored. Also, with CATALOG OFF specified, you cannot use the GEN attribute set to relative or +1, or the VERSION attribute set to NEW.
Using TAPECATALOG DEFINE Attributes TAPECATALOG DEFINE Attribute Descriptions POOL or ALTER POOL command in the DSM/Tape Catalog Operator Interface (MEDIACOM) Manual. In this case, you do not need to use this DENSITY attribute because the density value of the pool is assigned as the density value for all tapes assigned to the pool. If DENSITY is specified, only noncartridge-type tape drives should be used.
Using TAPECATALOG DEFINE Attributes TAPECATALOG DEFINE Attribute Descriptions You cannot use RETENTION and EXPIRATION in the same DEFINE, and you cannot use EXPIRATION with USE IN. FILECAT [ \node.]file-catalog-name is the logical name of the file catalog to search for an input tape file or where to create the entry for an output tape file. Include \node when the file catalog is not on your current default node.
Using TAPECATALOG DEFINE Attributes TAPECATALOG DEFINE Attribute Descriptions deleted from the catalog. When GEN is not used for an output tape, the default is +1. absolute is a positive number in the range of 1 through 32767. relative is a negative number in the range of -1 through -32768. If CATALOG is OFF, GEN is ignored when it is set to anything beside absolute.
Using TAPECATALOG DEFINE Attributes TAPECATALOG DEFINE Attribute Descriptions set as logical copy 2. This attribute is typically used for input, not output. The default is 1. If CATALOG is OFF, LOGICAL is ignored. This option is normally used for USE IN DEFINEs only. The BACKUP and BACKCOPY utilities manage the setting for USE OUT. BACKCOPY is a standard Backup Restore utility. LOGICAL is ignored by Backup and Restore 2.0. See also the PHYSICAL attribute on page 6-8.
Using TAPECATALOG DEFINE Attributes TAPECATALOG DEFINE Attribute Descriptions PHYSICAL is ignored by Backup and Restore 2.0. See also the LOGICAL attribute on page 6-7. POOL pool-name is the logical name of the DSM/TC pool used to select scratch tapes. The default is the name set by the MEDIACOM ALTER MEDIADEFS command on the node named by AVRSYSTEM or the system named in DEVICE. If neither is specified, the default is the local node. Use this attribute only when CATALOG ON and USE OUT are specified.
Using TAPECATALOG DEFINE Attributes TAPECATALOG DEFINE Attribute Descriptions With CATALOG ON specified, if you do not use the EXPIRATION or RETENTION attributes, the default is the retention value set by the MEDIACOM ALTER MEDIADEFS command on the node named by AVRSYSTEM or the system named in DEVICE. If neither is specified, the default is the local node. You cannot use RETENTION and EXPIRATION in the same DEFINE, and you cannot use RETENTION with USE IN.
Using TAPECATALOG DEFINE Attributes TAPECATALOG DEFINE Attribute Descriptions The value specified for version is a number in the range of 0 through 100. When used, it applies only to uncataloged files specified by a TAPE DEFINE or TAPECATALOG DEFINE with CATALOG OFF. When not used, the most current version of a cataloged input tape file is used. There can be only one valid version of a given tape file in DSM/TC. NEW indicates that this is a new version of tape-file-id within an existing generation.
Using TAPECATALOG DEFINE Attributes TAPECATALOG DEFINE Examples TAPECATALOG DEFINE Examples These examples use TAPECATALOG DEFINE in the DSM/TC environment. Labels ANSI—Writing a Single Tape File This request uses the default volume and file catalog because none is specified in the DEFINE. Only ANSI-labeled tapes are selected from the pool, and the volume is written compressed (if the drive used supports compression): ADD DEFINE =ANSI, CLASS TAPECATALOG, USE OUT, FILEID USER.
Using TAPECATALOG DEFINE Attributes Labels IBM—Reading a Single Tape File Labels IBM—Reading a Single Tape File Because no generation is specified in the DEFINE, this request uses generation -1 of the tape file IBM_FILE1 (the most recent) in the default file catalog: ADD DEFINE =IBM, CLASS TAPECATALOG, USE IN, FILEID IBM_FILE1, LABELS IBM FUP COPY =IBM, $DATA01.IBM.FILE1 Labels BACKUP—Writing Multiple Volumes This request uses the default volume and file catalog because none is specified in the DEFINE.
Using TAPECATALOG DEFINE Attributes General Examples General Examples These examples use the following default values (set with the MEDIACOM ALTER MEDIADEFS command) unless otherwise specified in the DEFINE: File catalog name PAYROLL_DEPT Volume catalog name OPERATION_TAPES Pool name ACCOUNTING_SCRATCH Retention period 30 Current default node \NCAL The DEFINE in this example specifies three scratch tapes for BACKUP.
Using TAPECATALOG DEFINE Attributes The DEFINE in this example requests the input tape file ACCOUNTS_PAYABLE, an IBM-MVS labeled tape. However, it is requesting the next-to-current generation of ACCOUNTS_PAYABLE, not the latest generation of this tape file ID. 17> 17> 17> 17> 17> 17> ADD & & & & & DEFINE =READ_ACCOUNT_PAYABLE,& CLASS TAPECATALOG,& USE IN,& LABELS IBM,& FILEID ACCOUNT_PAYABLE,& GEN -2,& The DEFINE in this example requests an IBM-MVS labeled scratch tape.
Using TAPECATALOG DEFINE Attributes DSM/Tape Catalog User’s Guide — 520233-008 6 - 16 General Examples
7 Tape Library Control Path Configuration Guidelines Applications request labeled tape volumes (physical tapes) using CLASS TAPE DEFINEs or CLASS TAPECATALOG DEFINEs. If a requested tape volume physically resides in a tape library, the NonStop Kernel tape server process ($ZSVR) automatically sends a request to the tape library to mount the tape cartridge in a tape drive. In most circumstances, no operator intervention is required.
Tape Library Control Path Configuration Guidelines Preparing the Software Environment Preparing the Software Environment This subsection describes how to prepare your tape library software environment. The required hardware should already be in place. Before further configuration: 1. Enable labeled tape processing. See Task 1. Enable Labeled Tape Processing on page 5-1. Then the system supports labeled tape operations and all tape requests are routed through $ZSVR.
Tape Library Control Path Configuration Guidelines Configuring the NonStop Server for the Tape Library 2. Specify the MEDIACOM ALTER MEDIADEFS command AUTOMATED ON option If AUTOMATED OFF is specified and the first tape selected is not available in the tape library, the operator receives a mount request. If AUTOMATED ON is specified and the first tape selected is not available in the tape library, $ZSVR automatically selects an alternate scratch tape for TMF and DSM/TC catalog requests.
Tape Library Control Path Configuration Guidelines Configuring the AUTOMATED Attribute Automated OFF means that TMF requests for online and audit dumps do not try a different scratch tape name if the selected scratch tape is not in the tape library. If AUTOMATED is specified as ON, and if the scratch tape is not in the tape library, a different scratch tape is requested, up to a maximum of 10 tape volumes.
Tape Library Control Path Configuration Guidelines Mapping Tape Drive Names to a Location in the Tape Library Mapping Tape Drive Names to a Location in the Tape Library For tape libraries using ACSLS, map the location of the tape drives in the tape library to the NonStop Kernel tape drive name. For tape libraries using SMM, skip this procedure. 1.
Tape Library Control Path Configuration Guidelines Communicating With a Tape Library 4.
Tape Library Control Path Configuration Guidelines Automatic Operation Automatic Operation All operational commands related to actual control of the tape library are entered through an ACSLS library server or an SMM Workstation. If a tape volume physically resides in the tape library, $ZSVR automatically sends a request to the tape library control software to mount the tape volume on a tape drive (either specified by the user in the DEFINE, by default, or provided by DSM/TC).
Tape Library Control Path Configuration Guidelines Control Path Flow Description ten attempts, none of the alternate selected tape volumes can be found in a tape library. If no tape volume is specified in a TAPE DEFINE request If a tape drive that is not in a tape library is specified. 4. $ZSVR sends a message to obtain a list of tape drives in order of proximity (number of passthroughs needed) to the specified tape volume. $ZSVR finds the closest available tape drive in the tape library.
Tape Library Control Path Configuration Guidelines Entering Tape Cartridges Into a Tape Library Entering Tape Cartridges Into a Tape Library To enter tape cartridges into a tape library (and if needed, label the tape volumes) and to add the tape volumes to a TMF catalog or DSM/TC environment, you must use either the SMM GUI or a combination of commands available through ACSLS, TMFCOM, and the MEDIACOM operator interface. See Related Reading on page 7-10 for more information.
Tape Library Control Path Configuration Guidelines Removing Labeled Tapes From a Tape Library 2. Enter the tape cartridge into the tape library. 3. On the NonStop Kernel side: To add a prelabeled tape volume to the DSM/TC environment, use the MEDIACOM command ADD TAPEVOLUME. If the tape volume contains information that needs to be cataloged, use the MEDIACOM command ADD TAPEFILE to add the tape file information to DSM/TC.
Tape Library Control Path Configuration Guidelines Using Tapes in a Tape Library Using Tapes in a Tape Library There are three types of labeled tape requests: Request Type Page TMF tape requests 7-11 TAPE DEFINE requests 7-11 TAPECATALOG DEFINE requests 7-12 Regardless of the request type, if the specified tape cartridge resides in the tape library, the tape cartridge (under most circumstances) is automatically mounted, used, and returned to its cell when the tape cartridge is dismounted from the
Tape Library Control Path Configuration Guidelines TAPECATALOG DEFINE Requests Because the HP NonStop operating system provides no cataloging facility for TAPE DEFINE requests, the user or a third-party cataloging facility must provide the tape volume names by using the VOLUME attribute. The operator receives a mount message: If no volumes are specified. If the volumes specified are not in the tape library.
Tape Library Control Path Configuration Guidelines Examples Using Tapes in the Tape Library (With Catalog) Examples Using Tapes in the Tape Library (With Catalog) The DEFINE requests used in these examples are created from a terminal with a TACL process running. They can also be created programmatically using normal procedure calls.
Tape Library Control Path Configuration Guidelines Examples Using Tapes in the Tape Library (No Catalog) Examples Using Tapes in the Tape Library (No Catalog) The DEFINE requests in these examples are created from a console with a TACL process running. They can also be created programmatically using normal procedure calls.
Tape Library Control Path Configuration Guidelines User Request Operations ADD DEFINE =FUPOUT, CLASS TAPE, LABELS ANSI, & VOLUME (ANSI01,ANSIO2) FUP COPY FILE1, =FUPOUT ADD DEFINE =FUPOUT2, CLASS TAPECATALOG, LABELS IBM, & VOLUME IBM001, COMPRESSION OFF, USE OUT, CATALOG OFF FUP COPY FILE2, =FUPOUT2 ADD DEFINE =FUPIN, CLASS TAPE, LABELS IBM, VOLUME IBM001 FUP COPY =FUPIN, FILE3 User Request Operations These examples use both TAPE DEFINEs and TAPECATALOG DEFINEs as they might be specified for
Tape Library Control Path Configuration Guidelines RECOVER FILES $DATA2.FST132.
8 Storage Server Interface (SSI) to the Tape Library Control Path The Storage Server Interface process ($ZSSI) is the interface between the automated cartridge system library software (ACSLS) that manages the storage and movement of tape cartridges for tape libraries and the NonStop Kernel tape management process $ZSVR. $ZSSI translates and routes messages between the $ZSVR process on the NonStop Kernel and the Client Server Interface (CSI) process on the ACSLS library server.
Storage Server Interface (SSI) to the Tape Library Control Path Run-Time Configuration Command Description Dismount Dismounts a tape cartridge from a tape library drive Eject Ejects one or more tape cartridges from the tape library Mount Mounts a tape cartridge on a specified tape library drive Query Mount Returns mount status information for queried tape cartridges Query Volume Returns volume status information for queried tape cartridges The $ZSSI subsystem also logs EMS events.
Storage Server Interface (SSI) to the Tape Library Control Path Startup Sequence PARAM name Description CSI^CONNECT^AGETIME Optional; # seconds connection aging (default 172800, minimum 600, maximum 31536000) CSI^RETRY^TIMEOUT Optional; per try network interface timeout (default 3) CSI^RETRY^TRIES Optional; number of retries (default 5) DEFINE name Class Description =TCPIP^HOST^FILE MAP Optional; if present, the NonStop Kernel TCP/IP software uses the HOSTS file specified by this DEFINE to re
Storage Server Interface (SSI) to the Tape Library Control Path Running the Portmapper The expected response is: PROGRAM 300031 VERSION 2 READY AND WAITING For more information on TCP/IP, see the TCP/IP Applications User Guide. Running the Portmapper The portmapper is a system service on which all other RPC-based services rely.
Storage Server Interface (SSI) to the Tape Library Control Path Running the Portmapper must be an existing CPU, different from the primary CPU. If not supplied, the portmapper cannot run as a process pair. TCPIP pname specifies the name of a TCP/IP process that provides a TCP/IP interface to an Ethernet LAN. If not specified and a parameter exists for TCPIP^PROCESS^NAME, that parameter is used. Otherwise, $ZTC0 is assumed. COLLECTOR pname specifies the name of the EMS collector to be used for EMS events.
Storage Server Interface (SSI) to the Tape Library Control Path Remote Procedure Call (RPC) Facility Remote Procedure Call (RPC) Facility The Remote Procedure Call (RPC) facility is a library of procedures that let one process (the caller process) have another process (the server process) execute a procedure call as if the caller process had executed the procedure call in its own address space (as in the local model of a procedure call).
Storage Server Interface (SSI) to the Tape Library Control Path Remote Procedure Call (RPC) Facility -b program version make an RPC broadcast to procedure 0 of the specified program and version using UDP and report all hosts that respond. The value for program can be a name or a number. -d program version delete registration for the RPC service of the specified program and version. This option can be specified only by a super-group member. The value for program can be a name or a number.
Storage Server Interface (SSI) to the Tape Library Control Path Tape Library Error Diagnosis If the TACL PARAM ZRPC^RPC^FILE exists, RPCINFO uses the value of that PARAM instead of $SYSTEM.ZRPC.RPC as the name of the RPC file. Tape Library Error Diagnosis This subsection illustrates how to use MEDIACOM commands and EMS events to help diagnose certain errors that can occur during communications with the tape library.
Storage Server Interface (SSI) to the Tape Library Control Path No Available Tape Library Drives To see the specific returned error, use a STATUS TAPEMOUNT, DETAIL command: MC>STATUS TAPEMOUNT,DETAIL Tape Mount Tape Name Action Write Protected Label Type AVR System Tape Use Open Exclusion Comment Process Name Process (CPU,PIN) Define Class Define Name Program Name 648 *RETRY NO ACTION NEEDED NO ANSI \SYS01 OUT EXCLUSIVE ZSSI ERROR 57, WILL RETRY $Z723 (5,165) TAPE =DEF \SYS01.$SYSTEM.SYS02.
Storage Server Interface (SSI) to the Tape Library Control Path DSM/Tape Catalog User’s Guide — 520233-008 8 - 10 Nonretryable Errors
9 Database Design of DSM/TC This section describes the design of the DSM/TC catalog database: Topic Page DSM/TC Catalog Database 9-1 File Catalog Tables and Structures 9-5 Volume Catalog Tables and Structures 9-11 Shorthand Views 9-14 Sizing Estimate for the DSM/TC Database 9-15 DSM/TC Catalog Database DSM/TC uses audited SQL/MP tables to archive the file and volume catalog information.
Database Design of DSM/TC Restoring Disk Files Restoring Disk Files DSM/TC contains enough information to restore a disk file based on the fully qualified file name and the time it was written to tape. The catalog can be consulted to determine exactly which tape volume or volumes contain the disk file. To invoke the RESTORE program to recover a disk file, use the MEDIACOM RECOVER DISKFILE command.
Database Design of DSM/TC Moving the Volume and File Catalogs to Another Volume Moving the Volume and File Catalogs to Another Volume Occasionally you need to move the volume catalog and file catalog to another volume without losing data on registered tapes. MEDIACOM does not provide a command interface to do this. To relocate a DSM/TC catalog subvolume from one physical location to another within the same system: 1.
Database Design of DSM/TC Moving the Volume and File Catalogs to Another Volume 7. Move the catalog by duplicating the DSM/TC catalog tables (substitute your subvolume names for those in this example): DUP $VOL1.DSMCAT.* WHERE SQL AND FILECODE = 900 , MAP NAMES $VOL1.DSMCAT.* TO $VOL2.DSMCAT2.* , CATALOGS $VOL2.DSMCAT2 FOR $VOL2.DSMCAT2.* , INDEXES IMPLICIT , VIEWS IMPLICIT , SAVEALL; 8. Update the DSM/TC map table.
Database Design of DSM/TC File Catalog Tables and Structures licensed) copy of the SQLCI2 object file. For these procedures, see the SQL/MP Installation and Management Guide. This procedure works only for relocation within one system, not to a second system. DSM/TC logical tape catalog names are preserved. You cannot use the procedure to alter the logical names.
Database Design of DSM/TC Tapefile Table Tapefile Table A Tapefile record represents a single generation of a file ID. Each tape file record is identified by file ID, generation, version, and copy numbers. One tape file record is created for each tape file, whether generated by an application or by the BACKUP program. A tape file is always named by a file ID. The name of the table is TAPEFILE. The name of the shorthand view is TFV10.
Database Design of DSM/TC Tapefile-to-Volume Table CATALOGFILES (CHAR(1)) The BACKUP catalog level used. Y means that CATALOGFILES was specified, which indicates that individual disk files are cataloged. N means that only the aggregate tape file is cataloged. Not used if TapeFileMode is USER. This field has a value of N for Backup and Restore 2.0 BACKUP operations. TAPEFILESTATUS (VARCHAR(7)) The current status of the tape file. Valid values are VALID and INVALID.
Database Design of DSM/TC Diskfile Table VERSION (SMALLINT) The version number of the tape file generation. Valid values start at 0. PHYSICALCOPY (SMALLINT) The physical copy number of this tape volume. This is used to distinguish between a BACKUP and a BACKCOPY of a tape file. Valid values start at 1. LOGICALCOPY (SMALLINT) The logical copy number of this tape volume. This is used to distinguish parallel BACKUP and BACKCOPY tape files. Valid values are 1 and 2.
Database Design of DSM/TC Diskfile Table qualified file names and the time they are written to tape. Because disk files are also contained in a tape file, the file ID and GEN fields can be used to access a disk file record. All disk files written to tape in a single invocation of the BACKUP program are cataloged in the same file catalog. The name of the table is DISKFILE. The name of the shorthand view is DFV10.
Database Design of DSM/TC Diskfile-to-Volume Table FILETYPE (CHAR(2)) Which type of disk file. Valid values are: EN for an ENSCRIBE file IN for a SQL/MP index PG for a SQL/MP program PV for a SQL/MP protection view SV for a SQL/MP shorthand view TA for a SQL table DISKFILEEOF (INTEGER) The size of the disk file in bytes. Valid values start at 0. If the EOF cannot be represented as a 32-bit signed integer, the column contains 232-1.
Database Design of DSM/TC Volume Catalog Tables and Structures VOLUMECATALOG (VARCHAR(30)) The volume catalog containing the pool. POOLNAME (VARCHAR(30)) The pool containing the tape volume. VOLSETID (VARCHAR(6)) The volume serial of the first tape volume in the volume set. VOLINDEX (SMALLINT) The position number of the volume in the tape volume set; for example, the fourth volume in the volume set. Valid values start at 1. FILEPOSITIONLBA (LARGEINT) Reserved for future use. Value is -1.
Database Design of DSM/TC Volume Table The status of tape after expiration: AUTOSCRATCH (CHAR(1)) Y means the tape volume becomes scratch. N means the tape volume becomes released. SEARCHSPACE (VARCHAR(8)) Indicates whether or not the pool is in the system search space. Valid values are IN (for included) or EX (for excluded). LASTSCRATCHVOL (VARCHAR(6)) Determines the last scratch tape volume suggested by DSM/TC for use, or reflects the last ASSIGNED volume used for APPEND.
Database Design of DSM/TC Volume-to-FileCatalog Table OWNERID (VARCHAR(47)) Contains the ten word PHANDLE of the process using or trying to use the tape. It might contain non printable characters. Otherwise, it is null. DENSITY (VARCHAR(4)) The density at which tape volumes in the pool are written. Valid values are 1600 and 6250. NULL is used for cartridge tapes.
Database Design of DSM/TC Shorthand Views Shorthand Views SQL shorthand views let you make customized reports based on the fields of the DSM/TC database described in this section. These views can be used for read access only because the DSM/TC database cannot be updated by software other than DSM/TC.
Database Design of DSM/TC Sizing Estimate for the DSM/TC Database Sizing Estimate for the DSM/TC Database Because SQL/MP automatically uses disk space compression when writing information in a database, the values in this estimate are greater than the actual space needed. The values are based on these assumptions: The average tape file name length is 20 characters. The average volume catalog name length is 18 characters. The average file catalog name length is 18 characters.
Database Design of DSM/TC Sizing Estimate for the DSM/TC Database DSM/Tape Catalog User’s Guide — 520233-008 9 - 16
A Using the DSM/TC Software System This detailed example shows the various aspects of the DSM/TC software system: Topic Page Setting the System Defaults A-1 Performing Operational Tasks A-5 Setting the System Defaults After DSM/TC is installed on the system, to begin configuring the system, the supergroup user or SECURITY-MEDIA-ADMIN group user must type MEDIACOM at the TACL prompt to start a MEDIACOM session: TACL> MEDIACOM MEDIACOM - T6028G06 (15NOV2002) Copyright (C) 2002 Compaq Computer Corporati
Using the DSM/TC Software System Support Level Automated Compression Setting the System Defaults COMPATIBLE OFF OFF 1 system defaults returned. Setting the System Defaults To set the system defaults: MC>alter mediadefs, filecat default_catalog,volcat default_catalog, pool backup_open, abendretention 0 1 system defaults altered.
Using the DSM/TC Software System \STORM.DEFAULT_CATALOG Adding Pools \STORM.$DATA1.DEFAULT 255,255 NG-G 5 Owner ------255,255 RWEP ----NG-G Version ------- 2 1 file catalog returned. MC>info volcat * Volume Catalog Name ---------------------\STORM.DEFAULT_CATALOG Catalog Location --------------------\STORM.$DATA1.DEFAULT 1 volume catalog returned. Adding Pools To add pools to the default volume catalog: MC>add pool ansi_pool,volcat default_catalog,labels ansi 1 pool added.
Using the DSM/TC Software System Adding Existing Prelabeled Tapes Adding Existing Prelabeled Tapes To add existing prelabeled tapes to the pools: MC>add tapevolume ans000,count 100,pool ansi_pool, volcat default_catalog 100 tape volumes added. MC>add tapevolume bkc000,count 100,pool backup_cart,type cart3480, volcat default_catalog,labels backup 100 tape volumes added. MC>add tapevolume bko000,count 100,pool backup_open,type open, volcat default_catalog,labels backup 100 tape volumes added.
Using the DSM/TC Software System Performing Operational Tasks Performing Operational Tasks These examples show some operational tasks performed in a DSM/TC environment, including creating a TAPECATALOG DEFINE for a BACKUP operation, selecting and mounting a scratch tape, the actual backup operation, and recovering a subvolume (RESTORE operation).
Using the DSM/TC Software System Creating a DEFINE for a BACKUP Operation EXCLUDED_POOL IBM_POOL ANY IBM ANY 6250 ANY ANY ON ON EXCLUDED INCLUDED 5 pools returned. MC>info tapevolume bko00? Volume Catalog Pool Name Tape Name ---------BKO000 BKO001 BKO002 BKO003 BKO004 BKO005 BKO006 BKO007 BKO008 BKO009 \STORM.
Using the DSM/TC Software System ----0 -----BKO000 Selecting and Mounting a Scratch Tape Volume -----BACKUP -------------\STORM ---NO ------------------ MOUNT SCRATCH TAPE 1 tape mount returned. MC>status tapemount,detail Tape Mount Tape Name Action Write Protected Label Type Pool Name Volume Catalog AVR System Tape Use Density Open Exclusion Comment Process Name Process (CPU,PIN) Define Class Define Name Program Name 0 BKO000 MOUNT ANY APPROPRIATE SCRATCH TAPE NO BACKUP BACKUP_OPEN \STORM.
Using the DSM/TC Software System Selecting and Mounting a Scratch Tape Volume MC>alter tapemount 0 1 tape mount altered. The EMS log shows: 000649 $ZSVR 0000 REQUEST FOR VOLUME BKO000 CANCELED 000600 $ZSVR *MC* 0000 MOUNT BKO001 DENSITY 6250 WITH RING Labeled BACKUP.
Using the DSM/TC Software System Selecting and Mounting a Scratch Tape Volume To display the status of the tape drive $TAPE: MC>status tapedrive $tape, detail Tape Drive Drive Status Label Type Tape Name Tape Status Pool Name Volume Catalog Process Name Process (CPU,PIN) Tape Use Open Exclusion Open Mode Define Class Define Name Program Name $TAPE INUSE BACKUP BKO001 INUSE BACKUP_OPEN \STORM.DEFAULT_CATALOG \STORM.0,27 (0,27) OUT EXCLUSIVE LP TAPECATALOG =TCAT \STORM.$SYSTEM.SYS20.
Using the DSM/TC Software System Selecting and Mounting a Scratch Tape Volume The INFO TAPEVOLUME command is used while waiting for the second tape mount: MC>info tapevolume bko00? Volume Catalog Pool Name Tape Name ---------BKO000 BKO001 BKO002 BKO003 BKO004 BKO005 BKO006 BKO007 BKO008 BKO009 \STORM.
Using the DSM/TC Software System Selecting and Mounting a Scratch Tape Volume An INFO TAPEVOLUME command is used while the second tape is being written: MC>info tapevolume bko00? Volume Catalog Pool Name Tape Name ---------BKO000 BKO001 BKO002 BKO003 BKO004 BKO005 BKO006 BKO007 BKO008 BKO009 \STORM.
Using the DSM/TC Software System BACKUP Information Output BACKUP Information Output This is output from the BACKUP program: BACKUP Program - T9074D46 (07SEP98) Copyright Compaq Computers Incorporated 1981-1998 Drives: $TAPE3 System: \LAUN11 Operating System: G06 Tape Version: 1 Backup options: BLOCKSIZE 8, NO PARTONLY Backup time: 11Feb1999 10:43 Tape: 1 Code $MYVOL.
Using the DSM/TC Software System BKO008 BKO009 BACKUP Information Output BACKUP BACKUP OPEN OPEN SCRATCH SCRATCH 10 tape volumes returned. MC>info tapevolume (bko001,bko003),detail Tape Name Pool Name Volume Catalog Labels Type Density TapeFormat Status BKO001 BACKUP_OPEN \STORM.DEFAULT_CATALOG BACKUP OPEN 6250 ARCHIVE ASSIGNED File Catalog Tape File Generation Version Status \STORM.
Using the DSM/TC Software System Tape File Mode Catalog Files Record Format Record Length Block Length Last Gen Volume Catalog Pool Name Volume Set ID BACKUP Information Output FILEMODE BACKUP FALSE UNDEFINED 0 2048 1 \STORM.DEFAULT_CATALOG BACKUP_OPEN BKO001 File Section File Sequence Tape Name Volume Index 1 1 BKO001 1 File Section File Sequence Tape Name Volume Index 2 1 BKO003 2 1 tape file returned.
Using the DSM/TC Software System Recovering a Subvolume Recovering a Subvolume There is a need later to recover a subvolume. The RECOVER DISKFILE command is used. MC>recover diskfile $Data1.subvol.*, tapefile friday_backup, listall, tapedate The tape file selected is shown as the following: File Catalog Volume Catalog Pool Name Tape File Generation Version Physical Copy Logical Copy Time Archived Tape File Mode Tape Name \STORM.DEFAULT_CATALOG \STORM.
Using the DSM/TC Software System Tape: 1 Block Returning the Tapes to Scratch Code $DATA.SUBVOL FILE1 FILE2 FILE3 FILE4 FILE5 101 101 101 101 101 EOF 125440 425440 155440 126440 125740 Last modif 18Apr93 19Apr93 18Apr93 19Apr93 18Apr93 19:02 6:02 12:02 12:32 13:02 Owner RWEP -1 -1 -1 -1 -1 Type Rec NNNN NNNN NNNN NNNN NNNN Tape volumes used: BKO001 Summary Information Files restored = 5 Files not restored = 0 1 recover diskfile completed.
Using the DSM/TC Software System Rejecting a Tape Mount 2. Enable the write protect on the labeled tape. 3. Execute the FUP COPY command on the labeled tape, which could resulted in a tape error. 4. Set the status of the tape volume to INUSE and dismount the tape from the tapedrive. 5. If the user had stopped either the primary ZSERVER process or brought down the processor where ZSERVER is primaried. In either of the cases ZSERVER backup process will take over and try to continue the operation. 6.
Using the DSM/TC Software System DSM/Tape Catalog User’s Guide — 520233-008 A - 18 Rejecting a Tape Mount
B CLASS TAPECATALOG DEFINE Syntax Summary The CLASS TAPECATALOG DEFINE attribute syntax elements are: AUTOMATED { ON | OFF } AVRSYSTEM \node BLOCKLEN block-length CATALOG { ON | OFF } CLASS class-type COMMENT comment-text COMPRESSION { IDRC | OFF } DENSITY { 1600 | 6250 } DEVICE [ \node.]$device EBCDIC { ON | OFF } EXPIRATION { mmmddyyyy } { ddmmmyyyy } FILECAT [ \node.
CLASS TAPECATALOG DEFINE Syntax Summary VERSION { version | NEW } VOLCAT [ \node.
C CLASS TAPECATALOG DEFINE Consistency Checks To display the current CLASS TAPECATALOG DEFINE attribute values, use the SHOW DEFINE command at the TACL prompt. SHOW DEFINE also checks the attributes for consistency and returns the number of the first consistency check that fails. For details on the SHOW DEFINE command, see the TACL Reference Manual. Table C-1. TAPECATALOG DEFINE Consistency Checks Check Number Description 1 Use RETENTION or EXPIRATION, but not both.
CLASS TAPECATALOG DEFINE Consistency Checks DSM/Tape Catalog User’s Guide — 520233-008 C-2
D CLASS TAPE DEFINE to CLASS TAPECATALOG DEFINE Conversion To illustrate converting to a CLASS TAPECATALOG DEFINE, this appendix shows an existing TAPE DEFINE and an equivalent TAPECATALOG DEFINE. This is an example TAPE DEFINE: INFO DEFINE =TAPE Define Name =TAPE CLASS TAPE VOLUME BCK001 LABELS BACKUP RETENTION 45 DEVICE \SYSTEM.
CLASS TAPE DEFINE to CLASS TAPECATALOG DEFINE Conversion DSM/Tape Catalog User’s Guide — 520233-008 D-2
E CLASS TAPE/TAPECATALOG DEFINE Equivalent Attributes If you are accustomed to using a CLASS TAPE DEFINE to access tapes, you can perform the same operations and take advantage of the COMPRESSION option by using a CLASS TAPECATALOG DEFINE. Table E-1.
CLASS TAPE/TAPECATALOG DEFINE Equivalent Attributes DSM/Tape Catalog User’s Guide — 520233-008 E-2
Index A Bypass label processing, giving approval 4-13 Abend retention, default 4-9 Absolute file generations 2-3 ACS command EJECT 6-10 ENTER 6-9 MOUNT 6-9, 6-12 ACS library server 7-1 Adding pre existing tapes, examples 4-16 Adding tape volumes, examples 4-15 Adding tapes in a tape library 6-9 ALLPROCESSORS paragraph 4-1 Append capable pools 1-7 Attribute summary, TAPECATALOG DEFINE 5-2 Automated use of tapes, tape library 6-11 Automatic mounting of tapes 4-12 Automatic operation, tape library 6-7 Automa
Index D D Data compression, default 4-9 Database protection 4-2 Defining DSM/TC defaults abend retention 4-9 automatic tape mounting 4-12 automatic tape selection 4-12 data compression 4-9 file catalog 4-7 NL and BLP 4-12 pool 4-7 retention 4-7 support level 4-6 system search list 4-9 volume catalog 4-7 Disk files 1-10 restoring 8-2 Diskfile table 8-8 Diskfile-to-volume table 8-10 DSM/TC definition 1-1 main components 1-2 operational characteristics 1-2 DSM/TC catalog database 8-1 DSM/TC catalog manager (
Index L L Pool creating 4-5 default 4-7 table 8-11 Portmapper system service, run command 7-4 Preexisting tape files, adding 4-16 Premounted output tapes 3-12 Labeled tapes managing 3-2 requesting 3-9 Locating tape files 8-1 M Managing different types of tape 1-6 Managing tape requests 3-9 examples 3-10 MEDDEM file expiration process 2-10 MEDIACOM interface 1-3 MEDIADBM catalog manager 4-3 Mismatched tapes, tape library 6-9 Moving VOLCAT and FILECAT to another volume 8-3 N NL behavior 4-12 NLCHECK set
Index T SQL shorthand views 8-14 system catalog creating 4-2 tables 8-1 warning message 6008 2-11 Status changes input tape 3-11 output tape 3-11 volume catalog entry 3-11 Storage Server Interface See $ZSSI process Substituting scratch tapes 3-13 Support level default 4-7 INTEGRATED 4-7 MEDIACAT 4-6 NOCATALOG 4-6 tape 3-1 TPTM 4-7 TPTMCOMPATIBLE 4-7 UNLABELED 4-7 SYSGEN 4-1 System date, monitoring 4-8 System defaults example adding other entities A-4 adding pools A-3 adding prelabeled tapes A-4 changing s
Index T Tape libraries (continued) using INFO MEDIADEFS 6-3 using INFO TAPEDRIVE 6-5 using the AUTOMATED option 6-3 using the COMPRESSION option 6-4 Tape library error diagnostics library server 7-8 MEDIACOM 7-8 nonretryable error 7-9 retryable error 7-8 STATUS TAPEMOUNT 7-8 tape drives unavailable 7-9 Tape library examples BACKUP and RESTORE (no catalog) 6-14 BACKUP and RESTORE (with catalog) 6-13 FUP (no catalog) 6-14 FUP (with catalog) 6-13 TMF operations 6-15 user request (no catalog) 6-15 user reques
Index U TAPECATALOG DEFINE examples labels BYPASS 5-13 labels IBM 5-13 labels OMITTED 5-13 TAPECATALOG DEFINE requests, tape library 6-12 TAPECOM users 1-3 Tapefile config table 8-5 Tapefile table 8-6 Tapefile-to-volume table 8-7 Tapeformat 1-5 Tape, automatic selection and mounting 4-12 TCP/IP socket interface 7-2 TMF database protection 4-2 TMF tape requests AUDIT DUMP 6-11 ONLINE DUMP 6-11 RECOVER FILES 6-11 TMFCOM 6-9 TMFCOM command ADD TAPEMEDIA 6-10 U Updating the DSM/TC database 8-2 Using ALTER ME
