HP NonStop AutoTMF Software User’s Guide Abstract HP NonStop™ AutoTMF™ Software enables programs that are not configured to use the HP NonStop™ Transaction Management Facility (TMF) product to access and update audited databases. This manual describes the uses, installation, and all other operational aspects of NonStop AutoTMF Software.
Document History ) Part Number Product Version Published 429952-013 NonStop AutoTMF AAR (Update 11) October 2010 429952-014 NonStop AutoTMF AAS (Update 12) June 2011 429952-015 NonStop AutoTMF AAV (Update 14) January 2013 429952-016 NonStop AutoTMF AAW(TCF) April 2013
Legal Notices © Copyright 2013 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
HP NonStop AutoTMF Software User’s Guide Glossary Index Tables . Legal Notices 1. Introduction to HP NonStop AutoTMF Software Capabilities of NonStop AutoTMF Software 1-2 Limitations 1-2 2.
COBOL and C Programs 3-5 pTAL Programs 3-6 C++ Programs 3-6 Programs referencing other SRLs 3-6 Preparing TNS/E Programs 3-7 Preparing Privileged TNS/E programs 3-7 Preparing Programs that Have a User Library 3-8 TNS and TNS/R Programs 3-9 TNS/E Programs 3-9 Preparing a User Library 3-9 Intercept Libraries 3-10 Combining a User Library with the NonStop AutoTMF Runtime 3-10 TNS Library 3-10 TNS/R Library 3-10 TNS/E Library 3-11 Changing the User Library with Prepare 3-11 Preserving Mod Timestamp, License and
Suppressing Inherited Transactions 4-11 UNLOCKFILE Optimization 4-11 Record-Level Transactions 4-12 Exceptions 4-12 Considerations 4-13 Changing Nowait IO to Waited IO 4-13 Configuration 4-13 Considerations: 4-14 Unstructured Access 4-14 Large-Transfer Writing 4-15 Transaction File (TFILE) 4-16 Unilateral Aborts 4-16 Forced Transaction Commit 4-17 Setting Transaction Time Out 4-18 Automatic Transaction Limitations 4-19 Program Logic 4-19 SQL tables 4-19 Number of concurrent transactions 4-19 5.
NonStop AutoTMF and Process Pairs 5-7 How AutoTMF works with Process Pairs 5-8 6.
INFO ATMFPROGRAMS 6-62 INFO GLOBALS 6-63 INFO LIBRARY 6-63 INFO LOCALS 6-63 INFO MAPDB 6-64 INFO PREPARE 6-64 INFO PROGRAM 6-65 LABELDISPLAY (LD) 6-68 LISTFILEOPENS (LFO) 6-68 LISTLOCKS (LL) 6-69 LOG 6-71 MODIFY AUTOTMF 6-72 MODIFY GLOBALS 6-72 MODIFY MAPDBS 6-72 MONITOR 6-73 NSKFIXUP 6-73 OBEY 6-75 OPEN 6-75 OUT 6-75 PREPARE 6-75 PROGINFO (PI) 6-78 PID file-set 6-79 PURGEDATA 6-79 RESET 6-79 RESET GLOBAL 6-79 RESET LOCAL 6-80 RUN[D] 6-80 START MONITOR 6-81 STATS 6-82 STATUS MONITOR 6-82 STATUS TRACE 6-82 S
Monitor Commands 6-95 LOG 6-95 STATUS 6-96 SECURITY 6-96 BACKUPCPU 6-97 SWITCH 6-97 A.
Host Language Runtime Library Versions A-13 TNS/R Host Runtime Language Libraries A-14 TNS/R Host Language Runtime Library Versions A-14 TNS/E Host Language Runtime DLLs A-15 New Versions of DLLs and Operating System Upgrades A-15 Transporting Applications A-17 Version Checking A-17 Security and Availability A-18 Overview A-18 Data File Access Security A-18 Object File Access Security A-19 Configuration Security A-19 Product Security A-19 System Database Security A-19 Mapping Database Security A-19 Monitor
=_ESCORT_OPTMZUNLOCKSOFF B-7 =_ESCORT_READ_NULL_RECS B-7 =_ESCORT_SKIP_NULL_RECS B-7 =_ESCORT_STATEMENT_DATA B-8 =_ESCORT_STATEMENT_KEYS B-8 =_ESCORT_STATEMENT_TRACE B-8 =_ESCORT_SUPPRESS_AUDIT B-9 =_ESCORT_SUPPRESS_INHRTX B-9 Command Interpreter DEFINEs B-10 =_ESCORT_SYSDB B-10 =_ESCORT_MONITOR B-10 C.
Trace Interpretation C-9 Reporting Problems C-12 AutoTMF Component Failures C-12 Prepared Program Incorrect Behavior or Failure C-12 Locking Problems, Long Running Transactions, Errors 35 or Performance Problems C-13 D.
HP NonStop AutoTMF Software User’s Guide—429952-016 x
What’s New in This Manual Manual Information HP NonStop AutoTMF Software User’s Guide Abstract HP NonStop™ AutoTMF™ Software enables programs that are not configured to use the HP NonStop™ Transaction Management Facility (TMF) product to access and update audited databases. This manual describes the uses, installation, and all other operational aspects of NonStop AutoTMF Software.
What’s New in This Manual New and Changed Information HP NonStop AutoTMF Software User’s Guide—429952-016 xii
About This Manual This manual describes the uses, installation, and all other operational aspects of the HP NonStop™ AutoTMF™ software. This software product enables programs that are not written to use the HP NonStop™ Transaction Management Facility (TMF) product to access and update audited databases. It automatically manages TMF transactions required to access audited data and enables a rapid migration to an audited database.
General Syntax Notation About This Manual each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num] [ text] K [ X | D ] address-1 { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Change Bar Notation About This Manual Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]...
Change Bar Notation About This Manual HP NonStop AutoTMF Software User’s Guide—429952-016 xvi
1 Introduction to HP NonStop AutoTMF Software This section of the manual discusses the following topics: An overview of HP NonStop AutoTMF software (AutoTMF) A description of the facilities that are enabled by NonStop AutoTMF software, both immediately and through a migration process HP NonStop AutoTMF software enables programs that are not programmed to use the HP NonStop Transaction Management Facility (TMF) product to access and update audited data.
Introduction to HP NonStop AutoTMF Software Capabilities of NonStop AutoTMF Software Because NonStop AutoTMF software provides transactions only when needed, you can migrate your application, incrementally, to one that manages business-level transactions for maintaining a consistent database.
2 Installation and Basic Management Prerequisites Installing NonStop AutoTMF Software Updating NonStop AutoTMF Software Upgrading the Operating System Disabling NonStop AutoTMF Software Removing NonStop AutoTMF Software Shortcut to Run ESCORT CI Prerequisites Read the softdoc before you install NonStop AutoTMF software. AutoTMF generates transactions on behalf of application programs. The TMF product views AutoTMF like any other transactional program.
Installation and Basic Management Installing NonStop AutoTMF Software Installing NonStop AutoTMF Software Have your AutoTMF licensing instructions available. Consult the softdoc file for any changes to the installation procedures. Then proceed as follows: 1. Move Files from the Product Media to the Installation Subvolume. 2. Install NonStop AutoTMF Software Files. 3. (Optional) Start an EMS distributor. 4. Create the System Database 5. Install the NonStop AutoTMF Software License. 6.
Installation and Basic Management Install NonStop AutoTMF Software Files all NonStop servers. The INSTALL macro determines which runtime library files to install depending on the processor type of the server. Table 2-2.
Install NonStop AutoTMF Software Files Installation and Basic Management TNS and TNS/R Installation In the example below, AutoTMF is installed in subvolume $TOOLS.AUTOTMF: 24> install $tools.autotmf HP Nonstop(tm) AutoTMF(tm) Software File Installer UNPAK - File decompression program - T1255G06 - (2008-06-03) Archive version: 1 File Mode RESTORE Program - T9074G08 (21JUL2008) (AFO) (C)2000 Compaq (C)2006 Hewlett Packard Development Company, L.P. Drives: (\SIERRA.
Start an EMS distributor Installation and Basic Management In the example below, NonStop AutoTMF software is installed on $TOOLS.AUTOTMF: 71> install $tools.autotmf HP Nonstop(tm) AutoTMF(tm) Software File Installer UNPAK - File decompression program - T1255H01 - (2009-09-25) Archive version: 1 File Mode RESTORE Program - T9074H01 (04FEB2009) (AFN) (C)2000 Compaq (C)2007 Hewlett-Packard Development Company, L.P. Drives: (\ATOM.
Installation and Basic Management Create the System Database AutoTMF templates and filter. Enter the following TACL commands in a separate terminal window: ADD DEFINE =_EMS_TEMPLATES, CLASS MAP, FILE ZESCTMPL EMSDIST TYPE P, COLLECTOR $0, TEXTOUT $HOME, FILTER ESCFLTR The EMS distributor will display NonStop AutoTMF events. Create the System Database The System Database (SysDB) is created using ESCORT CI.
Installation and Basic Management Install the NonStop AutoTMF Software License subvolume called ESCCATLG. Use the CATALOG option to specify a different catalog, as shown in the details under CREATE SYSDB on page 6-55. Install the NonStop AutoTMF Software License Follow the licensing procedure described in the documentation that accompanies your NonStop AutoTMF software. The license is installed by using an Escort CI command.
Installation and Basic Management Create the Mapping Database When you create MapDB, the NonStop AutoTMF monitor process is started to manage access to MapDB. See CREATE MAPDB on page 6-53 for details about this command. When the monitor process is started, the following messages should be displayed by the EMS distributor: 16:07 21APR13 099,03,781 $JTMF 100 ESCMON starting Version 1.9.
Installation and Basic Management Update System Coldload Procedures Update System Coldload Procedures Once you alter the database files to be audited, the NonStop AutoTMF monitor process becomes a critical component of application availability. You must ensure that the monitor process is started whenever system maintenance has required it to be stopped. You should include the start of the monitor process with the other operational steps that normally follow a system cold load.
Installation and Basic Management Running Different Versions of NonStop AutoTMF on the Same System 8. Restart the application programs. Running Different Versions of NonStop AutoTMF on the Same System If you need to run different versions of NonStop AutoTMF on the same system, for example to test a newer version of the product, you must configure an alternate AutoTMF environment (Monitor and MapDB) and install the test software in a different location than the subvolume currently in use.
Installation and Basic Management Shortcut to Run ESCORT CI 2. Use the UNPREPARE command to restore the application program object files to their original state. 3. Stop the NonStop AutoTMF monitor process. 4. Use SQLCI to purge the SysDB and MapDB tables. 5. Use SQLCI to drop any catalog created during installation. 6. Update your startup and shutdown procedures to remove the commands that start and stop the monitor process.
Installation and Basic Management Shortcut to Run ESCORT CI HP NonStop AutoTMF Software User’s Guide—429952-016 2-12
3 Preparing Programs Program Preparation Overview Preparing Programs Preparing Programs that Have a User Library Preserving Mod Timestamp, License and Progid Setting Tips for Preparing Programs Diagnosing Preparation Errors Program Preparation Overview You must prepare programs to use AutoTMF. Preparation changes object files to invoke the NonStop AutoTMF runtime library instead of making direct calls to operating system procedures.
Preparing Programs Preparing Programs change the modification timestamp of the object file, to the time the file was prepared, revoke the LICENSE attribute of a privileged program. delete the PROGID setting of the object file, if the user executing the prepare command is not the owner of the file, or the owner’s manager or SUPER.SUPER. You can preserve these attributes by configuring a licensed Escort CI and using it to prepare the object files.
Using the PREPARE Command Preparing Programs The following sample terminal session shows PREPARE used on a single object file: 9> escort HP Nonstop(tm) AutoTMF(tm) Command Interpreter(T0581V03) - System \RDF10 Copyright Hewlett-Packard Company 2000-2004 Copyright Carr Scott Software Incorporated 1996-2004 AutoTMF 1? prepare data.myobj.batchobj; --- $DATA.MYOBJ.BATCHOBJ preparation complete --- AutoTMF runtime library $SYSTEM.ESCORT.
Preparing TNS Programs Preparing Programs To view the prepared status of a collection of object files, use INFO PROGRAM. For example: AutoTMF 1? info program $data.srvobj.*; $DATA.SRVOBJ Type ...
Preparing TNS/R Programs Preparing Programs TNS/R language runtime libraries are implemented in Shared Runtime Libraries (SRLs). When a TNS/R object is made executable, each external reference is assigned to the system library, a user library, or to a system SRL. Once a reference is assigned to an SRL, the reference cannot be changed.
Preparing TNS/R Programs Preparing Programs pTAL Programs Programs written exclusively in pTAL do not reference any SRL. (A pTAL program that uses the CRE SRL will be prepared in the same way as a COBOL or C program.) ESCRUNNT is an executable user library that contains only the GPLIB libraries. Specifically, ESCRUNNT does not contain initialization routines for CRE data structures.
Preparing TNS/E Programs Preparing Programs Preparing TNS/E Programs In TNS/E programs, the retargeting of system procedure calls is performed in the same manner as it is for TNS and TNS/R objects. However, since the NonStop AutoTMF runtime for TNS/E programs is implemented as a DLL instead of as a user library, the PREPARE command simply sets the NonStop AutoTMF runtime DLL (ESCRUNDL) as a DLL of the program. The example below shows the preparation of program $data.testobj.
Preparing Programs that Have a User Library Preparing Programs The example below shows the preparation of a copy of a TNS/E version of FUP that was copied into $TOOLS.AUTOTMF.MYFUP: $TOOLS AUTOTMF 1> fup dup (escrundl,z*dll),$tools.autotprv.* FILES DUPLICATED: 7 ...log on as SUPER.SUPER $TOOLS AUTOTMF 3> v $tools.autotprv $TOOLS.AUTOTPRV 4> fup File Utility Program - T6553H02 - (25JUL2012) System \SYS (C)1981 Tandem (C)2006 Hewlett Packard Development Company, L.P.
Preparing a User Library Preparing Programs This error occurs because a program cannot be successfully prepared if it references a user library that does not contain the NonStop AutoTMF runtime library. If any of your programs refer to a user library, the user library should be prepared. TNS and TNS/R Programs Once the user library has been prepared, the NonStop AutoTMF runtime library must be bound into the user library object file.
Combining a User Library with the NonStop AutoTMF Runtime Preparing Programs Intercept Libraries Certain third-party software products use a user library to intercept NonStop OS procedure calls, much like AutoTMF does. In that case, the user library should not be prepared prior to binding the NonStop AutoTMF runtime to the user library. If a user library contains both intercept procedures and ordinary application procedures, special processing is required; contact product support for assistance.
Changing the User Library with Prepare Preparing Programs 3. Use nld to combine ESCRUNN and ESCRUNNL into two versions of the user library corresponding to the two classes of TNS/R programs: For use with PTAL and C++ TNS/R programs: nld ESCRUNN mynatlb -o mynatlbt -ul For use with COBOL and C TNS/R programs: nld ESCRUNNL mynatlb -o mynatlbc -ul 4. If the NonStop AutoTMF EMS message template file (ZESCTMPL) has not been installed, move a copy of it into the same subvolume as the user library.
Tips for Preparing Programs Preparing Programs The License attribute of a privileged program. Note that a warning message is displayed if the license is revoked: *Warning* * 1667 * * * * * The LICENSE for your-object was disabled. SUPER.SUPER must issue a FUP LICENSE command to restore it. See the AutoTMF documentation for a method to automatically preserve the license when preparing programs.
Diagnosing Preparation Errors Preparing Programs starting the NonStop AutoTMF preparation process, subsequent errors are more likely caused by the preparation and not by the application’s setup. Also, you should prepare all programs that are part of the application, even if you know that some programs will not require automatic transactions. This configuration is simple to manage and causes fewer errors when the application is run.
Preparing Programs Diagnosing Preparation Errors unprepared objects, use the ALLOWDUPLICATES option (causing duplicate externals), then rebind the object file. Duplicate Externals – The program has duplicate names in the external procedure list, resulting in unresolved externals when the program is run, probably leading to program failure. Re-bind the object file. To avoid duplicate externals, build programs using only unprepared object files, then prepare them.
4 Configuring Automatic Transaction Processing Configuration Commands You can configure AutoTMF features using commands to set global options and to specify file names and program names that use AutoTMF options. See ALTER GLOBAL on page 6-35, ADD ATMFFILESET on page 6-6, and ADD ATMFPROGRAMS on page 6-13 for complete use and syntax descriptions of these commands. The ADD commands have corresponding INFO, ALTER and DELETE commands.
Command Options Configuring Automatic Transaction Processing 3. Wild-card in subvolume (but not volume) part of file name ($DATA.FIRM*.PAY*) 4. Wild-card in volume part of file name ($D*.FIRM01.PAY*) Wild-card names in the same part are also ordered by the location of the first wild-card character. For example, PAY* would precede P*. To display the file sets in the defined search order for the current configuration, use the INFO ATMFFILESET and INFO ATMFPROGRAMS command.
Command Options Configuring Automatic Transaction Processing Table 4-1.
Automatic Transactions Configuring Automatic Transaction Processing Table 4-1.
Configuring Automatic Transaction Processing Separate Transactions when a transactional application has some previously unaudited files that are to be audited using automatic transactions. You may also use the ALTER GLOBAL ATMFCOMMONTX command to disable automatic transactions for all files that are not explicitly configured for those transactions. Note. Do not configure files that were previously audited as COMMONTX, since configuring such files can cause locking problems.
Configuring Automatic Transaction Processing Transaction Commit Transaction Commit To commit an automatic transaction, AutoTMF analyzes all file- access operations. File locking, record locking, and update operations are the primary factors that determine when automatic transactions may be committed.
Configuring Automatic Transaction Processing Transaction Isolation Excessive lock contention can be reduced through proper NonStop AutoTMF configuration, but changes in the configuration may cause more frequent transactions and a corresponding increase in processing requirements. Transaction Isolation Transaction isolation influences the duration of automatic transactions to reduce the effect of automatic transactions outside the process that started them.
Configuring Automatic Transaction Processing Audited Attribute Hiding Once a nowait transaction commit has begun, only a system-level failure can cause the transaction to abort. Even if the process terminates or is stopped externally, a nowait transaction commits successfully. The only drawback to using nowait transactions is that the process continues to perform work without knowing if a unilateral abort has occurred.
Configuring Automatic Transaction Processing Audited File Creation Audited File Creation Some programs create files, but the files are not audited. AutoTMF allows you to configure file names that will be created automatically as audited files. Note. The NonStop RDF product replicates the creation of an audited file on the backup node; the NonStop RDF product does not create a file on the backup node if a file is created as unaudited and is later altered to be audited.
Configuring Automatic Transaction Processing Requiring Files to Be Audited To prevent errors and deadlocks, AutoTMF automatically configures each file open for read-through-locks mode. This mode has no effect on locking operations such as READLOCK, only on non-locking access such as READ. You may disable this configuration by altering the ATMFREADTHRULOCK global or by specifying NO READTHRULOCK for a file set or program.
Configuring Automatic Transaction Processing Suppressing Inherited Transactions FEBEGINTRDISABLED (86) FENODEVBUFSPACE (89) FETRANSABRTOWNERDIED (90) FETRANSABRTBADDBID (91) FETRANSABRTNETDOWN (92) FETRANSABRTAUDOVFL (93) FETRANSABRTOPRCMD (94) FETRANSABRTDISCTKOVR (95) FETRANSABRTTIMEOUT (96) FEABORTEDTRANSID (97) FENOMORETCBS (98) Suppressing Inherited Transactions A non TMF-aware server may inherit a transaction from a TMF-aware requester when reading $RECEIVE.
Configuring Automatic Transaction Processing Record-Level Transactions Record-Level Transactions Certain programs use a complex record-locking and record-unlocking sequence such that at least one record is locked for long periods. AutoTMF will not commit an automatic transaction until a program releases all locks obtained under the transaction. If the processing contains no point where all locks are released, the automatic transaction is never committed.
Configuring Automatic Transaction Processing Considerations Considerations As mentioned above, record-level transactions increase transactional activity and processing complexity, and they are useful only in very specific situations. Users should configure record-level transactions when a careful analysis of a program’s locking behavior leaves no other option or after being instructed to do so by product support.
Configuring Automatic Transaction Processing Unstructured Access In addition to specifying WAITEDIO, use the WAITTIME option to specify the maximum number of seconds an operation will wait for record locks to be released. Considerations: When AutoTMF performs AWAITIO, it does not know the timeout value that will be specified in the application call to AWAITIO. Configure the WAITTIME option on a file basis. To avoid perpetual waits, AutoTMF uses the default wait time of 64 seconds.
Configuring Automatic Transaction Processing Large-Transfer Writing A structured audited file cannot be opened for write access. An attempt to perform such an open results in an error 80. TMF and the file system do not permit unstructured updates to an audited structured file. TMF auditing is based on the logical records of the file; unstructured access changes the physical structure of the file, so the changes cannot be properly reflected in the TMF audit.
Configuring Automatic Transaction Processing Transaction File (TFILE) Transaction File (TFILE) The TMF Application Programmers Guide describes the use of the TFILE ($TMP) to manage multiple transactions in a multi-threaded program. Because AutoTMF also manages multiple transactions and transactions in parallel with the program transactions, AutoTMF opens the TFILE. For this reason, the TFILE must be managed as a shared resource, even though the TFILE appears to the program as a dedicated resource.
Configuring Automatic Transaction Processing Forced Transaction Commit Providing transaction isolation controls to prevent a unilateral abort from affecting external users or database consistency; see the preceding subsection Transaction Isolation on page 4-7. Providing an AUTOCOMMIT option that allows you to force all outstanding automatic transactions to be committed before the process abends, to avoid reaching the TMF AutoAbort time limit.
Configuring Automatic Transaction Processing Setting Transaction Time Out While forcing a commit before a program has released locks is tantamount to altering the program’s logic and would leave the program in an uncertain state, failing to commit the transactions before reaching the unilateral abort is not an option. To prevent the loss of data in cases where the program’s behavior could cause a unilateral abort, AutoTMF uses a configurable AUTOCOMMIT timer.
Configuring Automatic Transaction Processing Automatic Transaction Limitations TXTIMEOUT is set as follows: value: n [ SEC[ONDS] | MIN[UTES] ], between 5 and 510 minutes. value overrides the TMF AutoAbort timer setting. A value entered as n SEConds is rounded up to minutes. NEVER: the transactions is never aborted by TMF due to a timeout. OFF: the default, specifies that the TMF AutoAbort is in effect. Note that the AutoTMF AUTOCOMMIT time limit always applies.
Configuring Automatic Transaction Processing Number of concurrent transactions Up to 1000 transactions on systems running the NonStop OS version G06.20 or later. To allow more than the default 100 transactions, you must configure the ATMFMAXTX global parameter or set the program attribute MAXTX.
5 Usage Guidelines This section describes typical uses and limitations of AutoTMF, drawn from the experiences of customers. Auditing Files Auditing Unstructured Files Preparing HP Utilities Preparing Third-party Applications Auditing Enscribe Queue Files NonStop AutoTMF and Process Pairs Auditing Files Once NonStop AutoTMF software is installed, the programs are prepared, and after NonStop AutoTMF configuration attributes have been specified, you can enable auditing of files.
Auditing Unstructured Files Usage Guidelines by the application. To ensure that AutoTMF generates transactions only for newly audited files, proceed as follows: 1. Create a list of all the files that are newly audited. 2. Set the global parameter ATMFCOMMONTX to OFF. 3. Configure the new audited files as COMMONTX or SEPARATETX. The choice of COMMONTX or SEPARATETX is determined by concurrency requirements.
Preparing HP Utilities Usage Guidelines Log files and SPOOLER files have been successfully replicated. Preparing HP Utilities Some HP products contain utility programs that create and update files, but do not provide the transactions required to access audited files. If you wish to audit and access these files using automatic transactions, you must prepare the programs.
ENFORM Usage Guidelines If you are not using a privileged Escort CI and are not logged on as SUPER.SUPER when issuing the PREPARE command, a warning notifies you that the prepared FUP is not licensed. You must then have the SUPER.SUPER user license your prepared copy of FUP. For example: 1. Prepare FUP specifying the “!”: ESCORT PREPARE test.fup!;EXIT; --- $DATA.TEST.FUP preparation complete --- AutoTMF User Library $DATA.ESCORT.ESCRUNTM *Warning* * 1667 * * * * * The LICENSE for $DATA.TEST.
EDIT, TEDIT, VS Usage Guidelines ENABLE checks the file attributes of database files; if a file is audited and the program has omitted SET TMF ON, ENABLE generates an error message and refuses to access the file. If you have existing ENABLE programs that do not specify TMF ON, you may configure HIDEAUDIT for files that will now be audited. Then, by preparing the ENABLGS server, you will be able to access audited files through an ENABLE application that assumes the files are not audited.
SORT and SORTPROG Usage Guidelines 1. Stop the Spooler. 2. Rebuild the control file by starting the Spooler with the REBUILD option. 3. Stop the Spooler once more. 4. Audit the new control file. 5. If the REBUILD is performed on the same system (if not required because of a takeover situation), move the control file to the backup system. 6. WARM START the Spooler. SORT and SORTPROG Do not prepare any FastSort components.
Preparing Third-party Applications Usage Guidelines Tracing shows the alteration of the open exclusion and the deblocking operations. Caution. Do not configure SEPARATETX for an audited file that is opened with the exclusion mode Process Exclusive.
How AutoTMF works with Process Pairs Usage Guidelines In the less typical case where a process pair directly accesses the database, and AutoTMF is used to manage audited access to the data, consider the following analysis of failure scenarios. In a primary process, AutoTMF operates in the normal way, creating and committing automatic transactions as required to perform audited database updates. When a primary process fails, some automatic transactions may be active.
6 NonStop AutoTMF Commands The command interpreter (CI) is the primary interface for installing, configuring, controlling and monitoring NonStop AutoTMF software. This chapter describes the command interpreter and is organized as follows: Running the Command Interpreter Command Syntax Command Summary Command Descriptions Monitor Commands Running the Command Interpreter Use this TACL RUN command to start the command interpreter: [RUN] $SYSTEM.ESCORT.
Command Syntax NonStop AutoTMF Commands Command Syntax The CI is a conversational-mode program. Most commands can be continued over many lines without a continuation character; therefore, use a semicolon (;) to terminate each command. Some commands, such as FC and RUN, are single-line commands and are terminated by the end of line; such commands can be continued by placing an ampersand (&) at the end of the line.
Command Summary NonStop AutoTMF Commands Table 6-1.
Command Summary NonStop AutoTMF Commands Table 6-1.
Command Summary NonStop AutoTMF Commands Command Name Description SECURITY Controls which users are permitted to issue monitor commands BACKUPCPU Alters the backup cpu of the monitor process SWITCH Causes primary and backup processes to exchange roles Table 6-3.
NonStop AutoTMF Commands Command Descriptions Command Descriptions ABEND MONITOR Causes the monitor to stop and produce a saveabend file. Use this command only when you are required to supply information about a monitor problem and are instructed to do so by product support. ABEND MONITOR [ * | process-name | mapdb ]; * (asterisk) stops all configured monitor processes. process-name the name of the AutoTMF monitor process to be stopped. The default is the current monitor for the session.
NonStop AutoTMF Commands ADD ATMFFILESET can be altered by using the ALTER ATMFFILESET and deleted by using the DELETE ATMFFILESET commands. ADD ATMFF[ILESET] file-set [ , attribute ] ...
NonStop AutoTMF Commands ADD ATMFFILESET DEFAULT: the AUTOCOMMIT value is the default, which is set by the global parameter ATMFAUTOCOMMIT. ATMFAUTOCOMMIT has a default of 115 minutes, based on the default TMF AutoAbort value of 120 minutes. If a program fails to unlock a record and prevents AutoTMF from committing automatic transactions, the non-committed updates are eventually lost because the TMF AUTOABORT timer will cause the abort of the long running transaction.
NonStop AutoTMF Commands ADD ATMFFILESET Be specific when defining the fileset. HIDEAUDIT hides the audit attribute for all files in the fileset, even if the audited file is not intended to be accessed under an AutoTMF automatic transaction. Note. If the program calls FILE_GETINFOLIST_ or FILE_GETINFOLISTBYNAME_, the audit attribute is only hidden if the check for audit is the first in the item list passed to the procedure.
NonStop AutoTMF Commands ADD ATMFFILESET To instruct the runtime to read null records for all audited entry-sequenced files, set the global parameter ATMFSKIPNULLRECS to OFF. To request this option for a specific program, use the =_ESCORT_READ_NULL_RECS define. If this option is specified, it overrides the value of the global parameter ATMFSKIPNULLRECS and of the =_ESCORT_SKIP_NULL_RECS define. READNULLRECS is the default.
NonStop AutoTMF Commands ADD ATMFFILESET If a record is inserted into an audited entry-sequenced file and subsequently backed out because a transaction is aborted, a zero length record is left in the file where the record had been inserted. This cannot occur if the file is not audited and can cause problems for programs that are not expecting to encounter such records. SKIPNULLRECORDS shelters the application programs from these unexpected records.
NonStop AutoTMF Commands ADD ATMFFILESET WAITTIME sets the maximum number of seconds an operation will wait for locks to be released. The value specified is from 1 to 4096 and rounded to the nearest power of 2 (1,2,4,8...). The default is 64 seconds. For this option to take effect, specify it both as an attribute of a program and as an attribute of the file using ADD ATMFPROGRAMS or ALTER ATMFPROGRAMS. For further details, see Changing Nowait IO to Waited IO on page 4-13.
NonStop AutoTMF Commands ADD ATMFPROGRAMS ADD ATMFPROGRAMS Configures automatic transactions for selected programs. Programs are specified by file pattern that may select a single program or all programs that match the pattern. The configuration for a program file set can be altered with the ALTER ATMFPROGRAMS and deleted with the DELETE ATMFPROGRAMS commands. ADD ATMFP[ROGRAMS] object-fileset [ , attribute ] ...
NonStop AutoTMF Commands ADD ATMFPROGRAMS commits all outstanding automatic transactions and abends the process if any automatic transaction exceeds the specified time. value: is n [ SEC[ONDS] | MIN[UTES] ], between 5 and 510 minutes. A value entered as n SEConds is converted to a minute value. NEVER: disables AUTOCOMMIT. AutoTMF never aborts the long running transaction. DEFAULT: the AUTOCOMMIT value is the default, which is set by the global parameter ATMFAUTOCOMMIT.
NonStop AutoTMF Commands ADD ATMFPROGRAMS the level of transaction isolation for automatic transactions: WEAK isolation commits outstanding transactions whenever a process replies to a request or waits for a new request. This is the default. NORMAL isolation commits outstanding transactions whenever a process sends a request to another process.
NonStop AutoTMF Commands ADD ATMFPROGRAMS commits automatic transactions after n updates and inserts, if the process is not holding locks on any of the participating records. This is an advisory setting for performance, not one that precisely controls management of automatic transactions. The value of n should be a power of 2 (1,2,4,8,16,32,...) in the range of 1 to 4096. If the value specified is not a power of 2, the value will be rounded to a power of 2. The default is 32.
NonStop AutoTMF Commands ADD ATMFPROGRAMS RECORDTX is used when a file is accessed by programs in which record locking sequences do not allow AutoTMF to commit automatic transactions (there is at least one lock held on a record in this file at any given time). For RECORDTX to take effect, it must be configured both as a program attribute and as a file attribute using ADD ATMFFILESET or ALTER ATMFFILESET.
NonStop AutoTMF Commands ADD ATMFPROGRAMS suppresses the use of TMF in programs. When specified, SUPPRESSUSERTX has the following effects: All BEGIN and ENDTRANSACTION operations requested by the application are ignored. All transactions inherited from requesters through messages on $RECEIVE are ignored. FILEINFO requests for audited files report that files are not audited. This facility is for testing only.
NonStop AutoTMF Commands ADD ATMFPROGRAMS For this option to take effect, specify it both as an attribute of a program and as an attribute of the file using ADD ATMFFILESET or ALTER ATMFFILESET. For further details, see Changing Nowait IO to Waited IO on page 4-13 WARNLONGTX { value | NEVER | DEFAULT } sets the frequency of the long transaction warning messages displayed in the EMS log. By default, the warnings are generated every 5 minutes.
NonStop AutoTMF Commands ALTER ATMFFILESET ALTER ATMFFILESET Alters the configuration of automatic transactions that were defined for a file set using the ADD ATMFFILESET command. ALTER ATMFF[ILESET] file-set [ , attribute ] ...
NonStop AutoTMF Commands ALTER ATMFFILESET value: is n [ SEC[ONDS] | MIN[UTES] ], between 5 and 510 minutes. A value entered as n SEConds is converted to a minute value. NEVER: disables AUTOCOMMIT. AutoTMF never aborts the long running transaction. DEFAULT: the AUTOCOMMIT value is the default, which is set by the global parameter ATMFAUTOCOMMIT. ATMFAUTOCOMMIT has a default of 115 minutes, based on the default TMF AutoAbort value of 120 minutes. NO AUTOCOMMIT is equivalent to DEFAULT.
NonStop AutoTMF Commands ALTER ATMFFILESET HIDEAUDIT | NO HIDEAUDIT requests that the audit attribute on a file be concealed from the application program when the program inquires about file attributes using procedure calls such as FILEINFO, FILERECINFO, FILEGETINFO, etc. Be specific when defining the fileset. HIDEAUDIT hides the audit attribute for all files in the fileset, even if the audited file is not intended to be accessed under an AutoTMF automatic transaction. Note.
NonStop AutoTMF Commands ALTER ATMFFILESET READNULLRECS (for entry-sequenced files only) reverses the effect of the SKIPNULLRECS option. See the description of SKIPNULLRECS below for details. To instruct the runtime to read null records for all audited entry-sequenced files, set the global parameter ATMFSKIPNULLRECS to OFF. To request this option for a specific program, use the =_ESCORT_READ_NULL_RECS define.
NonStop AutoTMF Commands ALTER ATMFFILESET to be generated even if the process has its own transaction and when the transaction must be managed separately from transactions for other files. SKIPNULLRECS (for entry-sequenced files only) ignores zero-length records when reading sequentially through an audited entry-sequenced file.
NonStop AutoTMF Commands ALTER ATMFFILESET READ and WRITE. After the AWAITIO completes, AutoTMF commits any outstanding transactions using the usual algorithms as directed by the configuration. AutoTMF saves the values returned by AWAITIO, and returns control to program as if the READ or WRITE operation were still in progress. For a READ, the data buffer contains the input data. WAITTIME sets the maximum number of seconds an operation will wait for locks to be released.
NonStop AutoTMF Commands ALTER ATMFPROGRAMS ALTER ATMFPROGRAMS Alters the configuration of automatic transactions that were defined for programs with the ADD ATMFPROGRAMS command. ALTER ATMFP[ROGRAMS] object-fileset [ , attribute ] ...
NonStop AutoTMF Commands ALTER ATMFPROGRAMS value: is n [ SEC[ONDS] | MIN[UTES] ], between 5 and 510 minutes. A value entered as n SEConds is converted to a minute value. NEVER: disables AUTOCOMMIT. AutoTMF never aborts the long running transaction. DEFAULT: the AUTOCOMMIT value is the default, which is set by the global parameter ATMFAUTOCOMMIT. ATMFAUTOCOMMIT has a default of 115 minutes, based on the default TMF AutoAbort value of 120 minutes. NO AUTOCOMMIT is equivalent to DEFAULT.
NonStop AutoTMF Commands ALTER ATMFPROGRAMS WEAK isolation commits outstanding transactions whenever a process replies to a request or waits for a new request. This is the default. NORMAL isolation commits outstanding transactions whenever a process sends a request to another process.
NonStop AutoTMF Commands ALTER ATMFPROGRAMS advisory setting for performance, not one that precisely controls management of automatic transactions. The value of n should be a power of 2 (1,2,4,8,16,32,...) in the range of 1 to 4096. If the value specified is not a power of 2, the value will be rounded to a power of 2. The default is 32. NOTX | NO NOTX disables or enables the generation of automatic transactions for audited file access.
NonStop AutoTMF Commands ALTER ATMFPROGRAMS For further details on the use of RECORDTX, see paragraph Record-Level Transactions on page 4-12. SEPARATETX | NO SEPARATETX enables or disables accesses to audited files in the program under separate automatic transactions. If specified, the program attribute overrides any setting of the COMMONTX file attribute. STOPONTMFERR | NO STOPONTMFERR stops a program that encounters a TMF environmental error.
NonStop AutoTMF Commands ALTER ATMFPROGRAMS This facility is for testing only. Programs that make use of TMF may depend on the correct operation of the calls that are eliminated by this option. Enabling this option may cause program failures and data corruption. TMF operations for a program may also be suppressed by using the class map define =_ESCORT_SUPPRESS_AUDIT with a dummy file. The default is NO SUPPTRESSUSERTX.
NonStop AutoTMF Commands ALTER ATMFPROGRAMS The AutoTMF runtime generates periodic EMS messages to alert the operator of long running transactions, which are usually caused by a program holding locks and preventing AutoTMF from committing an automatic transaction. The EMS message displays the transaction identifier of the long running transaction, the name of the process holding the locks and the time remaining before the transaction reaches the AutoCommit limit.
NonStop AutoTMF Commands ALTER FILE ALTER FILE Utility command similar to the FUP ALTER command. Changes attributes of Enscribe files. Unlike the FUP ALTER command, the AutoTMF ALTER FILE command can alter a collection of files specified as a file set.
NonStop AutoTMF Commands ALTER FILE enables or disables buffered writes are performed. If NO BUFFERED is specified, writes are not buffered. The default is buffered mode for audited files and not buffered for non audited files. CLEARONPURGE | NO CLEARONPURGE erases disk free space when files are purged. CODE file-code a numeric file code of the file. file-code is an integer between 0 and 65535. Codes 100 to 999 are reserved for use by HP.
ALTER GLOBAL NonStop AutoTMF Commands sets the mode of file writes: verified or not verified. The default is NO VERIFIEDWRITES. ALTER GLOBAL Sets or changes global configuration values for AutoTMF. Global parameters are the default for all environments.
NonStop AutoTMF Commands { { { { { { { { { { { { { { { { { { { { { ATMFTXHOLDOFF 0-to-n-seconds ATMFTXTIMEOUT { value | NEVER | OFF } ATMFWARNLONGTX { value | NEVER | DEFAULT } DYNAMICTRACE { ON | OFF } EMSCOLLECTOR collector-process MAX[MONITOR]OPENS 512-to-4096 SECURETRACE { ON | OFF } [SWAP]KMSF { ON | OFF } SWAPVOL[0] local-disk-volume SWAPVOL1 local-disk-volume SWAPVOL2 local-disk-volume SWAPVOL3 local-disk-volume ALTER GLOBAL } } } } } } } } } } } } } } } } } } } } } parameter-and-value ATMF { ON
NonStop AutoTMF Commands ALTER GLOBAL DEFAULT: the AUTOCOMMIT value is 115 minutes, based on the default TMF AutoAbort value of 120 minutes. If a program fails to unlock a record and prevents AutoTMF from committing automatic transactions, the non-committed updates are eventually lost because the TMF AUTOABORT timer will cause the abort of the long running transaction.
NonStop AutoTMF Commands ALTER GLOBAL NORMAL isolation commits outstanding transactions whenever a process sends a request to another process. STRONG isolation commits outstanding transactions whenever the process does one of the following: issues a READ or a WRITE to a device issues a WRITE to a non-audited disk file ISOLATION can also be set for selected programs using the ADD ATMFPROGRAMS command.
NonStop AutoTMF Commands ALTER GLOBAL To override ATMFMAXTX for a specific program, set the MAXTX option using ADD ATMFPROGRAMS or ALTER ATMFPROGRAMS. Note. You can set ATMFMAXTX to a value greater than 100 only on NonStop servers that support a maximum of 1000 transactions (T9055AER and later) ATMFMAXUPDATE 1-to-4096 commits automatic transactions after n updates and inserts, if the process is not holding locks on any of the participating records.
NonStop AutoTMF Commands ALTER GLOBAL The value can be overridden for a program file set using the ADD ATMFPROGRAMS or ALTER ATMFPROGRAMS and for a file set using the ADD ATMFFILESET or ALTER ATMFFILESET. ATMFSEPARATETX generates a separate parallel transaction for every file managed by AutoTMF. ATMFSEPARATETX should be used with caution as it might have a measurable negative impact on performance. The default is OFF.
NonStop AutoTMF Commands ALTER GLOBAL these cases, if the batch process is restarted after a failure, some completed server requests may be aborted. When the master process stops sending work to the server, there may be an outstanding active transaction, plus record locks and uncommitted updates. A commit timer will commit the active transactions after a specified idle period. The master process may send a terminating request to the servers but should not stop the server processes.
NonStop AutoTMF Commands ALTER GLOBAL locks and preventing AutoTMF from committing an automatic transaction. The EMS message displays the transaction identifier of the long running transaction, the name of the process holding the locks and the time remaining before the transaction reaches the AutoCommit limit. value: a number between 1 and 30 minutes, specified as n [ SEC[ONDS] | MIN[UTES]. A value entered as n SEC[ONDS] is converted to a minute value.
NonStop AutoTMF Commands ALTER LOCAL The default is ON, which restricts tracing privileges to the owner of the process. [SWAP]KMSF { ON | OFF } enables or disables KMSF swap file allocation. If an error occurs on the swap file allocation, the runtime reverts to the normal swap file allocation, either using the SWAPVOLn global specification or the default swap file. The default is OFF.
NonStop AutoTMF Commands ALTER MAPDB These attributes can also be changed using the ALTER MONITOR command. ALTER MAPDB [mapdb-subvol] { , option } ; option is { { { { { { { { { BACKUP 0-to-15 } } HOMETERM [ file-name | NONE ]} } MONITOR process-name } } PRIMARY 0-to-15 } } PRIORITY 1-to-199 } mapdb-subvol the MapDB subvolume. The default is the current session MapDB. option BACKUP 0-to-15 cpu number of the backup monitor process. HOMETERM file-name the home terminal for the monitor process.
NonStop AutoTMF Commands ALTER MONITOR ALTER MONITOR Alters attributes of the monitor process. Changes take effect when the monitor process is restarted. These attributes can also be changed using the ALTER MAPDB command. ALTER MONITOR [process-name] { , option }; option is { { { { { { { BACKUP 0-to-15 } } HOMETERM [ file-name | NONE ]} } PRIMARY 0-to-15 } } PRIORITY 1-to-199 } process-name the AutoTMF monitor process. The name must have 5 characters, including the $.
NonStop AutoTMF Commands CALC CALC A four-function calculator. Operators include addition, subtraction, multiplication, division and parentheses. Multiplication and division have precedence over addition and subtraction. Numeric operands are assumed to be decimal unless preceded by % (for octal), %h (for hexadecimal), or %b (for binary). An expression comprised of simple integers is processed using integer arithmetic.
COPY NonStop AutoTMF Commands COPY Similar to the FUP COPY command with enhancements. Copies records from an input file to an output file.
COPY NonStop AutoTMF Commands out-options is: { { { { { { { { { { { { { { { { { { { { { BLOCKOUT n } } BUFFERED } } EBCDICOUT } } FOLD } } PAD pad-character } } RECOUT n } } REWINDOUT | NO REWINDOUT } } UNLOADOUT | NO UNLOADOUT } } UNSTROUT } } UPDATE } } VAROUT } display-options { { { { { { { { { { { [O]CTAL [D]ECIMAL [H]EX [A]SCII BYTE NO HEAD } } } } } } } } } } } in-file the input file. in-file can be a process, tape, terminal, or disk file.
NonStop AutoTMF Commands COPY control-options COUNT num-records the number of records or rows to copy. If omitted, all records are copied. FIRST { ordinal-record-num } { KEY { record-spec | key-value } } { key-spec ALTKEY key-value [, key-value ] } the starting record of the input file to copy. If omitted, the copy starts at the first record or row in the input file. ordinal-record-num the number of records or rows from the beginning of the file that are to be skipped.
NonStop AutoTMF Commands COPY FROMLAST positions on the last record in the key range specified in the FIRST KEY option. UPSHIFT converts lowercase characters to uppercase. in-options BLOCKIN n the number of bytes in an input block, in the range of 1 to 32767, that are requested in a single physical read operation. If BLOCKIN is omitted, the RECIN value is used. The default is device dependent: 80 bytes for terminal, 132 bytes for process and unstructured files.
NonStop AutoTMF Commands COPY If NO REWINDIN is specified, the tape remains positioned without rewinding. The default is REWINDIN. This option also applies to labeled tapes. SHARE opens the input file in shared exclusion mode. The default is protected mode. SKIPMATCH positions the input file to the record immediately following the one whose key matches the specified key. The entire key must be supplied. If the file is not key sequenced, an error 46 is returned.
NonStop AutoTMF Commands COPY BUFFERED sets buffering on write operations to an unaudited out-file. EBCDICOUT translate output characters from ASCII to EBCDIC. FOLD divides output records longer than the output record length into as many output records as needed to copy the entire record. PAD pad-character pads the output records shorter than the output record length with padcharacter. pad-character is an ASCII character in quotation marks, or an integer in the range of 0 to 255.
NonStop AutoTMF Commands CPUS writes variable length blocked records. Each record is preceded by a one word indicator that contains the record length in bytes. Variable length records are word aligned in the output block. The last record in each block is followed by a terminator ( -1 ) if there is space in the block. The FOLD and PAD options are not supported when VAROUT is specified.
CREATE MAPDB NonStop AutoTMF Commands Because MapDB contains SQL tables, the MapDB subvolume must be created on an audited volume. CREATE MAPDB [ mapdb-subvol | ON volume ] [ , option ] ; option is { { { { { { { { { { { { { BACKUP 0-to-15 CATALOG SQL-catalog HOMETERM file-name MONITOR process-name PRIMARY 0-to-15 PRIORITY 1-to-199 SECURE "rwep" } } } } } } } } } } } } } mapdb-subvol subvolume where MapDB tables are created. The default MapDB subvolume name is ESCMAPDB.
NonStop AutoTMF Commands CREATE SYSDB EMS collector cannot be specified as the hometerm of a process when the process is launched. Functionally however, the home terminal for the monitor process is the default EMS collector, as shown by the AutoTMF STATUS MONITOR command. MONITOR process-name the AutoTMF monitor process to be associated with MapDB. The name must have 5 characters, including the $. The default is $ZESC. PRIMARY 0-to-15 the cpu number of the primary monitor process.
NonStop AutoTMF Commands DEADLOCK option CATALOG SQL-catalog SQL catalog where SysDB tables are to be registered. The catalog may also be specified by setting the catalog attribute of the =_DEFAULTS define. If CATALOG is omitted, AutoTMF creates a SQL catalog on the same volume as SysDB in subvolume ESCCATLG. EMSCOLLECTOR collector-process the EMS collector process where all event messages are sent. collector-process must be an existing collector process. If omitted, event messages are sent to $0.
NonStop AutoTMF Commands DELAY the duration of the deadlock in seconds where n is between 2 and 600. The deadlock can be stopped by entering the break key. The default is 60 seconds. Note. If any transactional activity has occurred in the AutoTMF CI before the DEADLOCLK command is issued, DEADLOCK fails with an error 13 on the OPEN of $TMP. Transactional activity includes any configuration command that requires access to SysDB or MapDB. If this error occurs, exit and restart the CI session.
NonStop AutoTMF Commands DROP MAPDB The DEQUEUE command terminates if the queue is empty. It times out after two seconds if a read on the queue can't find a record. DEQUEUE in-file, out-file [, dequeue-options ]; dequeue-options is: { { { { control-options in-options out-options display-options } } } } in-file an Enscribe queue file. out-file an Enscribe queue file, entry-sequenced file, the terminal or $NULL (or equivalent). dequeue-options See command options for COPY on page 6-47.
NonStop AutoTMF Commands FACTOR FACTOR Calculates the prime factors of the integer part of the expression. Accepts any numeric expression. FACTOR constant; constant a decimal constant with or without a decimal point, or a binary, octal, or hexadecimal integer prefixed by %b, %, or %h respectively. FC and ! Runs previous commands found in the command history. FC permits a command to be edited before execution. “!” runs a command without editing.
NonStop AutoTMF Commands FILES If omitted, the CI displays one line of information per file in the file-set. AGG[REGATES] displays the following information: the 32-bit and 64-bit values for aggregate eof and file size of partitioned files and tables, the GMT and LCT forms of the aggregate modification timestamp, the information normally displayed with the DETAIL option. FID file-set abbreviates FILEINFO DETAIL. FILES Displays the 8-character filename of the files in the file-set.
NonStop AutoTMF Commands HELP AUTOTMF-COMMANDS lists all AutoTMF commands available. autotmf-command [ DETAIL | EXAMPLES ] an AutoTMF command. Help displays the syntax and description of the command. Multi-word commands are entered with hyphens. For example, to obtain help on ADD AUTOTMFFILESET, type: HELP add-autotmffileset; DETAIL displays a description of the command parameters in addition to the syntax. EXAMPLES displays examples of the command usage.
NonStop AutoTMF Commands HISTORY HISTORY Lists the saved commands in the history buffer. These commands can be run using the FC or bang (!) commands. HISTORY count; count the number of commands to display. The default is 10. If fewer commands are in the history buffer, all commands are displayed. INFO ATMFFILESET Displays a configuration for a file set defined with the ADD ATMFFILESET command. INFO ATMFF[ILESET] [ file-set ] [, OBEYFORM ]; file-set the file set configured with ADD ATMFFILESET.
NonStop AutoTMF Commands INFO GLOBALS INFO GLOBALS Displays the list of configured AutoTMF global parameters. INFO GLOBAL[S] [,OBEYFORM]; OBEYFORM displays a list of the ALTER GLOBAL commands that were entered to modify the default global values. See command ALTER GLOBAL above for a list of global parameters and values. INFO LIBRARY Displays a list of processes that use the specified file as a user library. INFO LIBRARY library-object-file [, STOP ]; library-object-file a user library.
NonStop AutoTMF Commands INFO MAPDB INFO MAPDB Displays information about one or all configured MapDB subvolumes. Note that although AutoTMF does not support configuring remote MapDB subvolumes, remote MapDB entries can be present in the SysDB following a system migration. INFO MAPDB [ * | mapdb-subvol ]; * (or if omitted) All configured MapDB subvolumes mapdb-subvol A configured MapDB subvolume.
INFO PROGRAM NonStop AutoTMF Commands INFO PROGRAM Displays information about object files. If AutoTMF program attributes are configured for an object file in the file set specified, these attributes are also displayed.
NonStop AutoTMF Commands INFO PROGRAM used to analyze the prepared state of object files. See Preparing TNS Programs on page 3-4 for a description of the prepared state of a program. DETAIL displays an item-by-item analysis of each object file including: the type of the object file: TNS, TNS/R and so on. for SQL programs, whether the program is a valid SQL program, whether the program needs SQL compilation, and so on. the user library if there is one for this object.
NonStop AutoTMF Commands INFO PROGRAM PROC[EDURE]S [, OCA ] [, AXL ] lists the procedures in each object file. If AXL is specified, the procedures listed include the procedures invoked as a result of acceleration (millicode). If OCA is specified, the procedures listed include information from the OCAgenerated region in the object file.
NonStop AutoTMF Commands LABELDISPLAY (LD) LABELDISPLAY (LD) Displays label information for the specified table or view, such as catalog name, audit compression, columns data types, primary and alternate key columns, partitions, allocated extents, and so on. The command can be abbreviated to LD. L[ABEL]D[ISPLAY] sql-table [ ALLP[ARTS] | ALLI[NDEXES] ] ; sql-table a SQL table or View. ALLP[ARTS] displays the labels of all partitions of the table. ALLI[NDEXES] displays labels of all indexes of the table.
LISTLOCKS (LL) NonStop AutoTMF Commands OUTP[UT] | WRIT[E] displays files opened for write or update access only LISTLOCKS (LL) Displays granted and waiting lock requests for a file set. This command differs from FUP LISTLOCKS: AutoTMF LISTLOCKS has a more compact display and more options and allows the user to show locks for the entire system with one command.
NonStop AutoTMF Commands LISTLOCKS (LL) BYH[OLDER] display the locks by holder. Can be specified in conjunction with BYFile. DEADL[OCKS] [, RESOLVE ] display sets of granted and waiting lock requests that form a deadlock. Deadlocks might resolve themselves if the waiting requests are using timed I/O. Deadlocks usually involve multiple files on multiple volumes. Only deadlocks that are contained within the specified file-set are detected. Deadlocks that span multiple systems are not detected.
NonStop AutoTMF Commands LOG TXSTATUS displays a summary of all transactions or processes that are holding locks displayed by LISTLOCKS. WAITING displays all the lock holders and waiters for files and/or records that have at least one wait request outstanding. display-format FULL displays the full key, wrapped to multiple lines. Unprintable characters are shown in ? format, similar to the way Inspect displays binary data. Sequences of identical characters are displayed as *"".
NonStop AutoTMF Commands MODIFY AUTOTMF MODIFY AUTOTMF Copies all entries of the tables that were defined for system nodename and creates the same entries for the local system. First move the ATMFFILE and ATMFPROG tables to the MAPDB and then issue the MODIFY AUTOTMF command. If a configuration entry is already defined on the local system, that configuration entry is not copied from the original system.
NonStop AutoTMF Commands MONITOR copy the actual MAPDB tables verify that those tables are present on the local system make any changes that may be required to migrate the content of MAPDB tables to the local system. MODIFY MAPDBS REPLACE NODENAME nodename [ , LISTALL ]; nodename the Expand node name of the original system. LISTALL displays the entries that are being modified in the MAPDBS table. Note.
NSKFIXUP NonStop AutoTMF Commands is required when a program is compiled, bound, prepared, or moved, after a system cold load or when the user library is changed. This command does not perform the functions of the PREPARE command. The file need not be prepared. NSKFIXUP object-fileset, option; option is: { AXCEL { } } { LIBRARY library-file { { OCA { { TNS | TNSR | TNSE } } } } } object-fileset a TACL-style file name pattern specifying a collection of object files.
NonStop AutoTMF Commands OBEY Specifying the LIBRARY option implicitly restricts the processing of the command to the file type of the library object and is equivalent to specifying TNS, TNSR, or TNSE. OBEY Reads and runs a sequence of commands from another device. The commands are run serially until end-of-file is detected. An OBEY file may not contain an OBEY command. OBEY filename; filename a file containing a sequence of commands. OPEN Sets the current AutoTMF monitor process.
NonStop AutoTMF Commands PREPARE Only complete programs are prepared. Object files with no main procedure are either user libraries or components to be bound with other object files; these are skipped by the command.
NonStop AutoTMF Commands PREPARE If alternate-library does not contain the AutoTMF runtime library, an error message is displayed and the object files are not prepared. If this parameter in omitted, the user library is one of: The program’s current user library which must be bound with the AutoTMF runtime library. If the program is not bound with the AutoTMF runtime library, an error message is displayed and the object file is not prepared. The AutoTMF runtime library that is used by the CI.
PROGINFO (PI) NonStop AutoTMF Commands PREPARE preserves existing references to user libraries and checks that the references are properly prepared before preparing the programs. Note. Preparing a licensed privileged program removes the license attribute of the object file. You must re-license the program after it has been prepared. PROGINFO (PI) Displays information about object files.
NonStop AutoTMF Commands PURGEDATA the starting file to display, which is the first file that alphabetically follows the specified filename. .START filename the starting file to display. For a description of prep-info-option and object-info-option, see INFO PROGRAM entries. PID file-set Abbreviates PROGRAM INFO file-set DETAIL; PURGEDATA Clears data from a file. PURGEDATA file-name; file-name the name of a file. RESET Changes the AutoTMF CI environmental variables to their original settings.
RESET LOCAL NonStop AutoTMF Commands RESET LOCAL Resets the value of a local parameter to its default value, which is the value of the corresponding global parameter. RESET GLOBAL [ local-parameter | * ]; local-parameter parameter to reset. Local parameters are the same as global parameters. For a list of local and global parameters, see command description for ALTER GLOBAL on page 6-35. * resets all local parameters to their default (global) value. RUN[D] Runs a program during a CI session.
START MONITOR NonStop AutoTMF Commands START MONITOR Starts a AutoTMF monitor process for one MapDB or all MapDBs. START MONITOR [ process | mapdb-subvol ] [, option ]; option is: { { { { { { { BACKUP 0-to-15 HOMETERM file-name PRIMARY 0-to-15 PRIORITY 1-to-199 } } } } } } } process the name of the AutoTMF monitor process to launch. mapdb-subvol the MapDB subvolume. This is an alternative method to specify the process to be started.
NonStop AutoTMF Commands STATS the priority of the monitor process. STATS Scans an Enscribe file to determine the record count and distribution of record lengths. STATS is useful to determine if file records conform to expected lengths. STATS file-name; file-name an Enscribe file name. STATUS MONITOR Determines the status of the monitor process by sending the monitor inquiries. STATUS MONITOR [ * | [\sys.]process-name | mapdb ]; * all configured monitor processes. [\sys.
NonStop AutoTMF Commands STOP MONITOR STOP MONITOR Performs an orderly shutdown of the monitor process. STOP MONITOR [ process-name | mapdb ]; process-name the name of the AutoTMF monitor process to stop. The default is the current monitor for the session. mapdb a MapDB subvolume. This is an alternative method to specify the process to be stopped. STOP PROCESS This command attempts to stop a process in a way that allows AutoTMF to commit all active automatic transactions.
TRACE NonStop AutoTMF Commands TRACE Traces the activity of prepared programs. If dynamic tracing is enabled, which is the default, the runtime periodically checks a signal file for a tracing request, at the point when it intercepts calls to READUPDATE on $RECEIVE, and all forms of KEYPOSITION, OPEN, DELAY, READ, WRITEREAD calls and SERVERCLASS_SEND_. If dynamic trace is not enabled, the trace is initiated when a prepared process initializes its Escort segment and asks the Monitor for global information.
NonStop AutoTMF Commands TRACE option is { { { { { { { { { { { { { { { { { { { CLEAR } } DEBUG { TERM term-name | MYTERM }} } EDIT } } EXT 1-to-65535 } } FOR n } } MAXEXTENTS 16-to-978 } } MAXFILESIZE } } PROTECTED } } SEPARATE } } TRANSID } trace-index a value from 0 to 31 to assign an index to the trace operation. If trace-index is omitted, the runtime assumes trace-index 0. When STOP is specified, trace-index may be entered as “*, to stop all active traces.
NonStop AutoTMF Commands TRACE collects and displays the same information as the EXECUTE option, in addition to a trace of the data sent to, and returned from, the execution of intercepted I/O procedures. Each entry is timestamped and contains the name (or CPU, PIN) of the calling process. The traced data is formatted as follows: Character values are enclosed in quotes. All numeric values are displayed in ASCII decimal form, with a decimal point for scaled items.
NonStop AutoTMF Commands TRACE PROGRAM object-file-name | file-set captures trace information for all instances of the running program or set of programs. If this option is used in conjunction with the DEBUG option, the program must be uniquely specified, not as a pattern. PROCESS process-name | process-namelist | * PROCESS cpu-pin PROCESS cpu,* captures trace information for the selected set of processes. If PROCESS is used with the DEBUG option, the process must be uniquely specified (not as a pattern).
NonStop AutoTMF Commands TRACE sets a time limit of n minutes for tracing, starting when the command is entered. If n is set to 0, then there is no time limit. When the time limit expires, the trace configuration is reset and processes currently tracing with the configuration cease tracing. The default is 60 minutes. MAXEXTENTS 16-to-978 the total number of primary and secondary extents for the trace file. The default is 128. MAXFILESIZE a shorthand for EXT 2048 MAXEXTENTS 512, which is a 2 gigabyte file.
NonStop AutoTMF Commands UNPREPARE If DYNAMICTRACE is enabled, which is the default, tracing stops the next time the process checks the trace signal file, or when the process stops. If DYNAMICTRACE is not enabled, tracing continues until the trace time limit expires or the process stops. Note that to take effect, DYNAMICTRACE must be enabled prior to starting the application programs. UNPREPARE The UNPREPARE command restores a prepared object file to its original state.
NonStop AutoTMF Commands UNPREPARE If ALLOWDUPLICATES is omitted and the UNPREPARE detects this condition, an error message is displayed and the file is not unprepared LIBRARY alternate-library | NONE the file to set as the user library of the object files in the file set. NONE removes the library pointer from the object file.
NonStop AutoTMF Commands UPDATE Specifying the LIBRARY option implicitly restricts the processing of the command to the file type of the library object and is equivalent to specifying TNS, TNSR, or TNSE. Note. Unpreparing a licensed privileged program removes the license attribute of the object file. You must re-license the program after it has been unprepared. UPDATE Modifies records in an Enscribe file. The syntax for specifying records to update is the same as the COPY command.
UPDATE NonStop AutoTMF Commands The command displays the record in the format that is specified and allows the user to modify the record values.
NonStop AutoTMF Commands UPDATE n is a value between 1 and 255 that is less than or equal to the length of the FIRST KEY specified. COUNT num-records the number of records or rows to update. If omitted, all records are copied EXACT sets exact positioning on the record key (primary or alternate) specified in the FIRST KEY option. FIRST { ordinal-record-num } { KEY { record-spec | key-value } } { key-spec ALTKEY key-value [, key-value ] } the starting record of the input file to update.
NonStop AutoTMF Commands UPDATE the alternate key tag (a 2-byte string or a 16-bit integer) designating the alternate key to be used for positioning. ALTKEY key-value [, key-value ] the alternate key of the starting record or row. The format of key-value is described above.for entry-sequenced files, record-spec is the ordinalrecord-number. FROMLAST positions on the last record in the key range specified in the FIRST KEY option. REVERSE reads the input file from the starting record in reverse order.
NonStop AutoTMF Commands UPGRADE MAPDB UPGRADE MAPDB Creates additional tables in an existing MapDB. The tables are created if required for a new release of AutoTMF. The CI prompts you to issue the command when necessary. UPGRADE MAPDB subvol; subvol the MapDB subvolume to upgrade. VOLUME Changes the default volume and/or subvolume for filename expansion. VOLUME can be abbreviated to V. V[OLUME] [ volume | subvolume | volume.
STATUS NonStop AutoTMF Commands Activities that are logged include: Starting and stopping the log. Any errors obtaining configuration information from MapDB. Monitor opens and closes by requesting processes. The result of ATMFFILESET and ATMFPROGRAM configuration requests. Any mismatch between an AutoTMF runtime library and the monitor or MapDB. Fault tolerance process events, such as a backup process takeover. Local CPU failures and reloads. Remote network status changes Note.
NonStop AutoTMF Commands BACKUPCPU BACKUPCPU The BACKUPCPU command specifies the cpu for the monitor backup process. MONITOR BACKUPCPU [ cpu ] cpu the cpu number of the backup monitor process, in the range of 0 to 15, If cpu omitted, the backup process is terminated. SWITCH The SWITCH command causes the monitor primary and backup processes to exchange roles.
NonStop AutoTMF Commands HP NonStop AutoTMF Software User’s Guide—429952-016 6-98 SWITCH
A System Management System Database Map Database Monitor Process Configuring and Using an Alternate NonStop AutoTMF Environment Migrating the NonStop AutoTMF Software Configuration to a New System Runtime Library Host-language Runtimes in the Runtime Library Transporting Applications Version Checking Security and Availability Executing Prepared Applications System Database The System Database (SysDB) consists of two SQL tables: MAPDBS to store the description of map databases and associated monitor
Map Database System Management Map Database A Map Database (MapDB) contains AutoTMF configuration information for selected files and programs. In this release, the MapDB subvolume contains three SQL tables: ATMFATTR to store AutoTMF file configuration. ATMFPROG to store AutoTMF program configuration. REGISTRY to store NonStop AutoTMF default configuration parameter values referred to as locals. Locals are analogous to globals, but apply to one MapDB only.
Starting a Monitor System Management Configuring Monitor Priority All prepared programs will communicate with the monitor when a process is started. The monitor supplies all global configuration information and, if specified, any configuration for the program name. Further, all prepared programs will communicate with the monitor if an audited file is opened and there is some AutoTMF configuration for specific files.
System Management Configuring and Using an Alternate NonStop AutoTMF Environment In normal situations, the monitor process should be stopped only after all programs that access audited files have been stopped. The STOP MONITOR command should be used to stop the monitor. Configuring and Using an Alternate NonStop AutoTMF Environment You may configure an alternate AutoTMF environment for the following reasons: If you need to test or run different versions of AutoTMF on the same system.
Configuring an Alternate MapDB System Management product subvolume of your choice. In the example below, the user creates a product subvolume $DATA.ATMFAAO to test NonStop AutoTMF SPR labelled AAO 1> v y0581aao 2> INSTALL $data.atmfaao HP Nonstop(tm) AutoTMF(tm) Software File Installer UNPAK - File decompression program - T1255H01 - (2007-03-21) Archive version: 1 File Mode RESTORE Program - T9074H01 (20SEP2006) (AFJ) (C)2000 Compaq (C)2006 Hewlett-Packard Development Company, L.P. Drives: (\ATOM.
Configuring an Alternate MapDB System Management Create an alternate MapDB Use the CREATE MAPDB command specifying the alternate monitor process name. For example, to create a test MapDB that is called TSTMAPDB and uses the monitor $ZTST: AutoTMF 1? create mapdb tstmapdb,monitor $ztst; --- MapDB table $PRPC.TSTMAPDB.REGISTRY created. --- MapDB table $PRPC.TSTMAPDB.ATMFATTR created. --- MapDB table $PRPC.TSTMAPDB.ATMFPROG created. --- MapDB for AutoTMF created.
Configuring an Alternate SysDB System Management Issue the OPEN command after executing the CI: AutoTMF 2? open $ztst; Configuring an Alternate SysDB The SysDB has been engineered to be version-tolerant; multiple versions of AutoTMF can use the same SysDB concurrently. If however, you must completely segregate operating environments, you can also configure a separate SysDB and MapDB. To configure an alternate system database, the following steps are required: 1.
Migration Steps System Management The commands assume that SysDB tables, MapDB tables, configured object files and audited files are moved to same location on the new system. Only the system name and numbers are changed.
Runtime Library System Management 7. Issue MODIFY commands: MODIFY GLOBALS MODIFY AUTOTMF The object files or audited files reside in different locations The user first proceeds as describe above. The MODIFY AUTOTMF command makes the file and program attributes from source system visible to the INFO ATMFFILESET and INFO ATMFPROGRAMS commands. To complete the migration, proceed as follows: 1.
TNS/R Library System Management On NonStop S-series servers, use AXCEL and specify the UL option as follows: AXCEL $SYSTEM.ESCORT.ESCRUNTM, $SYSTEM.ESCORT.ESCRUNTM, UL; Note that the accelerator may produce a few warnings. On Integrity NonStop servers, use OCA as follows: OCA $SYSTEM.ESCORT.
HIGHPIN Attribute System Management HIGHPIN Attribute In order for a process to be run in a high pin (process number > 255), both the program object file and the user library file must have the HIGHPIN attribute set to ON. If either one is OFF, the process will occupy a low pin. The AutoTMF user library files are distributed with HIGHPIN ON. If you bind ESCRUNTM or link ESCRUNN or ESCRUNNL with another user library, the resulting user library loses the HIGHPIN attribute.
Updating the Runtime Library System Management 3. BIND and LINK the procedure into the runtime object files In Binder: select LIST * OFF SELECT CHECK PARAMETER STRONG SELECT SATISFY OFF ADD * FROM $DATA.ESCORT.ESCRUNTM ADD * FROM mnameo, DELETE SET LIKE $DATA.ESCORT.ESCRUNTM SET HIGHPIN ON BUILD ESCRUNTM ! nld mnamen $data.escort.escrunnl & -o $data.escort.escrunnm -ul -no_data_rearrange & -allow_duplicate_procs nld mnamen $data.escort.escrunn -o $data.escort.
TNS Host Runtime Language Libraries System Management Table A-1. HP Language Runtime Libraries included in the NonStop AutoTMF Software Runtime Product Product Number Release Subvol File COBOL 85 T9267 ZCOBOL85 C8LIB CRE T9280 ZCRERTL CFELIB CREKERN C T9549 ZC CLIB GPLIB T9600 ZGPLIB GPLIBXR GPLIBR (INITIALIZER only) COBOL 74 (T9251/T9261) is not currently supported.
TNS/R Host Runtime Language Libraries System Management TNS/R Host Runtime Language Libraries As described in Preparing TNS Programs, there are two classes of TNS/R AutoTMF runtime libraries: ESCRUNN/ESCRUNNT for PTAL only programs, ESCRUNNL and ESCRUNNM for COBOL and C programs. The following tables describe the host-language product release files that are included in the AutoTMF TNS/R runtime libraries: Table A-2.
TNS/E Host Language Runtime DLLs System Management 48> vproc escrunnm VPROC - T9617G03 - (07 AUG 2003) SYSTEM \NSKNED Date 20 JUL 2005, 16:38:39 Copyright 2003 Hewlett-Packard Development Company, L.P.
TNS/E Host Language Runtime DLLs System Management DLL Update Steps 1. Locate the DLL to install. The file ZREGPTR in $SYSTEM.SYSnn contains the name of the subvolume where the currently installed DLLs are running. 2. Use INFO PROGRAM (or PROGINFO (PI)) with the REBASE option to generate the ELD command that copies and rebases a public DLL to the AutoTMF operational subvolume. 3. Run the generated command. 4. Prepare the rebased DLL.
Transporting Applications System Management The macro displays the timestamp of the DLLs in the product subvolume and the timestamp of the system DLLs. It then prompts you to confirm you wish to proceed with the updates. The example below shows the execution of UPDDLLS in $SYSTEM.ESCORT: 13> volume $system.escort 14> run upddlls HP Nonstop(tm) AutoTMF(tm) DLL Update Installer Rebase and Prepare Public DLLs...
Security and Availability System Management 3. Whenever the CI opens a new monitor, the version checks are made for both the monitor process and the associated MapDB. 4. When a START MONITOR command is run, the monitor terminates if the CI version does not match the monitor’s version. The monitor also checks the version of MapDB. 5. When a prepared application process is running, each request from the AutoTMF runtime to the monitor contains a version number.
Object File Access Security System Management Object File Access Security Normally, only execute access authority is required to run a program. With AutoTMF, however, both read and execute access authority is required to run a prepared program. The AutoTMF runtime needs to determine if a program has embedded SQL and a few other important facts obtained by reading the object file.
Configuration Security System Management On the other hand, damage or destruction of the MapDB will also result in an outage of the application, so you might want to restrict update access of the MapDB to trusted users. Application programs have no need to access the MapDB; the monitor process provides all the MapDB information required by applications. Monitor Process Security The monitor process is an essential part of the application environment.
Executing Prepared Applications System Management The TRACE command can be secured to prevent exposure, as follows: The global setting for SECURETRACE should be ON, which is the default; use the ALTER GLOBAL command to configure SECURETRACE. The SysDB should be secured to prevent unauthorized users from altering this setting. When SECURETRACE is ON, the user who initiates a trace must be the process access ID of the processes that is being traced.
EMS Logging System Management ZESCTMPL: the EMS template file, to installed with the other system templates. ESCFLTR: the EMS filter file, which is used to configure an EMS distributor process to display only AutoTMF and TMF events. ZESCDDL: the DDL source for EMS definitions. To generate a DDL dictionary or an EMS definition file for a specific language, issue the following commands in the DDL compiler: ?NOLIST ?SOURCE $SYSTEM.ZSPIDEF.
B Special DEFINEs Introduction You can use Guardian DEFINEs to enable a number of AutoTMF optional features or to provide diagnostic and management information. Defines are useful to test an AutoTMF feature for a selected program, without altering the existing configuration. Configure AutoTMF features using the CI commands provided when possible, because this is easier and less error-prone than using DEFINEs.
DEFINE Types Special DEFINEs Table B-1. Runtime DEFINES (continued) DEFINE Name Description =_ESCORT_ATMF_TXHOLDOFF Specifies inter-request delay for holding transactions in active state. =_ESCORT_ATMF_WAITED Reverses the nowait mode set for completion of automatic transactions. =_ESCORT_AUDIT_RENAME Enables the renaming of audited files. =_ESCORT_DYNAMIC_TRC_OFF Disables dynamic tracing for a prepared program. =_ESCORT_DYNAMIC_TRC_ON Enables dynamic tracing of a prepared program.
Runtime DEFINES Special DEFINEs Runtime DEFINES =_ESCORT_ATMF_ISOLATION You can set the transaction isolation level for a program by specifying the =_ESCORT_ATMF_ISOLATION DEFINE. The DEFINE is added with the following TACL command: ADD DEFINE =_ESCORT_ATMF_ISOLATION, CLASS MAP, FILE value where value is one of WEAK, NORMAL or STRONG =_ESCORT_ATMF_MAXTIME You can set the maximum duration for automatic transactions with the =_ESCORT_ATMF_MAXTIME DEFINE.
=_ESCORT_ATMF_NOWAIT Special DEFINEs =_ESCORT_ATMF_NOWAIT you can commit automatic transactions in a NOWAIT fashion with the =_ESCORT_ATMF_NOWAIT DEFINE. The DEFINE is added with the following TACL command: ADD DEFINE =_ESCORT_ATMF_NOWAIT, CLASS MAP, FILE $X.Y.Z The FILE parameter is ignored. This DEFINE does not override the AUTOTMFFILESET parameter if a file is configured for SEPARATETX. =_ESCORT_ATMF_OFF You can disable AutoTMF for a process with the =_ESCORT_ATMF_OFF DEFINE.
=_ESCORT_ATMF_WAITED Special DEFINEs Automatic transactions are committed if: the process terminates (but not if the process is stopped), or the server is waiting for a request and the time since the last request exceeds the specified value, or the transaction has reached the limits set by the MAXTIME and MAXUPDATES parameters. Each transaction will span many server requests and updated records will be kept locked between server requests.
=_ESCORT_DYNAMIC_TRC_ON Special DEFINEs =_ESCORT_DYNAMIC_TRC_ON You can enable dynamic tracing of a program with the =_ESCORT_DYNAMIC_TRC_ON DEFINE. The program periodically checks the state of a signaling file to determine if tracing has been requested and will start tracing at that point. The DEFINE is added with the following TACL command: ADD DEFINE =_ESCORT_DYNAMIC_TRC_ON, CLASS MAP, FILE $X.Y.Z The FILE parameter is ignored.
=_ESCORT_OPTMZUNLOCKSOFF Special DEFINEs =_ESCORT_OPTMZUNLOCKSOFF Specify this define to disable the optimization of UNLOCKFILE operations. ADD DEFINE =_ESCORT_OPTMZUNLOCKSOFF, CLASS MAP, FILE $X.Y.Z The file parameter is ignored. This define overrides the value of the global parameter ATMFOPTIMIZEUNLOCK or of the ATMFPROGRAMS attribute OPTIMIZEUNLOCKS.
=_ESCORT_STATEMENT_DATA Special DEFINEs =_ESCORT_STATEMENT_DATA You can request a process trace that includes data records with the =_ESCORT_STATEMENT_DATA DEFINE. The DEFINE is added with the following TACL command: ADD DEFINE =_ESCORT_STATEMENT_DATA, CLASS MAP, FILE filename This define traces a superset of the information traced by the =_ESCORT_STATEMENT_TRACE. See the description of that DEFINE below.
=_ESCORT_SUPPRESS_AUDIT Special DEFINEs Edit trace files provide for the most efficient tracing, but an Edit trace file can only be opened by one process at a time. Tracing can be configured easily, and with more options, with the AutoTMF command interpreter; see TRACE on page 6-84. Using the TRACE command does not require changing the setup for executing the processes to be traced.
Command Interpreter DEFINEs Special DEFINEs Command Interpreter DEFINEs =_ESCORT_SYSDB This DEFINE is used for testing AutoTMF. It permits the user to establish an independent NonStop AutoTMF environment on the same system. In general, its use is not required and is not recommended in a production environment. In order to test a new version on AutoTMF in parallel with an existing version, you should use an alternate monitor and MapDB instead.
C Problem Resolution AutoTMF is designed to be invisible to an application program. AutoTMF is logically a layer that looks like the file system to the programs and like an application to the file system. Because the runtime is a library to the application programs, its operating environment is the application’s environment; thus, distinguishing between application problems and AutoTMF problems may be difficult.
Locking Problems Problem Resolution Other errors Program failures can be caused by configuration problems, by defects in the runtime library, or by defects in a program. If the runtime library detects a configuration problem or a version conflict, the runtime library sends a message to the home terminal of the program and to the EMS event log, commits the outstanding automatic transactions and abends the program.
Locking Problems Problem Resolution once locking is dictated by more stringent rules. Table C-1 below compares nonaudited and audited locking rules: Table C-1.
Incorrect Behavior Problem Resolution Long-running transactions result from locks that are not being released by the process, thus preventing AutoTMF from committing the automatic transaction. This situation is often found in cases where: Several files are updated under the common transaction and one file or another has a record locked at all times. A file managed under a separate transaction has at least one record locked at all times.
Diagnostic Tools Problem Resolution The home terminal for the monitor process is configured when the MapDB is created or when the monitor is started. See the description of the CI commands CREATE MAPDB, ALTER MONITOR and START MONITOR for details about configuring the monitor. The monitor activity can be logged to a file for cases where the monitor’s behavior is under suspicion.
EMS Log Problem Resolution EMS Log The AutoTMF monitor sends two classes of messages to the EMS log: Startup and shutdown information Critical events Events triggered by an application failure that is caused by AutoTMF are also sent to the EMS log. Consequently, the first place to look for the cause of a failure in the EMS log. To quickly view the NonStop AutoTMF events in the EMS log, start a distributor and use the ESCFLTR filter file to select the events.
Tracing Problem Resolution To list the values of system wide parameters, use the CI command INFO GLOBALS. To change any global parameter, use ALTER GLOBAL. To list the AutoTMF configuration for selected audited files (SEPARATEX, COMMONTX, and so on), use INFO ATMFFILESET. To configure files, use ADD ATMFFILESET. To list the AutoTMF configuration for selected programs, use INFO ATMFPROGRAMS. To configure programs, use ADD ATMFPROGRAMS.
Tracing Problem Resolution The CI TRACE command. By setting a tracing process DEFINEs: =_ESCORT_STATEMENT_TRACE, =_ESCORT_STATEMENT_DATA or =_ESCORT_STATEMENT_KEYS. You can trace a single process or all instances of a running program. Up to thirty two such traces, numbered 0 to 31, can be active simultaneously. To stop tracing, use TRACE STOP. Static vs. Dynamic Tracing You can trace a single process or a set of programs.
Tracing Problem Resolution Tracing to an Edit file is more efficient than the alternatives. However, an Edit file can only have one updater, so only one process at a time can be traced to an Edit file. Trace File Security Some restrictions on tracing may be applied for security reasons. The global parameter SECURETRACE is set to ON by default, which restricts tracing as described below.
Tracing Problem Resolution The trace shows the DEFINES that are active when the process begins execution and the operations to read the startup messages. The STARTUP and ASSIGN messages are formatted and displayed.. 14:44:03.782(8,102) *** Start Trace *** 14:44:03.823(8,102) Program $PRPC.RWCAWAIT.AWAIT, Term $Z31T (8,102) DEFINE =CAF,CLASS MAP,FILE=\FOXII.$PRPC.SOMEDATA.CAF (8,102) DEFINE =CAFKEYS,CLASS MAP,FILE=\FOXII.$PRPC.SOMEDATA.CAFKEYS (8,102) DEFINE =PBF,CLASS MAP,FILE=\FOXII.$PRPC.SOMEDATA.
Tracing Problem Resolution Audited - AutoTMF disabled or the file not configured for automatic transactions. OPEN($DATA.SOMEDATA.POSKEYS:1,RO/SH, ES) OPEN($DATA.SOMEDATA.CAF:2,RW/SH, KS, ATMF enabled) OPEN($DATA.SOMEDATA.PTDF:4,RW/SH, RL, ATMF common tx) OPEN($DATA.SOMEDATA.PBF:5,RW/SH, KS, ATMF common tx) OPEN($DATA.SOMEDATA.PRDF:6,RW/SH, KS, ATMF enabled) OPEN($DATA.SOMEDATA.
Reporting Problems Problem Resolution If a program abends or encounters unexpected errors and if the problem can be reproduced, trace the program to determine the sequence of procedure calls that lead to the failure. Reporting Problems To report a problem please collect supporting data and contact product support. This section lists the most commonly requested information to diagnose a problem. The user may be asked by the support specialist to collect additional information for specific problems.
Locking Problems, Long Running Transactions, Errors 35 or Performance Problems Problem Resolution If a prepared program fails, send the information listed above in addition to: The saveabend file (if applicable). The object file of the failing program. If the AutoTMF runtime has been combined with a user library, the object file of the user library. Locking Problems, Long Running Transactions, Errors 35 or Performance Problems The text of the message on the home terminal or EMS log.
Problem Resolution Locking Problems, Long Running Transactions, Errors 35 or Performance Problems HP NonStop AutoTMF Software User’s Guide—429952-016 C-14
D Error Messages In each message description, the following information appears: Message number Message text Cause—the condition or error that produced the message Effect—the effect of the condition or error on the system Recovery—the steps required to recover from a reported error Informational Messages 100 Monitor initialization Cause. The monitor process is initializing itself. Effect. The monitor process is not ready to service requests until initialization is completed. Recovery.
Informational Messages Error Messages 103 Monitor takeover Cause. The monitor primary process or its CPU has failed. Effect. The monitor backup process has taken over. The monitor is ready to service requests. Effect. Action: Informational message. No action is required. 104 Monitor backup created Cause. The monitor primary process has created a backup process. Effect. The monitor process is fault-tolerant. Recovery. Informational message. No action is required. 105 Monitor backup failed Cause.
Informational Messages Error Messages 107 Monitor status info Cause. The monitor process has displayed status information. Effect. Status information is placed in the EMS log. Recovery. Informational message only; no corrective action is needed. 141 Overdue commit on automatic transaction. Cause. A long-running automatic transaction has been detected. AutoTMF usually commits transactions after a short interval, but may not be able to do so if applications have long-lasting database locks.
Critical Event Messages Error Messages 150 AutoTMF message Cause. A message from AutoTMF has been generated. Effect. The nature of the problem is described in the message. Recovery. Corrective action depends on the message. Critical Event Messages 402 Monitor intentionally abended Cause. The monitor process has been intentionally abended to produce a saveabend file for problem diagnosis. Effect. The primary monitor process abends. The backup process takes over and continues processing. Recovery.
Critical Event Messages Error Messages 407 Version mismatch between the monitor and the runtime Cause. The Monitor process and the Runtime have incompatible versions. Effect. The program abends. Recovery. Verify that the runtime library and monitor are the same version. Contact product support for further assistance. 410 Error reading the object file Cause. The object file is secured to prevent reading by the user ID running the process. Effect. The program abends. Recovery.
Critical Event Messages Error Messages Effect. The process abends. Recovery. Since the product usually resizes the segment to satisfy memory requests, this error should not occur. Report this error to product support. 414 Allocate segment error Cause. Allocation of the extended segment failed. Effect. The process abends. Recovery. The error number is provided in the message. Determine the reason for the failure and correct it. 415 System operation failed Cause.
Critical Event Messages Error Messages 421 A file is not audited Cause. The AutoTMF global ATMFABENDNOAUDIT is enabled, the specified file is configured for automatic transactions, but the file is not audited. Effect. The process abends. Recovery. Audit the file or change the AutoTMF configuration. 422 Program calls unsupported SRL procedure Cause. Support for TNS/R native-mode programs required the elimination of a few public SRL procedures because linkable versions of the SRLs were not available.
Critical Event Messages Error Messages 430 Process was stopped by user request Cause. An authorized user requested a AutoTMF process stop. Effect. All automatic transactions were committed and the process has been abended. Recovery. Informational message only; no corrective action is needed. 433 System contains more logical processors than permitted by AutoTMF license. Cause. The referenced product is licensed for a maximum number of logical NSK processors (MAXCPUS).
Action Event Messages Error Messages 439 Error trying to write to trace file Cause. The runtime attempted to start tracing but was unable to write a trace file due to the specified file system error. Effect. The process continues without tracing. Recovery. Correct the cause of the file system error. For a dynamic trace, reissue the TRACE command. 600 Monitor start unauthorized Cause. An unauthorized user attempted to start the monitor process. Effect. The monitor process is not started. Recovery.
Action Event Messages Error Messages HP NonStop AutoTMF Software User’s Guide—429952-016 D-10
Glossary automatic transaction. A transaction that has been generated by NonStop AutoTMF software. common transaction. An automatic transaction that is used for accesses on all file opens that are not configured for separate transactions. nontransactional program. A program that does not manage or inherit transactions. See transactional program. prepared program. An object file that has been prepared to use NonStop AutoTMF software. process transaction.
transactional program.
Index Symbols $ZESC 2-8 A AFTER option in INFO PROGRAM 6-65 option in PREPARE 6-76 option in PROGINFO 6-78 option in UNPREPARE 6-89 ALL option in HELP 6-60 ALLOWDUPLICATES option in PREPARE 6-76 option in UNPREPARE 6-89 Alternate swap volumes A-21 ATMF option in ALTER GLOBAL 6-36 ATMFABENDNOAUDIT option in ALTER GLOBAL 6-36 ATMFATTR A-2 ATMFAUDITRENAME option in ALTER GLOBAL 6-36 ATMFAUTOCOMMIT option in ALTER GLOBAL 6-36 ATMFCOMMONTX option in ALTER GLOBAL 6-37 ATMFISOLATION option in ALTER GLOBAL 6-37 AT
AXCEL option in NSKFIXUP 6-74 AXLCHECK option in INFO PROGRAM 6-66 B BACKUP option in ALTER MAPDB 6-44 option in ALTER MONITOR 6-45 option in CREATE MAPDB 6-54 option in START MONITOR 6-81 BLOCKIN option in COPY 6-50 BLOCKOUT option in COPY 6-51 BUFFERED option in ALTER FILE 6-33 BYFILE option in LISTLOCKS 6-69 BYHOLDER option in LISTLOCKS 6-70 C CATALOG option in CREATE MAPDB 6-54 option in CREATE SYSDB 6-56 CLEAR option in TRACE 6-87 CLEARONPURGE option in ALTER FILE 6-34 COBOL option in INFO PROGRAM 6-
EDIT option in TRACE 6-87 EMSCOLLECTOR option in ALTER GLOBAL 6-42 ENABLE Preparing 5-4 Entry-sequenced files 6-9, 6-10, 6-23, 6-24, 6-40 Error 49 Unstructured Access 4-15 Error 80 Unstructured Access 4-15 Error Handling errors returned from Enscribe C-1 Error handling CI failures C-5 diagnostic commands C-6 error 75 C-2 locking C-7 messages D-1–D-9 monitor error logging C-4 monitor failures C-5 reporting problems C-12 ESCERROR 2-3 ESCFLTR 2-3 EMS event management A-22, C-6 ESCHELP 2-3 ESCMON 2-3 ESCORT 2-3
I Installation creating MapDB 2-7 creating SysDB 2-6 disabling NonStop AutoTMF software 2-10 first time 2-2 INSTALL macro 2-2 ISV subvolume 2-2 licensing 2-7 new version of NonStop AutoTMF software 2-9 updating cold load procedures 2-9 ISOLATION option in ADD ATMFPROGRAMS 6-14 option in ALTER ATMFPROGRAMS 6-27 Isolation Normal 4-7 Strong 4-7 Weak 4-7 K KEYS option in TRACE 6-86 KMSF option in ALTER GLOBAL 6-43 L Large Transfer 4-15 LIBRARY option in NSKFIXUP 6-74 option in PREPARE 6-76 option in UNPREPARE
option in HELP 6-61 Monitor priority A-3 Moving prepared programs A-17 N NO VERIFIEDWRITES option in ALTER FILE 6-34 NOITENT option in LISTLOCKS 6-70 NOPROCESS option in LISTLOCKS 6-70 NOPURGEUNTIL option in ALTER FILE 6-34 NOTRANSACTION option in LISTLOCKS 6-70 NOTX option in ADD ATMFFILESET 6-9 option in ADD ATMFPROGRAMS 6-16 option in ALTER ATMFFILESET 6-22 option in ALTER ATMFPROGRAMS 6-29 option in LISTLOCKS 6-70 NOTX option in ALTER ATMFFILESET 6-22 Nowait transactions 4-7 NOWAITTX option in ADD ATMF
Queue Files 5-7 option in COPY 6-50 RECORDTX option in ADD ATMFFILESET 6-10 option in ADD ATMFPROGRAMS 6-16 option in ALTER ATMFFILESET 6-23 option in ALTER ATMFPROGRAMS 6-29 RECOUT option in COPY 6-52 REGISTRY In MapDB A-2 In SysDB A-1 RESETBROKEN option in ALTER FILE 6-34 RESOLVE option in LISTLOCKS 6-70 REVERSE option in COPY 6-50 option in UPDATE 6-94 REWINDIN option in COPY 6-50 REWINDOUT option in COPY 6-52 R S READNULLRECS option in ADD ATMFFILESET 6-9 option in ALTER ATMFFILESET 6-23 READTHRULOC
option in ALTER ATMFPROGRAMS 6-30 SEPARATETX option in ALTER ATMFFILESET 6-23 SERIALWRITES option in ALTER FILE 6-34 SETMODE 141 Unstructured access 4-15 SHARE option in UPDATE 6-94 SHARE option in COPY 6-51 Shared Runtime Libraries 3-5 SKIPMATCH option in COPY 6-51 option in UPDATE 6-94 SKIPNULLRECS option in ADD ATMFFILESET 6-10 option in ALTER ATMFFILESET 6-24 Spooler preparing 5-5 spool data file creation 5-5 SPOOLER files 5-3 SRL 3-5 START option in INFO PROGRAM 6-65 option in PREPARE 6-77 option in PR
TRACING option in HELP 6-61 Tracing C-7 security C-9 static and dynamic C-8 to edit file C-9 with debugging C-8 TRANSID option in TRACE 6-88 TRIM option in COPY 6-51 TXSTATUS option in LISTLOCKS 6-71 TXTIMEOUT option in ADD ATMFFILESET 6-11, 6-18 option in ALTER ATMFFILESET 6-24 option in ALTER ATMFPROGRAMS 6-31 U Unilateral Aborts 4-16 UNLOADIN option in COPY 6-51 UNLOADOUT option in COPY 6-52 UNPREPARED option in INFO PROGRAM 6-66 UNRESOLVED option in INFO PROGRAM 6-67 UNSTROUT option in COPY 6-52 UNSTRU
