Figure 18, Figure 19, Figure 20, and Figure 21 show samples of the information available when you use F8 (Database) to view the detailed database information. On each view, you can use the F1 (Help) key to see a description of that view’s contents.
In database views that include sequence numbers, the journal sequence numbers may be truncated if the journal supports *MAXOPT3 for the receiver size and the journal sequence number value exceeds the available display field. When truncation is necessary, the most significant digits (left-most) are omitted. Truncated journal sequence numbers are prefixed by '>'.
Status values: Most fields that display status of a process have some or all of the possible values indicated in Possible values for detailed status. Not all statuses are used by each process. Possible values for the Jrn State and Cache (Src and Tgt) fields are indicated in Possible status values for Journal State fields (journal state) and Possible status values for Journal Cache fields (journal cache).
The displayed Process status fields are dependent on the configuration of the data group. When remote journaling is configured, the RJ Link field is shown instead of the Send process field and the DB Rdr field is shown. The configuration also determines whether the DBAPYT or AP Maint field is shown.
The DBAPYT field displays the status of the threaded job (sdn_DBAPYT) for multithreaded database apply processing. This field is displayed on views 1 and 2 (Figure 18 and Figure 19) only when multithreading is configured for a data group within an application group.
The AP Maint field displays the status of the access path maintenance job that persists while the database apply process is active. This field is displayed on views 1 and 2 (Figure 18 and Figure 19) only when the access path maintenance policy is enabled and multithreaded database apply processing is not configured. Multithreading and access path maintenance cannot be used in the same data group.
Problem counts: In the top right corner of database views 1 and 2 (Figure 18 and Figure 19), these fields display combined counts of replicated entries, new or in-progress recoveries, and errors for file entries, IFS tracking entries, and object tracking entries:
File and Tracking entries - The number of database files, journaled IFS objects, and journaled data areas and data queues being replicated for the data group.
Not journaled Src Tgt - The number of files and objects identified by file entries and tracking entries that are currently not journaled or that are journaled to a journal that is different than the configured journal on the source and target systems. If the number of not journaled errors on either system exceeds 99,999, that system’s field displays +++++.
Held error - The number of files and objects identified by file entries and tracking entries that are held due to an error (*HLDERR) status.
Rcy - The number of files and objects identified by file and tracking entries that have new or in-progress recoveries for problems detected by MIMIX.
Failed Rcys - The number of files and objects identified by file entries and tracking entries with failed recoveries.
Access path maint. errors - The number of database files with access path maintenance errors. This value will always be 0 in a data group that uses multithreaded database apply processing.
Held for other reasons - The number of files and objects identified by file entries and tracking entries that are held or inactive for other reasons.
Database view 4 (Figure 21) separates this information into columns for file entries, IFS tracking entries, and object tracking entries.
Apply sessions: If a data group has multiple database apply sessions, you will see an entry for each session in the Apply Status column on database views 1, 2, and 3 (Figure 18, Figure 19, and Figure 20). Each session has its own status value. In these sample figures, there are two active (-A) apply sessions because the data group is configured for multithreaded database apply processing. In this scenario, apply session A is used for replication of journaled data areas, data queues, and IFS objects, and apply session B is used for file objects.
In database view 1, the Open Commit column displays the value *DLK when there is an open commit cycle that has caused a deadlock condition for the apply process which MIMIX could not automatically resolve. User action is necessary to resolve the commit cycle.
Figure 18.Data group detail status—database view 1.
In this example, the RJ Link status of -A and the presence of the DB Rdr process status indicate that the data group uses remote journaling. The presence of the DBAPYT process status indicates that the data group is configured for multithreaded database apply processing. The display also shows that journal state is active (not “standby”) and journal caching is not active. The unprocessed entry count indicates that the final journal entry has not been applied. The > character preceding sequence numbers for the apply sessions indicates that leading values have been truncated in sequence numbers associated with *MAXOPT3 support.
Figure 19.Data group database status—view 2.
The columns available in the Database Apply section of Database view 2 are different than those shown in view 1. Other fields show the same information as in view 1.
Figure 20.Data group database status, view 3.
Figure 21.Data group detail status—database view 4.
In this example, the combined number of file and tracking entries and number of recoveries (from database views 1 and 2) are separated into columns for file entries, IFS tracking entries, and object tracking entries.
