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-010 NonStop AutoTMF AAO (Update 8) April 2008 429952-011 NonStop AutoTMF AAP (Update 9) April 2009 429952-012 NonStop AutoTMF AAQ (Update 10) January 2010 429952-013 NonStop AutoTMF AAR (Update 11) October 2010 429952-014 NonStop AutoTMF AAS (Update 12) June 2011
Legal Notices © Copyright 2011 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
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-5 C++ Programs 3-6 Programs referencing other SRLs 3-6 Preparing TNS/E Programs 3-6 Preparing Programs that Have a User Library 3-7 TNS and TNS/R Programs 3-7 TNS/E Programs 3-7 Preparing a User Library 3-8 Intercept Libraries 3-8 Combining a User Library with the NonStop AutoTMF Runtime 3-8 TNS Library 3-8 TNS/R Library 3-9 TNS/E Library 3-9 Changing the User Library with Prepare 3-9 Preserving the Modification Timestamp of Object Files 3-10 Preserving License Attri
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-14 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 Limitations 4-19 Program Logic 4-19 SQL tables 4-19 Number of concurrent transactions 4-19 5.
NonStop AutoTMF and Process Pairs 5-8 How to Use AutoTMF with Process Pairs 5-8 Recommendation 5-8 6.
INFO ATMFFILESET 6-60 INFO ATMFPROGRAMS 6-60 INFO GLOBALS 6-61 INFO LIBRARY 6-61 INFO LOCALS 6-61 INFO MAPDB 6-62 INFO PREPARE 6-62 INFO PROGRAM 6-63 LABELDISPLAY (LD) 6-66 LISTFILEOPENS (LFO) 6-66 LISTLOCKS (LL) 6-67 LOG 6-68 MODIFY AUTOTMF 6-69 MODIFY GLOBALS 6-69 MODIFY MAPDBS 6-70 MONITOR 6-70 NSKFIXUP 6-71 OBEY 6-72 OPEN 6-72 OUT 6-72 PREPARE 6-72 PROGINFO (PI) 6-75 PID file-set 6-76 PURGEDATA 6-76 RESET 6-76 RESET GLOBAL 6-76 RESET LOCAL 6-77 RUN[D] 6-77 START MONITOR 6-78 STATS 6-79 STATUS MONITOR 6-
VOLUME 6-91 Monitor Commands 6-91 LOG 6-91 STATUS 6-92 SECURITY 6-92 BACKUPCPU 6-93 SWITCH 6-93 A.
TNS Host Runtime Language Libraries A-12 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-1
=_ESCORT_OPTIMIZEUNLOCKS B-6 =_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.
Tracing time limit C-9 Trace Interpretation C-9 Problem Reporting C-11 NonStop AutoTMF Software Component Failures C-11 Prepared Program Incorrect Behavior or Failure C-12 Locking Problems, Long Running Transactions, Errors 35 or Performance Problems C-12 D.
HP NonStop SQL DDL Replicator User’s Guide—545799-005 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 Vaious minor corrections have been added throughout the document, based on reader input.
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.
About This Manual General Syntax Notation 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.
About This Manual Change Bar Notation 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 ]...
About This Manual Change Bar Notation HP NonStop AutoTMF Software User’s Guide—429952-014 xvi
1 Introduction to HP NonStop AutoTMF Software This section of the manual discusses the following topics: • • An overview of HP NonStop AutoTMF software 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. NonStop AutoTMF software generates transactions on behalf of application programs. The TMF product views NonStop AutoTMF software like any other transactional program.
Installation and Basic Management Installing NonStop AutoTMF Software Installing NonStop AutoTMF Software Have your NonStop AutoTMF software 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.
Installation and Basic Management Install NonStop AutoTMF Software Files 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.
Installation and Basic Management Start an EMS distributor 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-54. 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-52 for details about this command. When the monitor process is started, the following messages should be displayed by the EMS distributor: 15:58 11MAY11 099,05,093 $ZESC 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 7. Restart the NonStop AutoTMF monitor process. 8. Restart the application programs.
Installation and Basic Management Removing NonStop AutoTMF Software Removing NonStop AutoTMF Software 1. If you have prepared and bound your application’s user libraries with the NonStop AutoTMF runtime library, restore those user libraries with copies that are unprepared and unbound. 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.
Installation and Basic Management Shortcut to Run ESCORT CI HP NonStop AutoTMF Software User’s Guide—429952-014 2-12
3 Preparing Programs Overview Preparing Programs Preparing Programs that Have a User Library Preserving the Modification Timestamp of Object Files Preserving License Attribute when Preparing Privileged Programs Tips for Preparing Programs Diagnosing Preparation Errors Overview Before preparing any programs, ensure that you have a working version of the application to be prepared. Read the suggestions at the end of this section before preparing any programs.
Preparing Programs Preparing Programs Preparation does not invalidate object-file acceleration or SQL compilation, nor does preparation change binder or linker attributes such as HIGHPIN, HIGHREQUESTERS, INSPECT, and so on, or the Binder time stamp or the size of the object file. However, preparation removes LICENSE attribute of an object file, unless one of 2 conditions are met: • • the PREPARE is performed by SUPER.
Preparing Programs Preparing TNS Programs Use the INFO PROGRAM command to verify the state of the object file, for example: AutoTMF 7? info program myobj.batchobj,detail; $DATA.MYOBJ.BATCHOBJ Apr 29 2004, 14:07 Accelerated TNS Program User Library $SYSTEM.ESCORT.
Preparing Programs Preparing TNS/R Programs calls made by those libraries. These libraries also exist in the “system library” created by SYSGEN, but you cannot intercept calls that are made to the system library. If a TNS program currently calls a procedure in the system library routine at run time, the calls are automatically retargeted to the ESCRUNTM user library if the ESCRUNTM user library contains the same procedure. Any COBOL, C, or TAL TNS program can use the ESCRUNTM library.
Preparing Programs Preparing TNS/R Programs Table 3-1. TNS/R Program Classes and NonStop AutoTMF Libraries: Program Class Runtime library Linkable library Preparation Processing COBOL/C ESCRUNNM ESCRUNNL SRLs references eliminated; all calls intercepted in NonStop AutoTMF UL.
Preparing Programs Preparing TNS/E Programs C++ Programs C++ programs reference both the C++ and C SRLs. However, the C++ and C libraries have conflicting externals and cannot be linked together in the same library; therefore, a NonStop AutoTMF user library cannot intercept calls from C++ programs. If a program references the C++ SRL, the PREPARE command: • • Will direct calls to Enscribe, causing GPLIB to be intercepted by the ESCRUNNT user library.
Preparing Programs Preparing Programs that Have a User Library AutoTMF runtime DLL (ESCRUNDL) as a DLL of the program. The example below shows the preparation of program $data.testobj.egetemp: AutoTMF 3? prepare egetemp; --- $DATA.TESTOBJ.EGETEMP preparation complete --- AutoTMF DLL $TOOL.AUTOTMF.ESCRUNDL AutoTMF 4? info program egetemp,detail; $DATA5.JOJOTEST.EGETEMP May Executable TNS/E Program Not Preset; Nonempty Liblist DLLs: escrundl Pre-public DLL path: $TOOL.
Preparing Programs Preparing a User Library Preparing a User Library By default, the PREPARE command only modifies executable object files. If you attempt to prepare a program that references a user library, the following message is displayed: AutoTMF 1? prepare $DATA.LIB.TINFOB; *Warning* Object file $DATA.LIB.TINFOB has no MAIN procedure. * 1658 * A user library must be prepared with the USERLIB option * * and then bound with the AutoTMF runtime library.
Preparing Programs • Changing the User Library with Prepare For NonStop S-series servers: AXCEL myuserlb,myuserlb; UL • For NonStop Integrity servers: OCA myuserlb; UL 4. If the NonStop AutoTMF EMS message template file ZESCTMPL has not been installed, move a copy of ZESCTMPL into the same subvolume as the user library. It might be needed to generate messages to the home terminal. TNS/R Library 1. Create or locate a linkable version of the user library. 2.
Preparing Programs Preserving the Modification Timestamp of Object Files To force PREPARE to change a library in an object file, use the LIBRARY option. The specified library must contain the NonStop AutoTMF runtime library. The LIBRARY option can be used when you need to change the location of a user library (even if the object file is already prepared). AutoTMF 1? prepare myobj.myprog,library newobj.myusrlib; --- $DATA.MYOBJ.MYPROG preparation complete --- AutoTMF runtime library $DATA.NEWOBJ.
Preparing Programs Tips for Preparing Programs 1. In binder, type the following commands: ADD * FROM escort SET LIKE escort ALTER CALLABLE^SET^LICENSE, CALLABLE ON BUILD escort! 2. At the TACL prompt, SQL compile escort: SQLCOMP/ IN escort/ NOREGISTER ON 3. Log on as SUPER.
Preparing Programs Diagnosing Preparation Errors Diagnosing Preparation Errors The INFO PROGRAM command displays the preparation status of each object file: • • • • • Unprepared Calls – Program calls to procedures that are normally intercepted by NonStop AutoTMF software are not retargeted. Either the program was not prepared, or was prepared using an earlier release of NonStop AutoTMF software. In either case, issue the PREPARE again. No User Library – The program has no user library.
4 Configuring Automatic Transaction Processing Configuration Commands You can configure NonStop AutoTMF software features using commands to set global options and to specify file names and program names that use NonStop AutoTMF software options. See ALTER GLOBAL on page 6-34, ADD ATMFFILESET on page 6-6, and ADD ATMFPROGRAMS on page 6-12 for complete use and syntax descriptions of these commands. The ADD commands have corresponding INFO, ALTER and DELETE commands.
Configuring Automatic Transaction Processing Command Options 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.
Configuring Automatic Transaction Processing Command Options Table 4-1.
Configuring Automatic Transaction Processing Automatic Transactions 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, NonStop AutoTMF software analyzes all fileaccess 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 Transaction Isolation Transaction isolation influences the duration of automatic transactions to reduce the effect of automatic transactions outside the process that started them. There are three levels of isolation: • • Weak isolation commits active automatic transactions whenever a server process waits for or replies to a request on $RECEIVE.
Configuring Automatic Transaction Processing Audited Attribute Hiding The only drawback to using nowait transactions is that the process continues to perform work without knowing if a unilateral abort has occurred. A server process replies to a requestor, but the database update operations the server process has performed may be backed out by a system-level failure.
Configuring Automatic Transaction Processing Audited File Renaming Audited File Renaming Attempts to rename a file while the file is audited are rejected by the file system with an error. Each audit record contains the name of the disk file being updated, so renaming a file can make backout operations fail. NonStop AutoTMF software can rename audited files by performing a complex series of open, close, and alter operations. A file that is opened by other processes cannot be renamed. Note.
Configuring Automatic Transaction Processing Requiring Files to Be Audited Requiring Files to Be Audited The NonStop AutoTMF software manages access to audited files in a manner transparent to application programs. If the audited attribute is removed from any of the audited files it is managing, the application will continue to operate without any problem because NonStop AutoTMF software does not attempt to generate transactions for unaudited files.
Configuring Automatic Transaction Processing • • • • • • • • • Suppressing Inherited Transactions 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. The transaction has no effect on the program.
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. NonStop AutoTMF software 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 used to lock records that are not already locked, READUPDATELOCK may be used with RECORDTX. 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 Configuration To enable waited I/O, configure both the ATMFFileset and ATMFProgram WAITEDIO attributes. A program configured using the WAITEDIO option uses Waited I/O only for audited files that are also configured for Waited I/O. 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.
Configuring Automatic Transaction Processing Large-Transfer Writing Unstructured access to either unstructured files or structured files also permits large transfers to be used if the appropriate BULK I/O interfaces are used. When a file is audited, some the following rules apply to the use of unstructured access: • • • A structured audited file cannot be opened for write access. An attempt to perform such an open results in an error 80.
Configuring Automatic Transaction Processing Transaction File (TFILE) supports large transfers, it takes advantage of the feature to provide optimum performance. NonStop AutoTMF software cannot emulate unstructured writes (either with large or small transfers) to audited structured files. Transaction File (TFILE) The TMF Application Programmers Guide describes the use of the TFILE ($TMP) to manage multiple transactions in a multi-threaded program.
Configuring Automatic Transaction Processing • • • • Forced Transaction Commit Avoiding sending transactional requests to other processes so that those processes cannot cause unilateral aborts. Detecting unilateral aborts and abending the process. The program will not make database updates that assume that earlier updates were completed.
Configuring Automatic Transaction Processing Setting Transaction Time Out Eventually, a long running transaction can reach the TMF AutoAbort limit, at which point the transaction is unilaterally aborted and uncommitted updates are rolled back, causing potentially irrecoverable data loss.
Configuring Automatic Transaction Processing Limitations Note that the AutoTMF AutoCommit time limit always applies. If you configure a TXTIMEOUT value that exceeds the AutoCommit time limit, adjust the AutoCommit accordingly. Limitations Program Logic • A program must make one call to OPEN or to FILE_OPEN_ before the first call to any procedure that requires an open file number. Such procedures include READ, WRITE, KEYPOSITION, CONTROL, SETMODE, and so on.
Configuring Automatic Transaction Processing Number of concurrent transactions HP NonStop AutoTMF Software User’s Guide—429952-014 4-20
5 Usage Guidelines This section describes typical uses and limitations of NonStop AutoTMF software, 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.
Usage Guidelines Auditing Unstructured Files In a mixed NonStop AutoTMF software and application controlled transaction environment, you must specify to NonStop AutoTMF software which files are managed by NonStop AutoTMF software and which files are managed by the application. To insure that NonStop AutoTMF software generates transactions for 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.
Usage Guidelines Preparing HP Utilities operation, which sets the EOF to zero, is audited and can be rolled forward or replicated properly. 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.
Usage Guidelines ENFORM For example: > ESCORT PREPARE test.fup!;EXIT; --- $DATA.TEST.FUP preparation complete --- AutoTMF User Library $DATA.ESCORT.ESCRUNTM • 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.
Usage Guidelines ENABLE ENABLE ENABLE is both a transactional and nontransactional program. ENABLE generates transactions if your ENABLE program specifies SET TMF ON. ENABLE checks the file attributes of database files; if a file is audited and the program has not specified 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.
Usage Guidelines SORT and SORTPROG file to the spooler control file. Because the rebuilt control file is first created as a temporary file, the CREATEAUDIT attribute is not applied and the rebuilt file is not created as an audited file. If for any reason a rebuild of the Spooler is necessary, proceed as follows: 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.
Usage Guidelines • • Preparing Third-party Applications The LOCKFILE operation is performed under one automatic transaction. Writes to the file do not acquire record locks when the entire file is locked. All writes to the file are performed under a single transaction, which is committed when the file is closed. If the file is not closed before the TMF AutoAbort time limit, the program fails. Tracing shows the alteration of the open exclusion and the deblocking operations. Caution.
Usage Guidelines NonStop AutoTMF and Process Pairs NonStop AutoTMF and Process Pairs If AutoTMF is used, no error 75 occurs on a takeover because AutoTMF creates new automatic transactions in the backup process to access audited files. However, when a primary process fails, automatic transactions may or may not have been aborted, depending on the cause of the failure.
6 NonStop AutoTMF Software 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.
NonStop AutoTMF Software Commands Command Syntax 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.
NonStop AutoTMF Software Commands Command Summary Table 6-1.
NonStop AutoTMF Software Commands Command Summary Table 6-1.
NonStop AutoTMF Software Commands Command Summary Table 6-1. NonStop AutoTMF Software Commands (continued) Command Name Description UPDATE Updates a file record UPGRADE MAPDB Creates additional MapDB tables when required VOLUME Sets the CI session volume and subvolume Table 6-2.
NonStop AutoTMF Software 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 specifies the name of the NonStop AutoTMF software monitor process to be stopped.
NonStop AutoTMF Software 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 Software Commands ADD ATMFFILESET If n = 0, AUTOCOMMIT is disabled for this file set. If a program fails to unlock a record and prevents NonStop AutoTMF software 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. To prevent such data loss, AUTOCOMMIT should be set to a value that is less than the TMF AUTOABORT timer value, about 5 minutes or so.
NonStop AutoTMF Software 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 a NonStop AutoTMF software 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 Software Commands ADD ATMFFILESET IF NOWARNLONGTX is specified, SEPARATETX must also be specified 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 Software Commands ADD ATMFFILESET configures files to be accessed by the programs using separate automatic transactions. Specify SEPARATETX when automatic transactions for a file are always to be used (even if the process has its own transaction) and the transaction should be managed separately from transactions for other files.
NonStop AutoTMF Software Commands ADD ATMFPROGRAMS If WAITEDIO is specified for a NOWAIT file open, AutoTMF automatically performs an AWAITIO operation immediately following the various forms of 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.
NonStop AutoTMF Software Commands ADD ATMFPROGRAMS 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 Software Commands ADD ATMFPROGRAMS n is a number between 300 and 30000 but stored internally in minutes, so if specified in seconds some rounding of the value may occur. The default unit is minutes. If n = 0, AUTOCOMMIT is disabled for this program set.
NonStop AutoTMF Software Commands • ADD ATMFPROGRAMS 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 overrides the value of the global parameter ATMFISOLATION. MAXTIME 1-to-n-seconds specifies that transactions should be committed after n seconds. The value of n should be a power of 2 (1,2,4,8,16,32,...) in the range of 1 to 4096.
NonStop AutoTMF Software Commands ADD ATMFPROGRAMS NOWAIT[TX] returns control to the application without waiting for the transaction to be fully committed. Automatic transactions generated by the programs are committed in nowait mode. The status of a nowait transaction is checked by the runtime when the next transaction for the file is started or when the process terminates.
NonStop AutoTMF Software Commands ADD ATMFPROGRAMS 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. The RECORDTX program attribute can be specified in addition to other attributes, such as COMMONTX or SEPARATETX. The other attributes are ignored if RECORDTX is specified for both the file and the program.
NonStop AutoTMF Software Commands • • • ADD ATMFPROGRAMS 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. Programs that make use of TMF may depend on the correct operation of the calls that are eliminated by setting this option.
NonStop AutoTMF Software Commands ALTER ATMFFILESET For further details, see Changing Nowait IO to Waited IO on page 4-13 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 Software Commands ALTER ATMFFILESET instructs NonStop AutoTMF software to commit all automatic transactions if the separate transaction for this file exceeds the specified time limit. n is a number between 300 and 30000 but stored internally in minutes, so if specified in seconds some rounding of the value may occur. The default unit is minutes. If n = 0, AUTOCOMMIT is disabled for this file set.
NonStop AutoTMF Software Commands ALTER ATMFFILESET 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 a NonStop AutoTMF software automatic transaction. Note.
NonStop AutoTMF Software Commands ALTER ATMFFILESET Users should exercise caution when suppressing the long transaction warning and do so only if the cause for the delayed commit is well understood. 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.
NonStop AutoTMF Software Commands ALTER ATMFFILESET enables or disables (NO SEPARATETX) the use of separate transactions by the programs to access an audited file. SEPARATETX is used when an automatic transaction is to be generated even if the process has its own transaction and when the transaction must be managed separately from transactions for other files.
NonStop AutoTMF Software Commands ALTER ATMFFILESET converts NOWAIT I/O operations to WAITED I/O operations. If WAITEDIO is specified for a NOWAIT file open, AutoTMF automatically performs an AWAITIO operation immediately following the various forms of READ and WRITE. After the AWAITIO completes, AutoTMF commits any outstanding transactions using the usual algorithms as directed by the configuration.
NonStop AutoTMF Software 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 Software Commands ALTER ATMFPROGRAMS n is a number between 300 and 30000 but stored internally in minutes, so if seconds is entered, some rounding of the value may occur. The default unit is minutes. The default unit is minutes. If n = 0, AUTOCOMMIT is disabled for this program set.
NonStop AutoTMF Software Commands • • ALTER ATMFPROGRAMS 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 overrides the value of the global parameter ATMFISOLATION.
NonStop AutoTMF Software Commands ALTER ATMFPROGRAMS NOTX | NO NOTX disables or enables (NO NOTX) the generation of automatic transactions for audited file access. NOWAIT[TX] | NO NOWAIT[TX] | WAITED[TX] Enables or disables (NO NOWAIT[TX] or WAITED[TX]) the use of nowait transactions. If enabled, separate transactions are committed in nowait mode and the status of a nowait transaction is checked by the runtime when the next transaction for the file is started or when the process terminates.
NonStop AutoTMF Software Commands ALTER ATMFPROGRAMS The RECORDTX program attribute can be specified in addition to other attributes, such as COMMONTX or SEPARATETX. The other attributes are ignored if RECORDTX is specified for both the file and the program. If RECORDTX is specified for a program, but not the file, then the other options, such as COMMONTX or SEPARATETX, will be in effect. For further details on the use of RECORDTX, see paragraph Record-Level Transactions on page 4-12.
NonStop AutoTMF Software Commands • • • ALTER ATMFPROGRAMS 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 reports that files are not audited. 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.
NonStop AutoTMF Software Commands ALTER FILE For this option to take effect, specify it both as a program attribute and as a file attribute using ADD ATMFFILESET or ALTER ATMFFILESET. For further details, see Changing Nowait IO to Waited IO on page 4-13. Note. Removing an option specifying NO is different from setting it to the default value. The default value setting overrides the global (or local) value. Removing the option adopts the setting from the global (or local) setting.
NonStop AutoTMF Software Commands ALTER FILE specifies whether TMF auditing is on. If NO is specified, auditing is off. The audit mode is propagated to alternate key files. AUDITCOMPRESS | NO AUDITCOMPRESS specifies whether or not compression of audit records is occurring for this file. BUFFERED | NO BUFFERED specifies whether 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.
NonStop AutoTMF Software Commands ALTER FILE Guardian security string. SERIALWRITES | NO SERIALWRITES specifies whether serial writes to the mirrored disk are performed. If NO SERIALWRITES is specified, parallel writes are performed. The default is NO SERIALWRITES. VERIFIEDWRITES | NO VERIFIEDWRITES sets the mode of file writes: verified or not verified. The default is NO VERIFIEDWRITES.
NonStop AutoTMF Software Commands ALTER GLOBAL ALTER GLOBAL Sets or changes global configuration values for NonStop AutoTMF software. Global parameters are the default for all environments.
NonStop AutoTMF Software Commands { { { { { { { { ALTER GLOBAL SECURETRACE { ON | OFF } [SWAP]KMSF { ON | OFF } SWAPVOL[0] local-disk-volume SWAPVOL1 local-disk-volume SWAPVOL2 local-disk-volume SWAPVOL3 local-disk-volume } } } } } } } } parameter-and-value ATMF { ON | OFF } enables or disables automatic transaction processing. The default is ON if the system has been licensed to use NonStop AutoTMF software.
NonStop AutoTMF Software Commands ALTER GLOBAL The default AUTOCOMMIT value is 115 minutes, based on the default TMF AUTOABORT time limit of 120 minutes. The runtime monitors automatic transactions to determine those that have been active for more than the selected time. The process must be active, either receiving messages on $RECEIVE or performing database positioning operations. Processes in a "wait" state are not monitored for long transactions.
NonStop AutoTMF Software Commands ALTER GLOBAL ATMFMAXTIME 1-to-n-seconds specifies that transactions should be committed after n seconds. 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 16 seconds. MAXTIME can also be set for separate transactions and for selected programs. See ADD ATMFFILESET and ADD ATMFPROGRAMS for details.
NonStop AutoTMF Software Commands ALTER GLOBAL returns control to the application without waiting for the transaction to be fully committed. Automatic transactions are committed in nowait mode. The status of a nowait transaction is checked by the runtime when the next transaction for the file is started or when the process terminates. The default is OFF. NOWAIT can also be set for separate transactions and for selected programs. See ADD ATMFFILESET and ADD ATMFPROGRAMS for details.
NonStop AutoTMF Software Commands ALTER GLOBAL ATMFSKIPNULLRECS instructs the NonStop AutoTMF software runtime to ignore zero-length records when reading sequentially through an audited entry-sequenced file. 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.
NonStop AutoTMF Software Commands • • ALTER GLOBAL the server is waiting for a request and the time since the last request exceeds the specified value. the transaction reaches the limits set by the MAXTIME and MAXUPDATES parameters. Each transaction spans many server requests and updated records are kept locked between server requests. If the batch process sends work to many server processes, the servers processes must access different database records or a deadlock may occur.
NonStop AutoTMF Software Commands ALTER MAPDB specifies the default maximum number of simultaneous open requests supported by the monitor process. The default is 512. SECURETRACE ON | OFF controls tracing of processes by users other than the owner of the process. The default is ON. [SWAP]KMSF { ON | OFF } enables or disables KMSF swapfile allocation.
NonStop AutoTMF Software Commands ALTER MAPDB These attributes can also be changed using the ALTER MONITOR command. ALTER MAPDB [subvol] { , option } ; option is { { { { { { { { { BACKUP cpu-number HOMETERM [ file-name | NONE ] MONITOR process-name PRIMARY cpu-number PRIORITY process-priority } } } } } } } } } subvol name of MapDB subvolume. The default is the current CI session MapDB. option BACKUP cpu-number cpu (in the range of 0 to 15) of the backup monitor processes.
NonStop AutoTMF Software Commands ALTER MONITOR priority (in the range of 1 to 199) for the monitor process. Used when the monitor process is started. 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.
NonStop AutoTMF Software Commands ALTER LOCAL 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. PRIMARY cpu-number cpu (in the range of 0 to 15) of the primary monitor processes. Used when the monitor process is started. PRIORITY process-priority priority (in the range of 1 to 199) for the monitor process. Used when the monitor process is started.
NonStop AutoTMF Software Commands COMMENT (or “--”) the arithmetic operator +, -, * or / COMMENT (or “--”) Causes the command interpreter to ignore the remainder of the current line. COMMENT may not appear within the lines of a multiline command. In addition to the explicit COMMENT command, a pair of dashes (– –) causes the CI to ignore all remaining text on the current line. A dash-dash comment may appear within a multiline command.
NonStop AutoTMF Software Commands COPY COPY Similar to the FUP COPY command with enhancements. Copies records from an input file to an output file.
NonStop AutoTMF Software Commands COPY out-options is: { { { { { { { { { { { { { { { { { { { BLOCKOUT n 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 file containing data to be copied; can be a process, tape, terminal, or disk file.
NonStop AutoTMF Software Commands COPY 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. The first record in a file is record zero. The maximum value is 4294967295.
NonStop AutoTMF Software Commands COPY in-options BLOCKIN n number of bytes between 1 and 32767 in an input block that is requested in a single physical read operation. When BLOCKIN is not specified, the RECIN value is used. The default is device dependent: 80 bytes for terminal, 132 bytes for process and unstructured files. COMPACT | NO COMPACT zero length records should (or should not) be skipped when copied to the output file. The default is COMPACT.
NonStop AutoTMF Software Commands COPY This option applies to key sequenced files only. TRIM trim-character delete any trailing character matching the trim-character. The character is specified in ASCII using quotation marks or as an integer in the range 0 to 255. UNLOADIN | NO UNLOADIN (magnetic tapes only) input tape is unloaded (or not unloaded) after the tape has been rewound. The default is UNLOADIN. This also applies to labeled tapes.
NonStop AutoTMF Software Commands COPY output tape is rewound (or not rewound) after the copy operation has completed. If NO REWINDOUT is specified, the tape remains positioned without rewinding. The default is REWINDOUT. This option also applies to labeled tapes. UNLOADOUT | NO UNLOADOUT (magnetic tapes only) output tape is unloaded (or not unloaded) after rewinding. The default is UNLOADOUT. This option also applies to labeled tapes.
NonStop AutoTMF Software Commands CPUS display the output in ASCII format. This option is ignored if combined with OCTAL, HEX, DECIMAL or BYTE display options. NO HEAD omit the heading preceding each record when one of the display-options is specified. CPUS Displays the CPU configuration of a node. CPUS [ node-name ]; node-name a node in the Expand network.
NonStop AutoTMF Software Commands CREATE MAPDB option CATALOG SQL-catalog SQL catalog where MapDB tables are to be registered. The catalog may also be specified either by the VOLUME command or by specifying a catalog attribute for the =_DEFAULTS define. If omitted, the tables are registered in the catalog where SysDB tables are registered. SECURE "rwep" specifies the READ, WRITE, EXECUTE and PURGE security attributes of MapDB tables.
NonStop AutoTMF Software Commands CREATE SYSDB CREATE SYSDB Creates the system database (SysDB). SysDB is a set of SQL tables in a subvolume named ESCSYSDB. These tables are updated with registration information and the list of MapDBs and associated monitor processes. SysDB must be created on an audited volume. CREATE SYSDB [ ON volume ] [, option ]; option is { CATALOG SQL-catalog { { SECURE "rwep" } } } volume volume where SysDB will be created. The default is $SYSTEM.
NonStop AutoTMF Software Commands DELAY DEPTH 2-to-n the number of lock holders (file opens or transactions) between 2 and 10 that participate in the deadlock. Each holder will be waiting for a unique record locked by another holder, creating an n-way deadlock. Additional records are locked that are not material to the deadlock. The default depth is 2. TIME 2-to-n-seconds the duration of the deadlock in seconds where n is between 2 and 600. The deadlock can be stopped by entering the break key.
NonStop AutoTMF Software Commands DEQUEUE DEQUEUE Reads records from a source Enscribe queue file and writes them to a destination file. DEQUEUE syntax and functionality are is similar to the COPY command. The main difference between the commands is that instead of a READ of the source file, it uses READUPDATELOCK operations that dequeue (and therefore delete) each record as it is read from the queue file. Full transaction support is provided.
NonStop AutoTMF Software Commands EXIT EXIT Terminates the CI session. A CTRL–Y has the same effect. EXIT The EXIT command does not require a semi-colon and cannot be followed by any text. FACTOR Calculates the prime factors of the integer part of the expression. Accepts any numeric expression. FACTOR constant; constant an ordinary decimal constant with or without a decimal point, or a binary, octal, or hexadecimal integer prefixed by %b, %, or %h respectively.
NonStop AutoTMF Software Commands FILES file-set is a TACL-style file name pattern specifying a collection of files. If file-set is not specified, the current subvolume is assumed. DETAIL displays detailed information. If not specified, the CI displays one line of information per file in the file-set. FID file-set abbreviates FILEINFO DETAIL. FILES Displays the 8-character filename of the files in the file-set. FILES file-set; file-set is a TACL-style file name pattern specifying a collection of files.
NonStop AutoTMF Software Commands HELP requests the list of all NonStop AutoTMF software commands available. autotmf-command [ DETAIL | EXAMPLES ] is a NonStop AutoTMF software 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; If DETAIL is specified, a description of the command parameters is displayed in addition to the syntax.
NonStop AutoTMF Software 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 will be displayed. INFO ATMFFILESET Displays a configuration for a file set defined with the ADD ATMFFILESET command.
NonStop AutoTMF Software Commands INFO GLOBALS INFO GLOBALS Displays the list of configured NonStop AutoTMF software 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 filename [, STOP ]; filename the name of a user library.
NonStop AutoTMF Software Commands INFO MAPDB INFO MAPDB Displays information about the MapDBs in SysDB. INFO MAPDB { * | subvolume } [, DETAIL ]; * displays information for all configured MapDBs. subvolume an existing MapDB subvolume. INFO PREPARE Lists the external procedure names that are retargeted by the PREPARE command and intercepted by the NonStop AutoTMF software runtime library.
NonStop AutoTMF Software Commands INFO PROGRAM INFO PROGRAM Displays information about object files. If NonStop AutoTMF software program attributes are configured for an object file in the file set specified, these attributes are also displayed.
NonStop AutoTMF Software Commands INFO PROGRAM used to analyze the prepared state of object files. See Preparing TNS Programs on page 3-3 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 Software 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 Software 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.
NonStop AutoTMF Software Commands LISTLOCKS (LL) 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: NonStop AutoTMF software 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 Software Commands LOG 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. RESOLVE allows the user to resolve the detected deadlock. The command displays a list of transactions and processes that are participants in the deadlock and prompts the user to select either a process to abend, or a transaction to abort to resolve the deadlock.
NonStop AutoTMF Software Commands MODIFY AUTOTMF CLEAR clears the log file of existing data. STOP closes the current log file and stops logging. 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.
NonStop AutoTMF Software Commands MODIFY MAPDBS MODIFY MAPDBS Copies all entries of MAPDBS that were defined for the system called nodename and creates the same entries for the local system. If the MAPDBS entry is already defined on the local system, the MAPDBS entry is not copied from the original system.
NonStop AutoTMF Software Commands NSKFIXUP NSKFIXUP Operates on a collection of object files to alter the user library, causing the operating system to perform an object file fixup. Prevents the “library conflict” error that can occur when multiple instances of the same program are started concurrently and an operating system fixup is required. The fixup is required when a program is compiled, bound, prepared, or moved, after a system cold load or when the user library is changed.
NonStop AutoTMF Software Commands OBEY restricts the processing of the command to the designated object file types: code 100 files for TNS, code 700 files for TNSR, and code 800 files for TNSE. 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.
NonStop AutoTMF Software 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 Software Commands PREPARE specifies an object file to set as the user library for the prepared object file. If the library does not contain the NonStop AutoTMF software 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 NonStop AutoTMF software runtime library.
NonStop AutoTMF Software Commands PROGINFO (PI) about how to combine the NonStop AutoTMF software runtime library with a user library. 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 Software Commands PURGEDATA AFTER filename specifies the starting file to display, which is the first file that alphabetically follows the specified filename. .START filename specifies 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.
NonStop AutoTMF Software Commands RESET LOCAL 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-34. * resets all local parameters to their default (global) value. RUN[D] Runs a program during a CI session.
NonStop AutoTMF Software Commands START MONITOR START MONITOR Starts a NonStop AutoTMF software monitor process for one MapDB or all MapDBs. START MONITOR [ process | mapdb ] [, option ]; option is: { { { { { { { { PRIMARY cpu-number BACKUP cpu-number PRIORITY process-priority HOMETERM file-name } } } } } } } } process specifies the name of the NonStop AutoTMF software monitor process to be started. mapdb specifies the subvolume of a MapDB.
NonStop AutoTMF Software Commands STATS Note that internally, the default hometerm of the monitor is $ZHOME, as displayed by the TACL command STATUS $, because an 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. STATS Scans an Enscribe file to determine the record count and distribution of record lengths.
NonStop AutoTMF Software Commands STOP MONITOR STOP MONITOR Performs an orderly shutdown of the monitor process. STOP MONITOR [ process-name | mapdb ]; process-name specifies the name of the NonStop AutoTMF software monitor process to be stopped. The default is the current monitor for the session. mapdb specifies the subvolume of a MapDB. This is an alternative method to specify the process to be stopped.
NonStop AutoTMF Software Commands TRACE TRACE Specifies a NonStop AutoTMF software trace configuration and enables tracing. When prepared programs begin execution, the programs access the trace configuration and, if enabled, begin tracing selected operations to the trace file. Programs already executing are not traced unless dynamic tracing is enabled (see ALTER GLOBAL). Tracing is a diagnostic tool for NonStop AutoTMF software problems.
NonStop AutoTMF Software Commands TRACE filename | MYTERM name of the trace file. If MYTERM is specified, the trace output is sent to the home terminal of the CI that issued the TRACE command. The trace file is opened when the process is started. The file must be a process or an entry-sequenced file with a record length of at least 132 bytes. If the file does not exist, the file is created. The trace file can be an Edit file.
NonStop AutoTMF Software Commands ° TRACE When a security violation occurs, tracing is turned off. These rules guarantee that unauthorized users cannot gain access to data. DATA In addition to KEYS, trace entire data records sent to or returned from read, write and update operations.
NonStop AutoTMF Software Commands TRACE process-spec PROGRAM object-file-name | fileset restrict tracing to a selected 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,* restrict tracing to a selected set of processes. If PROCESS is used with the DEBUG option, the process must be uniquely specified (not as a pattern).
NonStop AutoTMF Software Commands UNPREPARE specifies that each process trace should be written to a separate trace file. Otherwise, all traces for a specific trace definition are written to the file specified in the command. When specifying SEPARATE, the trace file name must not have more than five characters, as a three-digit sequence number is appended to the file name to create unique file names (TRACE000, TRACE001, and so on). The collection of trace files is managed by the user.
NonStop AutoTMF Software Commands UNPREPARE a file pattern that describes a collection of application program files to be prepared. option AFTER filename specifies the starting file for the operation. The first file unprepared is the one that alphabetically follows the specified filename. ALLOWDUPLICATES forces the unprepare of an object file that contains a mixture of prepared and unprepared procedures and for which this operation will create duplicate external references.
NonStop AutoTMF Software Commands UPDATE By specifying NOOCA, UNPREPARE never processes a program using OCA. If the preparation invalidates the OCA region, the program runs in interpreted mode, unless you manually process the program using OCA. START filename specifies the starting file to unprepare in fileset. name, the current NonStop AutoTMF software runtime library will be used.
NonStop AutoTMF Software Commands UPDATE The command displays the record in the format that is specified and allows the user to modify the record values.
NonStop AutoTMF Software Commands UPDATE COUNT num-records is the number of records or rows to be copied. If omitted, all records are copied EXACT requests 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. If omitted, the update starts at the first record or row in the input file.
NonStop AutoTMF Software Commands UPDATE 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. SHARE opens the file in share exclusion mode. The default is protected.
NonStop AutoTMF Software Commands UPGRADE MAPDB UPGRADE MAPDB Creates additional tables in an existing MapDB. The tables are created if required for a new release of NonStop AutoTMF software. The CI prompts you to issue the command when necessary. UPGRADE MAPDB subvol; subvol the name of 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.
NonStop AutoTMF Software Commands STATUS 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 NonStop AutoTMF software runtime library and the monitor or MapDB. Fault tolerance process events, such as a backup process takeover. Local CPU failures and reloads.
NonStop AutoTMF Software Commands BACKUPCPU The command option is a single character and is a Guardian security specifier. The command requestor must match the monitor process access id at the specified security level. BACKUPCPU The BACKUPCPU command specifies the cpu for the monitor backup process. MONITOR BACKUPCPU [ cpu ] cpu specifies the cpu number where the monitor backup process should be started. If omitted, the backup process is terminated.
NonStop AutoTMF Software Commands HP NonStop AutoTMF Software User’s Guide—429952-014 6-94 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
System Management Map Database Map Database A Map Database (MapDB) contains NonStop AutoTMF software configuration information for selected files and programs. In this release, the MapDB subvolume contains three SQL tables: • • • ATMFATTR to store NonStop AutoTMF software file configuration. ATMFPROG to store NonStop AutoTMF software program configuration. REGISTRY to store NonStop AutoTMF default configuration parameter values referred to as locals.
System Management Starting a Monitor 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 NonStop AutoTMF software 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.
System Management Configuring an Alternate MapDB alternate 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.
System Management Configuring an Alternate MapDB 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.
System Management • Configuring an Alternate SysDB 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 NonStop AutoTMF software 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.
System Management Migration Steps 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.
System Management Runtime Library 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.
System Management TNS/R Library 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.
System Management HIGHPIN Attribute 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 NonStop AutoTMF software 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.
System Management Updating the Runtime Library 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.
System Management TNS Host Runtime Language Libraries 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.
System Management TNS/R Host Runtime Language Libraries TNS/R Host Runtime Language Libraries As described in Preparing TNS Programs, there are two classes of TNS/R NonStop AutoTMF software 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 NonStop AutoTMF software TNS/R runtime libraries: Table A-2.
System Management TNS/E Host Language Runtime DLLs 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.
System Management TNS/E Host Language Runtime DLLs 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.
System Management Transporting Applications 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...
System Management Security and Availability 2. The CI also requests the version from the selected monitor process, which must match the expected version in the CI. 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.
System Management Object File Access Security additional Enscribe operations), but these operations are subject to the same security control as provided for all application access to data. Object File Access Security Normally, only execute access authority is required to run a program. With NonStop AutoTMF software, however, both read and execute access authority is required to run a prepared program.
System Management Configuration Security responsibly. Often, personnel in operations, development, testing, and production control update the MapDB for their own file and program entities. 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.
System Management • Executing Prepared Applications A user specifies DEFINEs, such as =_ESCORT_STATEMENT_TRACE when executing the process; in this case, the user has control over tracing and debugging. The TRACE command can be secured to prevent exposure, as follows: • The global setting for SECURETRACE should be ON; use the ALTER GLOBAL command to set the SECURETRACE setting. The SysDB should be suitably secured to prevent unauthorized users from altering this setting.
System Management EMS Logging DEFINE. See ALTER GLOBAL on page 6-34 and =_ESCORT_EMS_COLLECTOR on page B-6 for details. A template called ZESCTMPL is shipped with the product and can be combined with existing templates to use with Viewpoint or any EMS distributor. The EMS filter file ESCFLTR is supplied in the product subvolume to configure an EMS distributor process to display NonStop AutoTMF software events.
B Special DEFINEs Introduction You can use Guardian DEFINEs to enable a number of NonStop AutoTMF software optional features or to provide diagnostic and management information. Defines are useful to test a NonStop AutoTMF software feature for a selected program, without altering the existing configuration. Configure NonStop AutoTMF software features using the CI commands provided when possible, because this is easier and less error-prone than using DEFINEs.
Special DEFINEs DEFINE Types Table B-1. Runtime DEFINES (continued) DEFINE Name Description =_ESCORT_ATMF_OFF Disables NonStop AutoTMF software for a prepared program. =_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_ON Enables dynamic tracing of a prepared program.
Special DEFINEs Runtime 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.
Special DEFINEs =_ESCORT_ATMF_NOWAIT =_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 NonStop AutoTMF software for a process with the =_ESCORT_ATMF_OFF DEFINE.
Special DEFINEs =_ESCORT_ATMF_WAITED 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.
Special DEFINEs =_ESCORT_DYNAMIC_TRC_ON =_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.
Special DEFINEs =_ESCORT_OPTMZUNLOCKSOFF =_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.
Special DEFINEs =_ESCORT_STATEMENT_DATA =_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.
Special DEFINEs =_ESCORT_SUPPRESS_AUDIT 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 NonStop AutoTMF software command interpreter; see TRACE on page 6-81. Using the TRACE command does not require changing the setup for executing the processes to be traced.
Special DEFINEs Command Interpreter DEFINEs Command Interpreter DEFINEs =_ESCORT_SYSDB This DEFINE is used for testing NonStop AutoTMF software. 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 NonStop AutoTMF software in parallel with an existing version, you should use an alternate monitor and MapDB instead.
C Problem Resolution HP NonStop AutoTMF software is designed to be invisible to an application program. NonStop AutoTMF software 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 NonStop AutoTMF software problems may be difficult.
Problem Resolution Program Failures (ABEND) If NonStop AutoTMF software stops or aborts a program due to a TMF environmental error, a message describing the error sent to the EMS log to alert the operator of the failure. Other errors Program failures can be caused by configuration problems, by defects in the runtime library, or by defects in a program.
Problem Resolution Locking Problems Locking Problems Contention and Deadlocks Audited files are subject to different locking protocols than non-audited files. When accessing audited files, locking is enforced by TMF to maintain data integrity. An application that was not designed for audited files may incur concurrency problems once locking is dictated by more stringent rules. The table below compares nonaudited and audited locking rules: Table C-1.
Problem Resolution Incorrect Behavior Long-Running Transactions Long-running transactions can lead to unilateral aborts if the TMF AutoAbort time limit is reached. Unilateral aborts can have a severe impact on an application because all non-committed updates from a process are rolled back. Long-running transactions result from locks that are not being released by the process, thus preventing NonStop AutoTMF software from committing the automatic transaction.
Problem Resolution NonStop AutoTMF Software Errors NonStop AutoTMF Software Errors Monitor Process Errors The monitor is a fault-tolerant process pair designed to be continuously available. All warning and error messages reported by the monitor are displayed on the monitor’s home terminal or, if no home terminal has been configured explicitly, to the default EMS collector.
Problem Resolution • • • EMS Log Because Enscribe procedure calls are intercepted by the NonStop AutoTMF runtime, you can set a breakpoint on an Enscribe procedure such as OPEN, READ, WRITE, so on, and step into the procedure code. If this occurs, just step out of the procedure code and resume debugging. You can see the open of the TFILE ($TMP) when displaying the files opened by the program.
Problem Resolution CI Commands Checking the Environment To check the overall processing environment, use the CI command ENV. ENV displays the names of the current MapDB, SysDB, the Guardian OS release version, the NonStop sever serial number of the system, and so on. Checking the NonStop AutoTMF Software Configuration You have options for processing of newly audited files. These options are configured as NonStop AutoTMF software file attributes and program attributes or global parameters.
Problem Resolution Tracing entire system, use the CI LISTLOCKS (LL) (or LL) command. Use the DEADLOCK option of the command to display deadlocks. Tracing NonStop AutoTMF software offers a comprehensive set of tracing options. Virtually all file system and TMF operations performed by a program can be traced along with the data that is read and written by the program. Tracing also displays the active DEFINEs, assigns, the startup message, and process termination messages.
Problem Resolution Tracing Tracing and Debugging Tracing is often done in conjunction with the debugging of a program using INSPECT. In addition to the standard TACL and Pathway DEBUG options, you can specify that a program should be started in INSPECT with the CI TRACE command. Tracing can be particularly useful when debugging Pathway servers since tracing does not require modifying the server configuration. Trace Files The trace output can be written to a disk file or terminal.
Problem Resolution Tracing 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.
Problem Resolution • Problem Reporting Audited - NonStop AutoTMF software disabled or 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.
Problem Resolution Prepared Program Incorrect Behavior or Failure If ESCMON or ESCORT fail, send the following information: • • • • • A description of the problem, its repeatability, frequency (if applicable), how to recreate the problem, and so on. The saveabend file. The text of the message on the home terminal or EMS log. VPROC output of the failing ESCMON or ESCORT object file. The global parameter values output by INFO GLOBALS.
Problem Resolution • • • Locking Problems, Long Running Transactions, Errors 35 or Performance Problems The output of LISTLOCKS (LL) at the time of the problem occurred to identify which file is in contention. A trace of the programs that access the file in contention. The output of INFO ATMFFILESET, INFO ATMFPROGRAMS and INFO GLOBALS to understand the file and program attributes and global settings.
Problem Resolution Locking Problems, Long Running Transactions, Errors 35 or Performance Problems HP NonStop AutoTMF Software User’s Guide—429952-014 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.
Error Messages Informational 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.
Error Messages Informational 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.
Error Messages Critical Event Messages 150 AutoTMF message Cause. A message from NonStop AutoTMF software 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.
Error Messages Critical Event 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.
Error Messages Critical Event 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.
Error Messages Critical Event Messages 421 A file is not audited Cause. The NonStop AutoTMF software 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 NonStop AutoTMF software configuration. 422 Program calls unsupported SRL procedure Cause.
Error Messages Action Event Messages 430 Process was stopped by user request Cause. An authorized user requested a NonStop AutoTMF software 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).
Error Messages Action Event Messages 704 Access to AutoTMF monitor failed Cause. Request to a monitor process returned an error. Effect. The process abends. Recovery. Correct the cause of the error displayed in the message and restart the process.
Error Messages Action Event Messages HP NonStop AutoTMF Software User’s Guide—429952-014 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.
Glossary transactional program.
Index Symbols $ZESC 2-8 A AFTER option in INFO PROGRAM 6-63 option in PREPARE 6-73 option in PROGINFO 6-76 option in UNPREPARE 6-86 ALL option in HELP 6-58 ALLOWDUPLICATES option in PREPARE 6-73 option in UNPREPARE 6-86 Alternate swap volumes A-21 ATMF option in ALTER GLOBAL 6-35 ATMFABENDNOAUDIT option in ALTER GLOBAL 6-35 ATMFATTR A-2 ATMFAUDITRENAME option in ALTER GLOBAL 6-35 ATMFAUTOCOMMIT option in ALTER GLOBAL 6-35 ATMFCOMMONTX option in ALTER GLOBAL 6-36 ATMFISOLATION option in ALTER GLOBAL 6-36 AT
AXCEL option in NSKFIXUP 6-71 AXLCHECK option in INFO PROGRAM 6-64 B BACKUP option in ALTER MAPDB 6-42 option in ALTER MONITOR 6-43 option in CREATE MAPDB 6-53 option in START MONITOR 6-78 BLOCKIN option in COPY 6-49 BLOCKOUT option in COPY 6-50 BUFFERED option in ALTER FILE 6-32 BYFILE option in LISTLOCKS 6-67 BYHOLDER option in LISTLOCKS 6-67 C CATALOG option in CREATE MAPDB 6-53 option in CREATE SYSDB 6-54 CLEAR option in TRACE 6-84 CLEARONPURGE option in ALTER FILE 6-32 COBOL option in INFO PROGRAM 6-
EDIT option in TRACE 6-84 EMSCOLLECTOR option in ALTER GLOBAL 6-40 ENABLE Preparing 5-5 Entry-sequenced files 6-10, 6-11, 6-22, 6-23, 6-39 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-5 monitor failures C-5 reporting problems C-11 ESCERROR 2-3 ESCFLTR 2-3 ESCHELP 2-3 ESCMON 2-3 ESCORT 2-3 ESCORT CI diagnostic commands
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-26 Isolation Normal 4-7 Strong 4-7 Weak 4-7 K KEYS option in TRACE 6-82 KMSF option in ALTER GLOBAL 6-41 L Large Transfer 4-15 LIBRARY option in NSKFIXUP 6-71 option in PREPARE 6-73 option in UNPREPARE 6-86 LICENSE Monitor STATUS 6-92
in ALTER FILE 6-33 NOITENT option in LISTLOCKS 6-68 NOPURGEUNTIL option in ALTER FILE 6-32 NOTX option in ADD ATMFFILESET 6-9 option in ADD ATMFPROGRAMS 6-15 option in ALTER ATMFFILESET 6-21 option in ALTER ATMFPROGRAMS 6-28 NOTX option in ALTER ATMFFILESET 6-21 Nowait transactions 4-7 NOWAITTX option in ADD ATMFFILESET 6-9 option in ADD ATMFPROGRAMS 6-16 option in ALTER ATMFFILESET 6-21 option in ALTER ATMFPROGRAMS 6-28 NOWARNLONGTX option in ADD ATMFFILESET 6-9 option in ADD ATMFPROGRAM 6-16 option in ALT
library conflict 3-12 object code 3-1 privileged programs 3-2 size of the object file 3-2 status of an object file 3-12 user libraries 3-7 PROGRAMS option in INFO PROGRAM 6-65 Q Queue Files 5-7 R READNULLRECS option in ADD ATMFFILESET 6-10 option in ALTER ATMFFILESET 6-22 READTHRULOCK option in ALTER ATMFFILESET 6-22 READTHRULOCKS option in ADD ATMFFILESET 6-10 option in ADD ATMFPROGRAMS 6-16 REBASE option in INFO PROGRAM 6-65 Rebased public DLLs DLL Update Steps A-16 Purpose A-15 UPDDLLS macro 2-3, A-16
in COPY 6-49 Shared Runtime Libraries 3-4 SKIPMATCH option in COPY 6-49 option in UPDATE 6-90 SKIPNULLRECS option in ADD ATMFFILESET 6-11 option in ALTER ATMFFILESET 6-23 Spooler preparing 5-5 spool data file creation 5-5 SPOOLER files 5-3 SRL 3-4 START option in INFO PROGRAM 6-63 option in PREPARE 6-74 option in PROGINFO 6-76 option in UNPREPARE 6-87 STATUS Monitor command 6-92 STOP option in TRACE 6-85 STOPONTMFERR option in ADD ATMFPROGRAMS 6-17 option in ALTER ATMFPROGRAMS 6-29 SUMMARY option in LISTLOC
with debugging C-9 TRANSID option in TRACE 6-85 TRIM option in COPY 6-50 TXSTATUS option in LISTLOCKS 6-68 TXTIMEOUT option in ADD ATMFFILESET 6-11, 6-18 option in ALTER ATMFFILESET 6-23 option in ALTER ATMFPROGRAMS 6-30 U Unilateral Aborts 4-16 UNLOADIN option in COPY 6-50 UNLOADOUT option in COPY 6-51 UNPREPARED option in INFO PROGRAM 6-64 UNRESOLVED option in INFO PROGRAM 6-65 UNSTROUT option in COPY 6-51 UNSTRUCTURED option in COPY 6-50 UPDATE option in COPY 6-51 UPSHIFT option in COPY 6-48 USERLIB opt
