Job replication overview - 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-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

When MIMIX is configured to replicate jobs associated with replicated job queues and the configuration has been made available by stopping and starting replication processes, system journal replication processes will replicate journal entries associated with a submit job request and for subsequent changes to the state of the job.

The object apply (OBJAPY) process places the job information associated with the replicated job into a staging are on the target system. The replicated jobs are not actually submitted by MIMIX on the target system. The command string of the submitted job that has been replicated to the staging area is available on the target system until either MIMIX has processed a job completion journal entry for the source job or user action is taken to manually run or remove the job. This capability is useful in the event of a switch. The jobs from the original source system that did not complete before the switch can be submitted or discarded on the new source system after the switch. This can be done by steps within switch procedures for an application group or manually.

The replicated jobs on a system are from when that system is, or was, the target system for replication. The replicated jobs that exist on a system can be seen using the Work with Replicated Jobs display (WRKREPJOB command) from the native user interface.

In environments with more than two nodes, when a data group is disabled either automatically or manually, all replicated jobs in the staging area for the target node of the data group are cleared. If the replicated job indicator was set, it is also cleared.