Replication job and supporting job names - 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

The replication path for database information includes the IBM i remote journal function, the MIMIX database reader process, and one or more database apply processes. If MIMIX source-send processes are used instead of remote journaling, then the processes include the database send process, the database receive process, and one or more database apply processes.

The replication path for object information includes the object send process, the object receive process, and the object apply process. When a data retrieval request is replicated, the replication path also includes the object retrieve, container send, and container receive processes. A data retrieval request is an operation that creates or changes the content of an object. A self-contained request is an operation that deletes, moves, or renames an object, or that changes the authority or ownership of an object.

Table 2 identifies the job names for each of the processes that make up the replication path as well as names of supporting jobs.

Table 1. MIMIX processes and their corresponding job names

Abbreviation

Description

Runs on

Job name

Notes

APMNT

Access path maintenance

Target

sdnAPM

1, 3

CNRRCV

Container receive process

Target

sdn_CNRRCV

3

CNRSND

Container send process

Source

sdn_CNRSND

3

DBAPY

Database apply process

Target

sdn_DBAPYs

3, 4

DBAPYT

Multithreaded database apply job

Target

sdn_DBAPYT

3, 10

DBRCV

Database receive process

Target

sdn_DBRCV

3

DBRDR

Database reader

Target

sdn_DBRDR

3

DBSND

Database send process

Source

sdn_DBSND

3

JRNMGR

Journal manager

System

JRNMGR

--

MXCOMMD

MIMIX Communications Daemon

System

MXCOMMD

--

MXIFCMGR

Collector service process

System

MXIFCMGR

9

MXIFCHIST

History collection process

System

MXIFCHIST

9

MXOBJSELPR

Object selection process

System

MXOBJSELPR

--

MXREPMGR

Replication manager 

Source or Target

MXREPMGR

8

MXRPMCTLR

Replication manager recovery controller process

Source

MXRPMCTLR

--

MXRPMHDLR

Replication manager recovery handler process

Source

MXRPMHDLR

--

OBJAPY

Object apply process

Target

sdn_OBJAPY

3

OBJRTV

Object retrieve process

Source

sdn_OBJRTV

3

OBJSND

Object send process

Source

nnn_OBJSND

6

OBJRCV

Object receive process

Target

nnn_OBJRCV

6

RCV_RQS

Receive request

Source or Target

RCV_RQS

--

STSSND

Status send

Target

sdn_STSSND

3

STSRCV

Status receive

Source

sdn_STSRCV

3

SYSMGR

System manager

Local

SM********

2

SYSMGRRCV

System manager processing jobs

Remote

SH******** and SL********

2

TEUPD

Tracking entry update process

Source or Target

sdn_TEUPD

3, 5

TGTJRNINSP

Target journal inspection

Target

**********

7

Note:
  1. When access path maintenance (APM) has been enabled by the APMNT policy and the data group is configured for single-threaded database apply processing, there is at least one APM job running. Additional jobs are started and ended dynamically as required by the workload.

  2. System manager processes run between a pair of systems. Each system manager process operates in one direction between the local and remote systems of a system manager RJ link.  The SM******** job is used only to start remote journaling, then ends. On the remote system of the RJ link, the SH******** job processes high-priority journal entries and the SL******** job processes low-priority journal entries. For all the jobs, the ******** in the job name format indicates the name of the system definition that is the other side of the RJ link for the job. In instances running MIMIX 9.0.23.00 or earlier, there is only one processing job on the remote system, SR********.

  3. The characters sdn in a job name indicate the short data group name.

  4. The character s is the apply session letter.

  5. The job is used only for replication with advanced journaling and is started only when needed.

  6. The name of object send and receive jobs indicate whether the object send job is shared among data groups. When a data group uses the default shared job for the system, the characters nnn are MX$. (The third character will be changed to a unique prefix if MX$ is already used as a data group short name.) The characters nnn can also be an explicitly named shared job, or it can be the data group short name when the job is dedicated to that data group.

  7. The job name ********** for a target journal inspection job is the name of the journal definition. A job exists for each journal on a system that is a target system for replication. Jobs do not exist when target journal inspection is not configured, when the system is not a target system, or when all data groups using target journal have not started. Also, jobs do not exist for the MXCFGJRN journal definition and journal definitions that identify the remote journal used in RJ configurations (whose names typically end with @R).

  8. The replication manager is a persistent job started when replication processes are started. It periodically checks for and processes recovery actions initiated to automatically correct problems or changes detected by replication processes, target journal inspection, and virtual switch procedures. This process is also started by the system manager to perform daily cleanup activities.

  9. The collector service and history collection jobs provide information to internal MIMIX functions as well as to the portal application in the Assure Unified Interface. Both jobs must be active.

  10. A multithreaded job is associated with a data group configured for multithreaded database apply processing. This job starts and ends with database apply session B.