HP NonStop TMF Reference Manual Abstract This manual describes how to use the TMFCOM command interface to the HP NonStop™ Transaction Management Facility (TMF). This manual includes command syntax, semantics, and examples, and is intended for system managers and operators. Product Version TMF H01 Supported Releases This publication supports H06.03 and all subsequent H-series release version updates (RVUs) until otherwise indicated by its replacement publication.
Document History Part Number Product Version 540138-001 TMF H01 Published July 2005
HP NonStop TMF Reference Manual Index Figures Tables What’s New in This Manual vii Manual Information vii New and Changed Information vii About This Manual ix Who Should Read This Manual ix How This Manual Is Organized ix TMF Documentation x Other Documentation xi Notation Conventions xii 1. Introduction to TMF About TMF 1-1 TMF Objects 1-2 TMFCOM Command Interpreter 1-4 2.
3. TMFCOM Commands Contents 3.
3. TMFCOM Commands (continued) Contents 3.
3. TMFCOM Commands (continued) Contents 3. TMFCOM Commands (continued) SHOW DUMPS 3-252 SHOW TAPEMEDIA 3-254 START TMF 3-256 STATUS AUDITDUMP 3-259 STATUS AUDITTRAIL 3-261 STATUS BEGINTRANS 3-268 STATUS CATALOG 3-269 STATUS DATAVOLS 3-270 STATUS OPERATIONS 3-276 STATUS RESOURCEMANAGER 3-282 STATUS SERVER 3-289 STATUS TMF 3-291 STATUS TRANSACTIONS 3-296 STOP TMF 3-305 VOLUME 3-309 ! 3-311 ? 3-314 4.
A. TMFCOM Messages (continued) Contents A. TMFCOM Messages (continued) Other Messages A-4 Error Information and Failure Data Capture Message Descriptions A-6 A-4 B. TMFCOM Command Reference Summary C. TMF Configuration Limits and Defaults Index Figures Figure 3-1. Figure 3-2. TMFCOM and TMFSERVE Processes 3-196 TMFSERVE on a Remote Node 3-198 Tables Table 1-1. Table 3-1. Table 3-2. Table 3-3. Table 3-4. Table 3-5. Table 3-6. Table 3-7. Table 3-8. Table 3-9. Table 3-10. Table 3-11. Table 3-12.
Tables (continued) Contents Tables (continued) Table 3-22. Table 3-23. Table 3-24. Table 3-25. Table C-1. Table C-2. Table C-3. Table C-4. Table C-5. Table C-6. Table C-7.
What’s New in This Manual Manual Information HP NonStop TMF Reference Manual Abstract This manual describes how to use the TMFCOM command interface to the HP NonStop™ Transaction Management Facility (TMF). This manual includes command syntax, semantics, and examples, and is intended for system managers and operators. Product Version TMF H01 Supported Releases This publication supports H06.03 and all subsequent H-series release version updates (RVUs) until otherwise indicated by its replacement publication.
What’s New in This Manual New and Changed Information HP NonStop TMF Reference Manual—540138-001 viii
About This Manual This manual describes the syntax and semantics of all TMFCOM commands for using the HP NonStop™ Transaction Management Facility (TMF) on HP NonStop servers.
TMF Documentation About This Manual Appendix B, TMFCOM Command Reference Summary, shows the TMFCOM command syntax, extracted from the command descriptions in Section 3 and presented in summarized form. Appendix C, TMF Configuration Limits and Defaults, lists the operational limits on parameters used by TMF.
Other Documentation About This Manual • • TMF Application Programmer’s Guide Read this guide for information about how to design requester and server modules to run in the TMF programming environment. Also read it for information about a set of procedures that can help in examining the content of TMF audit trails. TMF Management Programming Manual Read this manual for information about how to use the Subsystem Programmatic Interface (SPI) to communicate programmatically with the TMF software.
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
General Syntax Notation About This Manual | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}...
Notation for Messages About This Manual Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets.
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. 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).
Change Bar Notation About This Manual HP NonStop TMF Reference Manual—540138-001 xvi
1 Introduction to TMF TMF protects databases in a wide variety of environments, servicing online transaction processing (OLTP), online query processing (OLQP), batch processing, and decisionsupport systems.
TMF Objects Introduction to TMF TMF Objects You manage and operate TMF, and control your TMF environment, by issuing commands that create, alter, delete, and return information about various TMF objects. These objects, listed in Table 1-1, include such items as dumps, files, processes, and TMF itself. Table 1-1.
TMF Objects Introduction to TMF Table 1-1. TMF Objects (page 2 of 2) Object Object Keyword Description Resource Manager RESOURCEMANAGER A representation of anything that contains data, such as a database or a queue. TMF uses a resource manager facility that is a collection of routines that enables cooperation between different transaction management systems running on different platforms, used to support heterogeneous transaction processing. Tape media TAPEMEDIA A tape volume known to TMF.
TMFCOM Command Interpreter Introduction to TMF TMFCOM Command Interpreter As a system manager or operator, you operate on TMF objects by issuing commands through the TMFCOM command interpreter. Within TMF, the commands are received by the TMFSERVE server process, which either operates on the objects itself or passes necessary requests to other peer processes through a programmatic messaging system. TMFCOM and TMFSERVE interact in a common client-server relationship.
2 Using TMFCOM TMFCOM allows you to enter commands that initiate communication with TMF, request various TMF operations, and terminate communication with TMF. This section explains how to use TMFCOM, discussing the following topics: Topic Page Running TMFCOM 2-1 Entering TMFCOM Commands 2-6 Directing Output to an Alternate Destination 2-8 Using Partially Qualified File Names 2-9 Requesting Online Help 2-10 Caution.
Using TMFCOM Interactively Using TMFCOM input source−usually the workstation or terminal from which you issue the TMFCOM command. OUT output-file specifies a file to which TMFCOM output (other than prompts for entering TMFCOM commands) is to be written. This file, for example, might receive listings requested by INFO, SHOW, or STATUS commands. It might also receive TMFCOM commands generated by the OBEYFORM option as described in Section 3, TMFCOM Commands. Note.
Using TMFCOM Interactively Using TMFCOM TMFCOM replies with version information and a prompt for input: TMFCOM - T8652H01 - (01MAY2005 - TMF) (C) 2005 Hewlett-Packard Development Company, L.P. TMF 1> “TMF 1>” is the TMFCOM input prompt, which tells you that TMFCOM is ready to accept your first command. When you enter this command, TMFCOM processes it and displays another input prompt for your next command.
Using TMFCOM Noninteractively Using TMFCOM • If you press BREAK while TMFCOM is reading a continued line of a partially entered multiline command, TMFCOM does not interpret this command and prompts you instead for a new command. Note. On your workstation or terminal keyboard, the BREAK key might not actually be labeled “BREAK.” All keyboards, however, have some key or combination of keys that perform the BREAK operation. Before using TMFCOM, determine how this operation is selected on your keyboard.
Using TMFCOM From a Command File Using TMFCOM If any command on the line fails, TMFCOM reports the error and terminates without executing any of the subsequent commands. Using TMFCOM From a Command File TMFCOM can also read commands from an input file known as a command file. A command file is simply a text file that contains the TMFCOM commands you want to execute, which you prepare using your standard text editor.
Entering TMFCOM Commands Using TMFCOM Entering TMFCOM Commands As you enter TMFCOM commands, you can: • • • Include comments in command lines. Continue a single command over multiple lines. Enter multiple commands on a single line. Caution. The previous version of TMFCOM, now named TMFCOM1, allowed some syntax errors, usually spaces in file names. These syntax errors are detected by the latest version of TMFCOM covered by this manual and may cause errors in OBEY FILES or TACL scripts.
Continuing Commands on Multiple Lines Using TMFCOM Continuing Commands on Multiple Lines You can continue a single TMFCOM command over two or more lines. For example, you must do this when a command contains too many parameters to fit into one 2048character line (as sometimes occurs in OBEY command files). In other cases, lengthy comments on a command line force the text onto one or more additional lines.
Directing Output to an Alternate Destination Using TMFCOM If you include a command that requires an answer to a confirming question (such as ABORT TRANSACTION) before TMFCOM processes that command further, and you respond with NO or STOP, the current command is discontinued, and the next command is executed. After all the commands are executed, TMFCOM takes one of the following actions: • • If TMFCOM is running interactively, it prompts you for another command.
Using Partially Qualified File Names Using TMFCOM • If you omit \node,volume, or subvolume, the default is your current node, volume, or subvolume, respectively. If you omit the OUT option, the device from which you enter the TMFCOM command receives the output. As an illustration of the OUT option, to direct the output from a STATUS TMF command to a disk file named $OPS.STATUS.TMF, you enter the following command: TMF 25> STATUS /OUT $OPS.STATUS.
Requesting Online Help Using TMFCOM Requesting Online Help You can request online help to remember TMFCOM command names and syntax. This assistance is available through the HELP command, which can display: • • • A list of the TMFCOM commands associated with a specific keyword, such as ADD, ALTER, INFO, or SET The syntax diagram for a specific TMFCOM command A list of all TMFCOM commands Note. The HELP command output only shows commands and options available with the currently opened TMFSERVE process.
Requesting Online Help Using TMFCOM To obtain the syntax diagram for a specific TMFCOM command, enter the HELP command followed by the TMFCOM command that you want information about. To obtain the syntax for the ADD AUDITTRAIL command, for example, enter: TMF 43> HELP ADD AUDITTRAIL TMFCOM responds by displaying: ------------------------------------------------------------| | | ADD AUDITTRAIL Command | | | | Adds one or more audit trails to the TMF configuration.| | | | Security: super user group member.
Requesting Online Help Using TMFCOM To list all TMFCOM commands, enter the HELP command followed by the keyword ALL: TMF 44> HELP ALL TMFCOM responds by listing all TMFCOM commands in alphabetical order. -----------------------------------------------------------| ABORT TRANSACTION | | ADD AUDITTRAIL | | ADD DATAVOLS | | ADD DUMPS | | ADD RESOURCEMANAGER | | ADD TAPEMEDIA | | ALTER AUDITDUMP | | ALTER AUDITTRAIL | | ALTER BEGINTRANS | | . | | . | | .
3 TMFCOM Commands The TMFCOM utility program and its associated commands enable you to operate and manage a TMF environment. The TMFCOM commands and their attributes are described in this section, which presents these topics: Topic Page Command Description Elements 3-1 File Names and Process Identifiers 3-6 Commands: AB - AD 3-10 AL - CA 3-43 CL - DE 3-98 DI - FC 3-116 HE - IN 3-145 NE - RE 3-189 SE - SH 3-232 ST - VO 3-256 ! 3-311 ? 3-314 Caution.
Command Description Elements TMFCOM Commands Purpose, Syntax, and Parameters Each description begins by explaining the purpose or function of the command. Then, a syntax diagram and complete parameter descriptions indicate what keywords and variables make up the command: which are required, which are optional, and what the default assignments for the optional items are. The meanings of the symbols used in the syntax diagrams are described under Notation Conventions on page xii.
Command Description Elements TMFCOM Commands Table 3-1.
Command Description Elements TMFCOM Commands Table 3-1.
Command Description Elements TMFCOM Commands Table 3-1.
File Names and Process Identifiers TMFCOM Commands Usage Guidelines Details about the proper use of a command appear under “Usage Guidelines.” These details include information about when to apply the command, possible constraints and side-effects of the command, hints on enhancing performance and avoiding errors, and other considerations. When a command is extremely basic or straightforward, the command description omits the “Usage Guidelines.
File Names and Process Identifiers TMFCOM Commands Disk File Names The syntax for a file name that identifies a disk file is: [node.][[volume.]subvol.]file-id or [node.][volume.]temp-file-id node specifies the name of the node (system) on which the file resides. A node name consists of a backslash (\) followed by one to seven alphanumeric characters; the first alphanumeric character must be a letter. volume specifies the name of the volume on which the file resides.
File Names and Process Identifiers TMFCOM Commands The next example specifies all files in all subvolumes on the volume $DATA5: $DATA5.*.* The last example specifies all files in all subvolumes on all volumes (in other words, all files stored at the node): *.*.* Notice that, as a general rule, the asterisk can only replace a complete volume name, subvolume name, or file-id.
File Names and Process Identifiers TMFCOM Commands Process Identifiers TMFCOM commands can refer to (and display information about) both unnamed and named processes. Identifiers for Unnamed Processes The syntax used to identify an unnamed process is: (cpu,pin) cpu specifies the CPU number of the processor in which the process is running. cpu is one or two digits representing a value in the range 0 through 15. A leading zero must be suppressed.
ABORT TRANSACTION TMFCOM Commands ABORT TRANSACTION The ABORT TRANSACTION command backs out (cancels) the effects of an active transaction, or reattempts to back out an aborting or hung transaction, and releases the locks held by that transaction. ABORT TRANS[ACTION[S]] {transaction-id } {(transaction-id [,transaction-id]...)} [,IGNOREDATAERRORS | ,AVOIDHANGING] where transaction-id is: [node. [node-number. [node(tm-flags). [node-number(tm-flags). [(tm-flags). ] ] ] cpu.
ABORT TRANSACTION TMFCOM Commands cpu is the number of the processor on which the transaction originated. seq-num is a sequence number assigned by TMF to the transaction, which distinguishes it from other transactions originating in the same processor on the same home node under the current TMF configuration. (A new TMF configuration is defined when the first START TMF command following a DELETE TMF command is executed.
ABORT TRANSACTION TMFCOM Commands Security Restrictions You can issue the ABORT TRANSACTION command only if you are a member of the super user group. TMF State Requirement Before you can enter the ABORT TRANSACTION command, TMF must be started. Usage Guidelines Only transactions that are in the active, aborting, or hung state can be aborted using this command.
ABORT TRANSACTION TMFCOM Commands Examples In the following example, the STATUS TRANSACTION command indicates that the transaction identified as \TSII.2.1958908 is active: TMF 12> STATUS TRANSACTION Transaction Identifier ---------------------\TSII.2.1958908 \TSII.2.1968200 Process ------(2,118) (2,118) State Parent ----- -----active active Children -------- The ABORT TRANSACTION command, followed by the Y response to the confirm prompt, aborts that transaction: TMF 15> ABORT TRANSACTION \TSII.2.
ADD AUDITTRAIL TMFCOM Commands ADD AUDITTRAIL The ADD AUDITTRAIL command adds an audit trail to the TMF configuration. ADD AUDITTRAIL {MASTER | MAT {AUX[ILIARY]nn [,AUDITDUMP {ON | OFF [,FILESIZE integer [,ACTIVEVOL[S] {volume {(volume [,volume]...) [,FILESPERVOLUME integer } } }] ] } }] ] [,OVERFLOWVOL[S] {volume } {(volume [,volume]...)}] [,OVERFLOWTHRESHOLD integer [,RESTOREVOL[S] ] {volume } {(volume [,volume]...
ADD AUDITTRAIL TMFCOM Commands If AUDITDUMP is ON, use the ALTER AUDITDUMP command to modify other parameters relating to audit dumping. These parameters are explained in the ALTER AUDITDUMP command description.
ADD AUDITTRAIL TMFCOM Commands add more audit volumes to the configuration later, you can use the ALTER AUDITTRAIL command. Note. TMF is shipped from the factory with the $AUDIT disk volume configured as the active-audit volume. You are free to retain $AUDIT for this purpose, replace $AUDIT with another volume as the recipient of audit trails, or add other active-audit volumes to the configuration.
ADD AUDITTRAIL TMFCOM Commands OVERFLOWTHRESHOLD integer specifies the percentage of audit trail capacity that can be consumed before TMF begins overflow copying. This is an optional parameter. The minimum value is 50 and the maximum is 100. The default is 80(%). RESTOREVOL[S] specifies the volumes used when restoring audit dumps during execution of a RECOVER FILES command. If audit dumping is configured for the audit trail, you must specify at least one volume for this purpose.
ADD AUDITTRAIL TMFCOM Commands related to sets of data volumes. Each auxiliary audit trail is uniquely identified by the prefix AUX followed by a two-digit number: for example, AUX03. For attributes not specified in the ADD AUDITTRAIL command, you can assign values by entering SET AUDITTRAIL commands earlier in the same TMFCOM session; otherwise, the default values, if they exist, are used.
ADD AUDITTRAIL TMFCOM Commands If the primary transaction management process (TMP) fails before the ADD AUDITTRAIL command completes, the backup TMP takes over and undoes the effects of that command before processing any new requests from TMFCOM. If both TMPs fail before the ADD AUDITTRAIL command completes, TMF also undoes the effects of that command.
ADD DATAVOLS TMFCOM Commands ADD DATAVOLS The ADD DATAVOLS command adds one or more data volumes to the TMF configuration, including management attributes such as the audit trail to receive audit records from these volumes. ADD DATAVOL[S] {volume } {(volume [,volume]...) } { * [,NOT volume] } { * [,NOT (volume[,volume]...)]} [,AUDITTRAIL {MASTER | MAT {AUX[ILIARY]nn } } ] [,RECOVERYMODE {ONLINE | ARCHIVE}] [,IGNOREPREVIOUSCONFIG ] volume identifies a disk volume to be added as a data volume. Note.
ADD DATAVOLS TMFCOM Commands The NonStop Remote Database Facility (RDF) relies on TMF for many of its functions. For information about RDF interoperability with TMF audit trails, see the NonStop RDF System Management Manual for your version of RDF. RECOVERYMODE {ONLINE|ARCHIVE} determines whether audit-trail files are held on disk until they are no longer required for volume recovery.
ADD DATAVOLS TMFCOM Commands TMF State Requirement Before you can enter the ADD DATAVOLS command, TMF must be started. Usage Guidelines When the ADD DATAVOLS command completes successfully, TMF automatically recognizes the specified volumes and immediately attempts to start them. In the ADD DATAVOLS command, you can specify only unconfigured volumes; furthermore, the audit trail you specify must already exist in the configuration.
ADD DATAVOLS TMFCOM Commands circumstances, consider temporarily deleting a data volume if it was shut down cleanly or does not contain critical data. Examples The following ADD DATAVOLS command adds three data volumes to the TMF configuration: TMF 30> ADD DATAVOLS ($DATA, $DATA2, $DATA17), AUDITTRAIL MAT $DATA -- datavol added. $DATA2 -- datavol added. $DATA17 -- datavol added.
ADD DUMPS TMFCOM Commands ADD DUMPS The ADD DUMPS command adds dump entries to the TMF catalog. This command is used to reenter online and audit dump entries accidentally deleted from the catalog, or to recover a destroyed catalog. Use the ADD DUMPS command only under one of these conditions: • • • • The catalog files residing on the configuration volume in the ZTMFCONF subvolume (volume.ZTMFCONF) have been damaged or lost.
ADD DUMPS TMFCOM Commands Adding an Audit Dump to the Catalog To add an audit dump entry to the catalog, use the following syntax: ADD DUMPS audit-trail-file ,SERIAL serial-number ,TYPE AUDITDUMP {,DISKMEDIA disk } {,TAPEMEDIA {tape } {(tape [,tape]...)}} [,TIME {month[-]day[-]year, hr:min[:sec] [GMT]} {day[-]month[-]year, hr:min[:sec] [GMT]}] audit-trail-file identifies the audit-trail file dumped, using the following file name format: $ZTMFAT.ZTMFAT.
ADD DUMPS TMFCOM Commands the node at which your TMFSERVE process is running, xx can be any two alphabetic characters. When node is different than the one at which your TMFSERVE process is running, xx can be any two alphabetic characters except ZT. If node is not specified, ZT is assigned as xx by default.
ADD DUMPS TMFCOM Commands have a default value. If you specify 2 for copy in the ADD DUMPS command, always supply the part numbers of both copies of the dump in the TAPEMEDIA parameter, for example: TAPEMEDIA (TAPE1:1:2, TAPE2:2:2) TIME specifies the time that the audit dump was created. If TIME is not specified, the current TMFSERVE time is assumed by default–that is, the current time is recorded into the catalog with the audit dump whose name is being added. Caution.
ADD DUMPS TMFCOM Commands Adding Online Dump File Names to the Catalog To add one or more online dump entries to the catalog, use the following syntax: ADD DUMPS {online-dump-file } {(online-dump-file [,online-dump-file]...)} ,SERIAL serial-number ,TYPE ONLINEDUMP (master, data) {,DISKMEDIA {disk } {(disk [,disk]...)}} {,TAPEMEDIA {tape } {(tape [,tape]...
ADD DUMPS TMFCOM Commands Note. If only a master audit trail is configured, the values for master and data are identical. DISKMEDIA for an online dump to disk, identifies the disk volume on which the dump is located. Any number of disks can be specified for an online dump, without limit. The format for disk is: [node.]volume.{xx}serial-number.Ffile-number node is the node where the dump is located. volume is the volume on which the dump is located. {xx}serial-number identifies the dump.
ADD DUMPS TMFCOM Commands TAPEMEDIA for an online dump to tape, identifies the tape volume on which the online dump is stored. tape is specified as: tape-volume:part:copy where: tape-volume is the name of the tape volume. part specifies which part of the online dump is stored on this tape volume. For example, if each copy of the dump requires three tape volumes, part is 1, 2, or 3. Because part must be specified, it does not have a default value.
ADD DUMPS TMFCOM Commands year is a four-digit integer for the calendar year. Note. You can use either dashes (-) or spaces, or both, as delimiters to separate the month, day, and year values from one another, but you must use at least one of these delimiters. hr is an integer for the hour, from 0 through 23. min is an integer for the minute, from 00 through 59. sec is an integer for the second, from 00 through 59. GMT indicates that the TIME option is specified in Greenwich mean time.
ADD DUMPS TMFCOM Commands Usage Guidelines When an audit or online dump occurs, information describing the dump is recorded in the TMF catalog. Dump entries contain the names of the files dumped, the names of the tape or disk volumes containing the dumps, dump serial numbers, and other related information. If a dump entry is damaged, lost, or mistakenly deleted, you can restore it by issuing the ADD DUMPS command. Note.
ADD DUMPS TMFCOM Commands You must specify either the TAPEMEDIA option or the DISKMEDIA option, but you cannot specify both. You do not have to use the ADD TAPEMEDIA command to insert entries for the tape volumes into the TMF catalog; they are inserted automatically by the ADD DUMPS command. When adding entries for a multi-copy dump to the TMF catalog, be sure to specify part numbers for all copies of the dump in the TAPEMEDIA option of the same ADD DUMPS command.
ADD DUMPS TMFCOM Commands The next ADD DUMPS command restores to the TMF catalog an entry for an online dump for the file $DATA3.TMFNS02F.FILEA, which is stored on the tape volume T6250: TMF 34> ADD DUMPS $DATA3.TMFNS02F.FILEA, SERIAL 121, >>>TAPEMEDIA T6250:1:1, TYPE ONLINEDUMP (18,18), & >>>TIME MAR 12 2002, 10:15:12 & The subsequent ADD DUMPS command restores to the catalog an entry for an online dump of the file $DATA3.TMFN12.MAILFNS, which was dumped to the disk file \REMOTE.$DUMP.YC001000.
ADD DUMPS TMFCOM Commands TAPEMEDIA (TAPE20:1:1, TAPE21:1:2) . . . ADD DUMPS $DATA1.HRDATA.FILE499, SERIAL 101, & TYPE ONLINEDUMP (3,3), TIME 14-Mar-2002 05:34:15 GMT, & TAPEMEDIA (TAPE20:1:1, TAPE21:1:2) ADD DUMPS $DATA1.HRDATA.FILE500, SERIAL 101, & TYPE ONLINEDUMP (3,3), TIME 14-Mar-2002 05:32:15 GMT, & TAPEMEDIA (TAPE20:1:1, TAPE21:1:2, TAPE30:2:1, TAPE31:2:2) ADD DUMPS $DATA1.HRDATA.FILE501, SERIAL 101, & TYPE ONLINEDUMP (3,3), TIME 14-Mar-2002 05:34:15 GMT, & TAPEMEDIA (TAPE30:1:1, TAPE31:1:2) . .
ADD RESOURCEMANAGER TMFCOM Commands ADD RESOURCEMANAGER The ADD RESOURCEMANAGER command adds one or more recoverable resource managers to the resource manager directory. ADD {RESOURCEMANAGER | RM} {rm-name } {(rm-name [,rm-name]...)} ,OWNER {username | userid} where username is: group-name.user-name and userid is: (group-id,user-id) rm-name is the name of the recoverable resource manager to be added to the directory.
ADD RESOURCEMANAGER TMFCOM Commands TMF State Requirement Before you can enter the ADD RESOURCEMANAGER command, TMF must be started. Usage Guidelines In heterogeneous transaction processing, TMF can start a transaction and then subcontract portions (branches) of the transaction to one or more foreign transaction management systems operating on platforms other than the NonStop system. Alternatively, a foreign transaction management system can begin a transaction and then subcontract parts to TMF.
ADD RESOURCEMANAGER TMFCOM Commands be used by a gateway process. This directory is maintained by the TMP. Registration creates an entry for the resource manager in the directory. Associated with each resource manager is a resource manager file. When a gateway process asks to open a recoverable resource manager, the TMP verifies that the resource manager is registered and authenticates the resource manager’s authorization to open this file.
ADD TAPEMEDIA TMFCOM Commands ADD TAPEMEDIA The ADD TAPEMEDIA command adds one or more tape volumes to the TMF catalog and, optionally, labels these volumes. ADD TAPEMEDIA {tape-volume } {(tape-volume [,tape-volume]...)} {tape-labeling-options} {tape-status-options } where tape-labeling-options are: ,LABEL ON [!] ,DRIVE [node.
ADD TAPEMEDIA TMFCOM Commands and the volume has already been labeled, the ADD TAPEMEDIA command fails. DRIVE [node.]device-name identifies the tape drive on which you want to label tape volumes. Guardian labeled-tape processing must be enabled on the node (system) you specify in node. This parameter is required if you want to label tapes. node is the name of the local or remote node at which the tape drive is connected.
ADD TAPEMEDIA TMFCOM Commands BAD indicates that the tape volume is defective and cannot be used later for dumping files or for file recovery. RELEASED indicates that the contents of the tape volume are no longer required for file recovery, and that the tape is not available for re-use in dumping or for file recovery. SCRATCH indicates that the tape volume can be used for dumping files. Security Restrictions You can issue the ADD TAPEMEDIA command only if you are a member of the super user group.
ADD TAPEMEDIA TMFCOM Commands For more information about tape media, dumps directed to them, and catalog entries describing them, see the TMF Operations and Recovery Guide.
ALTER AUDITDUMP TMFCOM Commands ALTER AUDITDUMP The ALTER AUDITDUMP command changes the configured attribute values of an audit dump process.
ALTER AUDITDUMP TMFCOM Commands BLOCKSIZE {4 | 8 | 12 | 16 | 20 | 24 | 28 | 32 | 36 | 40 | 44 | 48 | 52} for dumps to tape, sets the tape data block length when multiplied by 1024 bytes. Using large data block lengths is more efficient, but length is limited by the density in bits per inch (bpi) at which the tape drive writes tapes. The following are recommended values: Density (bpi) 800 1600 6250 BLOCKSIZE 4 8 28 The originally assigned default is 28. Note.
ALTER AUDITDUMP TMFCOM Commands If the audit dump process fails while making serial copies, completed copies are kept in the catalog. When the audit dump process resumes, the number of completed copies is subtracted from the number of copies specified to determine the number of copies remaining to be made. The originally assigned default is COPIES 1 PARALLEL, which produces one copy, starting with the next tape dump operation.
ALTER AUDITDUMP TMFCOM Commands If the UNLOAD option is OFF, the tape is not unloaded after it is verified. If tape verification fails, an error message appears, the audit dump terminates, and the audit dump copy is marked invalid in the catalog. Tape verification approximately doubles the time needed for an audit dump. The originally assigned default is VERIFYTAPE OFF. UNLOAD for dumps to tape, determines whether the tape is unloaded after it is written.
ALTER AUDITDUMP TMFCOM Commands The format for disk is as follows: • • For disks on local nodes: [node.]volume[.prefix] For disks on remote nodes: node.volume.prefix prefix is two alphabetic characters, to which TMF appends a six-digit integer to name the audit dump file. If you specify a list of disks, TMF tries to send the audit dump to the first disk listed. If that disk cannot be accessed or is out of space, TMF tries the next disk, and so forth.
ALTER AUDITDUMP TMFCOM Commands DELDISKMEDIA deletes individual disk volumes from the configuration. The optional and required syntax items and the naming conventions for the prefix are the same as those for ADDDISKMEDIA. Note.
ALTER AUDITDUMP TMFCOM Commands Attributes that you do not specify remain unchanged. So, if you omit an optional parameter, one of the following actions takes place: • • If one or more previous TMFCOM commands (such as ALTER AUDITDUMP or ADD AUDITTRAIL) specified the parameter, the value entered in the last of these commands remains assigned. For example, if the last ALTER AUDITDUMP command assigned the node \NYORK for the SYSTEM parameter, the current ALTER AUDITDUMP command would use the node \NYORK.
ALTER AUDITDUMP TMFCOM Commands Examples The following command causes two parallel copies of each future audit dump for the master audit trail to be directed to magnetic tape drives on the remote system \LA01, changes the blocksize to 16, and requests that tape verification be performed: TMF 11> ALTER AUDITDUMP MAT, SYSTEM \LA01, COPIES 2 PARALLEL, & >>>BLOCKSIZE 16, VERIFYTAPE ON The next command specifies that two parallel copies of each audit dump for the master audit trail be directed to two magnetic
ALTER AUDITTRAIL TMFCOM Commands ALTER AUDITTRAIL The ALTER AUDITTRAIL command changes the configured attribute values of an audit trail and can execute while TMF is running. ALTER AUDITTRAIL {MASTER | MAT } {AUX[ILIARY]nn} [,AUDITDUMP {ON | OFF}] [,ADDACTIVEVOL[S] {volume {(volume [,volume]...) [,DELETEACTIVEVOL[S] {volume {(volume [,volume]...) } }] } }] [,FILESPERVOLUME integer] [,RESET FILESPERVOLUME ] [,ADDOVERFLOWVOL[S] {volume } {(volume [,volume]...
ALTER AUDITTRAIL TMFCOM Commands Unless you also issue an ALTER AUDITDUMP command, the attributes of the audit dump process default to the following values: BLOCKSIZE, the tape data block length: 28 (x 1024 bytes) COPIES, the number of copies to be made in series or in parallel of each dump: 1 parallel SYSTEM, the node (system) on which tape copies are made: the local node VERIFYTAPE, the tape-verification selection: OFF MEDIUM, the medium on which the dump is recorded: TAPE The originally assigned defaul
ALTER AUDITTRAIL TMFCOM Commands audit-trail files in succession to the same volume. When TMF is ready to write to an active-audit volume, it uses the next preallocated file that resides on that volume. Eventually, all preallocated files on the volume are used. If you specify DELETEACTIVEVOL for an active-audit volume that holds files that are needed by TMF, the volume is not immediately removed from the configuration.
ALTER AUDITTRAIL TMFCOM Commands RESET FILESPERVOLUME resets the FILESPERVOLUME attribute to the originally assigned default, which is 5. ADDOVERFLOWVOL[S] DELETEOVERFLOWVOL[S] adds or deletes overflow-audit volumes. If you specify DELETEOVERFLOWVOL for a volume that contains an overflowaudit file, the volume is marked as “deleting” until the overflow-audit file is no longer needed. OVERFLOWTHRESHOLD integer specifies the percentage of audit trail capacity in use above which TMF begins overflow copying.
ALTER AUDITTRAIL TMFCOM Commands BEGINTRANSDISABLE integer specifies the percentage of audit trail capacity that can be consumed before TMF disables new transactions. When the consumed capacity exceeds this value, new transactions are not allowed. When the consumed capacity falls back below this threshold, new transactions are no longer disabled by audit-trail usage (however, new transactions can be disabled for other reasons, as explained in the ALTER BEGINTRANS command description).
ALTER AUDITTRAIL TMFCOM Commands AUDITDUMP Option Considerations If you set the AUDITDUMP attribute to ON after TMF has been running with AUDITDUMP OFF, the first file dumped is the file to which audit information is being written (the current file). For example, if audit information is being written to file sequence number 12 when AUDITDUMP ON is specified, the first file to be dumped will be sequence number 12.
ALTER AUDITTRAIL TMFCOM Commands When you expect to conduct many recovery operations at or near the same time, and you wish to keep as many potentially required files on disk as possible, use the MAXRETAINEDATFILES option. When the recovery load diminishes, use the RESET MAXRETAINEDATFILES option to return to the standard restore-and-purge mechanism for tape files, freeing disk space for other purposes.
ALTER AUDITTRAIL TMFCOM Commands MAXRETAINEDATFILES does not guarantee that an audit-trail file will be restored from tape only once. Space requirements and the impact of other recoveries all play a part in determining which audit-trails files are retained indefinitely.
ALTER AUDITTRAIL TMFCOM Commands volume holds audit-trail files needed by TMF for backout, volume recovery, or system restart, the volume is marked as “deleting.” Any preallocated files stored on the volume are purged immediately, and new files are not written to the volume. When no more audit-trail files reside on the volume, it is removed from the TMF configuration.
ALTER AUDITTRAIL TMFCOM Commands The next command sets the AUDITDUMP attribute to OFF for the master audit trail: TMF 23> ALTER AUDITTRAIL MAT, AUDITDUMP OFF WARNING: After AUDITDUMP is turned OFF, potentially neither volume nor file recovery can recover your files because audittrail files could be purged. Please confirm the option, Auditdump OFF? (Y/N) . . . y Assume that a restore-audit volume was originally configured on the disk drive $TMF01, but now needs to be moved to another disk drive, $TMF02.
ALTER BEGINTRANS TMFCOM Commands ALTER BEGINTRANS The ALTER BEGINTRANS command changes options related to the automatic disabling and reenabling of transaction processing, control of the TMF autoabort feature, and limits on resource managers and transaction branches used in heterogeneous transaction processing.
ALTER BEGINTRANS TMFCOM Commands RESET TRANSCOUNTTHRESH selects the originally assigned default limits, which are 1500 for integer1 and 1600 for integer2. Note. For this and other optional parameters, the originally assigned default is the value initially assigned to the parameter by TMF. The originally assigned default is used for the parameter when no one has explicitly specified or altered this parameter’s value in a previous command.
ALTER BEGINTRANS TMFCOM Commands does not meet this requirement, it is rounded up to the next higher power of 2. As an example, if you enter 1000 for either of these values, TMF sets the value to 1024; if you enter 2000, it sets the value to 2048. RESET TRANSPERCPU selects the originally assigned default values, which are 1024 for both integer7 and integer8. AUTOABORT [timeout | 0 ] RESET AUTOABORT controls the autoabort feature.
ALTER BEGINTRANS TMFCOM Commands BRANCHESPERRM integer11 RESET BRANCHESPERRM specifies the maximum number of transaction branches that can be concurrently imported or exported by each recoverable or volatile resource manager. The specified value is rounded to the nearest multiple of 16. The minimum value allowed is 16, and the maximum is 1024. The default value is 128. RESET BRANCHESPERRM selects the originally assigned default value for integer11, which is 128.
ALTER BEGINTRANS TMFCOM Commands • If no previous TMFCOM command specified the parameter, the originally assigned default remains assigned. Note. You can specify multiple parameters in the ALTER BEGINTRANS command. You must specify at least one parameter, or an error results. For transaction processing to be reenabled after it has been disabled because one of the upper limits set by ALTER BEGINTRANS has been reached, all of the following conditions must exist: • • • • TMF must be started.
ALTER BEGINTRANS TMFCOM Commands either use SNOOP to lower the disconnect timer value and then reenter the ALTER BEGINTRANS command with the same AUTOABORT timeout value, or reenter the ALTER BEGINTRANS command with an AUTOABORT timeout value higher than the present disconnect timer value. Note.
ALTER CATALOG TMFCOM Commands ALTER CATALOG The ALTER CATALOG command changes the configured attribute values of the catalog process that affect the management of online and audit dumps. ALTER CATALOG, attribute [,attribute] where attribute is: [RELEASED {OFF | ON}] [RETAINDEPTH integer] [RESET RETAINDEPTH ] [ROUNDROBIN {OFF | ON}] RELEASED {OFF | ON} determines the status of an online or audit dump tape volume after all the dumps on it have been marked for deletion.
ALTER CATALOG TMFCOM Commands When the number of generations specified by integer is reached for all the files in an online dump, the status of the tape volume is changed as follows: • • To SCRATCH if you specified RELEASED OFF To RELEASED if you specified RELEASED ON Increasing integer causes the number of tape volumes required by TMF to increase, because more online dump generations are retained in the TMF catalog.
ALTER CATALOG TMFCOM Commands current status. The catalog is maintained by the catalog process, which starts when the START TMF command is issued and stops when the STOP TMF command completes execution. The catalog process starts in the same processors as the transaction management process (TMP), unless otherwise directed by the ALTER PROCESS command. Attributes that you do not specify remain unchanged.
ALTER CATALOG TMFCOM Commands protection window for your files. Because of these advantages, ROUNDROBIN ON is the generally recommended setting for this option. Note. ROUNDROBIN does not support the ability to divide the TMF tapes into multiple pools. In any TMF configuration, there is only one pool of tapes from which TMF can select. To display the complete list of tapes in the TMF catalog, use the INFO TAPEMEDIA command.
ALTER DATAVOLS TMFCOM Commands ALTER DATAVOLS The ALTER DATAVOLS command changes the configured attribute values of a data volume. ALTER DATAVOL[S] {volume } {(volume [,volume]...)} [,RECOVERYMODE {ONLINE | ARCHIVE}] volume identifies the data volume whose attributes are to be altered. Note. TMF is shipped from the factory with the $DSMSCM disk volume configured as a TMF data volume.
ALTER DATAVOLS TMFCOM Commands TMF State Requirement Before you can enter the ALTER DATAVOLS command, TMF must be started. Usage Guidelines The volumes acted on by this command must be in the started, disabled, or down state. (These states, and others, are explained in the discussion of the STATUS DATAVOLS command.) Caution.
ALTER DUMPS TMFCOM Commands ALTER DUMPS The ALTER DUMPS command changes dump entries in the TMF catalog. ALTER DUMPS {file-set } {(file-set [,file-set]...)} [,INVALID {OFF | ON} ] [,RELEASED {OFF | ON} ] [,SERIAL serial-number] file-set identifies the dump files whose entries are to be changed. For online dumps, enter file-set in the following format: [[{volume | *}.]{subvolume | *}.]{file-id | *} An asterisk (*) indicates “all”; thus, *.* indicates all files in all subvolumes on the default volume.
ALTER DUMPS TMFCOM Commands ON changes the entries for the specified dumps to indicate you no longer need these dumps. Use this option when recent dumps exist in the catalog but have been damaged or marked as deleted. If the catalog shows only one valid dump for a given serial number, and you release that dump, the entire dump serial number is removed from the catalog. SERIAL serial-number directs this ALTER DUMPS command to change the catalog entries for only the dumps with the specified serial number.
ALTER PROCESS TMFCOM Commands ALTER PROCESS The ALTER PROCESS command changes the configured attribute values of various TMF process types. ALTER PROCESS {process-type } {(process-type [,process-type]...
ALTER PROCESS TMFCOM Commands process-type identifies the type of TMF process whose configuration attributes are to be altered: Process-type Process-type Description AUDITDUMP Audit dump process, which dumps audit-trail files to disk or tape. AUDITRESTORE Audit restore process, which restores audit dumps from disk or tape. BACKOUT Backout process, which undoes the effects of incomplete transactions. CATALOG Catalog process, which manages the TMF catalog.
ALTER PROCESS TMFCOM Commands CPUS cpu-list RESET CPUS identifies the processor in which the selected process type runs. cpu-list can range from 0 through 15. Enter cpu-list in one of the following formats: {cpu-num } {(cpu-num [,cpu-num]...)} RESET CPUS clears the cpu-list. The processor is assigned as follows: • • • If the command specifies a cpu-list, this list is searched from beginning to end to beginning again, until a processor is found.
ALTER PROCESS TMFCOM Commands RESET SWAP explicitly directs the KMSF to select the default swap volume. For the TMFMON and TMP process types, the SWAP parameter has no effect. MAKESAVEABEND {ON | OFF} determines whether an INSPECT program save-abend file is created if a process of the specified type terminates abnormally. MAKESAVEABEND ON creates the file if abnormal termination occurs. MAKESAVEABEND OFF suppresses creation of the file. The default is MAKESAVEABEND ON.
ALTER PROCESS TMFCOM Commands EXTENDEDSEGSIZE (integer1, integer2) RESET EXTENDEDSEGSIZE determines the size, in megabytes, of the process' extended segment. The integer1 and integer2 values are the initial size and the growth limit, respectively, for the extended segment. The growth limit must be equal to or greater than the initial size and must be a multiple of the initial size.
ALTER PROCESS TMFCOM Commands specification applies to all processes of this type. For instance, when you specify CPUS 1,2,5 for the BACKOUT process type, all backout processes can run in those processors only. For each TMF process type, the description and start-up characteristics are listed next. Each description summarizes the process type’s purpose, execution characteristics, and default processor assignment.
ALTER PROCESS TMFCOM Commands requests from other TMF processes, TMCOM commands dealing with tape and dump media, and requests from tape-handling processes. Up to two catalog processes (a primary and a backup process) can run at any time, but never in the same processor. Process start-up: Catalog processes start when TMF is started, and terminate when TMF is stopped. If a catalog process stops or abends while TMF is running, the TMP automatically restarts it.
ALTER PROCESS TMFCOM Commands • ONLINEDUMP Description: An online dump process dumps audited database files to secondary storage, such as tape or disk. It runs only while the dump is in progress. By default, online dump processes are dynamically assigned to one or more processors as needed. You can override the default by adding or removing processors for this process type. Process start-up: An online dump processes starts whenever the TMFCOM DUMP FILES command is issued.
ALTER PROCESS TMFCOM Commands • TMP Description: A TMP process is one of the transaction management process pairs that coordinates the TMF configuration and distributed transactions. It is in charge of all operations that require a single point of control, such as starting and stopping TMF, initiating the recovery processes, and implementing configuration changes. It manages the data volumes and audit trails, and is the final authority on whether transactions should be committed or aborted.
ALTER PROCESS TMFCOM Commands • Stop and reload each processor individually Caution. If you use the second of these approaches, do not stop, at the same time, both members of any processor pair attached to a critical resource such as the $SYSTEM disk. Ensure that either the primary or backup processor remains running while you stop and reload the other member of the pair. For more information about the effect of altering process attributes, see Stopping and Restarting TMF Processes on page 3-89.
ALTER PROCESS TMFCOM Commands On NonStop servers, the TMP always runs four concurrent backout processes for each system, regardless of the number of processors on the system. These backout processes are created whenever the START TMF command is issued. You can change their processor assignment with the CPU parameter.
ALTER PROCESS TMFCOM Commands server and the applications that you run. As an example, the portion of the TMP’s extended segment used to support data volumes, audit trails, and dependent processes depends on the configuration of your system. Larger configurations require more space for control tables. The remaining space is used for dynamic allocation of TCBs.
ALTER PROCESS TMFCOM Commands and used until modified by the ALTER PROCESS command. The following ALTER PROCESS command for the BACKOUT process type, for example, changes the integer1 value from 5 MB to 20 MB, and the integer2 value from 40 MB to 80 MB: ALTER PROCESS BACKOUT, EXTENDEDSEGSIZE (20,80) In the “integer2 Default Value” column, the notation N/A means that the segment size for this process type does not automatically increase; any value you specify for integer2 in EXTENDEDSEGSIZE is ignored.
ALTER PROCESS TMFCOM Commands You cannot manually adjust the segment size beyond 128 MB; the growth to the 1024-MB upper limit is managed entirely by TMF. EXTENDEDSEGIZE Option Considerations for the TMFMON In addition to the considerations common to the TMP and TMFMON described under EXTENDEDSEGSIZE Option Considerations on page 3-85, the TMFMON’s extended segment has a relatively fixed component for various TMF Library tables and the support of disk volumes attached to each CPU.
ALTER PROCESS TMFCOM Commands Table 3-2. Stopping and Restarting TMF Processes Process Type How Stopped and Restarted TMP To manually stop and restart the TMP process pair: 1. Issue a STOP TMF command to obtain a clean shutdown of TMF. 2. Issue a STOP TMF, ABRUPT command to stop the TMP processes. (This operation is equivalent to a controlled TMF crash, which terminates both the primary and backup TMPs. A new TMP process pair is created automatically.) 3. Issue a START TMF command to restart TMF.
ALTER PROCESS TMFCOM Commands Table 3-2. Stopping and Restarting TMF Processes Process Type How Stopped and Restarted AUDITDUMP Processes of these types are transient in the system; they are started automatically as they are needed, and terminate automatically when they are no longer needed.
ALTER PROCESS TMFCOM Commands To correct this situation, you can use the TERM option in the ALTER PROCESS command as follows, with hometerm indicating a valid home terminal to be used by the TMP and TMFMON2 process types in TMF: ALTER PROCESS (TMFMON2, TMP), TERM hometerm Examples The following ALTER PROCESS command alters the configuration of the catalog process type so that processes of this type run on CPUs 0 and 1: TMF 62> ALTER PROCESS CATALOG, CPUS (0,1) The next command specifies that all backout
ALTER TAPEMEDIA TMFCOM Commands ALTER TAPEMEDIA The ALTER TAPEMEDIA command changes the configured attribute values of tape volumes. ALTER TAPEMEDIA {tape-volume } {(tape-volume [,tape-volume]...)} ,STATUS {ASSIGNED} {BAD } {RELEASED} {SCRATCH } tape-volume identifies the tape volume whose entries in the catalog are to be changed. For this parameter, use the name magnetically encoded on the tape volume. STATUS specifies the status of the tape volume named in this command.
ALTER TAPEMEDIA TMFCOM Commands Security Restrictions You can issue the ALTER TAPEMEDIA command only if you are a member of the super user group. TMF State Requirement Before you can enter the ALTER TAPEMEDIA command, TMF must be started.
ALTER TMF TMFCOM Commands ALTER TMF The ALTER TMF command changes the TMF configuration volume or switches the functions of the TMP’s primary and backup processes. ALTER TMF, {CONFIGVOL volume } {SWITCHPROCESS TMP} CONFIGVOL volume specifies the name of the volume that contains the configuration files to be used in the next TMF startup. The volume must be accessible by the TMFMON2 process, which creates other TMF processes during TMF startup.
ALTER TMF TMFCOM Commands You can restart TMF with a START TMF command. Caution. Be very careful when entering the ALTER TMF command with the CONFIGVOL option, because this command makes the previous TMF configuration inaccessible by changing the configuration volume. Because your TMF configuration is thereafter defined on the new configuration volume, it is a good precaution to ensure that this volume is a member of a mirrored disk pair.
CANCEL OPERATIONS TMFCOM Commands CANCEL OPERATIONS The CANCEL OPERATIONS command cancels a specific TMF file-recovery or dumpfiles operation. CANCEL OPERATION[S] operation-number operation-number is an integer that identifies the operation to be canceled, as described under “Usage Guidelines.” The lowest operation number assigned is 1, and the highest is 100. Security Restrictions You can issue the CANCEL OPERATIONS command only if you are a member of the super user group.
CANCEL OPERATIONS TMFCOM Commands Examples The following CANCEL OPERATIONS command cancels the operation identified by operation-number 45: TMF 81>CANCEL OPERATION 45 TMF 82> HP NonStop TMF Reference Manual—540138-001 3- 97
CLOSE RESOURCEMANAGER TMFCOM Commands CLOSE RESOURCEMANAGER The CLOSE RESOURCEMANAGER command initiates closure of one or more recoverable resource managers that are currently open by a gateway process. CLOSE {RESOURCEMANAGER | RM} {rm-name } {(rm-name [,rm-name]...)} rm-name is the name of the recoverable resource manager to be closed.
CLOSE RESOURCEMANAGER TMFCOM Commands Usage Guidelines Note. Resource managers, to which the CLOSE RESOURCEMANAGER command applies, support heterogeneous transaction processing. Resource managers are used in products such as NonStop TUXEDO. Although TMFCOM and the TMFSERVE programmatic interface provide TMF commands and options for operating on resource managers, system managers who use them do so in the context of issues involving multiple software subsystems and interplatform considerations.
CMDVOL TMFCOM Commands CMDVOL The CMDVOL command specifies the default volume and subvolume names for expanding unqualified file names other than those in OBEY commands. CMDVOL [volume ] [[volume.]subvolume] volume is the name of the default disk volume. subvolume is the name of the default subvolume. Security Restrictions Anyone can enter the CMDVOL command. TMF State Requirement You can enter the CMDVOL command at any time, whether or not TMF has been started.
CMDVOL TMFCOM Commands If you specify an invalid volume name in volume, or an invalid subvolume name in subvolume, an error message appears and the CMDVOL command is ignored. The CMDVOL command applies to all unqualified file names encountered in TMFCOM commands during this session except file names used as OBEY command parameters. (However, the CMDVOL command does apply to file names that appear within OBEY command files themselves.
DELETE CATALOG TMFCOM Commands DELETE CATALOG The DELETE CATALOG command clears from the TMF catalog all online dump, audit dump, and media entries, and resets to 64 the counter used for assigning dump serial numbers.
DELETE DATAVOLS TMFCOM Commands DELETE DATAVOLS The DELETE DATAVOLS command removes one or more data volumes from the TMF configuration. DELETE DATAVOL[S] {volume } {(volume [,volume]...)} [,ALLOWINCONSISTENCY] volume identifies a data volume to be deleted. ALLOWINCONSISTENCY indicates that the data volumes specified are to be deleted even if it is uncertain that they contain only consistent data.
DELETE DATAVOLS TMFCOM Commands catalog; this allows the audit dumps associated with the deleted volume to be recycled. If any online dumps for the deleted volume remain in the catalog, however, audit dump media will not be recycled, and the performance of the catalog process will eventually degrade as the catalog database grows.
DELETE DUMPS TMFCOM Commands DELETE DUMPS The DELETE DUMPS command removes dump entries from the TMF catalog and attempts to delete the associated dump files from disk. DELETE DUMPS {file-set } [!] {(file-set [,file-set]...)} [!] [,SERIAL serial-number] file-set [!] identifies the files in the online dump or the audit dump whose entries are to be deleted from the catalog. For online dumps, enter file-set in the following format: [[{volume | *}.]{subvolume | *}.
DELETE DUMPS TMFCOM Commands SERIAL serial-number directs this DELETE DUMPS command to remove the catalog entries only for dumps with the specified serial number. You can obtain information about dump serial numbers by using the INFO DUMPS command or by examining reports produced for an audit or online dump. Security Restriction You can issue the DELETE DUMPS command only if you are a member of the super user group.
DELETE DUMPS TMFCOM Commands Examples The following DELETE DUMPS command deletes dumps for the audited file $DATA3.TMFSN02F.F65289S from the TMF catalog: TMF 6> DELETE DUMPS $DATA3.TMFSN02F.F65289S The next DELETE DUMPS command deletes from the catalog all files that belong to dumps identified by serial number 1000, regardless of whether those dump files were purged from disk: TMF 7> DELETE DUMPS *.*.
DELETE RESOURCEMANAGER TMFCOM Commands DELETE RESOURCEMANAGER The DELETE RESOURCEMANAGER command deletes one or more recoverable resource managers from the resource manager directory. DELETE {RESOURCEMANAGER | RM} {rm-name } {(rm-name [,rm-name]...)} rm-name is the name of the recoverable resource manager to be deleted from the directory.
DELETE RESOURCEMANAGER TMFCOM Commands Usage Guidelines Note. Resource managers, to which the DELETE RESOURCEMANAGER command applies, support heterogeneous transaction processing. Resource managers are used in products such as NonStop TUXEDO. Although TMFCOM and the TMFSERVE programmatic interface provide TMF commands and options for operating on resource managers, system managers who use them do so in the context of issues involving multiple software subsystems and interplatform considerations.
DELETE TAPEMEDIA TMFCOM Commands DELETE TAPEMEDIA The DELETE TAPEMEDIA command removes tape-volume entries from the TMF catalog and also deletes the entries for dumps stored on the removed tape volumes. DELETE TAPEMEDIA {tape-volume } {(tape-volume [,tape-volume]...)} tape-volume identifies the tape volume whose entries are to be deleted from the catalog. For this parameter, use the name magnetically encoded on the tape volume.
DELETE TMF TMFCOM Commands DELETE TMF The DELETE TMF command purges the entire TMF configuration, including volume and file recovery information for the database. Only tape media names are retained in the TMF catalog. This command, entered only when TMF is stopped, produces an empty configuration with no audit trails and with default values for other configuration information. DELETE TMF is typically used to make major configuration changes.
DELETE TMF TMFCOM Commands flags value is not zero, it appears for each transaction listed by the STATUS TRANSACTIONS command. Example The following DELETE TMF command purges the TMF configuration. Immediately following this command, TMFCOM displays a warning and prompts you to confirm the delete operation: TMF >17 DELETE TMF WARNING: After a DELETE TMF command, neither volume recovery nor file recovery can recover your files. Use CAUTION when performing a DELETE TMF operation in a crisis situation.
DELETE TRANSACTION TMFCOM Commands DELETE TRANSACTION The DELETE TRANSACTION command forcibly removes a transaction from the system. DELETE TRANS[ACTION] transaction-id where transaction-id is: [node. [node-number. [node(tm-flags). [node-number(tm-flags). [(tm-flags). ] ] ] cpu.seq-num ] ] transaction-id identifies the transaction to be deleted: node is the name of the node (system) on which the transaction originated, which is known as the home node for the transaction.
DELETE TRANSACTION TMFCOM Commands seq-num is a sequence number assigned by TMF to the transaction, which distinguishes it from other transactions originating in the same processor on the same home node under the current TMF configuration. Security Restrictions You can enter the DELETE TRANSACTION command only if you are logged on under the super ID. (The super ID is the person with the user ID 255,255−in effect, the group manager of the super user group.
DELETE TRANSACTION TMFCOM Commands Example The following DELETE TRANSACTION command deletes the transaction identified as \TSII.2.1958911: TMF 19> DELETE TRANSACTION \TSII.2.
DISABLE AUDITDUMP TMFCOM Commands DISABLE AUDITDUMP The DISABLE AUDITDUMP command suspends an audit dump process, preventing the dumping of audit-trail files. DISABLE AUDITDUMP {MASTER | MAT } {AUX[ILIARY]nn} [,ABRUPT] MASTER | MAT AUX[ILIARY]nn specifies the audit trail associated with the audit dump process that is to be suspended, thus identifying that process. MASTER or MAT specifies the master audit trail. AUXILIARYnn or AUXnn specifies an auxiliary audit trail.
DISABLE AUDITDUMP TMFCOM Commands The ABRUPT option offers a quick method for suspending an audit dump in progress. Without this option, you would need to take the following steps to suspend that dump: 1. Issue a STATUS AUDITDUMP command to display the name of the current audit dump process. 2. Issue a DISABLE AUDITDUMP command, identifying the process by its associated audit trail, to disable the process. (At this point, remember, the dump currently in progress still continues.) 3.
DISABLE BEGINTRANS TMFCOM Commands DISABLE BEGINTRANS The DISABLE BEGINTRANS command suspends transaction processing throughout the TMF system. DISABLE BEGINTRANS Security Restrictions You can enter the DISABLE BEGINTRANS command only if you are a member of the super user group. TMF State Requirement Before you can enter the DISABLE BEGINTRANS command, TMF must be started.
DISABLE DATAVOLS TMFCOM Commands DISABLE DATAVOLS The DISABLE DATAVOLS command shuts down transaction processing (audited updates) for the specified data volume and places this volume in the disabled state so that it will not be automatically restarted by TMF. DISABLE DATAVOL[S] {volume } {(volume [,volume]...)} [,ABRUPT] volume identifies a data volume for which transaction processing is to be disabled.
DISABLE DATAVOLS TMFCOM Commands If you want to disallow audited updates on a volume that is already being processed by the DISABLE DATAVOLS command (entered without the ABRUPT option), issue a second DISABLE DATAVOLS command with ABRUPT specified. This second command overrides the first and prevents further audited activity on the volume. Much work on behalf of the DISABLE DATAVOLS command is done by the operating system’s disk process.
DISPLAY OPERATIONS TMFCOM Commands DISPLAY OPERATIONS The DISPLAY OPERATIONS command displays the Event Management Service (EMS) messages recorded for a specific TMF operation. DISPLAY OPERATION[S] operation-number [,LONG ] [,BEGINTIME date-time [GMT]] [,LOGFILE filename [,COLLECTOR process-name ] ] operation-number is an integer that identifies the operation for which EMS messages are displayed, as described under “Usage Guidelines.” The lowest operation number assigned is 1, and the highest is 100.
DISPLAY OPERATIONS TMFCOM Commands year is a four-digit integer for the calendar year. Note. You can use either dashes (-) or spaces, or both, as delimiters to separate the month, day, and year values from one another, but you must use at least one of these delimiters. hr is an integer for the hour, from 0 through 23. min is an integer for the minute, from 00 through 59. sec is an integer for the second, from 00 through 59. GMT indicates that the BEGINTIME value is specified in Greenwich mean time.
DISPLAY OPERATIONS TMFCOM Commands Usage Guidelines The DISPLAY OPERATIONS command returns information for one operation only. TMF recognizes each specific instance of a particular kind of operation (such as a TMF start, a TMF stop, or a file recovery) as a unique operation and assigns an operation serial number that distinguishes this operation from other recent operations of the same type.
DISPLAY OPERATIONS TMFCOM Commands If you enter the DISPLAY OPERATIONS command but do not have read-access to the EMS log files, TMFCOM displays Error Messages 951, 952, and 953 and aborts the command. To correct this situation, you must either log on with a super user group ID which automatically grants you read-access to the EMS log files, or have the EMS log files secured to permit you read-access.
DUMP FILES TMFCOM Commands DUMP FILES The DUMP FILES command copies audited files to either tape or disk, producing online dumps. These online dumps might be used later if file recovery is initiated through a RECOVER FILES command. DUMP FILES {file-set } {(file-set [,file-set]...)} [,BLOCKSIZE { 4 | 8 | 12 | 16 | 20 | 24 | 28 | 32 | 36 | 40 | 44 | 48 | 52}] [,COPIES { 1 | 2 } [PARALLEL] ] [,DISKMEDIA {disk } {(disk [,disk]...)} ] [,NOT {file-set } {(file-set [,file-set]...
DUMP FILES TMFCOM Commands as well. All file-set information cannot exceed the size of the SPI message buffer that supports communication between TMFCOM and TMFSERVE, which is 28 KB. If this limit is exceeded, TMFCOM displays Error Message 1050. You can specify a file-set as a file-name pattern. This pattern resembles a file name but designates a set of entities (that is, a set of disk volumes, subvolumes, or files) through the use of pattern-matching (wild-card) characters.
DUMP FILES TMFCOM Commands COPIES { 1 | 2 } [PARALLEL] for dumps to tape, specifies the number of copies made of each online dump. If you set COPIES to 1, only one tape drive is required and the copy is directed to that drive. If you set COPIES to 2, two tape drives are required and the copies are always produced in parallel, not in serial order, regardless of whether you enter the PARALLEL option.
DUMP FILES TMFCOM Commands • • Any value for prefix can be specified. If prefix is not specified, the local node default ZT is automatically assigned as the prefix. Optical disks are not supported for dump to disk operations. If you specify DISKMEDIA, you must omit the following options: BLOCKSIZE, COPIES, SYSTEM, TAPEMEDIA, and VERIFYTAPE. NOT file-set identifies one or more files that are not to be dumped. If you specify the same file in this option and in file-set, the file is not dumped.
DUMP FILES TMFCOM Commands TAPEMEDIA tape-volume for dumps to tape, identifies the tape volume to which the online dumps are written. tape-volume is the identifier magnetically encoded in the tape volume label and registered in the TMF catalog. The maximum number of tape volumes allowed by this command is 16. If the TAPEMEDIA parameter is specified in the DUMP FILES command, TMF attempts to use the tape volume specified by this parameter, as described under Online Dumps to Tape later in this discussion.
DUMP FILES TMFCOM Commands Security Restrictions You can issue the DUMP FILES command only if you are a member of the super user group. TMF State Requirement Before you can enter the DUMP FILES command, TMF must be started. Usage Guidelines The DUMP FILES command dumps the specified audited files to disk if the DISKMEDIA option is specified; otherwise, this command dumps them to tape. Note. For both online dumps and audit dumps, Expand links to remote disk volumes must support 56 KB input/output.
DUMP FILES TMFCOM Commands Online Dumps to Disk Online dumps can span disk volumes. These dumps are recorded in large files, called “disk dump files,” on the disks that are specified with the DISKMEDIA option. There must be enough cumulative space available on all of the specified disks to hold the online dumps. For maximum protection, store your online dumps on disks other than those containing the files being dumped. Store different generations of online dumps on different sets of disks.
DUMP FILES TMFCOM Commands • If no dump medium is specified (that is, if neither TAPEMEDIA nor DISKMEDIA is included) in the DUMP FILES command, tape media is assumed by default; TMF searches the TMF catalog for the first tape volume listed with SCRATCH status and requests the operator to mount that volume. The operator can respond by mounting that volume, or can select another TMF scratch tape volume defined in the TMF catalog.
DUMP FILES TMFCOM Commands Table 3-3. DUMP FILES Output Heading or Item Description Dump Files operation [nn] begun Notification that the dump operation has been started; nn is the operation serial number that distinguishes this operation from other recent operations of the same type. Operation TimeStamp The date and time that the operation began.
DUMP FILES TMFCOM Commands 17:02 20JAN02 243,00,049 TMF *0156* DUMP FILES [1] TMP Process: End operation. The next DUMP FILES command dumps all audited files residing on the disk file $DATA to tape. Because the TAPEMEDIA option is not specified in this command, TMFCOM prompts the operator to mount scratch tapes for the online dump to tape operation: TMF 36> DUMP FILES $DATA.*.
ENABLE AUDITDUMP TMFCOM Commands ENABLE AUDITDUMP The ENABLE AUDITDUMP command permits an audit dump process to resume execution after it has been suspended by the DISABLE AUDITDUMP command, allowing the process to dump audit-trail files once again. ENABLE AUDITDUMP {MASTER | MAT } {AUX[ILIARY]nn} MASTER | MAT AUX[ILIARY]nn specifies the audit trail associated with the audit dump process to resume execution, thus identifying that process. MASTER or MAT specifies the master audit trail.
ENABLE BEGINTRANS TMFCOM Commands ENABLE BEGINTRANS The ENABLE BEGINTRANS command resumes transaction processing after it has been suspended by the DISABLE BEGINTRANS command. ENABLE BEGINTRANS Security Restrictions You can enter the ENABLE BEGINTRANS command only if you are a member of the super user group. TMF State Requirement Before you can enter the ENABLE BEGINTRANS command, TMF must be started.
ENABLE DATAVOLS TMFCOM Commands ENABLE DATAVOLS The ENABLE DATAVOLS command reenables transaction processing (audited updates) for the specified data volumes, and makes them subject to automatic restart by TMF. If the data volumes specified are accessible, they are restarted immediately. ENABLE DATAVOL[S] {volume } {(volume [,volume],...) } { * [,NOT volume] } { * [,NOT (volume[,volume]...)]} volume identifies a disabled data volume for which transaction processing is to be reenabled.
ENABLE DATAVOLS TMFCOM Commands Examples The following ENABLE DATAVOLS command reenables transaction processing for the volume named $DATA2: TMF 67> ENABLE DATAVOLS $DATA2 $DATA2 -- enabled. TMF 68> The next ENABLE DATAVOLS command reenables transaction processing on all disabled data volumes except $DATA4 and $DATA5: TMF 68> $DATA1 $DATA3 $DATA6 $DATA7 ENABLE DATAVOLS *, NOT ($DATA4, $DATA5) -- enabled. -- enabled. -- enabled. -- enabled. . . .
ENV TMFCOM Commands ENV The ENV command displays the current operating environment for your TMFCOM session. ENV Security Restrictions Anyone can enter the ENV command. TMF State Requirement You can enter the ENV command at any time, even if TMF has been started. Usage Guidelines Unqualified file names that appear in TMFCOM commands are expanded according to the default node, volume, and subvolumes currently in effect.
ENV TMFCOM Commands Table 3-4. ENV Output (page 2 of 2) Heading or Item Description In File File (device) used for TMFCOM input (typically, your workstation or terminal). Out File File (device) used for TMFCOM output (typically, your workstation or terminal) Server Process Name of TMFSERVE process with which your TMFCOM is communicating.
EXIT TMFCOM Commands EXIT The EXIT command ends your current TMFCOM session. EXIT Security Restrictions Anyone can enter the EXIT command. TMF State Requirement You can enter the EXIT command at any time, whether or not TMF has been started. Usage Guidelines If you enter the EXIT command in your current TMFCOM session, TMFCOM terminates the session and returns control to the operating system.
FC TMFCOM Commands FC The FC command permits you to display and repeat or modify a command previously entered in the current TMFCOM session, as recorded in the TMFCOM command history buffer: | linenum | string | “quoted-string ”] FC [-linenum -linenum identifies the command to be displayed relative to the current command line. For instance, FC -3 displays the third command before the current one and allows you to repeat or modify it. linenum identifies the command to be displayed by command line number.
FC TMFCOM Commands command without any parameter, the last TMFCOM command you entered is displayed. You can use the HISTORY command to display the line numbers associated with the most recently entered TMFCOM commands. Only commands currently stored in the history buffer are displayed, and only those can be selected for action by the FC command. When you issue an FC command, the command you specify is displayed and a subcommand prompt (. .) appears.
FC TMFCOM Commands To correct the entry, following the subcommand prompt, enter the replacement character O under the incorrect letter (the first P) that appears on the previous line, then press the Return key (or its equivalent) to transmit the correction: TMF 82>INFP AUDITDUMP * TMF 82.. O TMFCOM now displays the corrected INFO AUDITDUMP command followed by another subcommand prompt that asks for any further corrections.
HELP TMFCOM Commands HELP The HELP command displays syntax information for TMFCOM commands. HELP [command ] [[command] object] [* | ALL ] command specifies the TMFCOM command for which information is to be displayed. object specifies a TMF object for which information is to be displayed. * | ALL displays a list of all TMFCOM commands. Security Restrictions Anyone can enter the HELP command. TMF State Requirement You can enter the HELP command at any time, whether or not TMF has been started.
HELP TMFCOM Commands Examples The following HELP command displays information about the TMFCOM command RESET, showing the objects upon which the command can operate: ~HELP RESET -----------------------------------------------------------| RESET AUDITTRAIL | | RESET DATAVOLS | | RESET DUMPS | | RESET TAPEMEDIA | -----------------------------------------------------------The next HELP command displays the purpose and syntax of the TMFCOM command RESET TAPEMEDIA.
HISTORY TMFCOM Commands HISTORY The HISTORY command displays a history of commands entered during the current TMFCOM session, as maintained in the TMFCOM command history buffer. HISTORY [lines ] [RESET LAST ] [RESET ALL ] lines specifies the number of command lines to display, counting from the most recently entered line. If lines is greater than the number of lines in the history buffer, all lines in the buffer are displayed. If lines is omitted, the last 20 lines are displayed.
HISTORY TMFCOM Commands • • To clear the most recently entered command line in the buffer, and change the current line number to that of the cleared command line, enter the HISTORY command with the RESET LAST option. To clear all commands in the buffer and reset the command line counter to 1, enter the HISTORY command with the RESET ALL option. In the display, all non-blank lines appear, whether or not they contained valid, executable commands.
HISTORY TMFCOM Commands The next HISTORY command clears all command lines in the buffer, and resets the current line number to 1: TMF 10> HISTORY RESET ALL TMF 1> INFO CATALOG Catalog Configuration: retaindepth 2, released on TMF 2> HISTORY 1>INFO CATALOG 2> HISTORY TMF 3> HP NonStop TMF Reference Manual—540138-001 3 -149
INFO AUDITDUMP TMFCOM Commands INFO AUDITDUMP The INFO AUDITDUMP command displays the configured attribute values of audit dump processes. INFO AUDITDUMP [MASTER | MAT ] [AUX[ILIARY]nn ] [(MASTER | MAT [,AUX[ILIARY]nn ])] [(AUX[ILIARY]nn [,MASTER | MAT ])] [(AUX[ILIARY]nn [,AUX[ILIARY]nn])] [ * ] [,OBEYFORM] MASTER | MAT AUX[ILIARY]nn specifies the audit trail associated with the audit dump process whose attributes are to be displayed, thus identifying that process.
INFO AUDITDUMP TMFCOM Commands Usage Guideline The INFO AUDITDUMP command displays a subset of the information presented by the INFO TMF command. Output Displayed The INFO AUDITDUMP command displays the attributes configured for the audit dump process by ALTER AUDITDUMP commands or their defaults. The primary items in the display are listed in Table 3-6. Table 3-6.
INFO AUDITTRAIL TMFCOM Commands INFO AUDITTRAIL The INFO AUDITTRAIL command displays the configured attribute values of audit trails. INFO AUDITTRAIL [MASTER | MAT ] [AUX[ILIARY]nn ] [(MASTER | MAT [,AUX[ILIARY]nn ])] [(AUX[ILIARY]nn [,MASTER | MAT ])] [(AUX[ILIARY]nn [,AUX[ILIARY]nn])] [ * ] [,OBEYFORM] MASTER | MAT AUX[ILIARY]nn identifies the audit trail for which attributes are to be displayed. MASTER or MAT specifies the master audit trail. AUXILIARYnn or AUXnn specifies an auxiliary audit trail.
INFO AUDITTRAIL TMFCOM Commands Usage Guideline The INFO AUDITTRAIL command displays a subset of the information presented by the INFO TMF command. Output Displayed The INFO AUDITTRAIL command displays the attributes configured for the audit trails by ADD AUDITTRAIL and ALTER AUDITTRAIL commands entered previously. The primary items in the display are listed in Table 3-7. Table 3-7.
INFO AUDITTRAIL TMFCOM Commands Examples The following INFO AUDITTRAIL command displays information for the master audit trail: TMF >77 INFO AUDITTRAIL MASTER AuditTrail Configuration: Master ActiveVols: $MAT1, $MAT2 Subvolume ZTMFAT, Prefix AA, filesize 20, filespervolume 3, auditdump on, overflowthreshold 75%, begintransdisable 90% MaxRetainedATFiles 0 OverflowVols: $DATA1 RestoreVols: $DATA2 The next INFO AUDITTRAIL command formats the configuration of the master audit trail as command file text, direc
INFO AUDITTRAIL TMFCOM Commands The following INFO AUDITTRAIL command displays information for all audit trails: TMF 79> INFO AUDITTRAIL * AuditTrail Configuration: Master ActiveVols: $MAT Subvolume ZTMFAT, Prefix AA, filesize 20, filespervolume 5 auditdump on, overflowthreshold 80%, begintransdisable 90% MaxRetainedATFiles 0 OverflowVols: None RestoreVols: $SPARE Auxiliary01: ActiveVols: $AUX Subvolume ZTMFAT, Prefix BB, filesize 20, filespervolume 3 auditdump off, overflowthreshold 90%, begintransdisabl
INFO BEGINTRANS TMFCOM Commands 3 TMFCOM Commands INFO BEGINTRANS The INFO BEGINTRANS command displays the configured attribute values for the BEGINTRANS object that disable and reenable transaction processing and that apply limits on resource managers and transaction branches used in heterogeneous transaction processing. INFO BEGINTRANS [,OBEYFORM] OBEYFORM formats the INFO BEGINTRANS output as command file text that can be executed by TMFCOM.
INFO BEGINTRANS TMFCOM Commands Table 3-8. INFO BEGINTRANS Output Heading or Item Description TRANSCOUNTTHRESH Upper and lower limits at which number of active transactions in the system automatically disables or reenables new transactions. TMFLIBMEMTHRESH Upper and lower limits at which percentage of processor memory allocated to TMFLIB automatically disables or reenables new transactions.
INFO BEGINTRANS TMFCOM Commands Examples The following INFO BEGINTRANS command displays the BEGINTRANS object attributes: TMF 81> INFO BEGINTRANS BeginTrans Configuration: TransCountThresh (1500, 1600) TmfLibMemThresh (85, 90) TmpMemThresh (90, 95) TransPerCpu (1024, 1024) AutoAbort 7200 SECONDS RecRMCount 256 RMOpenPerCpu 128 BranchesPerRM 128 After the next START TMF, the BeginTrans Configuration will be: TransPerCpu (1024, 1024) RecRMCount 128 RMOpenPerCpu 32 BranchesPerRM 128 (The parameter values dis
INFO CATALOG TMFCOM Commands INFO CATALOG The INFO CATALOG command displays the configured attribute values for the catalog process. INFO CATALOG [,OBEYFORM] OBEYFORM formats the INFO CATALOG output as command file text that can be executed by TMFCOM. TMF saves this output in the file designated by the OUT option available with all commands. Subsequently executing this command file produces a new data volume configuration that exactly matches the existing configuration.
INFO CATALOG TMFCOM Commands Table 3-9. INFO CATALOG Output Heading or Item Description Retaindepth Number of online dump generations retained in the catalog. Released Status to which online or audit tape volumes are set after all dumps on the volumes are marked for deletion. If ON, status becomes RELEASED; if OFF, status becomes SCRATCH. Roundrobin ROUNDROBIN attribute setting. If ON, the catalog is searched in round-robin fashion, so that all tapes in the catalog are used before any are re-used.
INFO DATAVOLS TMFCOM Commands INFO DATAVOLS The INFO DATAVOLS command displays the configured attribute values of data volumes, and can also filter and then display volumes based on selected configuration attributes. INFO DATAVOL[S] [volume ] [(volume [,volume]...)] [ * ] [,config-attrib [,config-attrib]...] [,OBEYFORM [, SORT {BYATID | BYNAME} ] ] volume identifies the data volume whose attribute values are to be displayed. * displays the attribute values of all configured data volumes.
INFO DATAVOLS TMFCOM Commands an Alternate Destination on page 2-8. If OBEYFORM is not specified, normal formatting is used. SORT {BYATID | BYNAME} displays the data volume information in the order indicated: BYATID lists data volumes first by audit-trail ID and then alphabetically by data volume name. BYNAME lists the data volumes by name, in alphabetical order. If the SORT parameter is omitted, this option is the default. Security Restrictions Anyone can enter the INFO DATAVOLS command.
INFO DATAVOLS TMFCOM Commands Examples The following INFO DATAVOLS command, issued without any volume names or other options, displays configuration attributes for all data volumes: TMF 90> INFO DATAVOLS Volume Audit Trail Recovery Mode ------------------------------------------------$DATA1 Master Online $DATA2 Master Online $DATA3 Master Online $DATA4 Master Online $DATA5 Master Archive $DATA6 Auxiliary01 Online $DATA7 Auxiliary01 Online $DATA8 Auxiliary01 Archive $DATA9 Auxiliary01 Online The next INFO
INFO DATAVOLS TMFCOM Commands Remember that a data volume cannot be added to a new TMF configuration if it was associated with a previous TMF configuration and thus might be inconsistent. Therefore, before submitting the CONFL2 command file for execution, you must take one of the following actions: • • Edit the ALTER DATAVOLS commands in COMFL2 to include the IGNOREPREVIOUSCONFIG option, which allows the data volumes to be added in spite of possible inconsistencies.
INFO DUMPS TMFCOM Commands INFO DUMPS The INFO DUMPS command displays online and audit dump entries in the TMF catalog. INFO DUMPS [file-set ] [(file-set [,file-set]...)] [,BRIEF | DETAIL | OBEYFORM ] [,MEDIUM {TAPE | DISK} ] [,SERIAL serial-number ] [,SORT {BYFILE | BYSERIAL} ] [,STATUS {ASSIGNED} {INVALID } {RELEASED} ] [,TYPE {AUDITDUMP | ONLINEDUMP} ] [,CATALOG [node.]volume.subvolume] [,NOT {file-set } {(file-set [,file-set]...
INFO DUMPS TMFCOM Commands Note. If you plan to refer to SQL/MX objects in a file-set list, you must use the Guardian names of the underlying files in all TMFCOM commands. You can run the MXGNAMES utility to convert one or more objects’ ANSI names to their underlying Guardian file names. You can then use the Guardian file names in the file-set list. For convenience, MXGNAMES provides an option that generates names formatted as TMF file-sets for direct use in TMFCOM commands.
INFO DUMPS TMFCOM Commands available with all commands. Subsequently executing this command file produces new dump entries that exactly match the existing entries for the dumps you select in INFO DUMPS. Use of the OUT option and command file execution are described in Directing Output to an Alternate Destination on page 2-8. If OBEYFORM is not specified, normal formatting is used. Note. If you use the OBEYFORM option, you must also use the SERIAL option and specify the file-set as “*.*.*”.
INFO DUMPS TMFCOM Commands STATUS selects the dumps for which information is listed, according to their status: ASSIGNED selects only those dumps whose status is ASSIGNED, meaning that the dump file is available for use in file recovery. INVALID selects only those dumps whose status is INVALID, meaning that the dump file is marked in the catalog as unreadable and cannot be used for file recovery.
INFO DUMPS TMFCOM Commands message buffer that supports communication between TMFCOM and TMFSERVE, which is 28 KB. If this limit is exceeded, TMFCOM displays Error Message 1050. Note. If you plan to refer to SQL/MX objects in a file-set list or a NOT file-set list, you must use the Guardian names of the underlying files in all TMFCOM commands. You can run the MXGNAMES utility to convert one or more objects’ ANSI names to their underlying Guardian file names.
INFO DUMPS TMFCOM Commands Output Displayed The INFO DUMPS command displays the attributes for dumps selected by the filtering parameters of this command. The primary items in the display are listed in Table 3-11. Table 3-11. INFO DUMPS Output Heading or Item Description System System on which report is produced. Current Date-Time Date and time report is produced. FileName Name of dumped file. Dump Serial Serial number of dump. Date-Time Date and time of dump (to the minute).
INFO DUMPS TMFCOM Commands BB000001 66 25-Feb-2002 09:52 audit disk BB000002 66 25-Feb-2002 09:52 audit disk BB000003 66 25-Feb-2002 09:52 audit disk BB000004 66 25-Feb-2002 09:52 audit disk BB000005 66 25-Feb-2002 09:52 audit disk \SAB.$DEV2. ZT000066.F0000001 \SAB.$DEV2. ZT000066.F0000001 \SAB.$DEV2. ZT000066.F0000001 \SAB.$DEV2. ZT000066.F0000001 \SAB.$DEV2. ZT000066.
INFO PROCESS TMFCOM Commands INFO PROCESS The INFO PROCESS command displays the configured attribute values for the various TMF process types. INFO PROCESS [process-type ] [(process-type [,process-type]...)] [ * ] [,OBEYFORM] process-type identifies the type of TMF process whose configuration is to be displayed. process-type may be any of the following names: Process-type Process-type Description AUDITDUMP Audit dump process, which dumps audit-trail files to disk or tape.
INFO PROCESS TMFCOM Commands * displays the configured attributes of all process-types. OBEYFORM formats INFO PROCESS output as command file text that can be executed by TMFCOM. TMF saves this output in the file designated by the OUT option available with all commands. Subsequently executing this command file produces a new process configuration that exactly matches the existing configuration.
INFO PROCESS TMFCOM Commands Table 3-12. INFO PROCESS Output Heading or Item Description ProgramFile Name of program file used by process type. Term Name of terminal used by process type. Swap Name of swap file specified for process type, followed by the notation “KSMF is Used.” For more information about SWAP file assignment and this notation, see the ALTER PROCESS command discussion.
INFO PROCESS TMFCOM Commands The next INFO PROCESS command displays the attributes common to all catalog and volume recovery processes: TMF 12> INFO PROCESS (CATALOG, VOLUMERECOVERY) Process Configuration: Catalog: . . . VolumeRecovery: . . . The subsequent INFO PROCESS command displays the attributes of all major TMF process types: TMF 13> INFO PROCESS * Process Configuration: AuditDump: . . . AuditRestore: . . . BackOut: . . .
INFO RESOURCEMANAGER TMFCOM Commands INFO RESOURCEMANAGER The INFO RESOURCEMANAGER command displays the entries for recoverable resource managers currently registered in the resource manager directory. INFO {RESOURCEMANAGER | RM} [rm-name ] [(rm-name [,rm-name]...)] [* ] [,OBEYFORM ] rm-name is the name of the recoverable resource manager whose entry is to be displayed.
INFO RESOURCEMANAGER TMFCOM Commands Usage Guidelines Note. Resource managers, to which the INFO RESOURCEMANAGER command applies, support heterogeneous transaction processing. Resource managers are used in products such as NonStop TUXEDO. Although TMFCOM and the TMFSERVE programmatic interface provide TMF commands and options for operating on resource managers, system managers who use them do so in the context of issues involving multiple software subsystems and interplatform considerations.
INFO RESOURCEMANAGER TMFCOM Commands The next INFO RESOURCEMANAGER command, using the OBEYFORM option, formats the output for a single resource manager as command file text in the file RECMGR on the default volume and subvolume: TMF 21> INFO /OUT RECMGR/ RM TUX-HP@ESSG, OBEYFORM The resulting output, which can be submitted as a command to TMFCOM, is as follows: Add RM TUX-HP@ESSG, OWNER (255,255) HP NonStop TMF Reference Manual—540138-001 3 -178
INFO TAPEMEDIA TMFCOM Commands INFO TAPEMEDIA The INFO TAPEMEDIA command displays the configured attribute values of tape volumes. INFO TAPEMEDIA [tape-volume ] [(tape-volume [,tape-volume]...)] [ * ] [,STATUS {ASSIGNED} {BAD } {RELEASED} {SCRATCH } [,OBEYFORM ] ] tape-volume identifies the tape volume whose entries in the catalog are to be displayed. For this parameter, use the name magnetically encoded on the tape volume. * displays all tape volume entries in the catalog. This is the default.
INFO TAPEMEDIA TMFCOM Commands available with all commands. Subsequently executing this command file produces tape media entries in the catalog that exactly match the existing entries. (The ADD TAPEMEDIA commands created by the OBEYFORM option specify STATUS SCRATCH regardless of the actual tape status, so that all tapes specified can be added back into the catalog.) The use of the OUT option and command file execution are described under Directing Output to an Alternate Destination on page 2-8.
INFO TAPEMEDIA TMFCOM Commands This INFO TAPEMEDIA command, using the OBEYFORM option, formats the output for all tape volumes as command file text in the file TPINFO on the default volume and subvolume: TMF 35> INFO /OUT TPINFO/ TAPEMEDIA *, OBEYFORM The resulting output, which can be submitted from TPINFO as commands to TMFCOM, is: ADD ADD ADD ADD ADD ADD TAPEMEDIA TAPEMEDIA TAPEMEDIA TAPEMEDIA TAPEMEDIA TAPEMEDIA TF0250, TF0251, TF0252, TF0253, TF0254, TF0255, LABEL LABEL LABEL LABEL LABEL LABEL OF
INFO TMF TMFCOM Commands INFO TMF The INFO TMF command displays the configured attribute values of TMF. INFO TMF [,{CNFGFORM | OBEYFORM}] CNFGFORM formats the INFO TMF output as command file text that can be executed by TMFCOM. TMF saves this output in the file designated by the OUT option available with all commands. Subsequently executing this command file produces a running system that exactly matches your present TMF configuration.
INFO TMF TMFCOM Commands TMF State Requirement You can enter the INFO TMF command at any time, whether or not TMF has been started. Usage Guidelines The INFO TMF command displays the current TMF configuration volume and combines the information presented by the INFO commands for the following objects: AUDITDUMP, AUDITTRAIL, BEGINTRANS (only when TMF is running), and CATALOG.
INFO TMF TMFCOM Commands require TMF to be running will not be executed unless you modify the file by adding a START TMF command preceding these commands. Note. To augment the information captured through the INFO TMF, CNFG command, you can capture current information about TMF online and audit dumps by using the INFO DUMPS, OBEYFORM command. For more information about this step, see INFO DUMPS on page 3-165.
INFO TMF TMFCOM Commands BranchesPerRM 128 The following INFO TMF command generates CNFGFORM output: TMF 41> INFO /OUT CNFILE/ TMF, CNFGFORM Alter TMF, ConfigVol $SYSTEM Alter Process AuditDump, & Pri 149, & RESET CPUS, & MakeSaveAbend On , & Debug Off , & Inspect On , & Reset ExtendedSegSize, & PFSSize 1048576, & Reset ProgramFile, & Reset Term, & Reset Swap Alter Process AuditRestore, & Pri 149, & RESET CPUS, & MakeSaveAbend On , & Debug Off , & Inspect On , & Reset ExtendedSegSize, & PFSSize 1048576, &
INFO TMF TMFCOM Commands Alter Process . . . Alter Process . . . Alter Process . . . Alter Process . . . Alter Process . . .
INFO TMF TMFCOM Commands tmpmemthresh (90,95) , & transpercpu (1024,1024) , & autoabort 7200 Seconds , & recrmcount 256 , & rmopenpercpu 96 , & branchesperrm 128 STOP TMF START TMF, DISABLE BEGINTRANS Add Datavol $AEGEAN, AuditTrail Mat, RecoveryMode Online, & IGNOREPREVIOUSCONFIG Add Datavol $ALGAE, AuditTrail Mat, RecoveryMode Online, & IGNOREPREVIOUSCONFIG Add Datavol $ATHENS, AuditTrail Mat, RecoveryMode Online, & IGNOREPERVIOUSCONFIG Add Datavol $ATLIS, AuditTrail Mat, RecoveryMode Online, & IGNOREPR
INFO TMF TMFCOM Commands , $OPR & ) SET AUDITTRAIL RESTOREVOL ( & $MEZRPT & ) ADD AUDITTRAIL Master ALTER AUDITDUMP Master, medium tape ALTER AUDITDUMP Master, copies 1 ALTER AUDITDUMP Master, verifytape Off ALTER AUDITDUMP Master, blocksize 28 ALTER AUDITDUMP Master, system \CYCLONE ALTER CATALOG, & retaindepth 3, & released off, & roundrobin off ALTER BEGINTRANS, & transcountthresh (1500,1600), & tmflibmemthresh (90,95), & tmpmemthresh (90,95), & transpercpu (1024,1024), & autoabort 7200 Seconds, & recr
NEXT AUDITTRAIL TMFCOM Commands NEXT AUDITTRAIL The NEXT AUDITTRAIL command changes audit-trail files for a specified audit trail; it stops new audit records from being added to the current audit-trail file and establishes the next file in the audit trail sequence as the current audit-trail file. NEXT AUDITTRAIL {MASTER | MAT } {AUX[ILIARY]nn} MASTER | MAT AUX[ILIARY]nn identifies the audit trail for which you want to change audit-trail files. MASTER or MAT specifies the master audit trail.
OBEY TMFCOM Commands OBEY The OBEY command executes a series of commands entered in a command file. OBEY [node.][volume.][subvolume.]file-id node identifies the node (system) on which the command file is stored. volume identifies the disk volume on which the command file is stored. subvolume identifies the subvolume on which the command file is stored. file-id identifies the command file, which contains one or more valid TMFCOM commands. Security Restrictions Anyone can enter the OBEY command.
OBEY TMFCOM Commands If TMFCOM encounters an error while executing a command from a command file, TMFCOM terminates command file execution and ignores the remaining commands in the command file. TMFCOM then reads its next command from the file from which it read the OBEY command.
OBEYVOL TMFCOM Commands OBEYVOL The OBEYVOL command specifies the default node, volume, and subvolume names for expanding an unqualified command file name used in an OBEY command. OBEYVOL [[[node.]volume.]subvolume] node is the name of the default node (system). volume is the name of the default disk volume. subvolume is the name of the default subvolume. Security Restrictions Anyone can enter the OBEYVOL command.
OBEYVOL TMFCOM Commands • • If you omit node, no default node is recorded for your session; the node on which your TMFSERVE process is running is assigned. If you omit node, volume, and subvolume, the recorded default node, volume, and subvolume for the OBEY command are cleared. As a result, unqualified file names are expanded according to the defaults in effect when you started TMFCOM.
OPEN SERVER TMFCOM Commands OPEN SERVER The OPEN SERVER command specifies the TMFSERVE process with which your TMFCOM process communicates to control TMF. OPEN SERVER {node } {[node.]server} [,CPU cpu-num ] [,PRI integer ] [,SWAP volume ] [,TERM [node.]term] node identifies the node (system) on which the TMFSERVE process runs. The syntax rules for specifying a node name appear under Disk File Names, earlier in this section. The default is the node on which your TMFCOM process is running.
OPEN SERVER TMFCOM Commands TERM [node.]term identifies the home terminal for the TMFSERVE process. This is the terminal where system start-up error messages are displayed. As a general rule, this option should not be used. Without this option, the default is the home terminal currently used by TMFCOM. Security Restrictions Anyone can enter the OPEN SERVER command. TMF State Requirement You can enter the OPEN SERVER command at any time, whether or not TMF has been started.
OPEN SERVER TMFCOM Commands Figure 3-1. TMFCOM and TMFSERVE Processes TMFCOM SPI Command Messages SPI Response Messages TMFSERVE TMF Volume Recovery TMP File Recovery Backout Catalog TMFDR VST003.vsd In general, you issue an OPEN SERVER command to communicate with an existing TMFSERVE process or to create and communicate with a new TMFSERVE process.
OPEN SERVER TMFCOM Commands TMFSERVE process. Up to 10 user processes can share the same TMFSERVE process. When you enter the OPEN SERVER command, one of the following actions takes place: • • If the TMFSERVE process you specify already exists, TMF establishes communication between this TMFSERVE process and your TMFCOM process. (For an existing process, the OPEN SERVER command can specify the TERM option but not the CPU, PRI, and SWAP options.
OPEN SERVER TMFCOM Commands Figure 3-2. TMFSERVE on a Remote Node \CHICAGO \DENVER TMFCOM TMFSERVE TMFSERVE TMP TMP TMFCOM VST004.vsd Understanding Interoperability Issues When you use a TMFCOM OPEN SERVER command to open a TMFSERVE process on a remote node in an EXPAND network, you may find your TMFCOM process interacting with a newer or older version of TMFSERVE.
OPEN SERVER TMFCOM Commands Table 3-15. TMFCOM vs TMFSERVE Version Interaction: Operational Commands TMFCOM Version TMFSERVE Version Result Current Current Works with no errors. Current Previous Produces a TMFCOM error message. Previous Current Works with no errors (because the new option cannot be specified through TMFCOM). Previous Previous Works with no errors (because the new option cannot be specified through TMFCOM).
OPEN SERVER TMFCOM Commands Priority: Object Name: HomeTerm: Swap Volume: Version: 125 \FOXII.$SYSTEM.SYS00.TMFSERVE \TSII.$ZTN1A $SYSTEM TMFSERVE - T8694G07 - (24NOV2003 - TMF) The next OPEN SERVER command creates a new TMFSERVE process and establishes a connection between this process and the current TMFCOM process.
RECOVER FILES TMFCOM Commands RECOVER FILES The RECOVER FILES command initiates file recovery: restoring a database to a consistent state. RECOVER FILES {file-set } {(file-set [,file-set]...)} [,NOT {file-set } {(file-set [,file-set]...
RECOVER FILES TMFCOM Commands file-set identifies the files to be recovered. Enter file-set in the following format: [[volume.]subvolume.]file-id Note. If you plan to refer to SQL/MX objects in a file-set list, you must use the Guardian names of the underlying files in all TMFCOM commands. You can run the MXGNAMES utility to convert one or more objects’ ANSI names to their underlying Guardian file names. You can then use the Guardian file names in the file-set list.
RECOVER FILES TMFCOM Commands NOT file-set identifies one or more files that are not to be recovered, whether or not they are specified in file-set and regardless of their redo-needed or undo-needed status. The NOT file-set list allows the same pattern-matching (wild-card) characters described earlier in the discussion of the file-set option for this command and the file-set option for the DUMP FILES command on page 3-125.
RECOVER FILES TMFCOM Commands TOFIRSTPURGE terminates file recovery when the first audit record for purging any file in the specified file sets is encountered; the purge record is not reapplied. SERIAL serial-number recovers only files from the online dump identified by serial-number. If you enter a number less than 64, TMFCOM returns an error message. When you select the SERIAL option, TMF always also uses the FROMARCHIVE option, even if you do not explicitly select it.
RECOVER FILES TMFCOM Commands day is a two-digit integer for the day of the month. year is a four-digit integer for the calendar year. Note. You can use either dashes (-) or spaces, or both, as delimiters to separate the month, day, and year values, but you must use at least one of these delimiters. hr is an integer for the hour, from 0 through 23. min is an integer for the minute, from 00 through 59. sec is an integer for the second, from 00 through 59.
RECOVER FILES TMFCOM Commands UNLOAD {ON | OFF} determines whether the tape volume is unloaded after it has been used. ON unloads the tape volume. OFF suppresses unloading. The default is ON. TOPHYSVOL volume identifies the physical target volume on which TMF should place the recovered files. If you specify both the TOPHYSVOL and the WHEREPHYSVOLIS options, the WHEREPHYSVOLIS option takes precedence. Caution.
RECOVER FILES TMFCOM Commands old-fileset-list identifies the source files in the online dump disk or tape, and can specify one or more file-sets, in the following format: file-set (file-set [, file-set]...
RECOVER FILES TMFCOM Commands Examples showing pattern-matching and wildcard-character use appear earlier in this discussion under file-set on page 3-202 and later, under Examples on page 3-213. Security Restrictions You can issue a RECOVER FILES command only if you are a member of the super user group. TMF State Requirement Before you can enter the RECOVER FILES command, TMF must be started.
RECOVER FILES TMFCOM Commands try to recover these files, you can enter the RECOVER FILES command again, using an earlier online dump on which the files might not be damaged. If a file to be recovered does not exist in the system, you must specify the FROMARCHIVE option. In cases of purged-file recovery, however, use the TOFIRSTPURGE and FROMARCHIVE options (rather than the FROMARCHIVE and TIME options). Caution.
RECOVER FILES TMFCOM Commands You can specify only one of the following options in the same RECOVER FILES command: TIME, TOFIRSTPURGE, or TOMATPOSITION. If you enter more than one of these options, an error message is generated. Caution. If you specify the TIME, TOFIRSTPURGE, or TOMATPOSITION option in a RECOVER FILES command, you must immediately make new online dumps of the data files recovered.
RECOVER FILES TMFCOM Commands after the dump would be impossible. In such a case, you can use the TOMATPOSITION option to recover the database to a specific location within the master audit trail (MAT) rather than to a specific time. However, the recovery steps involve the use of the SNOOP utility, a high level of TMF background, and perhaps the assistance of the Global Customer Support Center (GCSC) or your service provider. For more information about the procedure, see TMF Operations and Recovery Guide.
RECOVER FILES TMFCOM Commands Because the MAP NAMES option restores files only to the same instance of TMF, you cannot use this option to restore these files to another system. When you use the MAP NAMES option, the files in the new locations have the same user IDs and attributes as those in the old locations. When you use the MAP NAMES option, the FROMARCHIVE option is also used in all cases, even if you do not explicitly select it.
RECOVER FILES TMFCOM Commands when taking dumps of these files, or referring to them in the RECOVER FILES command, you must refer to these files by their logical or direct file names, not by their physical file names. Nevertheless, with the TOPHYSVOL parameter, you can identify the physical target disk volume where you wish TMF to place the logical recovered files. Furthermore, with the WHEREPHYSVOLIS parameter, you can recover all the logical files on a specified physical volume.
RECOVER FILES TMFCOM Commands 10:57 30DEC03 195,00,012 NonStop TMF on \:PLUTO *0165* RECOVER FILES [5] TMP Process FileRecovMgmt: Files Recovered: 1; Files Not Recovered: 0. 10:57 30DEC03 195,00,012 NonStop TMF on \:PLUTO *0156* RECOVER FILES [5] TMP Process: End operation. TMF 72> The next RECOVER FILES command initiates the recovery process interactively at a terminal. A moment later the BREAK key is pressed, terminating the display.
RECOVER FILES TMFCOM Commands . Here is a RECOVER FILES command that uses the MAP NAMES option to map all files being recovered to a different location. This example also presents the EMS messages generated by this operation: TMF 78> RECOVER FILES ($DATA09.AMFRNL2.*, $DATA10.AMFRNL2.*, & >>>$DATA11.AMFRNL2.*, $DATA12.AMFRNL2.*, $DATA06.AMFRNL2.*), MAP NAMES & >>>($DATA09.AMFRNL2.* TO $DATA13.AMFRNL2.*, & >>>$DATA10.AMFRNL2.* TO $DATA14.AMFRNL2.*, & >>>$DATA11.AMFRNL2.* TO $DATA15.AMFRNL2.*, & >>>$DATA12.
RECOVER FILES TMFCOM Commands This next RECOVER FILES operation recovers ten files, restoring two of them (\PLUTO.$DATA06.AMFRNL3.A1 and \PLUTO.$DATA06.AMFRNL3.A2) to the same location and the remaining eight to a different location: TMF 79> RECOVER FILES ($DATA09.AMFRNL2.*, $DATA06.AMFRNL3.*, & >>>$DATA10.AMFRNL2.*, $DATA11.AMFRNL2.*, & >>>$DATA12.AMFRNL2.*, $DATA06.AMFRNL2.*), MAP NAMES & >>>($DATA09.AMFRNL2.* TO $DATA13.AMFRNL2.*, & >>>$DATA10.AMFRNL2.* TO $DATA14.AMFRNL2.*, & >>>$DATA11.AMFRNL2.
RELOCATE DISKDUMPS TMFCOM Commands RELOCATE DISKDUMPS The RELOCATE DISKDUMPS command changes the disk dump media locations specified in the TMF catalog. RELOCATE DISKDUMPS {serial-number } {(serial-number [, serial-number]...)} {* } ,OLDDMLOC diskmedia-loc, NEWDMLOC diskmedia-loc serial-number directs this RELOCATE DISKDUMPS command to change the catalog entries for only the dumps with the specified serial number. You can obtain information about dump serial numbers by using the INFO DUMPS command.
RELOCATE DISKDUMPS TMFCOM Commands TMF State Requirement Before you can use the RELOCATE DISKDUMPS command, TMF must be started. Usage Guidelines After moving or restoring dumps to a different location, use the RELOCATE DISKDUMPS command to change the entries for the dumps in the TMF catalog. This command selects disk media names in the catalog that match the serial numbers and OLDDMLOC value specified, and changes their location to the NEWDMLOC value.
RESET AUDITTRAIL TMFCOM Commands RESET AUDITTRAIL The RESET AUDITTRAIL command resets audit trail attributes to their default values, canceling the effects of any previous SET AUDITTRAIL commands. Values changed by RESET AUDITTRAIL are local to your current session and only apply to ADD AUDITTRAIL commands subsequently issued within this session. RESET AUDITTRAIL {attribute [,attribute]...
RESET AUDITTRAIL TMFCOM Commands OVERFLOWTHRESHOLD resets the OVERFLOWTHRESHOLD attribute to 80 (if an overflow volume is configured), indicating that overflow copying begins when the audit trail capacity in use exceeds 80%. RESTOREVOL[S] removes any RESTOREVOL[S] specification; thus, no restore-audit volumes onto which audit dumps can be restored are identified. This attribute has no default but is required if the AUDITDUMP attribute is ON.
RESET AUDITTRAIL TMFCOM Commands Examples The following RESET AUDITTRAIL command resets the BEGINTRANSDISABLE attribute to 90%, overriding an earlier SET command that established a different value for this attribute: TMF 81> RESET AUDITTRAIL BEGINTRANSDISABLE Now, all subsequent ADD AUDITTRAIL commands that do not include the BEGINTRANSDISABLE parameter will use this 90% value for that attribute.
RESET DATAVOLS TMFCOM Commands RESET DATAVOLS The RESET DATAVOLS command resets data volume attributes to their default values, canceling the effects of any previous SET DATAVOLS commands. Values changed by RESET DATAVOLS are local to your current session and apply only to ADD DATAVOLS commands subsequently issued within this session. RESET DATAVOL[S] {attribute [,attribute]...
RESET DATAVOLS TMFCOM Commands carried forward to all the ADD DATAVOLS commands in your session, so that you need to enter only specific nondefault values as you wish.
RESET DUMPS TMFCOM Commands RESET DUMPS The RESET DUMPS command removes (clears) online and audit dump specifications, canceling the effects of previous SET DUMPS commands. This clearing by RESET DUMPS is local to your current session and affects only ADD DUMPS commands subsequently issued within this session. RESET DUMPS {attribute [, attribute]...
RESET DUMPS TMFCOM Commands Usage Guidelines The clearing of specifications by RESET DUMPS is local to your current session only, and is not propagated to TMFSERVE. This clearing affects only ADD DUMPS commands issued subsequently within your session and ceases to apply when your session ends. Note. You must establish values for the SERIAL and TYPE entries and for either the DISKMEDIA or the TAPEMEDIA entry. Default values are not allowed for these entries.
RESET TAPEMEDIA TMFCOM Commands RESET TAPEMEDIA The RESET TAPEMEDIA command removes certain tape volume attributes, or resets others to their defaults, canceling the effects of previous SET TAPEMEDIA commands. These changes by RESET TAPEMEDIA are local to your current session, and affect only ADD TAPEMEDIA commands subsequently issued within the session. RESET TAPEMEDIA {attribute [, attribute]...
RESET TAPEMEDIA TMFCOM Commands * resets all tape volume specifications to their default values and clears all tape volume specifications that have no defaults. Security Restrictions Anyone can issue the RESET TAPEMEDIA command. TMF State Requirement You can enter the RESET TAPEMEDIA command at any time, whether or not TMF has been started. Usage Guidelines The resetting or clearing of specifications by RESET TAPEMEDIA is local to your current session only, and is not propagated to TMFSERVE.
RESOLVE TRANSACTION TMFCOM Commands RESOLVE TRANSACTION The RESOLVE TRANSACTION command causes an unresolved distributed transaction to either commit or back out its changes. To fully resolve the transaction, this command must be issued on all nodes on which the transaction resides, except for the transaction’s home node. RESOLVE TRANS[ACTION[S]] {transaction-id } {(transaction-id [,transaction-id]...)} ,STATE {ABORTED | COMMITTED} where transaction-id is: [node. [node-number. [node(tm-flags).
RESOLVE TRANSACTION TMFCOM Commands tm-flags is a number representing flags used internally by TMF. If this number is zero, it does not appear in displays of the transaction-id presented by the STATUS TRANSACTIONS command. Note. If the tm-flags value is a number other than zero, you must include this number in parentheses in the RESOLVE TRANSACTION command. For example: TMF 3> RESOLVE TRANSACTION \SYSB(1).3.45678 cpu is the number of the processor on which the transaction originated.
RESOLVE TRANSACTION TMFCOM Commands audit trail. For a complete discussion of all transaction states, see the STATUS TRANSACTIONS command description later in this section.) If the connection between the nodes is reestablished, TMF automatically resolves the transactions that are in doubt. If communications cannot be reestablished, however, you may need to resolve the transactions manually.
RESOLVE TRANSACTION TMFCOM Commands Examples The following RESOLVE TRANSACTION command aborts the specified transaction, also displaying information about the transaction’s status: TMF 4> RESOLVE TRANSACTION \NEWYORK.6.5, STATE ABORTED \NEWYORK.6.5, State: aborted Distributed, Parent: \NEWYORK A STATUS TRANSACTIONS command has revealed that for the transaction \SANFRAN.7.8932, the tm-flags value was set to 1.
SET AUDITTRAIL TMFCOM Commands SET AUDITTRAIL The SET AUDITTRAIL command establishes attribute values for audit trails created by subsequent ADD AUDITTRAIL commands issued during the same TMFCOM session. SET AUDITTRAIL attribute [,attribute]... where attribute is any of the following: [AUDITDUMP {ON | OFF}] [FILESIZE integer ] [ACTIVEVOL[S] {volume } {(volume [,volume] ...) }] [FILESPERVOLUME integer] [OVERFLOWVOL[S] {volume } {(volume [,volume]...
SET AUDITTRAIL TMFCOM Commands FILESIZE integer specifies the size of the audit-trail files, in megabytes (MB). The minimum value is 1 and the maximum value is either 2047 or the maximum disk size (if less than 2047 megabytes.) The default value is 100, resulting in files of 100 MB (100 x 1,048,576 bytes) each. ACTIVEVOL[S] specifies the disk volumes that hold the audit-trail files.
SET AUDITTRAIL TMFCOM Commands For the START TMF command to execute successfully, all overflow-audit volumes must be up. OVERFLOWTHRESHOLD integer specifies the percentage of audit trail capacity in use above which TMF begins overflow copying. This is an optional parameter. The minimum value is 50 and the maximum is 100. The default is 80(%). RESTOREVOL[S] specifies the volumes to be used when restoring audit dumps during execution of a RECOVER FILES command.
SET AUDITTRAIL TMFCOM Commands You can display the attribute values established by the most recent SET AUDITTRAIL command in your session by entering the SHOW AUDITTRAIL command. For additional guidelines, see the ADD AUDITTRAIL command description earlier in this section.
SET DATAVOLS TMFCOM Commands SET DATAVOLS The SET DATAVOLS command establishes attribute values for data volumes added by subsequent ADD DATAVOLS commands issued during the same TMFCOM session. SET DATAVOL[S] attribute [,attribute]... where attribute is any of the following: AUDITTRAIL {MASTER | MAT } {AUX[ILIARY]nn} RECOVERYMODE {ONLINE | ARCHIVE} AUDITTRAIL {MASTER | MAT } {AUX[ILIARY]nn} identifies the audit trail to which newly added data volumes would send their audit records.
SET DATAVOLS TMFCOM Commands TMF State Requirement You can enter the SET DATAVOLS command at any time, whether or not TMF has been started. Usage Guidelines The values specified in SET DATAVOLS are local to your current session only and are not propagated to TMFSERVE. These values take effect when you issue subsequent ADD DATAVOLS commands within your session and cease to apply when your session ends.
SET DUMPS TMFCOM Commands SET DUMPS The SET DUMPS command establishes specifications for online and audit dump entries added to the catalog by subsequent ADD DUMPS commands issued during the same TMFCOM session. SET DUMPS attribute [,attribute]... where attribute is: [DISKMEDIA disk ] [DISKMEDIA (disk [,disk]...
SET DUMPS TMFCOM Commands the audit trail when dumped. For example: AA000036 • For an online dump to disk, any number of disks can be specified by disk without limit, and the format for disk is: [node.]volume.{xx}serial-number.Ffile-number node is the node where the dump is located. volume is the volume on which the dump is located. {xx}serial-number identifies the dump. xx is a two-character prefix, and serial-number is the six-digit serial number of the dump.
SET DUMPS TMFCOM Commands If you specify DISKMEDIA, you must not specify TAPEMEDIA; if you specify TAPEMEDIA, you must not specify DISKMEDIA. TAPEMEDIA tape-volume:part:copy for dumps to tape, identifies the tape volume on which the dump is recorded. Include this option if the catalog does not already contain an entry for the dump with the specified serial number. tape-volume is the name of the tape volume. part specifies which part of the dump is stored on this tape volume.
SET DUMPS TMFCOM Commands You can obtain both master and auxiliary audit trail sequence numbers by examining output from a previous INFO DUMPS, DETAIL command or a previous DUMP FILES command. Security Restrictions Anyone can issue the SET DUMPS command. TMF State Requirement You can enter the SET DUMPS command at any time, whether or not TMF has been started. Usage Guidelines The values specified in SET DUMPS are local to your current session only and are not propagated to TMFSERVE.
SET DUMPS TMFCOM Commands All subsequent ADD DUMPS commands that do not include the TYPE parameter will use this value for that attribute. TMF 26> ADD DUMPS $ZTMFAT.ZTMFAT.AA000024, SERIAL 1066, & >>>DISKMEDIA $DUMPER.ZT001066.AA000024, & >>>TIME JAN 12 2002, 20:20:00 TMF 27> . . . The next SET DUMPS command sets the DISKMEDIA option for an online dump named $DUMP.ZT001000.F0000001: TMF 27> SET DUMPS DISKMEDIA $DUMP.ZT001000.F0000001 TMF 28> . . .
SET TAPEMEDIA TMFCOM Commands SET TAPEMEDIA The SET TAPEMEDIA command establishes attribute values for tape volumes added by subsequent ADD TAPEMEDIA commands issued during the same TMFCOM session. SET TAPEMEDIA attribute [,attribute] ... where attribute is: [DENSITY density] [DRIVE [node.]tape-drive] [LABEL {ON [!] | OFF}] [STATUS {ASSIGNED} {BAD } {RELEASED} {SCRATCH }] [UNLOAD {ON | OFF}] DENSITY density specifies the density at which tapes are written.
SET TAPEMEDIA TMFCOM Commands LABEL ON [!] | OFF for dumps to tape, determines whether tape volumes are labeled: ON [!] ON labels tape volumes on the tape drive specified. If you choose this option, you must also specify the name of the tape drive in the DRIVE parameter. TMF invokes labeled-tape processing for the specified tape volumes to determine whether each one is labeled successfully. The exclamation point [!] is optional.
SET TAPEMEDIA TMFCOM Commands RELEASED indicates that the contents of the tape volume are no longer required for file recovery, but the tape cannot be used for dumping. SCRATCH indicates that the tape volume can be used for dumping files. UNLOAD {ON | OFF} determines whether the tape volume is unloaded after it is labeled. ON unloads the tape volume. OFF suppresses unloading. The default is ON. Security Restrictions Anyone can issue the SET TAPEMEDIA command.
SET TAPEMEDIA TMFCOM Commands Examples The following SET TAPEMEDIA command sets the UNLOAD specification OFF: TMF 46> SET TAPEMEDIA UNLOAD OFF All subsequent ADD TAPEMEDIA commands that do not include the UNLOAD parameter will use this value for that specification (rather than the default, ON): TMF 47> ADD TAPEMEDIA TT02, DRIVE $TAPE1 TMF 48> ADD TAPEMEDIA TT03, DRIVE $TAPE2 TMF 49> . . .
SHOW AUDITTRAIL TMFCOM Commands SHOW AUDITTRAIL The SHOW AUDITTRAIL command displays the attribute values established by SET AUDITTRAIL commands in the current TMFCOM session. If no SET AUDITTRAIL command was issued during the session, the SHOW AUDITTRAIL command presents no information. SHOW AUDITTRAIL [attribute [,attribute]...
SHOW AUDITTRAIL TMFCOM Commands RESTOREVOL[S] displays the RESTOREVOL[S] setting, listing the disk volumes to be used when restoring audit dumps during execution of a RECOVER FILES command. BEGINTRANSDISABLE displays the BEGINTRANSDISABLE setting, indicating the percentage of audit trail capacity that can be consumed before TMF disables new transactions. * displays all attribute values established by the SET AUDITTRAIL command in this session. If you do not specify any option, this is the default.
SHOW AUDITTRAIL TMFCOM Commands The next SHOW AUDITTRAIL command displays all audit trail attribute values established by SET AUDITTRAIL commands during this session: TMF 6> SHOW AUDITTRAIL activevol: $MAT, $MAT2 filespervolume: 4 overflowvols: $DATA1 overflowthreshold: 80 HP NonStop TMF Reference Manual—540138-001 3 -249
SHOW DATAVOLS TMFCOM Commands SHOW DATAVOLS The SHOW DATAVOLS command displays the attribute values established by SET DATAVOLS commands in the current TMFCOM session. If no SET DATAVOLS command was issued during the session, the SHOW DATAVOLS command presents no information. SHOW DATAVOL[S] [attribute [,attribute]...] [* ] where attribute is: [AUDITTRAIL] [RECOVERYMODE] AUDITTRAIL displays the AUDITTRAIL setting, indicating the audit trail to which the newly added data volumes send their audit records.
SHOW DATAVOLS TMFCOM Commands Examples The following SHOW DATAVOLS command displays the value of the AUDITTRAIL data volume attribute, as established by a SET DATAVOLS command earlier in this session: TMF 10> SHOW DATAVOLS AUDITTRAIL audittrail auxiliary01 The next SHOW DATAVOLS command displays all data volume attribute values established by SET DATAVOLS commands during this session: TMF 11> SHOW DATAVOLS audittrail auxiliary01 recoverymode online If the SET DATAVOLS command has not been used in this ses
SHOW DUMPS TMFCOM Commands SHOW DUMPS The SHOW DUMPS command displays the attribute values established by SET DUMPS commands in the current TMFCOM session. SHOW DUMPS [attribute [, attribute]...] [ * ] where attribute is: [DISKMEDIA] [TAPEMEDIA] [SERIAL ] [TYPE ] DISKMEDIA for a dump to disk, displays the DISKMEDIA setting, indicating the node, volume, subvolume, and disk on which the dump is located.
SHOW DUMPS TMFCOM Commands Usage Guideline The SHOW DUMPS command does not display default values for specifications. If no parameter is specified in SHOW DUMPS, this command displays the values of all specifications set by SET DUMPS commands during this session. If a SET DUMPS command was not issued during the session, the SHOW DUMPS command presents no information.
SHOW TAPEMEDIA TMFCOM Commands SHOW TAPEMEDIA The SHOW TAPEMEDIA command displays the attribute values established by SET TAPEMEDIA commands in the current TMFCOM session. SHOW TAPEMEDIA [attribute [, attribute]...] [ * ] where attribute is: [DENSITY [DRIVE [LABEL [STATUS [UNLOAD ] ] ] ] ] DENSITY displays the DENSITY setting, indicating the density at which tape volumes are written. DRIVE displays the DRIVE setting, indicating the tape drive on which tape volumes are written.
SHOW TAPEMEDIA TMFCOM Commands * displays all tape media specification values established by the SET TAPEMEDIA command in this session. If you do not specify any option, this is the default. Security Restrictions Anyone can enter the SHOW TAPEMEDIA command. TMF State Requirement You can enter the SHOW TAPEMEDIA command at any time, whether or not TMF has been started. Usage Guidelines The SHOW TAPEMEDIA command does not display default values for attributes.
START TMF TMFCOM Commands START TMF The START TMF command starts TMF transaction processing, optionally displaying the EMS events for the start operation as this operation progresses. Specifically, START TMF starts audit trail service and data volumes, resolves network transactions, cleans up transactions that were active when TMF last went down, and initiates new transactions.
START TMF TMFCOM Commands During START TMF operation, volume recovery might not be able to recover some files. The unrecovered files will not be available when the operation completes but they will be listed in EMS messages. To make them available, you might need to use the RECOVER FILES command to perform a file recovery. (To support file recovery, of course, you must regularly produce online and audit dumps.
START TMF TMFCOM Commands Examples The following START TMF command, entered without the NOWAIT parameter, starts TMF and displays the EMS messages for the start operation as it progresses: TMF 19> START TMF START TMF operation [39] begun. Operation TimeStamp: 24-Jun-2003 20:09:18 20:09 24JUN03 195,02,024 NonStop TMF on \PLUTO *0155* START TMF[1] TMP Process: Beg1n Operation. 20:09 24JUN03 195,02,024 NonStop TMF on \PLUTO *0148* START TMF[1] TMP Process: START TMF parameters: None.
STATUS AUDITDUMP TMFCOM Commands STATUS AUDITDUMP The STATUS AUDITDUMP command displays the current status of audit dump processes. STATUS AUDITDUMP [MASTER | MAT ] [AUX[ILIARY]nn ] [(MASTER | MAT [,AUX[ILIARY]nn]) ] [(AUX[ILIARY]nn [,MASTER | MAT]) ] [(AUX[ILIARY]nn [,AUX[ILIARY]nn])] [ * ] MASTER|MAT AUX[ILIARY]nn identifies the audit trail associated with the audit dump process whose status is to be displayed. MASTER or MAT specifies the master audit trail.
STATUS AUDITDUMP TMFCOM Commands Table 3-18. STATUS AUDITDUMP Output Heading or Item Description Audit Dump Name of the audit trail associated with this dump: MASTER is the master audit trail, and AUXILIARYnn is an auxiliary audit trail. State Audit dump process state: enabled or disabled. Status Audit dump process status: active or inactive. Process Audit dump process name. File Name of audit-trail file currently being dumped.
STATUS AUDITTRAIL TMFCOM Commands STATUS AUDITTRAIL The STATUS AUDITTRAIL command displays the current audit trail activity. STATUS AUDITTRAIL [MASTER | MAT ] [AUX[ILIARY]nn ] [(MASTER | MAT [,AUX[ILIARY]nn]) ] [(AUX[ILIARY]nn [,MASTER | MAT]) ] [(AUX[ILIARY]nn [,AUX[ILIARY]nn])] [* ] [,DETAIL] MASTER | MAT AUX[ILIARY]nn identifies the audit trail whose activity is to be displayed. MASTER or MAT specifies the master audit trail. AUXILIARYnn or AUXnn specifies an auxiliary audit trail.
STATUS AUDITTRAIL TMFCOM Commands Usage Guideline The STATUS AUDITTRAIL command displays the following items: • • • • • The name of the audit trail The percentage of audit trail capacity in use The name of the oldest audit-trail file that is not yet ready to be reused or purged by TMF The reason a file is pinned (retained) on disk One or more audit-trail file names, and an indication of their status These items are explained next under “Output Displayed.
STATUS AUDITTRAIL TMFCOM Commands Adding an active-audit volume to the audit trail increases audit trail capacity by the number of files specified in the FILESPERVOLUME attribute. You can use this option only if you have a volume that is not already configured as an active-audit volume or a data volume.
STATUS AUDITTRAIL TMFCOM Commands Table 3-19. STATUS AUDITTRAIL Output (page 2 of 4) Heading or Item Description Reason The reason the file named under “First Pinned File” is pinned, which is one of the following entries. (In the following list, each entry is followed by an explanation of its meaning.) Active transaction(s) An active transaction might have sent an audit record to this audit- trail file.
STATUS AUDITTRAIL TMFCOM Commands Table 3-19. STATUS AUDITTRAIL Output (page 3 of 4) Heading or Item Description Files Names of one or more audit-trail files, followed in parentheses by an indication of their status. If the DETAIL option is not specified, only the current audit file is displayed. If the DETAIL option is specified, the display also shows the names of every other file in the audit trail that is being managed on disk by TMF; these include preallocated, overflow, and restored files.
STATUS AUDITTRAIL TMFCOM Commands Table 3-19. STATUS AUDITTRAIL Output (page 4 of 4) Heading or Item Description Files (continued) overflowing The file is the target of an overflow operation, currently in progress. When this operation is done, this file’s status changes to OVERFLOW. preallocated Preallocated files are “placeholders” that are used to guarantee that disk space configured for the audit trail is not consumed by other applications.
STATUS AUDITTRAIL TMFCOM Commands Files: $AUX1.ZTMFAT.BB000001 $AUX1.ZTMFAT.BB000002 $AUX1.ZTMFAT.BB000003 $AUX1.ZTMFAT.BB000004 $AUX1.ZTMFAT.BB000005 $AUX1.ZTMFAT.BB000006 $AUX1.ZTMFAT.
STATUS BEGINTRANS TMFCOM Commands STATUS BEGINTRANS The STATUS BEGINTRANS command displays the current status of TMF transaction processing, indicating whether this feature is enabled or disabled. STATUS BEGINTRANS Security Restrictions Anyone can enter the STATUS BEGINTRANS command. TMF State Requirement Before you can enter the STATUS BEGINTRANS command, TMF must be started. Usage Guideline If transaction processing is disabled, STATUS BEGINTRANS reports all reasons why this is so.
STATUS CATALOG TMFCOM Commands STATUS CATALOG The STATUS CATALOG command displays the current activity of the catalog process, indicating the availability of the TMF catalog. STATUS CATALOG Security Restrictions Anyone can enter the STATUS CATALOG command. TMF State Requirement You can enter the STATUS CATALOG command at any time, whether or not TMF has been started.
STATUS DATAVOLS TMFCOM Commands STATUS DATAVOLS The STATUS DATAVOLS command displays the current status of data volumes. STATUS DATAVOL[S] [volume ] [(volume [,volume]...
STATUS DATAVOLS TMFCOM Commands ADDING indicates volumes being added to the configuration as data volumes. STARTING indicates configured volumes that are in one of the startup states (startupbegun, awaittransresolve, queuedforrecovery, recovering, or startupcompleting). STARTUPBEGUN indicates configured volumes that have just begun automatic startup processing. The associated disk process is processing the initial startup requests for these volumes.
STATUS DATAVOLS TMFCOM Commands NOTSTARTED indicates configured volumes that are not in the started state. DOWN indicates configured volumes that are in either the downclean or downdirty state. DOWNCLEAN indicates configured volumes that are inaccessible, perhaps because of device or process problems, and on which no updates have been made to audited files since the volume last underwent a clean shutdown. Audited files on volumes in this state do not contain any inconsistencies.
STATUS DATAVOLS TMFCOM Commands DISABLEDDIRTY indicates configured volumes that are disabled, but for which normal shutdown processing did not complete successfully. A volume enters the disabledirty state if it is disabled by a DISABLE DATAVOLS command that includes the ABRUPT option. When TMF cannot determine whether a volume is clean, TMF assumes that it is dirty.
STATUS DATAVOLS TMFCOM Commands Security Restrictions Anyone can enter the STATUS DATAVOLS command. TMF State Requirement Before you can enter the STATUS DATAVOLS command, TMF must either be in the started state or in the process of shutting down. Usage Guidelines You can control the volumes displayed, using the STATE, AUDITTRAIL, and RECOVERYMODE parameters.
STATUS DATAVOLS TMFCOM Commands Table 3-20. STATUS DATAVOLS Output Heading or Item Description Volume Name of the data volume. Audit Trail Audit trail to which this data volume generates audit records. Recovery Mode Recovery mode setting (either online or archive). State The current status of the data volume, indicating its state.
STATUS OPERATIONS TMFCOM Commands STATUS OPERATIONS The STATUS OPERATIONS command displays the status of TMF operations that were recently completed or are now in progress. STATUS OPERATION[S] [operation-number ] [(operation-number [,operation-number]...
STATUS OPERATIONS TMFCOM Commands DUMPFILES indicates online dumping to tape or disk. RECOVERFILES indicates file recovery. STARTTMF indicates TMF startup. STOPTMF indicates TMF shutdown. VOLUMERECOVERY indicates volume recovery. ANY indicates any operation. The default is ANY. STATE displays information only about operations that are in the state indicated by this parameter. This option applies only when the wild-card character (*) is specified for operation-number.
STATUS OPERATIONS TMFCOM Commands where: month is a three-character abbreviation for the name of the month: {JAN|FEB|MAR|APR|MAY|JUN|JUL|AUG|SEP|OCT|NOV|DEC} day is a two-digit integer for the day of the month. year is a four-digit integer for the calendar year. Note. You can use either dashes (-) or spaces, or both, as delimiters to separate the month, day, and year values, but you must use at least one of these delimiters. hr is an integer for the hour, from 0 through 23.
STATUS OPERATIONS TMFCOM Commands Security Restrictions Anyone can enter the STATUS OPERATIONS command. TMF State Requirement You can enter the STATUS OPERATIONS command at any time, whether or not TMF has been started. Usage Guidelines When you specify an operation number with the STATUS OPERATIONS command, TMFCOM displays the status of the latest operation assigned that operation number by the current incarnation of the TMP.
STATUS OPERATIONS TMFCOM Commands Output Displayed The STATUS OPERATIONS command displays the items explained in Table 3-21. Table 3-21. STATUS OPERATIONS Output Heading or Item Description Type The type of operation: AuditRestore, DeleteTMF, DumpFiles, RecoverFiles, StartTMF, StopTMF, and VolumeRecovery. State The state of the operation: InProgress or Finished. Begin Time The date and time the operation began. End Time The date and time the operation completed.
STATUS OPERATIONS TMFCOM Commands The last STATUS OPERATIONS command displays information about all operations that began at or after 1:00 p.m.
STATUS RESOURCEMANAGER TMFCOM Commands STATUS RESOURCEMANAGER The STATUS RESOURCEMANAGER command displays the current status of both recoverable and volatile resource managers. STATUS {RESOURCEMANAGER | RM} [rm-name ] [(rm-name [,rm-name]...)] [* ] [,STATE {CREATED } {CLOSED } {OPEN } {RECOVERING} {CRASHED } {VOLATILE }] [,PROCESS {process } {(process [,process]...) } {(cpu,pin) } {((cpu,pin) [,(cpu,pin)]...)}] [,DETAIL ] rm-name is the name of the resource manager whose status is to be displayed.
TMFCOM Commands STATUS RESOURCEMANAGER STATE displays information only for resource managers that are in the state indicated by this parameter. If this parameter is omitted, TMFCOM displays information for all resource managers requested, regardless of state. In this parameter, you can specify one of the following states: CREATED displays information only for resource managers in the created state.
STATUS RESOURCEMANAGER TMFCOM Commands PROCESS displays information only for resource managers that are currently open by the gateway processes indicated by process or (cpu, pin) specifiers: process is the name of the gateway process that has the resource manager open. (cpu, pin) is the CPU number and process identification number (PIN) of the gateway process that has the resource manager open.
STATUS RESOURCEMANAGER TMFCOM Commands Usage Guidelines Note. Resource managers, to which the STATUS RESOURCEMANAGER command applies, support heterogeneous transaction processing. Resource managers are used in products such as NonStop TUXEDO. Although TMFCOM and the TMFSERVE programmatic interface provide TMF commands and options for operating on resource managers, system managers who use them do so in the context of issues involving multiple software subsystems and interplatform considerations.
STATUS RESOURCEMANAGER TMFCOM Commands Output Displayed For each resource manager reported upon, the STATUS RESOURCEMANAGER command displays the items explained in Table 3-22. Table 3-22. STATUS RESOURCEMANAGER Output Heading or Item Description Name Name of the resource manager. Status State of the resource manager: created, closed, open, recovering, crashed, or volatile.
STATUS RESOURCEMANAGER TMFCOM Commands Name: Status: Process: ZZ-VOLATILE-3-5 VOLATILE (3,75) Name: Status: Process: ZZ-VOLATILE-5-7 VOLATILE $TXVRM The next command displays the status of all resource managers in the crashed state, without the DETAIL option: TMF 28> STATUS RM, STATE CRASHED Resource Manager Status -------------------------Name: TUX-A2_NT@MICROSOFT Status: CRASHED Process: None The following command displays the status of all resource managers that are open by the process $TXGW1, wit
STATUS RESOURCEMANAGER TMFCOM Commands The next command displays the status of all resource managers in the crashed state, and shows the transaction-level detail for each: TMF 50> STATUS RM, STATE CRASHED, DETAIL Resource Manager Status -------------------------Name: TUX-A2_NT@MICROSOFT Status: CRASHED Process: None Transid Branch Number State ----------------------------------------------------------------\SVLDEV.3.39480 1 prepared \PRUNE.5.
STATUS SERVER TMFCOM Commands STATUS SERVER The STATUS SERVER command displays status and other information about the currently open TMFSERVE process. STATUS SERVER Security Restrictions Anyone can enter the STATUS SERVER command. TMF State Requirement You can enter the STATUS SERVER command at any time, whether or not TMF has been started.
STATUS SERVER TMFCOM Commands Examples The following STATUS SERVER command retrieves information about the currently open TMFSERVE process: TMF 31> STATUS SERVER TMF Server Status: System: \FRESNO (175) Date-Time: 22-Dec-2003 20:30:15 Process: $Z193 (8,1120) Creator ID: (8,86) Process ID: (8,86) Priority: 146 Object Name: \FRESNO.$SYSTEM.SYS02.TMFSERVE HomeTerm: \FRESNO.
STATUS TMF TMFCOM Commands STATUS TMF The STATUS TMF command displays the current activity of TMF. STATUS TMF Security Restrictions Anyone can enter the STATUS TMF command. TMF State Requirement You can enter the STATUS TMF command at any time, whether or not TMF has been started.
STATUS TMF TMFCOM Commands Increasing FILESPERVOLUME allocates new audit-trail files on each of the currently configured active-audit volumes. This is the recommended approach because it distributes the load of the new files across the active volumes. Use this option only if the active volumes have sufficient room to accommodate the new files. Adding an active-audit volume to the audit trail increases audit trail capacity by the number of files specified in the FILESPERVOLUME attribute.
STATUS TMF TMFCOM Commands Table 3-24. STATUS TMF Output (page 1 of 2) Heading or Item Description System Name of the node (system) on which this TMF configuration is running. State Current operating status of TMF, reported as one of the following entries and subentries. (In the following list, each status entry and subentry is followed by an explanation of its meaning.
STATUS TMF TMFCOM Commands Table 3-24. STATUS TMF Output (page 2 of 2) Heading or Item Description State (continued) Stopping TMF is stopping and is in one of the following conditions (noted in parentheses in the display): Waiting for Transactions to Finish TMF is waiting for all transactions to be completed. Data Volumes TMF is stopping data volumes. Waiting for RDF TMF is waiting for the Remote Database Facility (RDF) to shut down. Services TMF is stopping audit trail service and other services.
STATUS TMF TMFCOM Commands Catalog Status: Status: active . . . The output from the next STATUS TMF command illustrates that some of the status might not be available when TMF is in certain states. This example shows the display when TMF is in the stopped state: TMF 64> STATUS TMF TMF Status: System: \FOXII, Time: 10-Feb-2002 09:58:14 State: stopped Transaction Rate: 0.
STATUS TRANSACTIONS TMFCOM Commands STATUS TRANSACTIONS The STATUS TRANSACTIONS command displays transaction identifiers and status. STATUS TRANS[ACTION[S]] [transaction-id [(transaction-id [,transaction-id]...) ] ] [,PROCESS {process } {(process [,process]... ) } {(cpu, pin) } {((cpu, pin) [,(cpu, pin)]...)}] [,STATE {ACTIVE } {ABORTING } {ABORTED } {COMMITTED} {ENDING } {HUNG } {PREPARED }] [,DETAIL | BRIEF ] transaction-id identifies the transaction for which status information is to be displayed.
STATUS TRANSACTIONS TMFCOM Commands tm-flags is a number representing flags used internally by TMF. If this number is zero, it does not appear in the STATUS TRANSACTIONS display. cpu is the CPU number of the processor on which the transaction originated. seq-num is a sequence number assigned to the transaction, which distinguishes it from other transactions originating in the same processor on the same home node.
STATUS TRANSACTIONS TMFCOM Commands ABORTED displays only transactions that have been aborted. A transaction enters this state when all of its effects are undone and its transaction state (aborted) record is written to the audit trail. A transaction normally stays in this state only briefly.
STATUS TRANSACTIONS TMFCOM Commands • • • Whether the autoabort function is disabled for this transaction If the transaction was unilaterally aborted on the remote node, the reason it was aborted The age of the transaction If BRIEF is specified, only the transaction identifiers of the selected transactions are listed. BRIEF is useful when you only need to list the transactions that match your selection criteria.
STATUS TRANSACTIONS TMFCOM Commands displayed is followed by a period and then the transaction branch number: for example, TUX-HP@ESSG.1. The branch number helps distinguish between two separate exports of the same transaction from the same resource manager. Notice that the branch number is only unique during the life of a START TMF command or an individual gateway process’ open of the resource manager.
STATUS TRANSACTIONS TMFCOM Commands • If a STOP TMF operation has already been requested, issue the STOP TMF, ABRUPT command to shut down TMF abruptly. Enter the STOP TMF, ABRUPT command from a TMFCOM process running under a different TACL process. Note. Although this approach causes TMF to crash, this should not create a problem because TMF shutdown was already in progress.
STATUS TRANSACTIONS TMFCOM Commands Examples The following STATUS TRANSACTIONS command lists all transactions on the local node, whose name is \TACO: TMF 71> STATUS TRANSACTIONS Transaction Identifier -------------------------\TACO.3.34567 \TACO.0.89760 Process ---------(3,234) (0,034) State Parent --------- -------active active \PIZZA.1.876 \TACO.2.37876 \FILLET.3.
STATUS TRANSACTIONS TMFCOM Commands The next command illustrates the display of foreign resource managers when the DETAIL option is selected: TMF 95> STATUS TRANSACTIONS, DETAIL Transaction Identifier Start Time Process Parent Child State # Attempts to Abort Starting MAT Seq. No Transaction Identifier Start Time Process Parent Child State # Attempts to Abort Starting MAT Seq. No Identifier Start Time Process Parent Child State # Attempts to Abort Starting MAT Seq.
STATUS TRANSACTIONS TMFCOM Commands The following STATUS TRANSACTIONS command presents detailed information about all transactions in the prepared state: TMF 20> STATUS TRANSACTIONS, STATE PREPARED, DETAIL Transaction Identifier Start Time Process Parent Child State # Attempts to Abort Starting MAT Seq. No :\PIZZA.1.
STOP TMF TMFCOM Commands STOP TMF The STOP TMF command shuts down TMF, terminating transaction processing and displaying the EMS events for the stop operation as it progresses. STOP TMF [,NOWAIT] [,ABRUPT] NOWAIT requests that when TMFCOM accepts the STOP TMF command, it suppresses display of the EMS event messages for the stop operation and immediately issues a prompt for another command. You can check the status of the stop operation later by issuing a STATUS TMF or DISPLAY OPERATIONS command.
STOP TMF TMFCOM Commands To confirm that it accepts the STOP TMF command, TMFCOM displays the following message: STOP TMF operation [operation-number] begun. The ABRUPT option terminates all TMF activities immediately, basically causing TMF to crash. With this option, transactions in the brief, final commit stage are allowed to finish, but all other in-progress transactions are aborted and no new transactions can start.
STOP TMF TMFCOM Commands TMF parameters: None. 20:16 24JUN03 195,03,063 NonStop TMF on \PLUTO Stopping TMF. . . . 20:16 24JUN03 195,03,063 NonStop TMF on \PLUTO Primary Component TranscrtlMgmt Stopped. 20:16 24JUN03 195,03,063 NonStop TMF on \PLUTO Primary Component ProcessMgmt Stopped. 20:16 24JUN03 195,03,063 NonStop TMF on \PLUTO Backup Component ProcessMgmt Stopped. . . . 20:16 24JUN03 195,03,063 NonStop TMF on \PLUTO Process: TMF Stopped.
STOP TMF TMFCOM Commands *** Display of STOP TMF operation [76] terminated by break*** TMF 122> Now, the user enters a new STOP TMF command, this time specifying ABRUPT.
VOLUME TMFCOM Commands VOLUME The VOLUME command specifies the default volume and subvolume names for expanding all unqualified file names. VOLUME [volume] [[volume.]subvolume] volume is the name of the default disk volume. subvolume is the name of the default subvolume. Security Restrictions Anyone can enter the VOLUME command. TMF State Requirement You can enter the VOLUME command at any time, whether or not TMF has been started.
VOLUME TMFCOM Commands • If you omit both volume and subvolume, the recorded default volume and subvolume are cleared. As a result, unqualified file names are expanded according to the defaults in effect when you started TMFCOM. At any time, you can display the currently recorded default volume and subvolume for your session, as well as the default volume and subvolume in effect at the beginning of your session, by entering the ENV command.
! TMFCOM Commands ! The ! (exclamation-point) command re-executes a command previously issued in the current TMFCOM session, as recorded in the TMFCOM command history buffer. ! [-linenum | linenum | string | "quoted-string "] -linenum identifies the command to be re-executed relative to the current command line. For instance, !-3 re-executes the third command prior to the current one. linenum identifies the command to be re-executed by command line number.
! TMFCOM Commands If you use the ! command without a line number or text string, TMFCOM re-executes the last command you entered. You can use the TMFCOM HISTORY command to display the line numbers associated with the most recently entered TMFCOM commands. Only commands currently stored in the command history buffer are displayed, and only those can be re-executed by the ! command.
! TMFCOM Commands In the following example, the ? command displays the last STATUS command entered in the session, and the ! command re-executes that command: TMF 13> ?STATUS TMF 13> STATUS CATALOG TMF 13> !STATUS TMF 13> STATUS CATALOG Catalog Status: Status: up ! HP NonStop TMF Reference Manual—540138-001 3 -313
? TMFCOM Commands ? The ? (question-mark) command displays a command previously entered in the current TMFCOM session, as recorded in the TMFCOM command history buffer. ? [-linenum | linenum | string | "quoted-string"] -linenum identifies the command to be displayed relative to the current command line. For example, ?-3 displays the third command before the current one. linenum identifies the command to be displayed by command line number.
? TMFCOM Commands If you use the ? command without a line number or text string, TMFCOM displays the last command you entered. You can use the TMFCOM HISTORY command to display the line numbers associated with the most recently entered commands. Only commands currently stored in the command history buffer are displayed, and only those can be selected for action by the ? command.
? TMFCOM Commands HP NonStop TMF Reference Manual—540138-001 3 -316
4 TMFCOM Tape Media Considerations TMFCOM commands that affect labeled magnetic tape media (those that add or alter tape volume or dump entries in the TMF catalog) require you to be aware of certain tape-labeling behavior.
TMFCOM Tape Media Considerations Other Types of Tape Drives and Devices Other Types of Tape Drives and Devices For labeling tapes using tape drives and devices other than open-reel tape drives, you must omit the DENSITY option from the ADD TAPEMEDIA or SET TAPEMEDIA command. For example, for labeling tapes on cartridge tape drives, digital audio tape (DAT) devices, or digital liner tape (DLT) devices, you would not specify the DENSITY option.
TMFCOM Tape Media Considerations Additional Guidelines for Using Tape Media The ALTER TAPEMOUNT command may be used to choose tapes from either set for input. • If the copies were made in series, however, they are interchangeable on the first reel only. Thus, if you use the first reel from Set A, the ALTER TAPEMOUNT command cannot be used to choose a reel from Set B. To switch sets, you must reject the current request and start over again, using the correct set throughout.
TMFCOM Tape Media Considerations Using the VERIFYTAPE Option Using the VERIFYTAPE Option In the ALTER AUDITDUMP and DUMP FILES commands, the VERIFYTAPE option determines whether a tape is verified after a dump is written to the tape. When the VERIFYTAPE option is in effect, TMF examines the tape volume for data integrity after the tape is written. This examination involves reading the volume labels, file labels, data records, and checksums.
TMFCOM Tape Media Considerations Considering File Size Factors Autoloaders help reduce the frequency of tape-handling by the operator and, depending on the model, allow you to place six or seven tapes in the hopper at once. The autoloader cycles through these tapes in order, loading them automatically. Cartridge magazines allow you to transport and mount collective sets of tapes.
TMFCOM Tape Media Considerations HP NonStop TMF Reference Manual—540138-001 4 -6 Considering File Size Factors
A TMFCOM Messages The messages generated by TMFCOM are described in this appendix. These messages appear on your workstation or terminal screen during a TMFCOM session. Alternatively, they can be directed to another output device or file through the TMFCOM command OUT option described in Directing Output to an Alternate Destination on page 2-8.
Message Types TMFCOM Messages Message Types TMFCOM displays three basic types of messages: • • • Informative messages that report status or other normal conditions and that require no action on your part Error messages (preceded by the word ERROR) that indicate a mistake in a command that prevented its execution; these messages typically require you to reenter the command correctly Warning messages (preceded by the word WARNING) that indicate a potentially dangerous or invalid operation, but that allow
File Names in Messages TMFCOM Messages File Names in Messages Many TMFCOM messages include as parameters file names that identify objects such as disk files, tape volumes, and processes. Often these messages report syntax errors that result from improperly specifying these file names in commands. When present, these names appear in the message descriptions as parameters such as file-id, volume, and process-name, among others.
Other Messages TMFCOM Messages As an example, for the following excessively long command, TMFCOM would report the error as follows: TMF 3> ALTER BEGINTRANS, TRANSCOUNTTHRESH (1500, 1600), TMFLIBMEMTHRESH (85,90), TMPM EMTHRESH (90,95), TTRANSPERCPU (1024,1024), AUTOABORT 7200 SECONDS, RECRMCOUNT 256, RMOPENPERCPU 128, BRANCHESPERRM 128 (more characters follow, exceeding 240 total...) ... (85,90), TMPMEMTHRESH (90, 95), TTRANSPERCPU (1024,1024), AUTOABORT 720 ...
Error Information and Failure Data Capture TMFCOM Messages • If the policies at your site permit: • • Copies of any audit-trail files you believe might be related to the problem (for example, those for which audit-reading errors are reported) Relevant information about the application running when the problem occurred For problems involving processor (CPU) halts or hangs, in addition to the standard items, please supply: • • Processor (CPU) dumps Copies of the following files from the $SYSTEM.
Message Descriptions TMFCOM Messages Message Descriptions The numbered messages are described in the following pages. 1 The command specified an invalid TAPEMEDIA name, tape-volume. If this name begins with a digit, all characters must be digits. If this name begins with a letter, subsequent characters can be alphanumeric. Also, the command might require the “part:copy” specification. tape-volume is the invalid tape-volume name.
Message Descriptions TMFCOM Messages 2 This request contained too many structures; either one structure or none is permitted. Cause. A Subsystem Programmatic Interface (SPI) violation occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider. 3 The command specified a filename that was not correctly formed. The invalid filename was: filename. filename is the invalid file name.
Message Descriptions TMFCOM Messages 5 In this context, the command cannot specify a remote file. The remote filename is: filename. filename is the remote file name. Cause. The command contained a parameter that referred to a remote file, but only local file names are allowed for that parameter. Effect. The command fails. Recovery. Re-enter the command, using a local file name. 6 The command specified an invalid TYPE parameter. be either ONLINEDUMP or AUDITDUMP. TYPE must Cause.
Message Descriptions TMFCOM Messages 8 The command specified an invalid SORT parameter. be either BYFILE or BYSERIAL. SORT must Cause. In an INFO DUMPS command, the SORT parameter specified an invalid order for listing dumps. Effect. The command fails. Recovery. Re-enter the command, specifying BYFILE to list the dumps alphabetically by file name or BYSERIAL to list the dumps in descending order by serial number. 9 In this context, the command must specify exactly one TransID. Cause.
Message Descriptions TMFCOM Messages 11 In this context, a TransID cannot contain wild-card characters. The invalid TransID is transaction-id. transaction-id is the invalid transaction identifier. Cause. The command specified one or more wild-card characters (*) in its transaction-id parameter list. However, only fully qualified transaction identifiers can be used in this command. Effect. The command fails. Recovery. Enter a STATUS TRANSACTIONS * command to list the valid transactions in the system.
Message Descriptions TMFCOM Messages 14 The command specified an invalid process name. The invalid process name was process-name. process-name is the invalid process name. Cause. The command specified an invalid process name. Perhaps this name was too long, contained improper characters, or did not begin with a dollar sign ($). Effect. The command fails. Recovery. Verify that the process name complies with the syntax rules listed in File Names and Process Identifiers on page 3-6.
Message Descriptions TMFCOM Messages 30 The command specified an invalid volume name. The invalid volume name was volume. volume is the invalid volume name. Cause. The command included an invalid volume name. Perhaps the name was too long, contained improper characters, or began with a character other than a dollar sign ($). Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 34 The command specified an invalid PRI option. The PRI parameter must be 204 for the TMP process, 211 for the TMFMON process, or a value between 1 and 199, inclusive, for all other processes. Cause. The command specified an invalid process priority in the PRI option. The TMP process’ priority must be 204. The TMFMON process’ priority must be 211. The priority of all other processes must fall in the range 1 through 199, inclusive. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 37 The command specified an invalid DENSITY parameter. Cause. The command specified an invalid DENSITY parameter, which indicates the density at which dumps are written to magnetic tape. Effect. The command fails. Recovery. Re-enter the command, using correct density value. For information about determining an appropriate density, see Section 4, TMFCOM Tape Media Considerations.
Message Descriptions TMFCOM Messages 39 The command specified an invalid START file name, filename. filename is the invalid file name. Cause. The command specified an invalid file name in the START parameter used to indicate the file at which an online dump begins in the specified volume and subvolume. Perhaps the name was too long or contained improper characters. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 42 The command specified an invalid BLOCKSIZE parameter. Cause. The command specified an invalid BLOCKSIZE parameter used to set the data-block density at which dumps are written to tape. The value specified in BLOCKSIZE, multiplied by 1024, gives the block size in bytes. For BLOCKSIZE, you can specify one of the following values: 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52. The maximum block size is also limited by the density at which the tape drive writes data.
Message Descriptions TMFCOM Messages 46 Subsystem Error: The priority order of the DISKMEDIA tokens is not consistent. Contact the Global Customer Support Center (GCSC) or your service provider. Cause. A Subsystem Programmatic Interface (SPI) violation occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider. 47 The command must supply at least one filename. Cause.
Message Descriptions TMFCOM Messages 50 The command specified an invalid RETAINDEPTH parameter. RETAINDEPTH must specify a value in the range 1 to 99, inclusive. Cause. The command specified an invalid RETAINDEPTH parameter used to determine the number of online dump generations that can remain in the catalog. The number specified can range from 1 to 99. Effect. The command fails. Recovery. Re-enter the command, using a RETAINDEPTH value of from 1 through 99.
Message Descriptions TMFCOM Messages 54 The command specified an invalid LABEL parameter, or omitted this parameter. Cause. The command specified an invalid LABEL parameter used to determine whether an output tape volume is labeled, or the command omitted this parameter altogether. LABEL, when present, can specify only ON (to request labeling) or OFF (to suppress labeling). Effect. The command fails. Recovery. Re-enter the command, including the LABEL parameter, set to either ON or OFF.
Message Descriptions TMFCOM Messages 57 The command omitted a master and/or auxiliary audit trail sequence number. Cause. The command did not include an audit-trail file sequence number. Effect. The command fails. Recovery. Re-enter the command, specifying a filename parameter that includes the audit-trail file sequence number. 58 In this context, the command must specify a file name that does not include wild-card characters. The invalid file name was filename. filename is the invalid file name. Cause.
Message Descriptions TMFCOM Messages 60 The command specified an improper INVALID parameter. Cause. The command specified an improper INVALID parameter used to determine whether a file is available for use in file recovery. You must set INVALID to either ON (to indicate that the file is available) or OFF (to indicate that it is not available). Effect. The command fails. Recovery. Re-enter the command with the INVALID parameter set to either ON or OFF. 61 The command specified an invalid MaxResp value.
Message Descriptions TMFCOM Messages 66 Subsystem Error: The value specified for the OVERWRITE LABEL option is invalid. This value can be only TRUE, FALSE, or NULL. Contact the Global Customer Support Center (GCSC) or your service provider. Cause. A Subsystem Programmatic Interface (SPI) error occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider.
Message Descriptions TMFCOM Messages 70 When adding an audit dump into the catalog, the command must specify exactly one filename. Cause. An ADD DUMPS command specified multiple file names in the audittrail-file parameter, but only one file name is allowed. This name must be entered in the format shown under “Recovery.” Effect. The command fails. Recovery. Re-enter the command, using just one file name entered in the following format: $ZTMFAT.ZTMFAT.
Message Descriptions TMFCOM Messages 74 Either a DUMP FILES command specified more than 16 disk volumes in the DISKMEDIA parameter, or an ALTER AUDITDUMP command would have resulted in a total of more than 16 disk volumes configured for the dump process. Cause. Either a DUMP FILES or an ALTER AUDITDUMP command specified too many disk volumes, as follows: • The DUMP FILES command named too many disk volumes in the DISKMEDIA parameter, which identifies the disk volumes that receive the dumps.
Message Descriptions TMFCOM Messages 76 One of the options specified is not allowed with MEDIUM DISK. Cause. The command specified a parameter that is not compatible with the MEDIUM DISK parameter. MEDIUM DISK specifies the kind of medium on which dumps are recorded, but the incompatible parameter might be one that applies only to tape-based dumps−for example, BLOCKSIZE, COPIES, SYSTEM, or VERIFYTAPE. Effect. The command fails. Recovery. Re-enter the command without the incompatible parameter.
Message Descriptions TMFCOM Messages 79 In this context, the command cannot include wild-cards in the DISKMEDIA parameter list. The invalid DISKMEDIA was: filename. filename is the invalid file name. Cause. The command contained one or more wild-card characters (*) in its DISKMEDIA parameter list. However, only fully qualified medium identifiers must be used in this command. Effect. The command fails. Recovery. Re-enter the command, using only fully qualified medium identifiers.
Message Descriptions TMFCOM Messages 82 The command specified an invalid DISKMEDIA name for a remote disk volume. The invalid DISKMEDIA is: filename. filename is the invalid file name. Cause. The command specified an invalid name for a remote disk volume in the DISKMEDIA parameter. Effect. The command fails. Recovery. Verify that the file name and particularly the volume component, complies with the syntax rules listed in File Names and Process Identifiers on page 3-6.
Message Descriptions TMFCOM Messages 89 The command specified an invalid IGNOREDATAERRORS option. Cause. An ABORT TRANSACTION command specified an invalid option in the IGNOREDATAERRORS parameter. This parameter determines whether TMF ignores data errors while undoing the effects of a transaction and can only be set to either ON or OFF. Effect. The command fails. Recovery. Re-enter the command with IGNOREDATAERRORS set to either ON or OFF.
Message Descriptions TMFCOM Messages 92 Subsystem Error: An ADD DATAVOLS or ALTER DATAVOLS command specified an erroneous RECOVERYMODE value. Contact the Global Customer Support Center (GCSC) or your service provider. Cause. A Subsystem Programmatic Interface (SPI) error occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider.
Message Descriptions TMFCOM Messages 95 Subsystem Error: A DELETE DATAVOLS command specified an erroneous ALLOWINCONSISTENCY value. Contact the Global Customer Support Center (GCSC) or your service provider. Cause. A Subsystem Programmatic Interface (SPI) error occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider.
Message Descriptions TMFCOM Messages 101 Subsystem Error: A RECOVER FILES command specified the FROMARCHIVE option with an illegal value. Contact the Global Customer Support Center (GCSC) or your service provider. Cause. A Subsystem Programmatic Interface (SPI) error occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider.
Message Descriptions TMFCOM Messages 104 Subsystem Error: An ABORT TRANSACTION command specified the AVOIDHANGING option with an illegal value. Contact the Global Customer Support Center (GCSC) or your service provider. Cause. A Subsystem Programmatic Interface (SPI) error occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider.
Message Descriptions TMFCOM Messages 110 The command specified an erroneous STATE value. Cause. A STATUS OPERATIONS command specified a value other than INPROGRESS, FINISHED, or ALL for the STATE parameter. Effect. The command fails. Recovery. Re-enter the command with STATE set to INPROGRESS, FINISHED, or ALL. 111 The command specified an erroneous TYPE value. Cause. A STATUS OPERATIONS command specified an improper value for the TYPE parameter.
Message Descriptions TMFCOM Messages 114 The command specified an erroneous TRANSCOUNTTHRESH value. Cause. An ALTER BEGINTRANS command specified one or more improper values for the TRANSCOUNTTHRESH parameter. (See the command syntax description for the acceptable values.) Effect. The command fails. Recovery. Re-enter the command with TRANSCOUNTTHRESH set to proper values. 115 The command specified an erroneous TMFLIBMEMTHRESH value. Cause.
Message Descriptions TMFCOM Messages 118 The command specified an erroneous AUTOABORT value. Cause. An ALTER BEGINTRANS command specified an improper value for the AUTOABORT parameter. (See the command syntax description for the acceptable values.) Effect. The command fails. Recovery. Re-enter the command with AUTOABORT set to a proper value. 119 The command specified a DISKMEDIA name that was not correctly formed. The invalid DISKMEDIA was: filename. filename is the invalid file name. Cause.
Message Descriptions TMFCOM Messages 120 The command specified an invalid DISKMEDIA name for a remote disk volume. The invalid DISKMEDIA was: filename. filename is the invalid file name. Cause. An ALTER AUDITDUMP command specified an invalid name for a remote disk volume in the ADDDISKMEDIA or DELDISKMEDIA parameter. Effect. The command fails. Recovery. Verify that the file name and particularly the volume component complies with the syntax rules listed in File Names and Process Identifiers on page 3-6.
Message Descriptions TMFCOM Messages 122 The volume name volume, for a volume being added as an overflow audit volume, is invalid. volume is the name of the volume specified in the command. Cause. An ALTER AUDITTRAIL command specified an overflow-audit volume name that was not valid. For example, perhaps the name was too long or contained wildcard characters. Effect. The command fails. Recovery. Check the syntax rules for the ADDOVERFLOWVOL[S] parameter of the ALTER AUDITTRAIL command.
Message Descriptions TMFCOM Messages 124 The volume name volume, for volume being deleted as an active audit volume, is invalid. volume is the name of the volume specified in the command. Cause. An ALTER AUDITTRAIL command specified an active-audit volume name that was not valid. For example, perhaps the name was too long or contained wild-card characters. Effect. The command fails. Recovery. Check the syntax rules for the DELETEACTIVEVOL[S] parameter of the ALTER AUDITTRAIL command.
Message Descriptions TMFCOM Messages 126 The volume name volume, for volume being deleted as a restore audit volume, is invalid. volume is the name of the volume specified in the command. Cause. An ALTER AUDITTRAIL command specified a restore-audit volume name that was not valid. For example, perhaps the name was too long or contained wild-card characters. Effect. The command fails. Recovery. Check the syntax rules for the DELETERESTOREVOL[S] parameter of the ALTER AUDITTRAIL command.
Message Descriptions TMFCOM Messages 128 The volume name volume, for a volume being added as an overflow audit volume, is invalid. volume is the name of the volume specified in the command. Cause. An ADD AUDITTRAIL command specified an overflow-audit volume name that was not valid. For example, perhaps the name was too long or contained wild-card characters. Effect. The command fails. Recovery. Check the syntax rules for the OVERFLOWVOL[S] parameter of the ADD AUDITTRAIL command.
Message Descriptions TMFCOM Messages 130 The volume name volume is invalid in the context used. volume is the name of the volume specified in the command. Cause. The command referred to a volume name that was not valid within the context of this command. For example, perhaps the command used a remote volume name where only local names are permitted or specified a name containing wild-card characters where only complete names are permitted. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 133 Subsystem Error: The value of the AuditDump attribute must be ON or OFF. Cause. A TMF error occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider. 134 The value specified for FILESPERVOLUME is invalid. Cause.
Message Descriptions TMFCOM Messages 136 The value specified for OVERFLOWTHRESHOLD is invalid. Cause. An ADD AUDITTRAIL or ALTER AUDITTRAIL command specified a value for the OVERFLOWTHRESHOLD parameter that did not fall within the proper limit, an integer from 50 to 100. This parameter determines the percentage of audit trail capacity in use above which TMF begins overflow copying. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 139 Subsystem Error: This command can specify only one AuditTrailId. Cause. A TMF error occurred. Effect. The command fails. Recovery. This command should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider. 140 A STATUS OPERATIONS command that specified the TYPE parameter also specified an operation number. Cause.
Message Descriptions TMFCOM Messages 142 A STATUS OPERATIONS command that specified the BEGINTIME parameter also specified an operation number. Cause. A STATUS OPERATIONS command that included the BEGINTIME parameter also referred to a specific TMF operation. When BEGINTIME is included, however, the command must specify the wild-card (*) character rather than a particular operation number. BEGINTIME then acts as a filter to display all operations that began at or after the time indicated. Effect.
Message Descriptions TMFCOM Messages 145 Subsystem Error: The SHOTGUN buffer received by the TMFSERVE process did not contain the required token ZTMF-TknOperationNum. Contact the Global Customer Support Center (GCSC) or your service provider. Cause. A TMF error occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider. 146 The command did not specify a valid dump serial number.
Message Descriptions TMFCOM Messages 148 The command did not specify a disk media location for the OLDDMLOC option. Cause. A RELOCATE DISKDUMPS command did not specify a disk media location in the OLDDMLOC parameter. Effect. The command fails. Recovery. Retry the command, specifying a valid disk media location in the OLDDMLOC parameter. 149 The command specified an invalid disk media location for the OLDDMLOC option. The invalid disk media location was dmloc.
Message Descriptions TMFCOM Messages 151 The command specified an invalid disk media location for the NEWDMLOC option. The invalid disk media location was dmloc. dmloc is the invalid disk media location specified in the NEWDMLOC parameter. Cause. A RELOCATE DISKDUMPS command specified the disk media location for the NEWDMLOC option in an invalid format. Effect. The command fails. Recovery. Check the syntax for the NEWDMLOC option and re-enter the command.
Message Descriptions TMFCOM Messages 154 The command specified more than one disk media location for the NEWDMLOC option. Cause. A RELOCATE DISKDUMPS command specified multiple disk media locations in the NEWDMLOC parameter. Effect. The command fails. Recovery. Retry the command, specifying a single value for the NEWDMLOC parameter. 155 TMF found no disk dumps that matched the requested criteria. Cause.
Message Descriptions TMFCOM Messages 158 The command must specify only one process-type option. Cause. An ALTER PROCESS command specified more than one process type (for example, FILERECOVERY and BACKOUT). Effect. The command fails. Recovery. Retry the command, specifying only one process type. 160 The command option WHEREPHYSVOLIS supplied an invalid volume name. Cause. A RECOVER FILES command specified an invalid volume name in the WHEREPHYSVOLIS parameter.
Message Descriptions TMFCOM Messages 162 The command option TOPHYSVOL allows only one physical volume name. Cause. A RECOVER FILES command specified more than one physical volume name in the TOPHYSVOL parameter. Effect. The command fails. Recovery. Re-enter the command, specifying just one volume name in the TOPHYSVOL parameter. 163 The command specified an invalid RECOVERVDPPHASE1 parameter. Cause. A RECOVER FILES command specified the RECOVERVDPPHASE1 parameter incorrectly. Effect. The command fails.
Message Descriptions TMFCOM Messages 167 The command specified an invalid RECRMCOUNT value. Cause. An ALTER BEGINTRANS command contained an invalid value for the RECRMCOUNT attribute. Effect. The command fails. Recovery. Retry the command with a valid value for the RECRMCOUNT attribute. The valid values are 16 through 16384, inclusive. The value specified will be automatically rounded to the nearest multiple of 16. 168 The command specified an invalid RMOPENPERCPU value. Cause.
Message Descriptions TMFCOM Messages 170 The resource manager name rmname is invalid. rmname is the invalid resource manager name specified in the command. Cause. The resource manager name specified in rmname is invalid. Effect. The command fails for this resource manager name. Recovery. Retry the command with a valid resource manager name.
Message Descriptions TMFCOM Messages 173 The command specified both a wild-card resource manager name and a specific volume name. Cause. An INFO RESOURCEMANAGER or a STATUS RESOURCEMANAGER command included both a wild-card character (*) and a resource manager name to identify the resource managers for which to display information. Although TMFCOM accepts either of these entries, it does not accept both in the same request. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 176 The command can specify only one resource manager name. Cause. The command specified multiple resource managers, but only one resource manager is allowed. Effect. The command fails. Recovery. Retry the command, specifying only the correct single resource manager. 201 ABORT TRANSACTION command failed because of errcode.
Message Descriptions TMFCOM Messages 202 The TAPEMEDIA "tape-volume" is already listed in the TAPEMEDIA specification. tape-volume is the tape volume name. Cause. The command specified the tape volume named tape-volume more than once. Effect. The command fails. Recovery. Re-enter the command, specifying tape-volume only once. 208 TMFCOM does not recognize this command. Cause. This command is not defined in TMF. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 236 The ALTER BEGINTRANS command specified an invalid AUTOABORT parameter. AUTOABORT must indicate either a timeout value in the proper range or OFF. Cause. The command specified an invalid value for the AUTOABORT parameter. Effect. The command fails. Recovery. Re-enter the command, specifying either an appropriate timeout value for the AUTOABORT parameter, or 0 to turn the autoabort feature off.
Message Descriptions TMFCOM Messages 254 The user ID SUPER.SUPER (255,255) must be used to execute this command. The user ID of this user is groupid,userid. groupid is your user group ID. userid is your user ID. Cause. This command can only be issued by a person logged on under the super ID (user ID 255,255). Effect. The command fails. Recovery. Ask someone with the super ID to enter this command on your behalf, or enter another command.
Message Descriptions TMFCOM Messages 256 Only the owner of the TMF configuration files (user ID groupid1, userid1), or someone with the SUPER.SUPER ID (user ID 255,255), can execute this command. The user ID of this user is groupid2,userid2. groupid1 is the user group ID of the owner of the TMF configuration files. userid1 is the user ID of the owner of the TMF configuration files. groupid2 is your user group ID. userid2 is your user ID. Cause.
Message Descriptions TMFCOM Messages 257 Only someone with the user ID groupid1,userid1, or someone with the SUPER.SUPER ID (user ID 255,255), can execute this command. The user ID of this user is groupid2,userid2. groupid1 is the user group ID required to execute the command. userid1 is the user ID required to execute the command. groupid2 is your user group ID. userid2 is your user ID. Cause.
Message Descriptions TMFCOM Messages 258 Subsystem Error: Unable to PROCESS_CREATE_ the process process-name using filename because of errcode. process-name is the name of the process that could not be created. filename is the name of the object file for this process.
Message Descriptions TMFCOM Messages 259 Subsystem Error: Unable to OPEN the TMF process process-name (filename) because of errcode. process-name is the name of the process that could not be opened. filename is the name of the object file for this process. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer.
Message Descriptions TMFCOM Messages 260 Subsystem Error: Unable to WRITEREAD a startup message to TMF process process-name (filename) because of errcode. process-name is the name of the process that could not receive the message. filename is the name of the object file for this process.
Message Descriptions TMFCOM Messages 263 The TAPEMEDIA named "tape-volume" already exists in the catalog. tape-volume is the name of the existing tape volume. Cause. This command attempted to add a tape volume named tape-volume to the TMF catalog, but a tape volume with this identity is already defined there. Effect. The command fails. Recovery. None required. 264 The catalog contains no TAPEMEDIA matching the mediaset tapevolume. tape-volume is the name of the nonexistent tape volume. Cause.
Message Descriptions TMFCOM Messages 266 The command could not label the tape because MEDIASRV returned error errcode. See the DSM/Tape Catalog Messages Manual for more information about this error. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 269 Labeled-tape support is not configured. One or more audit trails are configured for automatic audit dumping, so labeled-tape support must be enabled for this system. Configuration is performed through system generation. Cause. Audit dumping to tape cannot take place because labeled-tape support is not enabled. Effect. Audit dumping to tape remains disabled. Recovery. Ask your system manager to configure labeled-tape support, using the system generation program.
Message Descriptions TMFCOM Messages 272 The RESOLVE TRANSACTION command failed because of errcode. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause. While a RESOLVE TRANSACTION command was in process, the condition indicated by errcode occurred. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 276 The command attempted to add an existing audit dump to the TMF catalog. Cause. An ADD DUMPS command attempted to add to the TMF catalog an audit dump record that was already entered there. Effect. None. Recovery. None required. 277 The command attempted to add an existing dump to the catalog, but the MAT specified did not match that of the existing dump. Cause.
Message Descriptions TMFCOM Messages 279 The "part:copy" specification of the TAPEMEDIA tape-volume is out of sequence with other portions of the dump. part identifies the portion of the dump stored on this tape volume. copy identifies the copy number of the dump stored on this tape volume. tape-volume is the tape-volume name. Cause. The command specified, in the part:copy subparameter, a portion of the dump that is out of sequence with the other portions. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 281 The TAPEMEDIA tape-volume is already recorded as part of another dump in the catalog. tape-volume is the tape-volume name. Cause. The command attempted to add a tape volume already defined as part of another dump in the TMF catalog. Effect. The command fails. Recovery. None required. 282 The file filename is already recorded as part of this dump. filename is the name of the file. Cause.
Message Descriptions TMFCOM Messages 283 Subsystem Error: The volume that the file filename resides on is not configured as a data volume, or the virtual volume that the file resides on contains one or more physical volumes that are not enabled for TMF. filename is the name of the referenced file. Cause. For a file on a data volume, a TMF error occurred.
Message Descriptions TMFCOM Messages 290 The Guardian procedure ENFORMSTART returned an error. error was errcode. The errcode supplies a numeric code that further defines the error and identifies the subsystem and system procedure that transmitted this code: the Guardian procedure ENFORMSTART. Cause. While a command was in process, the condition indicated by errcode occurred. Effect. The command fails. Recovery. For details about this error, refer to the Guardian Procedure Errors and Messages Manual.
Message Descriptions TMFCOM Messages 295 Unable to open the catalog because of errcode. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause. While the command attempted to open the TMF catalog, the condition indicated by errcode occurred. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 296 Unable to determine catalog status because of errcode. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause. While the command attempted to obtain the status of the TMF catalog, the condition indicated by errcode occurred. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 297 Unable to obtain scratch reels because of errcode. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause. While the command attempted to obtain scratch reels for dumps, the condition indicated by errcode occurred. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 298 Unable to start the specified dump because of errcode. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause. While the command attempted to start a dump, the condition indicated by errcode occurred. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 299 The DELETE CATALOG command returned errcode. log for possible further explanation. Please see the errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 300 Unable to acquire the specified TAPEMEDIA, tape-volume, because of errcode. tape-volume is the tape volume that could not be accessed. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 301 Unable to end the specified dump because of errcode. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause. While the command attempted to terminate a dump in progress, the condition indicated by errcode occurred. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 302 Unable to add the specified TAPEMEDIA, tape-volume, because of errcode. tape-volume is the tape volume that could not be added. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 303 Unable to add the specified file, filename, because of errcode. filename is the file that could not be added. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 304 Unable to find the specified TAPEMEDIA, tape-volume, because of errcode. tape-volume is the tape volume that could not be located. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 305 Unable to find the specified file, filename, because of errcode. filename is the file that could not be located. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 306 Unable to find the specified dump because of errcode. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause. While the command attempted to locate a dump, the condition indicated by errcode occurred. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 307 Unable to alter the specified TAPEMEDIA, tape-volume, because of errcode. tape-volume is the tape volume that could not be altered. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 308 Unable to delete the specified TAPEMEDIA, tape-volume, because of errcode. tape-volume is the tape volume that could not be deleted. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 309 Unable to count the number of copies of the specified file, filename, because of errcode. filename is the file for which copies could not be counted. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 310 Unable to alter the specified dump because of errcode. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause. While the command attempted to alter dump entries in the TMF catalog, the condition indicated by errcode occurred. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 311 Unable to delete the specified dump because of errcode. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause. While the command attempted to remove a dump entry from the TMF catalog, the condition indicated by errcode occurred. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 314 Unable to add the specified DISKMEDIA, filename, because of errcode. filename is the disk file that could not be added. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 315 The command attempted to add a device for an existing dump in the catalog, but the dump medium (TAPE or DISK) specified did not match that of the existing dump. Cause. The command attempted to add an additional device for a particular dump to the TMF catalog, but the device is not the same type as the devices previously assigned for this dump. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 317 The command did not purge some or all of the DISKMEDIA from disk because of errcode. See the log for the specific DISKMEDIA. The dump has been deleted from the catalog. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 318 The command did not purge some or all of the DISKMEDIA from disk because of errcode. See the log for the specific DISKMEDIA. The dump has not been removed from the catalog. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause.
Message Descriptions TMFCOM Messages 320 The DISKMEDIA filename is out of sequence with the other DISKMEDIA listed or with the DISKMEDIA already added into the catalog. filename is the disk file that is out of sequence. Cause. The command specified a disk volume that was out of sequence with the other disk volumes specified in this command or those already configured in the catalog. Effect. The command fails. Recovery. Re-enter the command, specifying the disk volume in the proper sequence.
Message Descriptions TMFCOM Messages 325 This command would result in no active audit trail volumes being configured. Cause. The command attempted to remove all active-audit volumes from the system, but a TMF configuration must have at least one such volume. Effect. The command fails. Recovery. Re-enter the command without specifying all remaining audit volumes; leave at least one such volume in the system.
Message Descriptions TMFCOM Messages 328 Volume volume, which was specified as an active audit volume, already contains files on the ZTMFAT subvolume. This is not allowed. volume is the volume name. Cause. The command attempted to configure as an active-audit volume a disk volume that already contains files stored in the ZTMFAT subvolume. This subvolume name is reserved for audit files. Volumes with files in the ZTMFAT subvolume cannot be newly added as audit volumes to the configuration. Effect.
Message Descriptions TMFCOM Messages 330 File System error fserrcode occurred while attempting to add volume volume to the audit trail configuration as at-volumetype. fserrcode supplies a numeric code that further defines the error and indicates it was transmitted by the File System. volume is the name of the volume specified in the command. at-volume-type is the volume type specified in the command. Cause.
Message Descriptions TMFCOM Messages 331 File System error fserrcode occurred while attempting to delete volume volume from the audit trail configuration as at-volume-type. fserrcode supplies a numeric code that further defines the error and indicates it was transmitted by the File System. volume is the name of the volume specified in the command. at-volume-type is the volume type specified in the command. Cause.
Message Descriptions TMFCOM Messages 332 Attempt to add volume volume failed because an audit trail can only have 16 volumes configured as at-volume-type. volume is the name of the volume specified in the command. at-volume-type is the volume type specified in the command. Cause. The command attempted to add a 17th volume of type at-volume-type, but only up to 16 of this type are permitted.
Message Descriptions TMFCOM Messages 334 Volume volume cannot be deleted as at-volume-type because it is not configured as that type. volume is the name of the volume specified in the command. at-volume-type is the volume type specified in the command. Cause. The command attempted to remove an audit volume of type at-volumetype, but the volume is not configured as that type. For example, perhaps the command attempted to delete an ACTIVEVOL named $VOL1, but $VOL1 is configured as an OVERFLOWVOL. Effect.
Message Descriptions TMFCOM Messages 336 Volume volume cannot be deleted as an active audit volume because it holds the CURRENT audit trail file. volume is the name of the volume specified in the command. Cause. The command attempted to remove the volume that holds the current audittrail file. Effect. The command fails. Recovery. Re-enter the command, selecting another volume to remove. 337 Volume volume cannot be deleted as an active audit volume because it holds the NEXT audit trail file.
Message Descriptions TMFCOM Messages 338 Volume volume, being configured as at-volume-type, has files residing in the ZTMFAT subvolume that are either old audit trail files or are not audit trail files at all. volume is the name of the volume specified in the command. at-volume-type is the volume type specified in the command. Cause.
Message Descriptions TMFCOM Messages 340 An auxiliary audit trail cannot be configured with AUDITDUMP ON unless the master audit trail is also configured with AUDITDUMP ON. Cause. The command attempted to configure an auxiliary audit trail with the AUDITDUMP option set to ON, but the master audit trail has this option set to OFF. If any auxiliary audit trail is to be dumped, the master audit trail must be dumped. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 343 You cannot alter the active audit volume configuration for an audit trail unless TMF is started. Cause. The command attempted to change the active volume configuration for an audit trail, but TMF is not yet started. Effect. The command fails. Recovery. Start TMF (or ask your system manager to do so). Then, re-enter the command. 346 The resource manager named rmname already exists. rmname is the duplicate resource manager name specified in the command. Cause.
Message Descriptions TMFCOM Messages 348 The resource manager named rmname is currently open. rmname is the name of the open resource manager specified in the command. Cause. The command attempted to delete the resource manager specified in rmname, but this resource manager is open at present. Effect. The command fails for this resource manager name. Recovery.
Message Descriptions TMFCOM Messages 350 The resource manager named rmname is not currently open. rmname is the name of the unopen resource manager specified in the command. Cause. The command attempted to close the resource manager specified in rmname, but this resource manager is not currently open. Effect. The command fails for this resource manager name. Recovery. Retry the command with another resource manager name, or select another TMFCOM command.
Message Descriptions TMFCOM Messages 353 The ALTER BEGINTRANS, AUTOABORT timer command failed because the autoabort timer value cannot be less than the disconnect timer value. Use the INFODISCONNECTTMR command in SNOOP to determine the disconnect timer value timer is the timer value specified in the ALTER BEGINTRANS command. Cause.
Message Descriptions TMFCOM Messages 355 Audit trails cannot be added after TMF has been started following a DELETE TMF operation. Cause. An ADD AUDITTRAIL command attempted to add an audit trail after a new TMF configuration had been generated. New audit trails, however, can only be added after the DELETE TMF command purges the old configuration but before the START TMF command generates the new one. Effect. The command fails. Recovery. See your system manager.
Message Descriptions TMFCOM Messages 357 Volume volume, being configured as at-volume-type, does not exist. volume is the name of the volume specified in the command. at-volume-type is the audit volume type specified in the command. Cause. An ADD AUDITTRAIL or ALTER AUDITTRAIL command attempted to add a volume named volume as an at-volume-type, but this volume does not exist. Effect. The command fails. Recovery. Re-enter the command, using the name of an existing volume.
Message Descriptions TMFCOM Messages 359 AUDITDUMP could not be set to OFF for the master audit trail because auxiliary audit trails were configured with AUDITDUMP ON. Cause. The command attempted to configure a master audit trail with the AUDITDUMP option set to OFF, but this option is set to ON for the auxiliary audit trail (or trails). This option must be consistent for all audit trails. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 362 Subsystem Error: Status ATFiles specified an illegal ATFileStatus value. Contact the Global Customer Support Center (GCSC) or your service provider. Cause. A TMF error occurred. Effect. The command fails. Recovery. This message should never appear. Contact the GCSC or your service provider. 363 Subsystem Error: Status ATFiles specified an illegal ATFileDumpStatus value. Contact the Global Customer Support Center (GCSC) or your service provider. Cause.
Message Descriptions TMFCOM Messages 365 The command specified the same ADDDISKMEDIA or DELDISKMEDIA identifier more than once. The duplicated identifier is: disk. disk is the duplicated identifier. Cause. An ALTER AUDITDUMP command included more than one instance of the same disk medium identifier in the ADDDISKMEDIA or DELDISKMEDIA parameter. Effect. The command fails. Recovery. Re-enter the command with the correct audit-trail identifier specified only once.
Message Descriptions TMFCOM Messages 370 Subsystem Error: The backup TMP could not handle the request. Cause. A TMF error occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider. 371 This command requires that TMF is either started or in the process of stopping. Cause.
Message Descriptions TMFCOM Messages 380 START TMF operation operation-number begun. operation-number is an integer assigned by TMF to uniquely identify this specific operation at your terminal and in the EMS log file. Cause. A START TMF command has been executed, resulting in startup of the TMF system and transaction processing. Effect. None; informative message only. Recovery. None required. 381 STOP TMF operation operation-number begun.
Message Descriptions TMFCOM Messages 385 Subsystem Error: A STOP TMF command specified the ABRUPT option with an illegal value. Contact the Global Customer Support Center (GCSC) or your service provider. Cause. A TMF error occurred. Effect. The command fails. Recovery. This message should never appear. Contact the GCSC or your service provider. 386 The state of the specified transaction (transid) does not permit the attempted operation. transid is a transaction identifier. Cause.
Message Descriptions TMFCOM Messages 390 volume -- not added (not accessible). volume is the name of the volume specified in the command. Cause. The command attempted to add a volume but could not do so, probably because the volume is inaccessible. Effect. The command fails. Recovery. Make the volume accessible; bring up the volume or the processor to which it is attached. 391 volume -- not added (DP rejected startup request, see EMS log). volume is the name of the volume specified in the command. Cause.
Message Descriptions TMFCOM Messages 393 volume -- not added (already configured as a data volume). volume is the name of the volume specified in the command. Cause. The command attempted to add a data volume but could not do so because the volume already exists in the current configuration as a data volume. Effect. None. Recovery. None required. 394 volume -- not added (already configured as active audit trail volume). volume is the name of the volume specified in the command. Cause.
Message Descriptions TMFCOM Messages 395 ARCHIVE recovery mode requires that the specified audit trail be configured for audit dumping. Cause. The command set the RECOVERYMODE option to ARCHIVE, but the audit trail was not configured for audit dumping. Effect. The command fails. Recovery. Possible recovery actions are as follows: • • • • If you unintentionally set RECOVERYMODE to ARCHIVE, re-enter the ADD DATAVOLS or ALTER DATAVOLS command with RECOVERYMODE set to ONLINE.
Message Descriptions TMFCOM Messages 396 ARCHIVE recovery mode requires that the MASTER audit trail be configured for audit dumping. Cause. The command set the RECOVERYMODE option to ARCHIVE, but the master audit trail was not configured for audit dumping. Effect. The command fails. Recovery. Possible recovery actions are as follows: • • • • If you unintentionally set RECOVERYMODE to ARCHIVE, re-enter the ADD DATAVOLS or ALTER DATAVOLS command with RECOVERYMODE set to ONLINE.
Message Descriptions TMFCOM Messages 398 volume did not match the selection criteria specified in the command. volume is the name of the volume specified in the command. Cause. The command specified the volume but supplied additional selection criteria that did not match the volume’s attributes. For example, a STATUS DATAVOLS command requested information about a single volume named $DATA10 but specified that only information about volumes in the STARTED state was to be returned.
Message Descriptions TMFCOM Messages 400 volume -- not deleted (dirty, ALLOWINCONSISTENCY not specified). volume is the name of the volume specified in the command. Cause. A DELETE DATAVOLS command attempted to remove a data volume in the DOWNDIRTY state, but did not specify the ALLOWINCONSISTENCY option that would have permitted this deletion. The DOWNDIRTY state indicates that the volume is potentially inconsistent. Effect. The volume remains in the configuration. Recovery.
Message Descriptions TMFCOM Messages 422 A STOP TMF command was issued while TMF was starting. Cause. A STOP TMF command attempted to shut down TMF while TMF was being started. Effect. The command fails. Recovery. Re-enter the STOP TMF command, this time using the ABRUPT option, or wait until TMF is fully started and then re-enter the command as it was previously entered. Caution.
Message Descriptions TMFCOM Messages 425 A CANCEL OPERATIONS command specified an operation that does not exist. Cause. A CANCEL OPERATIONS command requested removal of a non-existent operation. Effect. The command fails. Recovery. Enter a STATUS OPERATIONS * command to list all operations currently recorded in the system, and check to ensure that you are specifying the correct operation number. 426 A CANCEL OPERATIONS command specified an operation that is in the process of being canceled. Cause.
Message Descriptions TMFCOM Messages 440 Operation operation-number has begun. operation-number is an integer assigned by TMF to uniquely identify this specific operation at your terminal and in the EMS log file. Cause. The operation specified has begun. Effect. None. Recovery. Informative message only; no corrective action is needed. 441 The command specified an invalid process-type parameter. Cause. An ALTER PROCESS or INFO PROCESS command specified an illegal value for the process-type parameter.
Message Descriptions TMFCOM Messages 443 Subsystem Error: An ALTER PROCESS command specified the DEBUG option with an illegal value. Contact the Global Customer Support Center (GCSC) or your service provider. Cause. A TMF error occurred. Effect. The command fails. Recovery. This message should never appear. Contact the GCSC or your service provider. 444 Subsystem Error: An ALTER PROCESS command specified the INSPECT option with an illegal value.
Message Descriptions TMFCOM Messages 447 The command specified an erroneous TERM value. Cause. An ALTER PROCESS command specified an invalid file identifier in the TERM parameter. Effect. The command fails. Recovery. Re-enter the command, specifying a valid file identifier. 448 The command specified an erroneous EXTENDEDSEGSIZE value.
Message Descriptions TMFCOM Messages 450 File system error fserrcode occurred while attempting to access the new configuration volume confvol. fserrcode is the File System error number. confvol is the new configuration volume. Cause. An ALTER TMF command attempted to access the new configuration volume, but could not do so because of a File System error. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 453 The command specified could not be executed because an ALTER TMF, CONFIGVOL command was already in progress. Cause. TMFCOM received a command while TMF was performing an ALTER TMF, CONFIGVOL operation. Effect. The command fails. Recovery. Wait until the ALTER TMF, CONFIGVOL operation completes and then reenter the command. 454 The command specified failed because file system error fserrcode occurred while accessing the configuration volume file.
Message Descriptions TMFCOM Messages 460 The INFO DUMPS Query Server reported File System Error fserrcode on catalog file filename. fserrcode is the File System error number. filename is the file on which the error was encountered. Cause. An INFO DUMPS command encountered a File System error on the catalog file noted. Effect. The command fails. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for a description of, and recovery actions for, the File System error.
Message Descriptions TMFCOM Messages 462 The INFO DUMPS Query Server did not find SerialNumber serialnumber in the catalog. serial-number is the serial number of the dump. Cause. An INFO DUMPS command could not locate the dump identified by serialnumber. Effect. The command fails. Recovery. Ensure that you are using the correct dump serial number, or select another dump and re-enter the command. 463 The INFO DUMPS Query Server reported Sort Error sort-errcode1,sort-errcode2 in the catalog.
Message Descriptions TMFCOM Messages 464 The INFO DUMPS Query Server did not find any files that matched fileset fileset. fileset is the fileset name specified in the command. Cause. An INFO DUMPS command could not locate the dump files identified by fileset. Effect. The command fails. Recovery. Ensure that you are using the correct fileset, or select another fileset and re-enter the command. 465 The token code token requires a ZTMF-TKN FileSet token in the SPI command language.
Message Descriptions TMFCOM Messages 501 The SPI usedlen usedlen was greater than the maximum maxlen. usedlen is the specified size of the SPI buffer. maxlen is the maximum size permitted for the SPI buffer. Cause. A Subsystem Programmatic Interface (SPI) violation occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the information supplied in usedlen and lengthread. Then, contact the GCSC or your service provider.
Message Descriptions TMFCOM Messages 503 The ShotGun buffer received by the TMFSERVE process contained a minimum server version minserv that was greater than the server version procserv of the TMFSERVE process. Contact the Global Customer Support Center (GCSC) or your service provider. minserv is the minimum server version. procserv is the procserv server version. Cause. A Subsystem Programmatic Interface (SPI) violation occurred. Effect. The command fails. Recovery. This message should never appear.
Message Descriptions TMFCOM Messages 505 The SPI buffer TMFSERVE received contained an unknown command: unknown-command. The object was: unknown-object. unknown-command is the unknown command. unknown-object is the object referred to in the command. Cause. A Subsystem Programmatic Interface (SPI) violation occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the information supplied in unknown-command and unknown-object.
Message Descriptions TMFCOM Messages 507 Subsystem Error: ShotGun CLS. This is an empty response as defined by the Cause. A Subsystem Programmatic Interface (SPI) violation occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider. 508 Subsystem Error: not valid. The context token received by TMSERVE was Cause. A Subsystem Programmatic Interface (SPI) violation occurred.
Message Descriptions TMFCOM Messages 511 BEGINTRANS was already enabled by an operator command. However, there may be other reasons why BEGINTRANS is disabled. The STATUS BEGINTRANS command will provide that information. Cause. An ENABLE BEGINTRANS command was issued without a previous DISABLE BEGINTRANS command. BEGINTRANS could still be disabled for other reasons, including an audit trail reaching its begin-transaction-disable threshold, or a processor or the TMP reaching its memory threshold. Effect.
Message Descriptions TMFCOM Messages 514 The command specified an erroneous TMPMEMTHRESH value. Cause. An ALTER BEGINTRANS command specified one or more invalid values in the TMPMEMTHRESH parameter. Effect. The command fails. Recovery. Re-enter the command, specifying valid values for TMPMEMTHRESH. 515 The command specified an erroneous TRANSPERCPU value. Cause. An ALTER BEGINTRANS command specified one or more invalid values in the TRANSPERCPU parameter. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 521 TMF was unable to delete the catalog because of File System error fserrcode. fserrcode is the File System error number. Cause. A DELETE CATALOG command attempted to remove the TMF catalog, but the condition indicated by fserrcode occurred during the delete operation. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 604 No volumes matched volume. volume is the volume name. Cause. The command referred to a volume that TMF could not locate. Effect. None. Recovery. Informative message only; no corrective action is needed. 605 No files matched filename. filename is the file name. Cause. The command referred to a file that TMF could not locate. Effect. None. Recovery. Informative message only; no corrective action is needed.
Message Descriptions TMFCOM Messages 607 volume -- deleted (but could not clear configuration information). volume is the volume name. Cause. A DELETE DATAVOLS command deleted the data volume from the TMF configuration but could not remove the related information from the volume label. Perhaps the files were inconsistent when the volume was deleted. Effect. The configuration information remains in the volume label. Recovery.
Message Descriptions TMFCOM Messages 950 Subsystem Error: The TMFSERVE process encountered an internal error. Please report errcode to the Global Customer Support Center (GCSC) or your service provider. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause. A TMF error occurred. Effect. The command fails.
Message Descriptions TMFCOM Messages 952 Guardian error fserrcode was received while communicating with the EMSDIST process process-name. fserrcode supplies a numeric code that further defines the File System error. process-name is the name of the EMS distributor process. Cause. An error occurred as a result of communication with the named EMSDIST process. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the error code.
Message Descriptions TMFCOM Messages 955 EMS distributor process distributor-process-name reported that File System error fserrcode was returned from the procedure-name File System procedure while attempting to access collector process collector-process-name. distributor-process-name is the name of the EMS distributor process. fserrcode supplies a numeric code that further defines the File System error. procedure-name is the name of the File System procedure.
Message Descriptions TMFCOM Messages 956 EMS distributor process process-name reported that File System error fserrcode was returned from the procedure-name procedure while attempting to access log file filename. process-name is the name of the EMS distributor process. fserrcode supplies a numeric code that further defines the File System error. procedure name is the name of the File System procedure. filename is the name of the log file. Cause.
Message Descriptions TMFCOM Messages 957 EMS distributor process process-name reported that File System error fserrcode was returned from the procedure-name File System procedure while attempting to load filter file file-name. process-name is the name of the EMS distributor process. fserrcode supplies a numeric code that defines the File System error. procedure-name is the name of the File System procedure (either OPEN or READ) that detected the error. file-name is the name of the filter file. Cause.
Message Descriptions TMFCOM Messages 959 EMS distributor process process-name reported event filter error errcode from filter name filter-name while processing log file file-name. process-name is the name of the EMS distributor process. errcode supplies a numeric code that defines the error. filter-name is the name of the filter. file-name is the name of the log file. Cause. A TMF error occurred. Effect. The command fails. Recovery. This message should never appear.
Message Descriptions TMFCOM Messages 961 EMS distributor process process-name reported the collector’s log file file-name had a reason-text error. process-name is the name of the EMS distributor process. file-name is the name of the log file. reason-text describes the reason for the error. Cause. A TMF error occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider.
Message Descriptions TMFCOM Messages 963 The next log file was unavailable or inaccessible because of a reason-text error. The last logfile accessed was filename. reason-text describes the reason for the error. file-name is the name of the log file. Cause. A TMF error occurred. Effect. The command fails if this message is not listed as a warning. Recovery. This message appeared because the log file was unavailable for the reason specified.
Message Descriptions TMFCOM Messages 965 The RECOVER FILES command specified the RECOVERVDPPHASE1 option, which also requires a valid TOPHYSVOL option. Cause. A RECOVER FILES command specified the RECOVERVDPPHASE1 option, but omitted the TOPHYSVOL option that is also required. Effect. The command fails. Recovery. Re-enter the command, specifying both the RECOVERVDPPHASE1 and TOPHYSVOL options. 966 The DELETE TMF command was encountered in a command file or in the command line.
Message Descriptions TMFCOM Messages 1002 Subsystem Error: Guardian error errcode was received while communicating with the TMFSERVE process. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer. Cause. A TMF error occurred. Effect. The command fails. Recovery. This message should never appear.
Message Descriptions TMFCOM Messages 1005 Subsystem Error: TMFSERVE. Unable to create a process name for Cause. A TMF error occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider. 1006 Subsystem Error: Unable to OPEN the TMFSERVE process because of error errcode from OPEN of process process-name.
Message Descriptions TMFCOM Messages 1007 Subsystem Error: Unable to WRITEREAD a startup message to the TMFSERVE process process-name because of error errcode from WRITEREAD. process-name is the name of the process that could not receive the startup message. errcode supplies a numeric code that further defines the error and identifies the subsystem or system procedure that transmitted this code: TMF, the File System, the NEWPROCESS process-control procedure, or the Enform query language and report writer.
Message Descriptions TMFCOM Messages 1012 Subsystem Error: To communicate with a process on another system, the HOMETERM of this TMFCOM process must be expressible in network format (7 or fewer characters including the dollar sign). The HOMETERM name is term-name. term-name is the home terminal name. Cause. A Subsystem Programmatic Interface (SPI) violation occurred. Effect. The command fails. Recovery. This message should never appear.
Message Descriptions TMFCOM Messages 1015 Subsystem Error: An error was encountered while converting a timestamp. Error errcode was returned from the Guardian CONVERTTIMESTAMP procedure. errcode supplies a numeric code that further defines the error and identifies the system procedure that transmitted this code as CONVERTTIMESTAMP. Cause. A Subsystem Programmatic Interface (SPI) violation occurred. Effect. The command fails. Recovery. This message should never appear.
Message Descriptions TMFCOM Messages 1018 The RECOVER FILES command specified the RECOVERVDPPHASE1 option with the MAP NAMES option. These are mutually exclusive. Cause. A RECOVER FILES command included both the RECOVERVDPPHASE1 and MAP NAMES options. However, you can enter only one of these in any single command. Effect. The command fails. Recovery. Re-enter the RECOVER FILES command, specifying either RECOVERVDPPHASE1 or MAP NAMES, but not both.
Message Descriptions TMFCOM Messages 2000 Exceeded maximum OBEY depth of 4. Cause. A TMFCOM or OBEY command referred to a command file that itself contained one or more OBEY commands nested more than four levels. (When a command file includes an OBEY command, and that OBEY command refers to another command file that also includes an OBEY command, two levels of nesting exist; this chain can only be continued to a total of four levels.) Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 2101 History Error: An attempt to add an empty command line to the history buffer. Contact the Global Customer Support Center (GCSC) or your support representative. Cause. A TMF error occurred. Effect. The command fails. Recovery. This error should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider. 2103 Expecting RESET. Cause.
Message Descriptions TMFCOM Messages 2108 Line Number not in the history buffer. Cause. An FC, ?, or ! command specified a line number that could not be found in the history buffer to identify a command on which to operate. Effect. The command fails. Recovery. Check the syntax rules for the command description. Then re-enter the FC, ?, or ! command with a different line number or other appropriate command line identifier.
Message Descriptions TMFCOM Messages 2202 File system error fserrcode occurred on the I/O. fserrcode supplies a numeric code that further defines the error and identifies the subsystem that transmitted this code as the File System. Cause. A File System error occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the information supplied in fserrcode. Then, contact the GCSC or your service provider. 2205 Unable to create a process name.
Message Descriptions TMFCOM Messages 2207 File System error fserrcode occurred on the WRITEREAD. fserrcode supplies a numeric code that further defines the error and identifies the subsystem that transmitted this code as the File System. Cause. A File System error occurred. Effect. The command fails. Recovery. Correct the File System error, and retry the command just entered. 2208 text text text that explains an error that occurred while trying to start the TMFSERVE process. Cause. A TMF error occurred.
Message Descriptions TMFCOM Messages 2217 The specified server already exists and cannot be altered. Cause. A Subsystem Programmatic Interface (SPI) violation occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered and the circumstances. Then, contact the GCSC or your service provider. 2992 No help for specified text. Cause. The HELP command specified a command name or object for which no online help exists. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7000 Expecting a number. Cause. The command did not specify a numeric value where TMFCOM expected one. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it correctly. 7004 Unknown system. Cause. The command referenced a system (node) that was not configured in the network. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7007 Expecting FILESIZE in the range 1-2047. Cause. An ADD AUDITTRAIL or ALTER AUDITTRAIL command did not specify a valid file size in the FILESIZE option. An audit trail’s file size must be from 1 through 2047, inclusive. Effect. The command fails. Recovery. Re-enter the command, using a file size from 1 through 2047. 7008 Expecting FILESPERVOLUME in the range 1-100. Cause.
Message Descriptions TMFCOM Messages 7011 Expecting CPU number in the range 0-15. Cause. An ALTER PROCESS command did not specify a valid value in the CPU option, perhaps using a number greater than 15 or a negative value for a processor number. This value must be an integer from 0 through 15, inclusive. Effect. The command fails. Recovery. Re-enter the command, using an integer from 0 through 15 for the processor number. 7012 Expecting PFSSIZE in the range 131,072 - 1,048,576. Cause.
Message Descriptions TMFCOM Messages 7014 Expecting audit trail sequence number between 1 and 999999. Cause. A RECOVER FILES command did not specify a valid audit-trail sequence number in the TOMATPOSITION parameter. This sequence number must be the numeric portion of the MAT file name, with leading zeros optional, ranging from 1 through 999999. Effect. The command fails. Recovery. Re-enter the command, using a valid audit trail sequence number.
Message Descriptions TMFCOM Messages 7018 Expecting DENSITY value of 0, 1600, or 6250. Cause. An ADD TAPEMEDIA or SET TAPEMEDIA command did not specify a valid value in the DENSITY option. This value must be 0, 1600, or 6250. Effect. The command fails. Recovery. Re-enter the command, specifying a valid density. 7019 Expecting one of 0, 1600, or 6250. Cause. The command did not specify 0, 1600, or 6250 where TMFCOM expected one of these values. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7022 Expecting ASSIGNED, BAD, RELEASED, or SCRATCH. Cause. An ADD TAPEMEDIA, ALTER TAPEMEDIA, INFO TAPEMEDIA, or SET TAPEMEDIA command did not specify a correct tape status where TMFCOM expected one of the following: ASSIGNED, BAD, RELEASED, or SCRATCH. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it correctly. 7023 Expecting TAPEMEDIA part number; value must be greater than zero. Cause.
Message Descriptions TMFCOM Messages 7026 Missing parameter. Cause. The command omitted one or more required parameter strings. Effect. The command fails. Recovery. Check the syntax rules for the command. Then, re-enter the command, specifying all required strings. 7027 Expecting a quoted string. Cause. The command did not specify a quoted string where TMFCOM expected one. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it correctly. 7028 Keyword too long. Cause.
Message Descriptions TMFCOM Messages 7030 Command line too long. Cause. The command exceeded the number of characters permitted in the command line. Effect. The command fails. Recovery. Re-enter the command, using the continuation indicator (&) to allow the command to span multiple entry lines. 7031 Expecting semicolon or return. Cause. The command did not include a delimiting semicolon or terminating return where TMFCOM expected one. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7034 Illegal process name. Cause. The command specified an illegal process name. Effect. The command fails. Recovery. Check the syntax rules for the command. Then, re-enter the command, specifying an appropriate process name. 7035 Illegal DISKMEDIA name. Cause. The command specified an illegal name in the DISKMEDIA parameter. Effect. The command fails. Recovery. Check the syntax rules for the command.
Message Descriptions TMFCOM Messages 7038 Expecting comma or return. Cause. The command did not include a delimiting comma or terminating return where TMFCOM expected one. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7039 Expecting comma or ")". Cause. The command did not include a required delimiting comma or terminating (closing) parenthesis where TMFCOM expected one. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7042 Expecting one of CPU, PRI, SWAP, or TERM. options are validated but are not used. The SWAP and TERM Cause. The command specified an unrecognizable optional parameter, for example a misspelled or erroneous keyword. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly.
Message Descriptions TMFCOM Messages 7046 Expecting a valid file name. Cause. The command did not specify a valid file name where TMFCOM expected one. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7047 Expecting a valid file name set. Cause. The command did not specify a valid file-set where TMFCOM expected one. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7048 Expecting SERVER. Cause.
Message Descriptions TMFCOM Messages 7050 Expecting AUDITTRAIL, DATAVOL[S], DUMPS, RESOURCEMANAGER, RM, or TAPEMEDIA. Cause. An ADD command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7052 Expecting AUDITDUMP, AUDITTRAIL, BEGINTRANS, CATALOG, DATAVOL[S], DUMPS, PROCESS, TAPEMEDIA, or TMF. Cause.
Message Descriptions TMFCOM Messages 7056 Expecting AUDITDUMP, BEGINTRANS, or DATAVOL[S]. Cause. A DISABLE command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7058 Expecting OPERATION[S]. Cause. A DISPLAY command omitted the required OPERATION or OPERATIONS keyword. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7062 Expecting AUDITDUMP, AUDITTRAIL, BEGINTRANS, CATALOG, DATAVOL[S], DUMPS, RESOURCEMANAGER, RM, PROCESS, TAPEMEDIA, or TMF. Cause. An INFO command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7064 Expecting AUDITTRAIL. Cause. A NEXT command omitted the required AUDITTRAIL keyword. Effect. The command fails.
Message Descriptions TMFCOM Messages 7067 Expecting AUDITTRAIL, DATAVOL[S], DUMPS, or TAPEMEDIA. Cause. A RESET command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7068 Expecting TRANSACTION. Cause. A RESOLVE command omitted the required TRANSACTION keyword. Effect. The command fails. Recovery. Re-enter the command, including the TRANSACTION keyword.
Message Descriptions TMFCOM Messages 7071 Expecting TMF. Cause. A START command omitted the required TMF keyword. Effect. The command fails. Recovery. Re-enter the command, including the TMF keyword. 7072 Expecting AUDITDUMP, AUDITTRAIL, BEGINTRANS, CATALOG, DATAVOL[S], OPERATIONS[S], SERVER, TMF, or TRANS[ACTION[S]]. Cause. A STATUS command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7076 Expecting ONLINE or ARCHIVE. Cause. An ADD DATAVOLS or SET DATAVOLS command did not specify the correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7077 Expecting DISKMEDIA, TAPEMEDIA, SERIAL, TYPE, or "*". Cause.
Message Descriptions TMFCOM Messages 7080 Expecting STATUS or OBEYFORM. Cause. An INFO DUMPS command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7081 Expecting AUDITDUMP or ONLINEDUMP. Cause. An ADD DUMPS command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7084 Expecting only one DISKMEDIA disk. Cause. The command specified multiple disk volumes in the DISKMEDIA option, but only one disk volume is allowed. Effect. The command fails. Recovery. Re-enter the command, specifying only a single disk volume. 7085 Cannot specify both DISKMEDIA and TAPEMEDIA in a single command. Cause. The command specified both the DISKMEDIA and TAPEMEDIA options, but only one of these is allowed. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7088 Expecting TMF. Cause. A START or STOP command did not include the TMF object keyword. Effect. The command fails. Recovery. Re-enter the command with the TMF keyword. 7092 Expecting OBEYFORM. Cause. An INFO command did not specify OBEYFORM where TMFCOM expected this keyword. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7093 Expecting PROCESS. Cause.
Message Descriptions TMFCOM Messages 7096 Expecting one of CPUS, PRI, MAKESAVEABEND, DEBUG, INSPECT, PROGRAMFILE, TERM, EXTENDEDSEGSIZE, PFSSIZE, or RESET. Cause. An ALTER PROCESS command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7097 Expecting one of CPUS, PRI, PROGRAMFILE, TERM, EXTENDEDSEGSIZE, PFSSIZE, or SWAP. Cause.
Message Descriptions TMFCOM Messages 7100 Expecting a CPU number. Cause. An ALTER PROCESS command specified the CPUS option, but no processor number was present. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7101 Expecting a valid device name. Cause. The command did not specify a valid device name where TMFCOM expected one. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly.
Message Descriptions TMFCOM Messages 7104 Expecting a single TMF transaction identifier without "(..)". Cause. The command specified a single transaction identifier but enclosed it within parentheses. (Use parentheses only when specifying multiple identifiers.) Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7105 Expecting AVOIDHANGING or IGNOREDATAERRORS. Cause.
Message Descriptions TMFCOM Messages 7108 Expecting ONLINE or ARCHIVE. Cause. The command did not specify either ONLINE or ARCHIVE where TMFCOM expected one of these keywords. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7109 Expecting a valid BLOCKSIZE value. Must be one of 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, or 52. Cause. The command specified a BLOCKSIZE value that was not a multiple of 4 and within the range 4 through 52. Effect.
Message Descriptions TMFCOM Messages 7112 Expecting "(". Cause. An ALTER PROCESS command was entered with the CPUS option, but the cpu-list did not include a leading left-parenthesis. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it with the required left-parenthesis. 7113 Expecting ")". Cause. An ALTER PROCESS command was entered with the CPUS option, but the cpu-list did not include a trailing right-parenthesis. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7116 More than 16 volume names in list. Cause. The command included a DISKMEDIA parameter that specified more than 16 disk volumes. Effect. The command fails. Recovery. Check the syntax rules for the command. Then, re-enter the command, specifying 16 or fewer volume names. 7117 Unable to use an 8-character volume name as the default. Cause. A VOLUME command specified a disk volume on a node other than the local node. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7119 Expecting EXTENDEDSEGSIZE integer2 value between 1 and 128. The minimum value for integer2 depends on the process type and software release. Cause. An ALTER PROCESS command specified an integer2 value for the EXTENDEDSEGIZE parameter that was outside the range allowed for the process. In general, TMFCOM accepts values between 1 and 128, but the minimum value actually allowed in specific cases depends on the process type and software release. Effect.
Message Descriptions TMFCOM Messages 7122 Illegal file name. Cause. The command contained an invalid file name−perhaps one that contained improper characters or was too long. Effect. The command fails. Recovery. Verify that the file name complies with the syntax rules listed in File Names and Process Identifiers on page 3-6. Then, re-enter the command with a correct file name. 7123 Unable to open OUT file. Cause. The command contained an OUT option that specified an invalid file name.
Message Descriptions TMFCOM Messages 7125 First character must be alphabetic. Cause. The command contained a subvolume name or file identifier that did not begin with a letter. Effect. The command fails. Recovery. Verify that the subvolume name or file identifier complies with the syntax rules listed in File Names and Process Identifiers on page 3-6. Then, re-enter the command, ensuring that the subvolume name or file identifier begins with a letter. 7126 Comment exceeds maximum length. Cause.
Message Descriptions TMFCOM Messages 7129 Wild-card characters not allowed. Cause. The command included a parameter that contained wild-card characters, but such characters are prohibited for this parameter. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it correctly. 7130 The filename must be restricted. [[{volume|*}.]{subvolume|*}.]{file-id|*} Cause.
Message Descriptions TMFCOM Messages 7134 Expecting a quote. Cause. The command did not specify a quotation mark (“) where TMFCOM expected one. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7135 No concatenated commands are allowed after ?, !, or FC. Cause. In a command line containing multiple commands, a command followed the ?, !, or FC command. (Although other commands permit this, ?, !, and FC do not.) Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7138 Illegal default volume specified. Cause. A VOLUME command specified an illegal default volume name. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7140 Expecting a "/". Cause. The command did not specify a slash (/) character where TMFCOM expected one. Effect. The command fails. Recovery. Check the syntax rules for the command.
Message Descriptions TMFCOM Messages 7145 Expecting a period. Cause. The command did not specify a delimiting period where TMFCOM expected one. Such periods are used, for example, as delimiters in qualified file names. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter the command accordingly. 7151 Invalid TMF transaction identifier. Cause. The command contained a TMF transaction identifier that was not valid. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7154 Invalid day. Must be 01 - 31. Cause. The TIME option of an ADD DUMPS or RECOVER FILES command, or the BEGINTIME option of a DISPLAY OPERATIONS or STATUS OPERATIONS command, did not specify the day as a two-digit integer ranging from 01 through 31. Effect. The command fails. Recovery. Re-enter the command, specifying a valid day. 7155 Invalid date-time field.
Message Descriptions TMFCOM Messages 7157 The day number is not valid for the month entered. Cause. The TIME option of an ADD DUMPS or RECOVER FILES command, or the BEGINTIME option of a DISPLAY OPERATIONS or STATUS OPERATIONS command, specified an invalid day for the month entered--for example, JUN 31 or SEP 31. Effect. The command fails. Recovery. Re-enter the command, specifying a valid day of the month. 7158 Invalid Hour entered. Must be 00 - 23. Cause.
Message Descriptions TMFCOM Messages 7160 Invalid Second entered. Must be 00 - 59. Cause. The TIME option of an ADD DUMPS or RECOVER FILES command, or the BEGINTIME option of a DISPLAY OPERATIONS or STATUS OPERATIONS command, did not specify the second value as a two-digit integer ranging from 00 through 59. Effect. The command fails. Recovery. Re-enter the command, specifying a valid second. 7161 Expecting GMT. Cause.
Message Descriptions TMFCOM Messages 7164 Expecting TAPE or DISK. Cause. The command did not specify either TAPE or DISK where TMFCOM expected one of these keywords. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7165 More than two SYSTEM names were entered. Cause. The command specified more than two system (node) names, but only two are allowed. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7168 Expecting BEGINTRANSDISABLE, FILESPERVOLUME, or OVERFLOWTHRESHHOLD. Cause. A RESET AUDITTRAIL command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7169 Illegal COPIES. Must be 1, 2, or 3. Cause. The command specified an invalid number of dump copies in the COPIES parameter.
Message Descriptions TMFCOM Messages 7172 Expecting AUTOABORT, BRANCHESPERRM, RECRMCOUNT, RESET, RMOPENPERCPU, TMFLIBMEMTHRESH, TMPMEMTHRESH, TRANSCOUNTTHRESH, or TRANSPERCPU. Cause. An ALTER BEGINTRANS command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly.
Message Descriptions TMFCOM Messages 7176 Invalid AUTOABORT MINUTE value. 357913. Must be between 1 and Cause. The AUTOABORT option of an ALTER BEGINTRANS command did not specify the MINUTE value as an integer ranging from 1 through 357913. Effect. The command fails. Recovery. Re-enter the command, specifying a valid minute value. 7177 Invalid AUTOABORT SECOND value. 21474836. Must be between 20 and Cause.
Message Descriptions TMFCOM Messages 7180 Invalid RMOPENPERCPU value. Must be between 16 and 1024. Cause. An ALTER BEGINTRANS command specified a RMOPENPERCPU value that was outside the range 16 through 1024. Effect. The command fails. Recovery. Re-enter the command, specifying a valid RMOPENPERCPU value. 7181 Incorrect threshold values. The values must be between 1 and 100, and value1 must be less than value2. Cause.
Message Descriptions TMFCOM Messages 7183 Incorrect TRANSPERCPU values. and 1073741824. The values must be between 1 Cause. An ALTER BEGINTRANS command specified one or more incorrect values in the TRANSPERCPU parameter. Each of the values must be in the range from 1 to 1073741824. Effect. The command fails. Recovery. Re-enter the command, specifying correct TRANSPERCPU values. 7184 Expecting RELEASED, RESET, or RETAINDEPTH. Cause.
Message Descriptions TMFCOM Messages 7187 Expecting INVALID, RELEASED, or SERIAL. Cause. An ALTER DUMPS command did not specify the correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7188 Expecting a dump file name. Cause. An ALTER DUMPS command did not specify a dump file name. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7191 Expecting TMP. Cause. The command did not specify TMP where TMFCOM expected this keyword. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7192 Expecting an operation number. Cause. A CANCEL OPERATIONS or DISPLAY OPERATIONS command did not specify an operation number. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly.
Message Descriptions TMFCOM Messages 7195 Invalid operation number. Must be between 1 and 100. Cause. A CANCEL OPERATIONS, DISPLAY OPERATIONS, or STATUS OPERATIONS command specified an operation number that did not fall within the range from 1 through 100. Effect. The command fails. Recovery. Re-enter the command, specifying an operation number in the correct range. 7196 Expecting ALLOWINCONSISTENCY. Cause. A DELETE DATAVOLS command did not specify ALLOWINCONSISTENCY where TMFCOM expected this keyword.
Message Descriptions TMFCOM Messages 7199 A wild-card value "*" is not valid in this context. Cause. This command does not allow the wild-card character (*) in the location entered. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7200 A NOT volume list is only valid with a wild-card "*" volume name. Cause. This command only allows the wild-card character (*) as a volume name in the NOT fileset parameter list. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7203 A wild-card resource manager name "*" must be entered only once and it must be the only resource manager name. Cause. The command specified the wild-card character (*) as a resource manager name multiple times, or along with other resource manager names. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7204 A wild-card resource manager name value "*" is not valid for this command. Cause.
Message Descriptions TMFCOM Messages 7206 Invalid resource manager name. Must be 1 to 128 characters long, start with an alphabetic character, and contain alphanumeric or the following characters $, _, -,^, @, &. Cause. An ADD RESOURCEMANGER, CLOSE RESOURCEMANGER, DELETE RESOURCEMANGER, INFO RESOURCEMANGER, or STATUS RESOURCEMANGER command specified an invalid resource manager name. Effect. The command fails. Recovery. Check the syntax rules for the command.
Message Descriptions TMFCOM Messages 7210 Invalid or non-existent group-name.user-name. Cause. The command did not specify a valid group name or user name. Effect. The command fails. Recovery. Check the syntax rules for the command. Then, re-enter the command, specifying a valid name. 7211 Expecting a CPU,PIN. Cause. A STATUS RESOURCEMANAGER or STATUS TRANSACTIONS command did not specify a cpu,pin value where TMFCOM expected one. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7214 Expecting only a process name. Cause. A STATUS RESOURCEMANAGER or STATUS TRANSACTIONS command specified values in addition to the process identifier in the PROCESS parameter. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7215 Invalid process name. Cause. A STATUS RESOURCEMANAGER or STATUS TRANSACTIONS command did not specify a valid process identifier. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7218 Expecting one of BRIEF, DETAIL, MEDIUM, OBEYFORM, SERIAL, SORT, STATUS, or TYPE. Cause. An INFO DUMPS command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7219 Expecting TAPE or DISK. Cause. An INFO DUMPS command did not specify either TAPE or DISK where TMFCOM expected one of these keywords. Effect.
Message Descriptions TMFCOM Messages 7222 Expecting AUDITDUMP or ONLINEDUMP. Cause. An INFO DUMPS command did not specify AUDITDUMP or ONLINEDUMP where TMFCOM expected one of these keywords. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7223 Expecting only one item of this type in this context. of multiple items are not allowed. Lists Cause. The command specified multiple items where TMFCOM expected only one item. Effect. The command fails.
Message Descriptions TMFCOM Messages 7226 Expecting PARALLEL. Cause. A DUMP FILES command did not specify PARALLEL where TMFCOM expected this keyword. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7227 Expecting BLOCKSIZE, COPIES, DISKMEDIA, NOT, START, SYSTEM, TAPEMEDIA, UNLOAD, or VERIFYTAPE. Cause. A DUMP FILES command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails.
Message Descriptions TMFCOM Messages 7230 Expecting both OLDDMLOC or NEWDMLOC disk media locations. Cause. A RELOCATE DUMPS command did not specify both OLDDMLOC and NEWDMLOC where TMFCOM expected these keywords. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7231 Expecting a diskmedia location. Cause. A RELOCATE DUMPS command omitted the disk media location in either or both of the OLDDMLOC or NEWDMLOC parameters. Effect. The command fails.
Message Descriptions TMFCOM Messages 7234 Expecting NOWAIT or ABRUPT. Cause. A STOP TMF command did not specify either NOWAIT or ABRUPT where TMFCOM expected one of these keywords. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7235 Expecting BEGINTRANS. Cause. A START TMF command did not specify BEGINTRANS where TMFCOM expected this keyword. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly.
Message Descriptions TMFCOM Messages 7238 Expecting AUDITTRAIL, RECOVERYMODE, SORT, or STATE. Cause. A STATUS DATAVOLS command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it correctly. 7239 Expecting BEGINTIME, SORT, STATE, or TYPE. Cause. A STATUS OPERATIONS command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect.
Message Descriptions TMFCOM Messages 7242 Expecting ACTIVE, ABORTING, ABORTED, COMMITTED, ENDING, HUNG, or PREPARED. Cause. A STATUS TRANSACTIONS command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it correctly. 7243 Expecting PROCESS, STATE, DETAIL, or BRIEF. Cause.
Message Descriptions TMFCOM Messages 7246 PROCESS_CREATE_ error error, error-detail on file programfile-name occurred while attempting to create an EMS Distributor process. At this time, you can correct the problem and THEN respond to the following query to retry or cancel the operation. error is the error code returned by the PROCESS_CREATE_ procedure. error-detail is the error-detail code returned by the PROCESS_CREATE_ procedure, and further defines the error that occurred.
Message Descriptions TMFCOM Messages 7247 File System Error - fserrcode occurred when attempting to issue a WRITEREAD request to the EMS Distributor processname. At this time, you can correct the problem and THEN respond to the following query to retry or cancel the operation. fserrcode supplies a numeric code that further defines the error and identifies the subsystem that transmitted this code as the File System. process-name is the name of the distributor process. Cause. A File System error occurred.
Message Descriptions TMFCOM Messages 7249 In this context, the filename cannot contain a system name. Cause. The command specified a filename that included a system (node) name, but node names are prohibited. Effect. The command fails. Recovery. Re-enter the command, specifying the file name without the node name. 7250 Cannot use both TAPEMEDIA and DISKMEDIA in the same command. Cause. An ADD DUMPS command specified both TAPEMEDIA and DISKMEDIA, but only one of these options is permitted. Effect.
Message Descriptions TMFCOM Messages 7253 The filename contains a component (volume, subvolume, or filename) that contains more than 8 characters, including wild-card characters. Cause. The command specified a volume, subvolume, or file identifier that was too long. Effect. The command fails. Recovery. Re-enter the command with filename components of 8 characters or less. 7254 The HELP request contains more than 31 non-blank characters. Cause. A HELP command exceeded 31 characters (excluding spaces).
Message Descriptions TMFCOM Messages 7257 MEDIUM, STATUS, NOT, and START are not allowed with OBEYFORM. Cause. The INFO DUMPS command specified an improper keyword with the OBEYFORM parameter; MEDIUM, STATUS, NOT and START are not allowed with OBEYFORM. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7258 OBEYFORM requires a single file-set of "*.*.*". Cause. The INFO DUMPS command specified multiple *.*.
Message Descriptions TMFCOM Messages 7260 The currently opened TMFSERVE process does not support the START, NOT, CATALOG, or multiple file-sets in the RECOVER FILES or INFO DUMPS command. Requires TMFSERVE version G07AEN or later. Cause. The current TMFCOM session is directing its commands to an older version of TMFSERVE in which the START, NOT, and CATALOG options as well as multiple fileset specifications are not available in the RECOVER FILES command. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7265 Expecting RECOVERYMODE. Cause. An ALTER DATAVOLS command did not specify RECOVERYMODE where TMFCOM expected this keyword. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7266 Expecting AUDITTRAIL or RECOVERYMODE. Cause. A SET DATAVOLS command did not specify either AUDITRAIL or RECOVERYMODE where TMFCOM expected one of these keywords. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7269 Expecting DENSITY, DRIVE, LABEL, STATUS, or UNLOAD. Cause. A SET TAPEMEDIA command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command and re-enter it accordingly. 7270 Expecting a START filename with format [[$volume.]subvol.]{file-id|*} or [volume.]*.*. Cause.
Message Descriptions TMFCOM Messages 7273 The "/OUT..." option is not allowed in an OBEY command. Cause. An OBEY command specified the OUT option, directing output to an alternate output device. For the OBEY command, this option is illegal. Effect. The command fails. Recovery. Re-enter the command without the OUT option. 7274 The required LABEL value is not specified in the command and has not been set by a SET TAPEMEDIA LABEL...command Cause.
Message Descriptions TMFCOM Messages 7277 Expecting MAXRETAINEDATFILES in the range 1-9999. Cause. An ALTER AUDITTRAIL command specified a MAXRETAINEDATFILES integer value outside the proper range. Effect. The command fails. Recovery. Re-enter the command, with a MAXRETAINEDATFILES integer value from 1 through 9999. 7278 The currently opened TMFSERVE process does not support MAXRETAINEDATFILES in ALTER AUDITTRAIL, MAP NAMES and SERIAL in RECOVER FILES, or ROUNDROBIN in ALTER CATALOG.
Message Descriptions TMFCOM Messages 7280 Expecting BEGINTRANSDISABLE, FILESPERVOLUME, OVERFLOWTHRESHOLD, or MAXRETAINEDATFILES. Cause. An ALTER AUDITTRAIL command with a RESET option, or a RESET AUDITTRAIL command, did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command, then re-enter it. 7281 Expecting RELEASED, RESET, RETAINDEPTH, or ROUNDROBIN. Cause.
Message Descriptions TMFCOM Messages 7284 Invalid MAP NAMES, NAMES expected. Cause. A RECOVER FILES command did not specify the NAMES keyword where TMFCOM expected it in the MAP NAMES option. Effect. The command fails. Recovery. Check the syntax rules for the command, then re-enter it. 7285 INVALID MAP NAMES, TO expected. Cause. A RECOVER FILES command did not specify the TO keyword where TMFCOM expected it in the MAP NAMES option. Effect. The command fails. Recovery.
Message Descriptions TMFCOM Messages 7288 Invalid MAP NAMES, comma or right parenthesis missing. Cause. A RECOVER FILES command omitted a comma or right-parenthesis where TMFCOM expected one in the MAP NAMES option. Effect. The command fails. Recovery. Check the syntax rules for the command, then re-enter it. 7289 Unexpected error returned by FileNameMap^Scan. Cause. A TMF error occurred. Effect. The command fails. Recovery. This message should never appear. Make a note of the command entered.
Message Descriptions TMFCOM Messages 7292 Expecting NOT, FROMARCHIVE, NOWAIT, TOFIRSTPURGE, TOMATPOSITION, SYSTEM, TIME, UNLOAD, TOPHYSVOL, WHEREPHYSVOLIS, RECOVERVDPPHASE1, SERIAL, or MAP NAMES. Cause. A RECOVER FILES command did not specify a correct keyword where TMFCOM expected one of those listed in the message. Effect. The command fails. Recovery. Check the syntax rules for the command, then re-enter it.
Message Descriptions TMFCOM Messages HP NonStop TMF Reference Manual—522418-002 A-234
B TMFCOM Command Reference Summary This appendix presents syntax descriptions for the individual TMFCOM commands, listed in alphabetical order.
ABORT TRANSACTION TMFCOM Command Reference Summary ABORT TRANSACTION Backs out (cancels) the effects of an active transaction, or re-attempts to back out an aborting or hung transaction, and releases the locks held by that transaction. Security: super user group member. ABORT TRANS[ACTION[S]] {transaction-id } {(transaction-id [,transaction-id]...)} [,IGNOREDATAERRORS | ,AVOIDHANGING] transaction-id: [node. [node-number. [node(tm-flags). [node-number(tm-flags). [(tm-flags). ] ] ] cpu.
ADD AUDITTRAIL TMFCOM Command Reference Summary ADD AUDITTRAIL Adds an audit trail to the TMF configuration. Security: super user group member. ADD AUDITTRAIL {MASTER | MAT {AUX[ILIARY]nn } } [,AUDITDUMP {ON | OFF }] [,FILESIZE integer ] [,ACTIVEVOL[S] {volume {(volume [,volume]...) [,FILESPERVOLUME integer } }] ] [,OVERFLOWVOL[S] {volume } {(volume [,volume]...)}] [,OVERFLOWTHRESHOLD integer [,RESTOREVOL[S] ] {volume } {(volume [,volume]...
TMFCOM Command Reference Summary ADD DUMPS ADD DUMPS Adds dump entries to the TMF catalog, as when reentering online and audit dump entries accidentally deleted from the catalog or recovering a destroyed catalog. There are two forms of the ADD DUMPS command: one for adding an audit dump entry to the catalog, and another for adding one or more online dump entries to the catalog. Security: super user group member.
TMFCOM Command Reference Summary Adding Online Dump File Names to the Catalog Adding Online Dump File Names to the Catalog To add one or more online dump entries to the catalog, use the following syntax: ADD DUMPS {online-dump-file } {(online-dump-file [,online-dump-file]...)} ,SERIAL serial-number ,TYPE ONLINEDUMP (master, data) {,DISKMEDIA {disk } {(disk [,disk]...)}} {,TAPEMEDIA {tape } {(tape [,tape]...
ADD RESOURCEMANAGER TMFCOM Command Reference Summary ADD RESOURCEMANAGER Adds one or more recoverable resource managers to the resource manager directory. Security: super user group member. ADD {RESOURCEMANAGER | RM} {rm-name } {(rm-name [,rm-name]...)} ,OWNER {username | userid} username: group-name.user-name userid: (group-id,user-id) ADD TAPEMEDIA Adds one or more tape volumes to the TMF catalog and, optionally, labels these volumes. Security: super user group member.
ALTER AUDITDUMP TMFCOM Command Reference Summary ALTER AUDITDUMP Changes the configured attribute values of an audit dump process. Security: super user group member.
ALTER AUDITTRAIL TMFCOM Command Reference Summary ALTER AUDITTRAIL Changes the configured attribute values of an audit trail and can execute while TMF is running. Security: super user group member. ALTER AUDITTRAIL {MASTER | MAT } {AUX[ILIARY]nn} [,AUDITDUMP {ON | OFF}] [,ADDACTIVEVOL[S] {volume {(volume [,volume]...) [,DELETEACTIVEVOL[S] {volume {(volume [,volume]...) } }] } }] [,FILESPERVOLUME integer] [,RESET FILESPERVOLUME ] [,ADDOVERFLOWVOL[S] {volume } {(volume [,volume]...
TMFCOM Command Reference Summary ALTER AUDITTRAIL Caution. Before you decrease the size of an audit trail, determine whether such a change might interrupt transaction processing. TMF does not alert you to the possibility that the audit trail could exceed its begin-transaction-disable threshold when you issue an ALTER AUDITTRAIL command to decrease the files per active volume or delete an active volume from the configuration.
ALTER BEGINTRANS TMFCOM Command Reference Summary ALTER BEGINTRANS Changes various options related to the automatic disabling and reenabling of transaction processing, control of the TMF autoabort feature, and limits on resource managers and transaction branches used in heterogeneous transaction processing. Security: super user group member.
TMFCOM Command Reference Summary ALTER CATALOG ALTER CATALOG Changes the configured attribute values of the catalog process that affect the management of online and audit dumps. Security: super user group member. ALTER CATALOG, attribute [,attribute] attribute: [RELEASED {OFF | ON}] [RETAINDEPTH integer] [RESET RETAINDEPTH ] [ROUNDROBIN {OFF | ON}] ALTER DATAVOLS Changes the configured attribute values of a data volume. Security: super user group member. ALTER DATAVOL[S] {volume } {(volume [,volume]...
ALTER DUMPS TMFCOM Command Reference Summary ALTER DUMPS Changes dump entries in the TMF catalog. Security: super user group member. ALTER DUMPS {file-set } {(file-set [,file-set]...)} [,INVALID {OFF | ON} ] [,RELEASED {OFF | ON} ] [,SERIAL serial-number] file-set: For online dumps: [[{volume | *}.]{subvolume | *}.]{file-id | *} For audit dumps: $ZTMFAT.ZTMFAT.{file-id | *} ALTER PROCESS Changes the configured attribute values of various TMF process types.
TMFCOM Command Reference Summary ALTER PROCESS {process-type } {(process-type [,process-type]...
TMFCOM Command Reference Summary ALTER TAPEMEDIA ALTER TAPEMEDIA Changes the configured attribute values of tape volumes. Security: super user group member. ALTER TAPEMEDIA {tape-volume } {(tape-volume [,tape-volume]...)} ,STATUS {ASSIGNED} {BAD } {RELEASED} {SCRATCH } ALTER TMF Changes the TMF configuration volume or switches the functions of the TMP’s primary and backup processes. Security: super user group member. ALTER TMF, {CONFIGVOL volume } {SWITCHPROCESS TMP} Caution.
TMFCOM Command Reference Summary CLOSE RESOURCEMANAGER CLOSE RESOURCEMANAGER Forces closure of one or more recoverable resource managers that are currently open by a gateway process. Security: super user group member. CLOSE {RESOURCEMANAGER | RM} {rm-name } {(rm-name [,rm-name]...)} CMDVOL Specifies the default volume and subvolume names for expanding unqualified file names other than those in OBEY commands. Security: any user. CMDVOL [volume ] [[volume.
TMFCOM Command Reference Summary DELETE DUMPS DELETE DUMPS Removes dump entries from the TMF catalog, and attempts to delete the associated dump files from disk. Security: super user group member. DELETE DUMPS {file-set } [!] {(file-set [,file-set]...)} [!] [,SERIAL serial-number] file-set: For online dumps: [[{volume | *}.]{subvolume | *}.]{file-id | *} For audit dumps: $ZTMFAT.ZTMFAT.
DELETE TMF TMFCOM Command Reference Summary DELETE TMF Purges the entire TMF configuration, including volume and file recovery information for the database. Only tape media names are retained in the TMF catalog. Security: Logon under super ID (user ID 255,255). DELETE TMF Caution. Contact the Global Customer Support Center (GCSC) or your service provider before issuing this command.
TMFCOM Command Reference Summary DISABLE AUDITDUMP DISABLE AUDITDUMP Suspends an audit dump process, preventing the dumping of audit-trail files. Security: super user group member. DISABLE AUDITDUMP {MASTER | MAT } {AUX[ILIARY]nn} [,ABRUPT] Caution. Leaving audit dumps disabled for long durations can cause audit-trail files to accumulate. This accumulation, in turn, can potentially cause TMF to reach the OVERFLOWTHRESHOLD and BEGINTRANSDISABLE limits.
DISPLAY OPERATIONS TMFCOM Command Reference Summary DISPLAY OPERATIONS Displays the Event Management Service (EMS) messages recorded for a specific TMF operation. Security: read-access to the EMS log files. DISPLAY OPERATION[S] operation-number [,LONG ] [,BEGINTIME date-time [,LOGFILE filename [,COLLECTOR process-name [GMT]] ] ] date-time: {month[-]day[-]year, hr:min[:sec]} {day[-]month[-]year, hr:min[:sec]} month: {JAN|FEB|MAR|APR|MAY|JUN|JUL|AUG|SEP|OCT|NOV|DEC} filename: [volume.][subvolume.
DUMP FILES TMFCOM Command Reference Summary DUMP FILES Copies audited files to either tape or disk, producing online dumps. These online dumps might be used later if file recovery is initiated through a RECOVER FILES command. Security: super user group member. DUMP FILES {file-set } {(file-set [,file-set]...)} [,BLOCKSIZE { 4 | 8 | 12 | 16 | 20 | 24 | 28 | 32 | 36 | 40 | 44 | 48 | 52}] [,COPIES { 1 | 2 } [PARALLEL] ] [,DISKMEDIA {disk } {(disk [,disk]...)} ] [,NOT {file-set } {(file-set [,file-set]...
TMFCOM Command Reference Summary ENABLE AUDITDUMP Caution. Error messages generated by TMF and other subsystems during online dump operations can sometimes have a vital impact that is not always obvious. For example, a disk or tape parity or checksum error can prevent a file from being dumped. For this reason, you should check the individual messages and summary information displayed by the DUMP FILES command to ensure that you are aware of all such errors.
TMFCOM Command Reference Summary ENV Displays the current operating environment for your TMFCOM session. Security: any user. ENV EXIT Ends your current TMFCOM session. Security: any user. EXIT FC Permits you to display and repeat or modify the last command entered. Security: any user. FC [-linenum | linenum | string | “quoted-string ”] HELP Displays syntax information for TMFCOM commands. Security: any user.
TMFCOM Command Reference Summary INFO AUDITDUMP INFO AUDITDUMP Displays the configured attribute values of audit dump processes. Security: any user. INFO AUDITDUMP [MASTER | MAT ] [AUX[ILIARY]nn ] [(MASTER | MAT [,AUX[ILIARY]nn ])] [(AUX[ILIARY]nn [,MASTER | MAT ])] [(AUX[ILIARY]nn [,AUX[ILIARY]nn])] [ * ] [,OBEYFORM] INFO AUDITTRAIL Displays the configured attribute values of audit trails. Security: any user.
INFO CATALOG TMFCOM Command Reference Summary INFO CATALOG Displays the configured attribute values for the catalog process. Security: any user. INFO CATALOG [,OBEYFORM] INFO DATAVOLS Displays the configured attribute values of data volumes; also filters and then displays volumes based on selected configuration attributes. Security: any user. INFO DATAVOL[S] [volume ] [(volume [,volume]...)] [ * ] [,config-attrib [,config-attrib]...
INFO DUMPS TMFCOM Command Reference Summary INFO DUMPS Displays online and audit dump entries in the TMF catalog. Security: any user. INFO DUMPS [file-set ] [(file-set [,file-set]...)] [,BRIEF | DETAIL | OBEYFORM ] [,MEDIUM {TAPE | DISK} ] [,SERIAL serial-number ] [,SORT {BYFILE | BYSERIAL} ] [,STATUS {ASSIGNED} {INVALID } {RELEASED} ] [,TYPE {AUDITDUMP | ONLINEDUMP}] [,CATALOG [node.]volume.subvolume] [,NOT {file-set } {(file-set [,file-set]...
TMFCOM Command Reference Summary INFO PROCESS INFO PROCESS Displays the configured attribute values for the various TMF process types. Security: any user. INFO PROCESS [process-type ] [(process-type [,process-type]...
INFO TAPEMEDIA TMFCOM Command Reference Summary INFO TAPEMEDIA Displays the configured attribute values of tape volumes. Security: any user. INFO TAPEMEDIA [tape-volume ] [(tape-volume [,tape-volume]...)] [ * ] [,STATUS {ASSIGNED} {BAD } {RELEASED} {SCRATCH } ] [,OBEYFORM ] INFO TMF Displays the configured attribute values of TMF. Security: any user.
OBEYVOL TMFCOM Command Reference Summary OBEYVOL Specifies the default volume and subvolume names for expanding an unqualified command file name used in an OBEY command. Security: any user. OBEYVOL [[[node.]volume.]subvolume] OPEN SERVER Specifies the TMFSERVE process with which your TMFCOM process communicates to control TMF. Security: any user. OPEN SERVER {node } {[node.]server} [,CPU cpu-num ] [,PRI integer ] [,SWAP volume ] [,TERM [node.
RECOVER FILES TMFCOM Command Reference Summary RECOVER FILES Initiates file recovery: restoring a database to a consistent state. Security: super user group member. RECOVER FILES {file-set } {(file-set [,file-set]...)} [,NOT {file-set } {(file-set [,file-set]...
TMFCOM Command Reference Summary RECOVER FILES Caution. When you issue a RECOVER FILES command to initiate file recovery to the timestamp, and the time listed in the TMF catalog is not the time that the online dump actually took place, you risk destruction of your database because you will probably not recover all the data you need.
TMFCOM Command Reference Summary RELOCATE DISKDUMPS RELOCATE DISKDUMPS Changes the disk media locations specified in the TMF catalog. Security: super user group member. RELOCATE DISKDUMPS {serial-number } {(serial-number [,serial-number]...)} {* } ,OLDDMLOC diskmedia-loc, NEWDMLOC diskmedia-loc RESET AUDITTRAIL Resets audit trail attributes to their default values, canceling the effects of any previous SET AUDITTRAIL commands. Security: any user. RESET AUDITTRAIL {attribute [,attribute]...
TMFCOM Command Reference Summary RESET DUMPS RESET DUMPS Removes (clears) online and audit dump specifications, canceling the effects of previous SET DUMPS commands. Security: any user. RESET DUMPS {attribute [, attribute]...} { * } attribute: [DISKMEDIA] [SERIAL ] [TAPEMEDIA] [TYPE ] Note. You must establish values for the SERIAL and TYPE entries and for either the DISKMEDIA or the TAPEMEDIA entry. Default values are not allowed for these entries.
RESOLVE TRANSACTION TMFCOM Command Reference Summary RESOLVE TRANSACTION Causes an unresolved distributed transaction to either commit or back out its changes. To fully resolve the transaction, this command must be issued on all nodes on which the transaction resides, except for the transaction’s home node. Security: super user group member. RESOLVE TRANS[ACTION[S]] {transaction-id } {(transaction-id [,transaction-id]...)} {,STATE {ABORTED | COMMITTED}} transaction-id: [node. [node-number.
SET AUDITTRAIL TMFCOM Command Reference Summary SET AUDITTRAIL Establishes attribute values for audit trails created by subsequent ADD AUDITTRAIL commands issued during the same TMFCOM session. Security: any user. SET AUDITTRAIL attribute [,attribute]... attribute: [AUDITDUMP {ON | OFF}] [FILESIZE integer ] [ACTIVEVOL[S] {volume } {(volume [,volume] ...) }] [FILESPERVOLUME integer] [OVERFLOWVOL[S] {volume } {(volume [,volume]...)}] [OVERFLOWTHRESHOLD integer] [RESTOREVOL[S] {volume } {(volume [,volume].
TMFCOM Command Reference Summary SET DUMPS SET DUMPS Establishes specifications for online and audit dump entries added to the catalog by subsequent ADD DUMPS commands issued during the same TMFCOM session. Security: any user. SET DUMPS attribute [,attribute]... attribute: [DISKMEDIA disk ] [DISKMEDIA (disk [,disk]...
TMFCOM Command Reference Summary SHOW AUDITTRAIL SHOW AUDITTRAIL Displays the attribute values established by SET AUDITTRAIL commands in the current TMFCOM session. Security: any user. SHOW AUDITTRAIL [attribute [,attribute]...] [ * ] attribute: [AUDITDUMP ] [FILESIZE ] [ACTIVEVOL[S] ] [FILESPERVOLUME ] [OVERFLOWVOL[S] ] [OVERFLOWTHRESHOLD] [RESTOREVOL[S] ] [BEGINTRANSDISABLE] SHOW DATAVOLS Displays the attribute values established by SET DATAVOLS commands in the current TMFCOM session.
SHOW TAPEMEDIA TMFCOM Command Reference Summary SHOW TAPEMEDIA Displays the attribute values established by SET TAPEMEDIA commands in the current TMFCOM session. Security: any user. SHOW TAPEMEDIA [attribute [, attribute]...] [ * ] attribute: [DENSITY [DRIVE [LABEL [STATUS [UNLOAD ] ] ] ] ] START TMF Starts TMF transaction processing, optionally displaying the EMS events for the start operation as this operation progresses. Security: super user group member.
TMFCOM Command Reference Summary STATUS AUDITDUMP STATUS AUDITDUMP Displays the current status of audit dump processes. Security: any user. STATUS AUDITDUMP [MASTER | MAT ] [AUX[ILIARY]nn ] [(MASTER | MAT [,AUX[ILIARY]nn]) ] [(AUX[ILIARY]nn [,MASTER | MAT]) ] [(AUX[ILIARY]nn [,AUX[ILIARY]nn])] [ * ] STATUS AUDITTRAIL Displays the current audit trail activity. Security: any user.
STATUS DATAVOLS TMFCOM Command Reference Summary STATUS DATAVOLS Displays the current status of data volumes. Security: any user. STATUS DATAVOL[S] [volume ] [(volume [,volume]...
STATUS OPERATIONS TMFCOM Command Reference Summary STATUS OPERATIONS Displays the status of TMF operations that were recently completed or are now in progress. Security: any user. STATUS OPERATION[S] [operation-number ] [(operation-number [,operation-number]...
TMFCOM Command Reference Summary STATUS RESOURCEMANAGER STATUS RESOURCEMANAGER Displays the current status of both recoverable and volatile resource managers. Security: any user. STATUS {RESOURCEMANAGER | RM} [rm-name ] [rm-name [,rm-name]...)] [* ] [, STATE {CREATED } {CLOSED } {OPEN } {RECOVERING} {CRASHED } {VOLATILE }] [,PROCESS {process } {(process [,process]...) } {(cpu,pin) } {((cpu,pin) [,(cpu,pin)]...
STATUS TRANSACTIONS TMFCOM Command Reference Summary STATUS TRANSACTIONS Displays transaction identifiers and status. Security: any user. STATUS TRANS[ACTION[S]] [transaction-id [(transaction-id [,transaction-id]...) ] ] [,PROCESS {process } {(process [,process]... ) } {(cpu, pin) } {((cpu, pin) [,(cpu, pin)]...)}] [,STATE {ACTIVE } {ABORTING } {ABORTED } {COMMITTED} {ENDING } {HUNG } {PREPARED }] [,DETAIL | BRIEF ] transaction-id: [node. ] [node-number. ] [node(tm-flags). ]cpu.
TMFCOM Command Reference Summary VOLUME VOLUME Specifies the default volume and subvolume names for expanding all unqualified file names. Security: any user. VOLUME [volume ] [[volume.]subvolume] ! Re-executes a command previously entered in the current session. Security: any user. ! [-linenum | linenum | string | “quoted-string ”] ? Displays a command previously entered in the current session. Security: any user.
TMFCOM Command Reference Summary HP NonStop TMF Reference Manual—540138-001 B -44 ?
C TMF Configuration Limits and Defaults The tables in this appendix summarize various limits and defaults for TMF. Caution. Some of the limits and defaults described in this appendix may have changed since this manual was published with RVU H06.03. If such changes were made, they will be described in TMF Supplement for Limits and Defaults Changed after RVU H06.03. If that Supplement currently exists, please read it for new information about limits and defaults.
TMF Configuration Limits and Defaults Table C-2. Audit Trail Limits and Defaults Parameter Limits Default Active-audit volumes per audit trail 1 through 16 None Audit dumping feature On Audit-trail files per active-audit volume 1 through 100. Active-audit volumes multiplied by files per active-audit volume must be 2 or greater.
TMF Configuration Limits and Defaults Table C-4. Audit Dump and Online Dump Limits and Defaults Parameter Limits Default Number of parallel audit dump copies 1 through 2 1 Number of serial audit dump copies 1 through 3 1 Number of disk volumes that can be added to an audit dump configuration when audit dumping is directed to disk media 1 through 16 None Number of tape or disk volumes in a DUMP FILES command 1 through 16 None Table C-5.
TMF Configuration Limits and Defaults Table C-6. Process Limits and Defaults (page 2 of 3) Parameter Limits Default Audit restore process type Number of processes Extended segment size 0 if not needed; 1 or more as needed 0.5 through 128 MB (127.5 MB actual) 0.5 MB Backout process type Number of processes Extended segment size Always 4 5 through 128 MB (127.
TMF Configuration Limits and Defaults Table C-6. Process Limits and Defaults (page 3 of 3) Parameter Limits Default TMFMON2 process type Number of processes Extended segment size 1 per processor Always 0.25 MB 0.25 MB TMP process type Number of processes Extended segment size 1 primary and 1 backup process See discussion, EXTENDEDSEGIZE Option Considerations for the TMP on page 3-87. Volume recovery process type Number of processes 0 through 8.
TMF Configuration Limits and Defaults HP NonStop TMF Reference Manual—540138-001 C- 6
Index A ABORT TRANSACTION command 3-10/3-13, B-2 Aborted transactions 3-298 Aborting transactions 3-10/3-13, 3-229, 3-297 ABRUPT parameter DISABLE AUDITDUMP command 3-116, 3-117 DISABLE DATAVOLS command 3-119/3-120 STOP TMF command 3-305/3-306 Active audit volumes 3-16, 3-53, 3-219, 3-233, 3-247 See also Audit volumes Active transactions 3-12, 3-297 ACTIVEVOLS parameter ADD AUDITTRAIL command 3-15 RESET AUDITTRAIL command 3-219 SET AUDITTRAIL command 3-233 SHOW AUDITTRAIL command 3-247 ADD AUDITTRAIL comman
A Index Audit dumps See also Audit dump process adding 3-25/3-27 disk volumes for 3-25, 3-46, 3-49, 3-127, 3-224, 3-238/3-240, 3-252 file recovery from 3-201/3-214 performing 3-14, 3-22, 3-51, 3-232 serial numbers of 3-25, 3-106 tape volumes for 3-26, 3-44, 3-46, 3-224, 3-240, 3-252 verifying 3-45 Audit restore process 3-172 Audit trails adding 3-14/3-19 changing attributes of 3-51/3-60 default attribute values for 3-219/3-221 disk volumes for 3-15, 3-52, 3-219, 3-233 displaying attribute values of 3-152/
B Index AUXILIARY parameter (continued) DISABLE AUDITDUMP command 3-116 INFO AUDITDUMP command 3-150 INFO AUDITTRAIL command 3-152 NEXT AUDITTRAIL command 3-189 STATUS AUDITDUMP command 3-259 STATUS AUDITTRAIL command 3-261 STATUS DATAVOLS command 3-273 AVOIDHANGING parameter, ABORT TRANSACTION command 3-11/3-12 Awaittransresolve data volume state 3-271 AWAITTRANSRESOLVE state 3-274 B Backout process 3-172 BACKOUT process type 3-80 BAD tape volume status 3-41, 3-92, 3-179, 3-244 Beginning file recovery 3
C Index Changing BEGINTRANS options 3-61/3-66 Changing catalog process attributes 3-67/3-70 Changing data volume attributes 3-71/3-72 Changing dump entries 3-73/3-74 Changing extended segment size 3-85 Changing process attributes 3-75/3-91 Changing tape volume attributes 3-92/3-93 Changing the configuration volume 3-94 Clearing catalog entries 3-102 CLOSE RESOURCEMANAGER command 3-98/3-99, B-15 Closed resource managers 3-283 Closing resource managers 3-98/3-99 CMDVOL command 3-100/3-101, 3-193, 3-310, B-1
D Index cpu parameter (continued) RESOLVE TRANSACTION command 3-229 STATUS TRANSACTIONS command 3-297 CPU parameter, OPEN SERVER command 3-194 CPUS parameter, ALTER PROCESS command 3-77, 3-84 Crashed resource managers 3-283 crash-count parameter, RESOLVE TRANSACTION command 3-113 Created resource managers 3-283 D Data errors 3-11 Data volumes adding 3-20/3-23 changing attributes of 3-71/3-72 default attribute values for 3-222/3-223 deleting 3-103/3-104 disabling 3-119/3-120 displaying attribute values of
D Index DETAIL parameter INFO DUMPS command 3-166 STATUS AUDITTRAIL command 3-261 STATUS RESOURCEMANAGER command 3-284 STATUS TRANSACTIONS command 3-298 Device names 3-8 Direct file names 3-212 DISABLE AUDITDUMP command 3-116/3-117, B-18 DISABLE BEGINTRANS command 3-118, 3-136, B-18 DISABLE DATAVOLS command 3-119/3-120, B-18 DISABLE parameter, START TMF command 3-256 Disabled data volume state 3-272 Disabledclean data volume state 3-272 Disableddirty data volume state 3-273 Disabling audit dump processes
E Index DRIVE parameter (continued) SET TAPEMEDIA command 3-243 SHOW TAPEMEDIA command 3-254 DUMP FILES command 3-125/3-134, 4-4, B-20 Dumps adding 3-24/3-34 audit, performing 3-14, 3-22, 3-232 changing catalog entries for 3-73/3-74 clearing specifications for 3-224/3-225 deleting 3-105/3-107 displaying attribute values of 3-252/3-253 displaying catalog entries for 3-165/3-171 identifying files for 3-105 online, performing 3-22 performing 3-51, 3-125/3-134, 3-201/3-214 removing specifications for 3-224/3-
G Index FILESIZE parameter ADD AUDITTRAIL command 3-15, 3-58 RESET AUDITTRAIL command 3-219 SET AUDITTRAIL command 3-233 SHOW AUDITTRAIL command 3-247 FILESPERVOLUME parameter ADD AUDITTRAIL command 3-16, 3-18 ALTER AUDITTRAIL command 3-54 RESET AUDITTRAIL command 3-219 SET AUDITTRAIL command 3-233 SHOW AUDITTRAIL command 3-247 file-ids 3-7 file-set parameter ALTER DUMPS command 3-73 DELETE DUMPS command 3-105 DUMP FILES command 3-125, 3-128 INFO DUMPS command 3-165, 3-168 RECOVER FILES command 3-202 Fini
M Index LABEL ON parameter ADD TAPEMEDIA command 3-39 SET TAPEMEDIA command 3-244 LABEL parameter RESET TAPEMEDIA command 3-226 SHOW TAPEMEDIA command 3-254 Labeling tape volumes 3-39, 3-40, 3-226 Log file, EMS 3-122 LOGFILE parameter, DISPLAY OPERATIONS command 3-122 Logical file names 3-212 LONG parameter, DISPLAY OPERATIONS command 3-121 M MAKESAVEABEND parameter, ALTER PROCESS command 3-78 MAP NAMES parameter, RECOVER FILES command 3-206/3-208, 3-211/3-212 Master audit trails See also Auxiliary audit
O Index O OBEY command 2-5, 3-141, 3-190/3-191, B-27 OBEY files See command files OBEYFORM parameter INFO AUDITDUMP command 3-150 INFO AUDITTRAIL command 3-152 INFO BEGINTRANS command 3-156 INFO DATAVOLS command 3-159, 3-161 INFO DUMPS command 3-32, 3-166 INFO PROCESS command 3-173 INFO RECOURCEMANAGER command 3-176 INFO TAPEMEDIA command 3-179 INFO TMF command 3-182 OBEYVOL command 3-101, 3-190, 3-192/3-193, 3-310, B-28 object parameter, HELP command 3-145 OLDDMLOC parameter, RELOCATE DISKDUMPS command 3
Q Index PFSSIZE parameter, ALTER PROCESS command 3-79 Physical file names 3-212 Pins (process identifications numbers) 3-9 Prepared transaction state 3-298 Prepared transactions 3-229, 3-298 PRI parameter ALTER PROCESS command 3-77, 3-84 OPEN SERVER command 3-194 Process identification numbers (pins) See Pins PROCESS object ALTER command 3-75/3-91, B-12 INFO command 3-172/3-175, B-26 PROCESS parameter STATUS RESOURCEMANAGER command 3-284 STATUS TRANSACTIONS command 3-297 Processes changing attributes of 3
S Index RESOLVE TRANSACTION command 3-228/3-231, 3-257, B-33 Resolving distributed transactions 3-228/3-231, 3-257 Resource manager files 3-37 Resource manager registration 3-37 Resource managers 3-37 adding 3-36/3-38 closing 3-98/3-99 deleting 3-108/3-109 displaying attribute values of 3-176/3-178 displaying status of 3-282/3-288 RESOURCEMANAGER object ADD command 3-36/3-38, B-6 CLOSE command 3-98/3-99, B-15 DELETE command 3-108/3-109, B-16 INFO command 3-176/3-178, B-26 STATUS command 3-282/3-288, B-41
S Index Sessions ending 3-141 starting 2-1 SET AUDITTRAIL command 3-232/3-235, B-34 SET DATAVOLS command 3-236/3-237, B-34 SET DUMPS command 3-238/3-242, B-35 SET TAPEMEDIA command 3-243/3-246, 4-1/4-2, B-35 Setting audit trail attributes 3-232/3-235 Setting data volume attributes 3-236/3-237 Setting dump specifications 3-238/3-242 Setting tape volume attributes 3-243/3-246 SHOW AUDITTRAIL command 3-247/3-249, B-36 SHOW DATAVOLS command 3-250/3-251, B-36 SHOW DUMPS command 3-252/3-253, B-36 SHOW TAPEMEDIA
T Index Stopping TMF processes 3-88 Subvolume names 3-7 subvolume parameter CMDVOL command 3-100 NEXT AUDITTRAIL command 3-190 OBEY command 3-190 OBEYVOL command 3-192 VOLUME command 3-309 Suppressing display of EMS messages 3-256, 3-305 Suspending audit dump processes 3-116/3-117 SWAP parameter ALTER PROCESS command 3-77, 3-84 OPEN SERVER command 3-194 Switching audit trail files 3-189 Switching the primary and backup TMP process 3-95 SWITCHPROCESS TMP parameter, ALTER TMF command 3-94 System names See N
T Index TERM parameter ALTER PROCESS command 3-78 OPEN SERVER command 3-195 TIME parameter ADD DUMPS command 3-27, 3-30, 3-32 RECOVER FILES command 3-204 TMF configuration, deleting 3-111/3-112 TMF library process 3-172 TMF management process 3-172 TMF object ALTER command 3-94/3-95, B-14 DELETE command 3-111/3-112, B-17 INFO command 3-182/3-185, B-27 START command 3-256/3-258, B-37 STATUS command 3-291/3-295, B-41 STOP command 3-305/3-308, B-42 TMF objects 1-2/1-3 TMF shutdown 3-120 TMF (Transaction Mana
U Index Transactions aborting 3-10/3-13, 3-229/3-230 committed 3-229 deleting 3-113/3-115 disabling 3-61/3-62 displaying status of 3-296/3-304 enabling 3-61/3-62 heterogeneous 3-37/3-38, 3-61 hung 3-11, 3-114 identifying 3-10, 3-113, 3-228, 3-296 prepared 3-229/3-230 Prolonged ENDING state 3-300/3-301 resolving distributed 3-228/3-231 sequence numbers for 3-11, 3-114, 3-229 TRANSACTIONS object, STATUS command 3-296/3-304, B-42 Transactions, heterogeneous 3-37/3-38, 3-61 Transactions, resolving distributed
W Index volume parameter (continued) INFO DATAVOLS command 3-161 OBEY command 3-190 OBEYVOL command 3-192 STATUS DATAVOLS command 3-270 VOLUME command 3-309 Volume recovery process 3-172 VOLUMERECOVERY process type 3-83 W WHEREPHYSVOLIS parameter, RECOVER FILES command 3-206, 3-212 Wrongdiskmounted data volume state 3-273 Z ZTMFAT subvolumes 3-18, 3-25 Special Characters ! command 3-311/3-313, B-43 $ZTMFAT volumes 3-25 ? command 3-314/3-315, B-43 HP NonStop TMF Reference Manual—540138-001 Index -17
Special Characters Index HP NonStop TMF Reference Manual—540138-001 Index -18
