RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

If you use the TIMESTAMP option, the operation is called a stop-update-to-time operation, which
is discussed further below.
NOTE: The timestamp you specify must be at least 5 minutes later than the current time at your
primary system. If you specify an earlier time, an error message appears. Additionally, all
transactions that committed prior to the timestamp are applied and retained in the backup database.
Any transactions that committed at or after the specified timestamp are backed out of the backup
database. When you subsequently restart Update, any transactions undone during the previous
stop-update-to-time operation are reapplied to the backup database, thereby keeping the backup
database in full synchronization with the primary database.
day
is a number from 1 to 31.
month
is the first three letters of the month, such as JAN, FEB, MAR.
year
is a four-digit number, such as 2004.
hour
is a number from 0 to 23.
min
is a number from 00 to 59. min must be preceded by a colon (:).
Where Issued
Primary system only.
Security Restrictions
You can issue the STOP UPDATE command if you are a member of the super ID group and have
a remote password from the RDF primary system to the backup.
RDF State Requirement
You can issue the STOP UPDATE command only when RDF is running.
Usage Guidelines
Use the STATUS RDF command to determine whether updating is enabled or disabled. If updating
is disabled, the STATUS RDF display specifies the state “Update stopped” and shows no status
information for the updater processes.
When you disable updating with the STOP UPDATE command, the extractor continues to send all
relevant audit from the primary system to the receiver, and the latter stores it in the image trails.
Therefore if you STOP UPDATE, you still have full RDF protection. If your primary system should
fail, you have only to issue the RDF TAKEOVER command and the updaters are restarted in order
to apply all remaining committed transactions stored in the image trails to the backup database.
When you stop the updaters without the TIMESTAMP option, the backup database is not typically
in a consistent state. This does not mean that the backup database is not out of running
synchronization with the primary database, but it does mean the some transactions may have been
partially applied to the backup database. Stopping the updaters without the TIMESTAMP option
is useful for performing a variety of different operations, such as maintenance tasks or producing
reports based on what is commonly known as BROWSE ACCESS. For related information, see
“Reading the Backup Database (BROWSE versus STABLE Access)” (page 140) in Chapter 5.
If you want to read the backup database when it is in a fully consistent state with respect to
transaction boundaries, then use the TIMESTAMP option with the STOP UPDATE command. This
stop-update-to-time operation is fully discussed in the section “Access to Backup Databases with
242 Entering RDFCOM Commands