The Work with Data Groups display appears. Type an 8 (Display status) next to the data group you want and press Enter

3. The Data Group Status display shows a merged view of data group activity on the source and target systems. (See Figure 13.)

Only fields for the type of information replicated by the data group are displayed.

For example, if the data group replicates only objects from the system journal, you will only see fields for system journal replication. If the data group replicates from both the system journal and the user journal, you will see fields for both. To see additional status information for object processes or database processes, do the following:

• If the data group contains object information, press F7 (Object) to view additional object status displays. The Data Group Object Status display appears.

• If the data group contains database information, press F8 (Database) to view additional database status displays. The Data Group Database Status display appears. Tracking entry information for advanced journaling is also available.

4. For object information, there are three views. For database information, there are four views available. Use F11 to change between views.

Note: If the data group contains both database and object information, you can toggle between object details and database details by using the F7 and F8 keys.

Merged view

The initial view displayed is the merged view. This view summarizes status for the replication paths configured for the data group. The status of each process is

represented by the color of the box surrounding the process and a status letter. Table 25 shows possible status values.

Figure 13 shows a sample of the merged view of the Data Group Status display. The data group in this view is configured for user journal replication using remote

journaling and for system journal replication. Also, access path maintenance is enabled.

Figure 13. Merged view of data group status. The inverse highlighted blocks are not shown in this example.

Note: Journal sequence numbers shown in the Source Statistics and Target Statistics areas 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

Data Group Status 17:39:36 Data group . . . . : CRITICALAP Database errors . . . . : 1 Elapsed time . . . : 00:52:51 Objects in error/active : 4 / 0 Transfer definition: PRIMARY-A State. . . : *ASYNCPEND --- Source Statistics --- System: LONDON-A Jrn Mgr-A RJLNK Mon-A Receiver Sequence # Date Time Trans/Hour Database Source Jrn. LONDN0002 >0,000,002,591 4/20/08 11:02:35 Link-A RJ Tgt Jrn. LONDN0002 >0,000,002,591 4/20/08 11:02:35 Last Read . LONDN0002 >0,000,002,591 4/20/08 11:02:35 Entries not read: 0 Est. time to read:

Object Current . . AUDRCV0108 22,314,732 4/22/08 17:37:13 748 Send-I Last Read . AUDRCV0103 22,175,464 4/21/08 11:05:56 *SHARED Entries not read : 139,268 Est. time to read:

--- Target Statistics --- System: CHICAGO-A Jrn Mgr-A DB Rdr- A AP Maint-A RJLNK Mon-A Sys Jrn Insp -A Last Received Unprocessed Entry Count Est Time User Jrn Insp-A Sequence # Entry Count Trans/Hour To Apply DB Apply-A >0,000,002,590 Obj Apply-A 22,023,868 4 F3=Exit F5=Refresh F7=Object view F8=Database F9=Automatic refresh F10=Restart statistics F12=Cancel F14=Start DG F24=More keys

most) are omitted. Truncated journal sequence numbers are prefixed by '>'.

This is shown in Figure 13.

Top left corner: The top left corner of the Data Group Status display identifies the data group, the elapsed time, and the status of the transfer definition in use. The elapsed time is the amount of time that has elapsed since you accessed this display or used the F10 (Restart statistics) key.

Top right corner: The top right corner of the display identifies the number of errors identified by MIMIX. If the workstation supports colors, the number files and objects in error will be displayed in red.

• The Database errors field identifies the number of errors in user journal replication processes. This includes all file entries, IFS tracking entries, and object tracking entries in error. When access path maintenance¹ is enabled, this also includes the number of logical and physical files that have access path maintenance failures for the data group.

Table 25. Possible values for detailed status. Not all statuses are used by each process.

Color and Status

Description

Red When displayed on the Data group, Database errors, or Objects in error fields, a problem exists that requires action.

Red - I The process is inactive.

Red - W The process is suspended at a recovery point. This status is only available for apply processes.

Yellow When displayed on the Data group field, a problem exists that may require attention.

Yellow - P One or more of the processes is active but others are inactive. On the merged view, this status is only possible for the Object Send field.

Turquoise - T The process has a backlog which exceeds its configured threshold. On fields which summarize status for multiple processes, use F7 and F8 to view the specific threshold. The -T is not shown in statistical fields. If a threshold condition persists over time, refer to the MIMIX Administrator Reference book for information about possible resolutions.

White - U The status of the process is unknown.

Blue - A The process is active.

Blue - C The RJ Link is in catch-up mode.This status is only possible for the Database Link process in the merged view and the RJ link field in some database views.

Green - D The data group is disabled. This also means the data group is currently inactive.

1. Access path maintenance is available only on installations running MIMIX 7.1.15.00 or higher.

• The Objects in error/active fields indicate the number of objects that are failed and the number of objects with pending activity entries. The first number in these fields indicates the number of objects defined to the data group that have a status of

*FAILED. The second number indicates the number of objects with active (pending) activity entries.

• The State field identifies the state of the remote journal link. The values for the state field are the same as those which appear on the Work with RJ Links display.

This field is not shown if the data group uses source-send processes for user journal replication.

Source statistics: The middle of the display shows status and summarized statistics for the journals being used for replication and the processes that read from them. The following process fields are possible:

System - Identifies the current source system definition. The status value is an indication of the success in communicating with that system.

Jrn Mgr - Displays the status of the journal manager process for the source system.

DA Poll - Displays the status of the data area poller. This field is present only if the data group replicates data areas using this process.

RJLNK Mon - Displays status of the RJLNK monitor on the source system. This field is present only for data groups that use remote journaling.

Database (Link or Send) - Identifies the status of the process which transfers user journal entries from the source system to the target system.

Link - Displayed when the data group is configured for remote journaling. The status is that of the of the RJ link.

Send -Displayed when the data group id configured for MIMIX source-send processes. The status is that of the database send process.

Object Send - Displays a summation of status from the object send, object retrieve, and container send processes. The highest priority status from each process determines the status displayed. Use F7 (Object view) to see the

individual processes. When the data group uses a shared object send job, either the value *SHARED or a three-character job prefix is displayed below the Send process status, The value *SHARED indicates that the data group uses the MIMIX generated shared object send prefix for this source system. A three-character prefix indicates this data group uses a shared object send job on this system that is shared only with other data groups which specify the same prefix.

For the Database and Object processes, additional fields identify current journal information, the last entry that has been read by the process, and statistics related to arrival rate, entries not read, and estimating the time to read.

Current - For the Database Send and Object Send processes, this identifies the last entry in the currently attached journal receiver. This information is used to show the arrival rate of entries to the journals.

Note: If the data group uses remote journaling, current information is displayed in two rows, Source jrn and RJ tgt jrn. The source journal sequence number refers to the last sequence number in the local journal on the

source system. The remote journaling target journal sequence number refers to the last sequence number in the associated remote journal on the target system.

Transactions per hour - For current journal information, this is based on the number of entries to arrive on the journal over the elapsed time the statistics have been gathered. For last read information, this is based on the actual number of entries that have been read over the elapsed time the statistics have been gathered.

Last Read - Identifies the journal entry that was last read and processed by the object send, database send, or database reader.

Transactions per hour - For current journal fields, this is based on the number of entries to arrive on the journal over the elapsed time the statistics have been gathered. For last read fields, this is based on the actual number of entries that have been read over the elapsed time the statistics have been gathered and will change due to elapsed time and the rate at which entries arrive in the journal.

Entries not read - This a calculation of the number of journal entries between the last read sequence number and the sequence number of the last entry in the current receiver for the source journal. An asterisk (*) preceding this field indicates that the journal receiver sequence numbers have been reset between the last entry in the current receiver and the last read entry.

Estimated time to read - This is a calculation using the entries not read and the transactions per hour rate. This calculation is intended to provide an estimate of the length of time it may take the process (database reader, database send, or object send) to complete reading the journal entries.

Target statistics: The lower part of the display shows status and summarized statistics for all target system processing. The following process fields are possible:

System - Identifies the current target system definition. The status value is an indication of the success in communicating with that system.

Jrn Mgr - Displays the status of the journal manager process for the target system.

DB Rdr - Displays status of the database reader. This field is present only for data groups that use remote journaling.

AP Maint - Displays status of the access path maintenance¹ processes. This field is only present when optimized access path maintenance has been enabled.

RJLNK Mon - Displays status of the RJLNK monitor on the target system. This field is present only for data groups that use remote journaling.

Sys Jrn Insp - Displays the status of target journal inspection for the system journal (QAUDJRN) on the target system of the data group. This field is displayed when the journal definition for the system journal on the current target system permits target journal inspection and the data group is enabled and has been started at least once.

1. Access path maintenance is available only on installations running MIMIX 7.1.15.00 or higher. In earlier levels of MIMIX, if parallel access path maintenance is enabled, its status is displayed in the Prl AP Mnt field that appears in this location.

User Jrn Insp - Displays the status of target journal inspection for the user journal on the target system of the data group. This field is displayed when the journal definition for the user journal on the current target system permits target journal inspection and the data group is enabled, performs user journal replication, permits journaling on target, and has been started at least once.

DB Apply and Obj Apply - Each field displays the combined status for the apply jobs in use by the process. For each process, additional fields show statistics for the last received journal sequence number, number of unprocessed entries, approximate number of transactions per hour being processed, and the

approximate amount of time needed to apply the unprocessed transactions for all database or object apply sessions.

Object detailed status views

Figure 14, Figure 15, and Figure 16 show samples of the information available when you use F7 (Object) to view the detailed object information. Use F11 to move between the three views of detailed object status. On each view, you can use the F1 (Help) key to see a description of that view’s contents.

In all object views, 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 '>'.

The possible status values are indicated in Table 25, with the following additional status values that are unique to several system journal replication processes.

The Min, Act, and Max fields for the Retrieve, Send, and Apply processes indicate the minimum, active, and maximum number of jobs for each process. The number of active jobs vary based on the work load. The active count is highlighted with color for the following conditions:

Red - The number of active jobs is zero (0).

Yellow - The number of active jobs is greater than zero (0) but less than the minimum number of processes.

Turquoise - The process has a backlog that exceeds its configured threshold.

When this occurs, the backlog field for the process is also highlighted in the color turquoise.

Blue - The number of active jobs is equal to or greater than the minimum number of processes.

Figure 14 and Figure 17 show the active count highlighted.

Figure 14. Data group detail status, object view 1.

Figure 15. Data group detail status, object view 2.

Data Group Object Status System: CHICAGO

Figure 16. Data group detail status, object view 3.

Database detailed status views

Figure 17, Figure 18, Figure 19, and Figure 20 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 '>'.

Most fields that display status of a process have some or all of the possible values indicated in Table 25. Possible values for the Jrn State and Cache (Src and Tgt) fields are indicated in Table 27 (journal state) and Table 28 (journal cache).

The data group configuration determines whether the Send process field is replaced by the RJ Link field. When remote journaling is configured, the RJ Link and DB Rdr fields are shown.

The AP Maint field is displayed on views 1 and 2 (Figure 17 and Figure 18) only when the access path maintenance¹ policy is enabled. When present, this field displays the status of the access path maintenance job that persists while the database apply process is active.

DG Object Journal Entry Detail System: CHICAGO 18:01:20 Data group . . . . : CRITICALAP Source system: LONDON-A Entry Sequence # Receiver Date Time Current entry TSF 10,022,314,732 AUDRCV0108 4/22/08 17:37:13 Last read entry - 10,022,175,464 AUDRCV0103 4/21/08 11:05:56 Last received - Target system: CHICAGO-A --- Object Send --- Entry Sequence # Date Time Type Object Active TCO >0,022,023,868 4/20/08 13:59:23 *DOC BVT#I/PBBDOCXX.002 Processed TCO >0,022,023,868 4/20/08 13:59:23 *DOC BVT#I/PBBDOCXX.002 --- Object Apply --- Entry Sequence # Date Time Type Object Processed TCA >0,022,023,871 4/20/08 13:59:23 *DOC BVT#I/PBBDOCXX.002 F3=Exit F5=Refresh F7=Merged view F8=Database view F9=Automatic refresh F11=View 1 F12=Cancel F24=More keys

1. Access path maintenance is available only on installations running 7.1.15.00 or higher.

In the top right corner of database views 1 and 2 (Figure 17 and Figure 18), these fields display combined counts of replicated entries and errors for file entries, IFS tracking entries, and object tracking entries:

• File and Tracking entries

• Not journaled Src Tgt - If the number of not journaled errors on either system exceeds 99,999, that system’s field displays +++++.

• Held due to error

• Access path maint. errors

• Held for other reasons

Database view 4 (Figure 20) separates this information into columns for file entries, IFS tracking entries, and object tracking entries.

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 17, Figure 18, and Figure 19). Each session has its own status value. In these sample figures there is only one apply session (A) which is active (-A).

Figure 17. Data group detail status—database view 1.

In this example, the Link status of -A and the presence of the Reader status indicate that the data group uses remote journaling and access path maintenance. The display also shows that journal standby state is active 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 session indicate truncated sequence numbers that are asso-ciated with *MAXOPT3 support.

Figure 18. Data group database status—view 2.

In this example, the Link status of A and the presence of the Reader status indicates that the data group uses remote journaling. The display also shows that access path maintenance is used and active, and that journal standby state is active and journal caching is not active.

Figure 19. Data group database status, view 3.

Data Group Database Status System: CHICAGO Current entry UMX 12,345,678,900,000,002,591 LONDN0002 4/20/08 11:02:35 RJ target entry UMX 12,345,678,900,000,002,591 LONDN0002 4/20/08 11:02:35 Last read entry UMX 12,345,678,900,000,002,591 LONDN0002 4/20/08 11:02:35 Last received - 12,345,678,900,000,002,590 - 4/20/08 11:01:04

Figure 20. Data group detail status—database view 4. In this example, the combined number of file and tracking entries shown in Figure 17 and Figure 18 are separated into separate col-umns for file entries, IFS tracking entries, and object tracking entries.