To access IFS tracking entry or object tracking entry displays for a data group, do the following:
From the MIMIX Basic Main Menu select option 6 (Work with Data Groups) and press Enter.
The Work with Data Groups display appears. Type 17 (File entries) next to the data group you want and press Enter.
Next to the data group you want, type the number for the option you want and press Enter. The following table shows the options for tracking entries.
Table 1. Tracking entry options on the Work with Data Groups display Select Option
Result
50=IFS trk entries
Lists all IFS tracking entries for the selected data group on the Work with DG IFS Trk. Entries display.
51=IFS trk entries not active
Lists IFS tracking entries for the selected data group with inactive status values (*HLD, *HLDERR, *HLDIGN, *HLDRNM, and *RLSWAIT) on the Work with DG IFS Trk. Entries display.
52=Obj trk entries
Lists all object tracking entries for the selected data group on the Work with DG Obj. Trk. Entries display.
53=Obj trk entries not active
Lists object tracking entries for the selected data group with inactive status values (*HLD, *HLDERR, *HLDIGN, and *RLSWAIT) on the Work with DG Obj. Trk. Entries display.
-
The tracking entry display you selected appears. Significant capability is available for addressing common replication problems and journaling problems. Do the following:
-
Use F10 to toggle between views showing status, recovery status, journaling status, and the database apply session in use.
-
Any entry with a status of *HLD, *HLDERR or *HLDIGN indicates that action is required. The identified object remains in this state until action is taken. Statuses of *HLD and *HLDERR result in journal entries being held but not applied. Use Possible actions based on replication status of a tracking entry to identify choices based on the tracking entry status.
-
Use options identified in Options for working with tracking entries to address journaling problems or replication problems.
-
Press F10 as needed until you see the Recovery Status column. This column identifies the most severe status of any recoveries for the object. Use option 17 (Rcy details) to go to the Work with Recoveries display where you can use available options for addressing failed recoveries. Different options are available for recoveries processed by replication manager and those processed inline by audits or third delay-retry activity. See Displaying recoveries.
-
Status |
Preferred Action1 |
---|---|
*ACTIVE |
Unless an error has occurred, no action is necessary. Entries in the user journal for the IFS object are replicated and applied. If necessary, any of the options to hold journal entries can be used. |
*HLD |
User action is required to release the entry (option 26) so that held journal entries from user journal can be applied to the target system. |
*HLDERR |
User action is required. Attempt to resolve the error by synchronizing the file (option 16). |
*HLDIGN |
User action is required to either synchronize the object (option 16) or to change the configuration if you no longer want to replicate the object. Journal entries for the object are discarded. Replication is not occurring and the object may not be synchronized. Depending on the circumstances, Release may also be an option. |
*HLDRTY |
The tracking entry is held because the data area, data queue, or IFS object could not be processed while the object is still being processed by the data group of the journal to which the object was previously journaled. After a short delay, the database apply job will automatically attempt to process this entry again. The preferred action is to allow MIMIX to periodically retry the tracking entry. By default, the database apply job will automatically attempt to process the entry every 5 minutes for up to 1 hour. Manually releasing the tracking entry will cause MIMIX to attempt to process the entry immediately. |
*HLDRNM |
This is a transitional state for IFS tracking entries that should resolve to *ACTIVE. If this status persists, check the journaling status for the entry. Object tracking entries cannot have this status. |
*RLSWAIT |
If the status does not change to *ACTIVE, you may need to synchronize (option 16) |
Option |
Additional Information |
---|---|
4=Remove |
|
5=Display |
Identifies an object, its replication status, journaling status, and the database apply session used. |
6=Print |
Creates a spooled file which can be printed |
9=Start journaling |
See Starting journaling for IFS objects and Starting journaling for data areas and data queues . |
10=End journaling |
See Ending journaling for IFS objects and Ending journaling for data areas and data queues. |
11=Verify journaling |
See Verifying journaling for IFS objects and Verifying journaling for data areas and data queues . |
16=Synchronize |
Synchronizes the contents, attributes, and authorities of the object represented by the tracking entry between the source and target systems. For more information, see topic ‘Synchronizing tracking entries’ in the Assure MIMIX Administrator Reference book. |
17=Rcy Details |
Use this option to access details about the recoveries for the object identified by the entry See Displaying recoveries. |
18=Ack failed rcy |
You can optionally use this option to acknowledge the status of failed recoveries for the object identified by the entry. Be aware manual recovery of the error condition is preferred and that acknowledging failed recovery status does not resolve the problem that recovery actions were attempting to correct. For more information, see Acknowledging failed recoveries for an object. |
23=Hold |
See Holding journal entries associated with a tracking entry . |
24=Ignore |
See Ignoring journal entries associated with a tracking entry . |
25=Release wait |
See Waiting to synchronize and release held journal entries for a tracking entry. |
26=Release |
|
27=Release clear |
See Releasing and clearing held journal entries for a tracking entry. |
35=Work with related objects |
Displays IFS tracking entries that have the same file identifier (FID) as the specified tracking entry. See Related tracking entries. |