Displaying status of monitors on the local system - assure_mimix - 10.0

Each node or system in the product configuration has MIMIX monitors which run on that system to check for specific potential problems. The Work with Monitors display indicates the status and other details about monitors on the local system.

Monitor status must be checked from each system. To check status on a system, do the following:

1. Select option 1 (Work with application groups) from the MIMIX Basic Main Menu and press Enter.

2. The Monitors field located in the upper right corner of the Work with Application Groups display summarizes the status of the MIMIX monitors on the local system with one of the following values.

   *ACTIVE - All enabled monitors on the local system are active.

   *ATTN - Either one or more monitors on the local system failed or there are both active and inactive monitors on the local system. Investigation is necessary.

   *INACTIVE - All enabled monitors on the local system are inactive.

   Figure 36.Monitors field on the Work with Application Groups display

   

3. Do one of the following to access the Work with Monitors display:

   • From with Work with Application Groups display, press F14 (Monitors).

   • Select option 12 (Work with monitors) from the MIMIX Basic Main Menu.

   • Enter the command: WRKMON 

   The Work with Monitors display lists the shipped monitors and any user-created monitors on the local system.

4. Verify which monitors are needed on the local system. The following table identifies monitors that are part of MIMIX.

5. Check the Status column for status values of FAILED, FAILED/ACT, and INACTIVE. These values require investigation or additional action.

   Table 1. Possible monitors and the nodes on which they should be active

   Monitor	When and Where Needed
   journal-name - remote journal link monitor Checks the journal message queue for indications of problems with the remote journal link. A monitor exists for both the local and remote system of the RJ link.	Primary node and the current Backup node of application groups which perform logical replication.
   MMIASPMON - independent ASP threshold monitor Checks the QSYSOPR message queue for indications that the independent ASP threshold has been exceeded. This monitor improves the ability to detect overflow conditions that put your high availability solution at risk due to insufficient storage. Note: This monitor is shipped disabled. If you want to use this monitor, user action is required to enable it on all systems in the MIMIX installation that are using independent ASPs.	On all nodes which control an independent ASP.
   MMNFYNEWE - monitor for new object notification entries Monitors the source system for the newly created libraries, folders, or directories that are not already included or excluded for replication by a data group configuration. Note: This monitor is shipped disabled. User action is required to enable this monitor on the source system within your MIMIX environment. Once enabled, the monitor will automatically start with the master monitor.	Primary node when the application group is configured for logical replication.
   MQRCDIMG - MQ record image monitor This monitor is optional for environments that use Assure MIMIX IBM MQ. The monitor runs at a scheduled time and invokes the IBM MQ for IBM i command RCDMQMIMG for each queue manager on the system. Note: This monitor is shipped disabled. User action is required to enable this monitor on the source system within your MIMIX environment. Once enabled, the monitor will automatically start with the master monitor.	Primary node