RDF System Management Manual
Table Of Contents
- RDF System Management Manual
- What’s New in This Manual
- About This Manual
- 1 Introducing RDF
- RDF Subsystem Overview
- RDF Processes
- RDF Operations
- Reciprocal and Chain Replication
- Available Types of Replication to Multiple Backup Systems
- Triple Contingency
- Loopback Configuration (Single System)
- Online Product Initialization
- Online Database Synchronization
- Online Dumps
- Subvolume- and File-Level Replication
- Shared Access DDL Operations
- EMS Support
- SMF Support
- RTD Warning Thresholds
- Process-Lockstep Operation
- Support for Network Transactions
- RDF and NonStop SQL/MX
- Zero Lost Transactions (ZLT)
- Monitoring RDF Entities With ASAP
- 2 Preparing the RDF Environment
- 3 Installing and Configuring RDF
- 4 Operating and Monitoring RDF
- 5 Managing RDF
- Recovering From File System Errors
- Handling Disk Space Problems
- Responding to Operational Failures
- Stopping RDF
- Restarting RDF
- Carrying Out a Planned Switchover
- Takeover Operations
- Reading the Backup Database
- Access to Backup Databases in a Consistent State
- RDF and NonStop SQL/MP DDL Operations
- RDF and NonStop SQL/MX Operations
- Backing Up Image Trail Files
- Making Online Dumps With Updaters Running
- Doing FUP RELOAD Operations With Updaters Running
- Exception File Optimization
- Switching Disks on Updater UPDATEVOLUMES
- 6 Maintaining the Databases
- 7 Online Database Synchronization
- 8 Entering RDFCOM Commands
- 9 Entering RDFSCAN Commands
- 10 Triple Contingency
- 11 Subvolume- and File-Level Replication
- 12 Auxiliary Audit Trails
- 13 Network Transactions
- Configuration Changes
- RDF Network Control Files
- Normal RDF Processing Within a Network Environment
- RDF Takeovers Within a Network Environment
- Takeover Phase 1 – Local Undo
- Takeover Phase 2 – File Undo
- Takeover Phase 3 – Network Undo
- Takeover Phase 3 Performance
- Communication Failures During Phase 3 Takeover Processing
- Takeover Delays and Purger Restarts
- Takeover Restartability
- Takeover and File Recovery
- The Effects of Undoing Network Transactions
- Takeover and the RETAINCOUNT Value
- Network Configurations and Shared Access NonStop SQL/MP DDL Operations
- Network Validation and Considerations
- RDF Re-Initialization in a Network Environment
- RDF Networks and ABORT or STOP RDF Operations
- RDF Networks and Stop-Update-to-Time Operations
- Sample Configurations
- RDFCOM STATUS Display
- 14 Process-Lockstep Operation
- Starting a Lockstep Operation
- The DoLockstep Procedure
- The Lockstep Transaction
- RDF Lockstep File
- Multiple Concurrent Lockstep Operations
- The Lockstep Gateway Process
- Disabling Lockstep
- Reenabling Lockstep
- Lockstep Performance Ramifications
- Lockstep and Auxiliary Audit Trails
- Lockstep and Network Transactions
- Lockstep Operation Event Messages
- 15 NonStop SQL/MX and RDF
- Including and Excluding SQL/MX Objects
- Obtaining ANSI Object Names From Updater Event Messages
- Creating NonStop SQL/MX Primary and Backup Databases from Scratch
- Creating a NonStop SQL/MX Backup Database From an Existing Primary Database
- Online Database Synchronization With NonStop SQL/MX Objects
- Offline Synchronization for a Single Partition
- Online Synchronization for a Single Partition
- Correcting Incorrect NonStop SQL/MX Name Mapping
- Consideration for Creating Backup Tables
- Restoring to a Specific Location
- Comparing NonStop SQL/MX Tables
- 16 Zero Lost Transactions (ZLT)
- A RDF Command Summary
- B Additional Reference Information
- C Messages
- D Operational Limits
- E Using ASAP
- Index
Process-Lockstep Operation
HP NonStop RDF System Management Manual—524388-003
14-2
Starting a Lockstep Operation
The RDF/IMPX and RDF/ZLT independent product CDs include the following files
associated with the lockstep capability:
Starting a Lockstep Operation
Transactions protected by a lockstep operation are begun, performed, and terminated
just as any other transaction: call BeginTransaction, do the necessary database
updates, and then call EndTransaction.
What defines a lockstep operation is the invocation of the new DoLockstep procedure.
You issue the DoLockstep call immediately after the associated EndTransaction
call.
The DoLockstep Procedure
How you invoke the DoLockstep procedure differs depending on whether your
applications are written in COBOL or TAL.
Including the DoLockstep in COBOL85 Applications
To invoke the DoLockstep procedure from a COBOL85 program, you must first include
the DoLockstep object module in the SPECIAL-NAMES paragraph in the
CONFIGURATION section.
CONFIGURATION SECTION.
SOURCE-COMPUTER. HP NONSTOP.
OBJECT-COMPUTER. HP NONSTOP.
SPECIAL-NAMES.
FILE "<$vol>.<subvol>.LSLIBTO" IS LOCKSTEP-LIB.
where <$vol>.<subvol> is the location where you have placed the object file.
You then invoke the DoLockstep procedure in the PROCEDURE division by using the
following statement:
ENTER TAL "DOLOCKSTEP" IN LOCKSTEP-LIB GIVING RETURN-CODE
The lockstep software provided with the RDF/IMPX and RDF/ZLT products includes a
sample COBOL85 program (SLOCKCOB) that demonstrates how to use the
DoLockstep procedure in a COBOL program.
SLOCKCOB Sample code for invoking the DoLockstep procedure from a
COBOL 85 program.
LSGO RDF lockstep gateway object code.
LSLIBTO DoLockstep procedure object code.
FDOLOCK Forward declarations of the DoLockstep procedure call.