There are times when recoveries exist but are no longer associated with a job. The following conditions could cause recoveries to become orphaned:
• An unplanned switch has occurred
• The MIMIX subsystem was ended unexpectedly
• A recovery job was ended unexpectedly
When automatic audit recovery is enabled, orphaned recoveries are converted to error notifications during system cleanup. If the orphaned recovery is older than the cleanup time specified in the system definition, it is deleted.
When automatic database recovery or automatic object recovery is enabled, orphaned recoveries are deleted, when possible.
Because recoveries are displayed on both systems, but jobs associated with them are only accessible from the originating system, you need to verify that the recovery is orphaned before removing it.
Determining whether a recovery is orphaned
Do the following to determine whether a recovery is orphaned:
1. From a command line, type WRKRCY and press Enter.
2. Press F11 to display the Timestamp view. This view allows you to see the From System column which lists the system from which the recovery originated.
3. Ensure you are operating from the originating system. Then type a 12 next to the recovery.
4. Do one of the following:
• If an error message is displayed indicating that the job associated with the recovery is not found, follow the steps in “Removing an orphaned recovery” on page 168.
• When the Display Job display appears, type a 10 in the Selection field and press Enter. The status of the job is displayed. If the job associated with the recovery is no longer valid, follow the steps in “Removing an orphaned recovery” on page 168.
13=Hold job Places an active recovery job on hold. This action is valid for
recoveries with names that begin with # and is only available from the system on which the recovery job is running.
14=Release job Releases a held recovery job. This action is valid for recoveries with names that begin with # and is only available from the system on which the recovery job is held.
Table 33. Options available for recoveries WRKRCY
Option
Description
Removing an orphaned recovery
These procedures assume that you have already confirmed that the recovery is orphaned using the procedures in “Determining whether a recovery is orphaned” on page 167.
Do the following to remove an orphaned recovery:
1. From the originating system, type WRKRCY on the command line and press Enter.
2. After you have ensured that the recovery is orphaned, type a 4 next to the orphaned recovery you wish to remove and press Enter.
3. Press Enter to confirm your request to remove the recovery.
MIMIX uses a number of processes to perform replication. These processes, along with a number of supporting processes must be active to enable MIMIX to function.
These pairs of commands will start and end replication:
• The Start MIMIX (STRMMX) and End MIMIX (ENDMMX) commands will start or stop replication processes as well as all supporting processes for the products in a MIMIX installation library in a single operation. These commands are the preferred method for starting and ending MIMIX.
• The Start Application Group (STRAG) and End Application Group (ENDAG) commands will start or stop replication processes in environments configured with application groups. Each command calls a default procedure with steps to perform its operations and can be customized.
• The Start Data Group (STRDG) and End Data Group (ENDDG) commands will start or stop data group replication processes. These commands are the basis for controlling replication processes and are invoked programmatically by the
previously identified commands.
This chapter provides information about and procedures for use each set of commands. The following topics are included:
• “Before starting replication” on page 171 applies to all methods of starting replication.
• “Commands for starting replication” on page 171 describes the STRMMX, STRAG, and STRDG commands and considerations for their use.
• “What occurs when a data group is started” on page 174 describes what the STRDG command does in addition to starting replication, choices for specifying a journal starting point, and options for clearing pending and error entries.
• “Starting MIMIX” on page 179 provides a procedure for using the STRMMX command.
• “Starting an application group” on page 180 provides a procedure for using the STRAG command.
• “Starting selected data group processes” on page 181 provides a procedure for using the STRDG command and identifies when the start request should include clearing pending entries.
• “Starting replication when open commit cycles exist” on page 183 describes when MIMIX cannot start replication due to open commit cycles and how to resolve them and start replication.
• “Before ending replication” on page 184 to all methods of ending replication.
• “Commands for ending replication” on page 184 describes the ENDMMX,
ENDAG, and ENDDG commands and considerations for their use, such as when to perform a controlled end or when to end the RJ link.
• “Ending MIMIX” on page 179 provides procedures for using the ENDMMX command and describes when you may also need to end the MIMIX subsystem.
• “Ending an application group” on page 194 provides a procedure for using the ENDAG command.
• “Ending a data group in a controlled manner” on page 195 provides procedures for preparing to end, ending, and confirming that the end completed without problems.
• “Ending selected data group processes” on page 198 provides a procedure using the ENDDG command.
• “What replication processes are started by the STRDG command” on page 199 describes which replication processes are started with each possible value of the Start processes (PRC) parameter. Both data groups configured for remote journaling and data groups configured for MIMIX source-send processing are addressed.
• “What replication processes are ended by the ENDDG command” on page 203 describes what replication processes are ended with each possible value for the End Options (PRC) parameter. Both data groups configured for remote journaling and data groups configured for MIMIX source-send processing are addressed.