Checklist: Converting to single-threading - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2023
First publish date
1999
ft:lastEdition
2024-06-11
ft:lastPublication
2024-06-11T18:33:16.692940

Use this checklist to convert the configuration of one or more resource groups in an application group to values required for single-threaded database apply processing.

The instructions in this checklist use menu options to invoke the Convert RG for Multithreading (CVTRG) command. The conversion request does the following:

  • If you specify multiple resource groups to convert, each resource group is processed independently. Resource groups whose data groups are already configured for single-threading are not processed.

  • Each data group in a specified resource group is checked for conversion requirements. If any data group does not meet the following requirements, that resource group is not converted:

  • A controlled end of replication processes has been performed.

  • No open commit cycles exist. This is a requirement when default values are used. However, if you specify *DISACARD for the Open commit handling prompt on the conversion request, the presence of open commits does not prevent conversion.

  • File entries have a status of *ACTIVE or *HLDIGN.

  • After single-threading requirements are successfully checked, the conversion process changes the configuration as indicated in Table 35.

  • If a data group meets conversion requirements but fails to convert, all configuration changes for other data groups in the same resource group are reverted.

The CVTRG command runs interactively. The time needed to perform a conversion depends on the number of data group object entries and file entries associated with the selected resource groups.

While the CVTRG command is running, do not switch the application groups associated with the resource groups, and do not change the data group definitions or their selection rules (entries).

Table 1. Configuration values changed by a conversion to single-threaded database apply processing.

The specific configuration values changed by a conversion to single-threading request depends on whether there is any saved configuration data to use and whether you allow it to be used by the conversion process.

If a resource group was previously converted to multithreading, there may be saved pre-conversion configuration data from that conversion process.

  • If saved configuration data exists and the value *YES (default) is specified for the Use saved config. for revert (USECONFIG) prompt, the saved data is used by the conversion to single-threading. Saved values will replace existing configuration values in the resource group’s associated data group definitions, object entries, and file entries.

  • Note: Be aware that if you specify *YES, any other changes that you made to the data groups, object entries, and data group file entries since the save occurred will be lost. New object entries and file entries, including those created automatically for a new file, added after the save will be lost. Changes made to object and file entries since the save will be lost. Object and file entries you deleted since the save will no longer be deleted.

  • If you specify *NO, any saved configuration is not used and is deleted.

If saved configuration data does not exist or is not used, the conversion will change the associated data group definitions to values compatible with single-thread database apply processing, as follows:

  • Database Apply sessions (NBRDBAPY) is set to 6.

  • Target constraint management (element of DBAPYPRC) is set to *NO.

  • Lock member during apply (element of FEOPT) is set to Exclusive, Allow Read (*EXCLRD).

The conversion process issues a message to the job log that identifies whether saved configuration was found and used.

To convert an application group or resource group to single-threading, do the following:

  1. From a command line on a management system, enter the command:

    
              installation-library/WRKAG
  2. From the Work with Application Groups display, do one of the following:

    • If you plan to convert all or more than one eligible resource groups in an application group, continue with Step 3.

    • If you plan to convert only one resource group, type 13 (Data resource groups) next to the appropriate application group and press Enter. This will access the Work with Data Rsc. Grp. Ent. display. Unless these instructions indicate otherwise, steps for converting an individual resource group are the same as for an application group.

  3. Next to the application group or resource group to be converted, type 10 (End) and press Enter. This will start a controlled end of replication processes.

    Wait for the End procedure to complete.

  4. If you are converting an application group, type 13 (Data resource groups) next to it and press Enter.

  5. On the Work with Data Rsc. Grp. Ent. display, resource groups that ended will have a status of *INACTIVE in the Replication Status column.

  6. For a resource group being converted, type 8 (Data groups) next to the resource group and press Enter to access its data groups.

  7. Default values on the conversion request will check for the existence of open commit cycles and prevent the conversion if any are present. Optionally, you can use this step to manually check each data group associated with a resource group being converted to check for open commit cycles before starting the conversion process. To manually check each data group listed, do the following:

    a.Type 8 (display status) and press Enter.

    b.Press F8 (Database) to access the Data Group Detail Status display.

    c.For each apply session listed in the Target Statistics section, verify that the value shown in the Open Commit column at the right side of the display is *NO.

    Note: If there are open commit cycles (*YES) for any data group associated with the conversion, you have the following options:
    • Address the open commit cycles using topic “Confirming the end request completed without problems” in the Assure MIMIX Operations book. Then start these instructions again from the first step.

    • Postpone the conversion to a different time when applications can be ended or when activity is slow enough that you can end replication without having open commit activity. Then start these instructions again from the first step.

    • If you cannot close all open commits and do not have a time when commit activity is minimal, you can continue with the conversion and specify to have the conversion process discard open commits. If you choose this option, you must also run audits to repair any not-synchronized conditions after the conversion completes.

  8. Repeat Step 6 and Step 7 for each resource group that you plan to convert.

  9. Press F12 (Cancel) as needed to return to the Work with Application Groups display. (If you are converting a single resource group, you can return to the Work with Data Rsc. Grp. Ent. display.)

  10. To start the conversion process, do one of the following:

    • To convert all eligible resource groups in an application group, type 33 (Convert to single-threaded) next to the application group and press Enter.

    Note: To convert a subset of the eligible resource groups in an application group, type 33 and press F4 (Prompt) instead of Enter. If you do this, you will not see the confirmation display in Step 11. However, you will be able to specify multiple resource groups in Step 12.
    • To convert a single resource group, type 33 (Convert to single-threaded) next to the resource group and press Enter.

  11. The Conf. Convert to Single-thread display appears. Press Enter to confirm your selection.

  12. The Convert RG for Multithreading (CVTRG) display appears, showing the selected resource groups and application group.

    Note: You can only change the Resource group prompt if you prompted the option as described in Step 10.
  13. The Open commit handling prompt determines how the conversion process handles any open commit cycles. The recommended value is *FAIL. However, if you cannot resolve open commits or cannot perform the conversion during a time when commit activity is minimal, you can specify *DISCARD, which will identify files with open commit activity for automatic recovery processing, discard the open commit cycles, and allows the conversion to continue.

  14. The Use saved config. for revert prompt determines whether any existing configuration data saved from an earlier multithreaded conversion will be used to replace the current configuration for the data groups, object entries, and file entries associated with a resource group. If saved data exists and *YES is specified, you will lose any changes made to the affected configuration objects since the save occurred. To limit the configuration changes to only those required for single-threading, specify *NO.

  15. To start the conversion, press Enter.

  16. When the command completes, the message “See the following messages for CVTRG results” appears at the bottom of the display.

    a.Click on the message and press F1 (Help). Then press F10 (Display messages in job log).

    b.You should see one of the following completion messages. To display all information for a message, click the message and press F1.

    LVI3926. No resource groups in application group name.

    LVI392E. No specified resource groups in application group name use multithreading.

    LVI3933. All specified resource groups in app. group name converted to single-threading.

    LVI3936. Converted-number of total-number resource groups converted to single-threading.

    LVE351E. Converted-number of total-number resource groups converted to single-threading.

  17. When you are ready to resume replication, a clear pending start is required for the data groups that were part of the conversion. The simplest way to perform this is to do one of the following:

    • For an application group, use option 9 (Start) from the Work with Application groups display.

    • For a resource group, use option 9 (Start) from the Work with Data Rsc. Grp. Ent. display.

  18. If you specified to discard open commits in Step 13, running audits for the affected data groups is recommended. Do the following:

a.From a command line, enter:


      installation-library/WRKAUD

b.Type 9 (Run rule) next to the audits for the converted data groups and press Enter.