Within data groups that are part of a resource group, the database apply process (DBAPY) supports these significantly different choices for the database apply processing of file data:
-
Multithreaded database apply processing - The database apply process uses a multithreaded job when processing most record-level transactions for files replicated through the user journal. This improves performance of the database apply process, simplifies apply session assignment, and eliminates scenarios where the workload is not balanced among apply sessions. Multithreaded database apply processing is supported only in configurations that use application groups.
-
Single-threaded database apply processing - The database apply process uses a configurable number of single-threaded apply sessions that run in parallel to process transactions for all user journal replication. Transactions for files and members can be configured to a specific apply session, and you can serialize transactions for IFS objects, data areas, and data queues replicated through the user journal with transactions for database files. MIMIX can attempt to balance the workload among configured apply sessions.
For data groups that are not part of an application group, only single-threaded database apply processing is supported. These data groups must be associated with a resource group and application group before they can be eligible for conversion to multithreading.
The same type of database apply processing (either multithreaded or singe-threaded) must be used for all data groups within a resource group.
Designating the type of database apply processing: The choice of multithreaded or single-threaded database apply processing is made when configuring new resource groups from within the Assure UI portal or when configuring new data groups from the native user interface. New resource group and data group settings default to use multithreading. All data groups within a resource group must be configured for the same type of database apply processing. A conversion process is required to change between single-threaded and multithreaded processing. Conversion is supported for a single resource group or for one or more resource groups in an application group.
Implementation details vary between the Assure UI portal and the native user interface. Regardless of which interface you use to create new configurations, the choice of multithreading or single-threading effectively means that the database Apply sessions field (NBRDBAPY parameter) has different possible values based on your choice. Your choice also determines what values are available in other fields that are required for multithreading.
The Create Data Group Definition (CRTDGDFN) command uses the Number of DB apply sessions (NBRDBAPY) parameter to designate the type of jobs used for database apply processes. The shipped default value *THREADED resolves to the default threading level allowed by the installed product. To use single-threaded apply sessions instead, you must specify a numeric value from 1 to 6. When more than 1 is specified, these jobs run in parallel.