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-3
Invoking DoLockStep by way of TAL
Invoking DoLockStep by way of TAL
The lockstep software provided with the RDF/IMPX and RDF/ZLT products includes a
TAL header file containing the DoLockstep procedure declaration and the
corresponding object file. You must modify your program to source in the header file
FDOLOCK. For example, include the following lines of code where you add procedure
declarations.
?LIST
?NOLIST, SOURCE EXTDECS
?LIST
?NOLIST, SOURCE FDOLOCK;
?LIST
After recompiling your program, you must then decide whether you want to bind the
object explicitly into your program or treat the object as a user library.
Typically you should explicitly bind the object into your program. The object file
(LSLIBTO) is very small, and there are no benefits to treating it as a user library.
To bind LSLIBTO into your program, issue the following statement:
Select Search <$vol.subvol>.LSLIBTO
where <$vol.subvol> is the location where you have placed the object file.
If you do not want to bind the object into your program and if you do not already use a
user library, then you can skip the bind step and treat LSLIBTO as a user library.
The TAL procedure call syntax is:
status := DoLockstep;
where status is an int.
DoLockStep Execution
DoLockstep communicates with an RDF gateway process that acts as the coordinator
of the lockstep operation. This gateway initiates a new lockstep transaction against a
special RDF lockstep file. The gateway passes information about the lockstep
transaction to the RDF extractor. When the RDF receiver has flushed all audit records
up to and including the lockstep audit into the image trail, it replies to the extractor that
the lockstep data is safe. When the extractor receives that information, it replies to the
gateway which, in turn, passes status back to the DoLockstep call, and the latter then
returns status to the application.
DoLockstep is a waited operation that waits until the RDF subsystem has safely stored
all audit data up to and including all audit data associated with the lockstep transaction
in the image trail. Therefore, if the communications line between the primary and
Note. The DoLockstep procedure can only be invoked from TAL and COBOL85 programs.
Non-native C and native mode languages (C, C++, native mode COBOL, and pTAL) are not
supported.