Resolving system manager problems and backlogs - assure_mimix - 10.0

Assure MIMIX Operations Guide

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Operations Guide
Copyright
2023
First publish date
1999
Last updated
2024-03-12
Published on
2024-03-12T11:06:36.794496

System manager processes are required for MIMIX to operate. These instructions describe how to check status for individual system manager processes, how to check for a backlog, and how to resolve problems.

Each system manager process operates in one direction between a pair of systems. In the simplest environment with one pair of systems (one management and one network), each system participates in two system manager processes.

In environments with three or more systems, the number of system manager processes in which each system participates depends on how the systems are configured. Each management system communicates with all other management systems and with each network system unless limited by the configuration of the network systems.

To check system manager processes, do the following:

  1. Do one of the following:

    • From MIMIX Intermediate Main Menu, select option 2 (Work with Systems) and press Enter.

    • From the Work with Application Groups display, use option 12 (Node entries). On the resulting Work with Node Entries display, press F7 (Systems).

    The Work with Systems display appears. The status shown in the System Managers column is a summary of all system manager processes through which a system communicates, and includes status of their system manager RJ links and processing jobs.

  2. You can attempt to resolve system manager statuses of *ACTREQ, *INACTIVE, or *INACTRJ from this display by doing the following:

    1. Type a 9 (Start) next to the system definition you want and press Enter.

    2. When the Start MIMIX Managers display appears press Enter.

    3. Press F5 (Refresh).

      To check specific system manager processes or check for a backlog, or if the problem persists after attempting a start request, continue with these instructions.

  3. Type a 7 (System manager status) next to the system definition you want and press Enter.

    The Work with System Pair Status display appears, showing a list that represents all of the system manager processes associated with the selected system definition. Each row identifies a pair of systems between which a system manager process exists and the direction (source to target) in which it transfers data.

  4. Check each represented system manager process for statuses of *INACTIVE or *INACTRJ and do the following to resolve them:

    1. To start the system manager processes for the identified source system of a pair of systems, type a 9 (Start) next to the pair and press Enter.

    2. The Start MIMIX Managers display appears. The value *SYS is preselected for the Manager prompt. Check the values of other prompts and change them as needed to ensure that the values are appropriate for the system specified.

    3. Press Enter.

      The start request will start all system managers associated with the source system of the pair for which the Start option was selected. In a two-node environment, this affects both system manager processes between the two systems. In environments with three or more systems, this affects system manager processes between the selected system and all other systems with which it communicates.

    4. Press F5 (Refresh).

  5. For every process with a status of *ACTIVE, check the unprocessed entries count. Unprocessed entries means that a backlog of high-priority journal entries exists and action may be required.

    The count identifies the number of high-priority entries from the system manager source that have not been processed by the target’s processing job, and includes entries that remote journaling has not sent to the target system.

    1. Press F5 (Refresh) to ensure that the data displayed is current.

    2. For process that have *ACTIVE status, evaluate the timestamp shown for unprocessed high-priority entries. If the timestamp does not change when data is refreshed (F5), contact Support.