About the RUNSWTFWK command - assure_mimix - 10.0

The Run Switch Framework (RUNSWTFWK) command is used to perform the switchover, synchronization, and switch back processes. RUNSWTFWK provides underlying support for MIMIX Switch Assistant. When you are using the MIMIX Model Switch Framework to perform a switching operation, the MIMIX Model Switch Framework will issue status messages to inform you of the current status of the switching operation.

During a switching operation, MIMIX Model Switch Framework waits for the data group to end before continuing processing. As long as the submit of the switch is successful, MIMIX Model Switch Framework processes the next data group in line. It does not wait for the switch to complete. Thus, a failure during a switching operation may result in a partially switched status.

In the event that MIMIX Model Switch Framework fails during a switching operation, you must resolve the problem that occurred on the data group as well as complete the switch of the data group manually. For information about switching, see the Assure MIMIX Operations book.

The RUNSWTFWK command can only be run from the backup system. When you enter the RUNSWTFWK command you can specify:

• If you want the MIMIX Model Switch Framework to automatically start the data groups after a planned switch or if you would rather start the data groups yourself.

• If you want MIMIX to set the auditing level when performing a STRDG operation. You also have the option to manually ensure that the audit levels for all objects that are configured for replication by MIMIX have been set properly, otherwise, replication errors may occur.

• The Wait time (seconds) (WAIT) prompt is used to specify the number of seconds to wait for all of the active data group processes to end. The function of the default value *DFT is different for planned switches than it is for unplanned switches. For a planned switch, the value *DFT is equivalent to the value *DGSELECT.  For an unplanned switch, the value *DFT is set to wait 300 seconds (5 minutes) for all of the active data group processes to end.

• If you specify a value for the WAIT parameter you can use the Timeout option parameter (TIMOUTOPT) to specify what action to take when the wait time you specified is reached. The function of the default value *DFT is different for planned switches than it is for unplanned switches. For a planned switch, the value *DFT is equivalent to the value *QUIT. When the value specified for the WAIT parameter is reached, the current process quits and returns control to the caller. For an unplanned switch, the value *DFT is equivalent to the value *NOTIFY. When the value specified for the WAIT prompt is reached, an inquiry message is sent to notify the operator of a possible error condition.

• Whether or not you want the MIMIX Model Switch Framework to switch a data group when there are data group entries with an active (pending) status. The Conditions that end switch (ENDSWT) parameter is used to specify which conditions should end the switch process. The function of the default value *DFT is different for planned switches than it is for unplanned switches.

  • For a planned switch, the value *DFT is equivalent to the value *ALL. The value *ALL uses all available options to end the switch process and is the most conservative way to switch data groups. Additionally, choosing ENDSWT(*ALL) ensures that your programs will automatically include any future ENDSWT parameter values that may be added to maintain a conservative approach to the switching operation.

  • For an unplanned switch, the value *DFT

  • is equivalent to the value *NONE. The value *NONE does not end switching even when conditions exist that are not compatible with best practices for switching. For example, if open commit cycles exist at the time of a switch, the uncommitted changes are not applied to the target system, and the data may be lost if the open commits are not resolved before the data group is started following the switch.

  • For an unplanned switch, the switch process is ended if there are any backlogs for the database apply process (similar to the value *DBPND). No other conditions that end switching are checked and switching is not ended even when conditions exist that are not compatible with best practices for switching. For example, if open commit cycles exist at the time of a switch, the uncommitted changes are not applied to the target system and the data may be lost if the open commits are not resolved before the data group is started following the switch.

  • For more information about how to check for pending object activity entries and open database commit cycles, see the Assure MIMIX Operations book.

• Whether or not you want the MIMIX Model Switch Framework to create and attach a new journal receiver for the user (database) journal during the switching operation. If you do not want the MIMIX Model Switch Framework to create new journal receivers for a specified data group choose CHGUSRRCV(*NO).

• Whether or not you want the MIMIX Model Switch Framework to create and attach a new journal receiver for the system (audit) journal (QAUDJRN) during the switching operation. If you want the MIMIX Model Switch Framework to create a new journal receiver for the first data group that handles object replication you should choose CHGSYSRCV(*FIRST).

For more information about the options available to you when you are using the RUNSWTFWK command, enter the command and press F1 when the cursor is at the top of the display.