Tracking entries identify library-based objects (data areas and data queues) and IFS objects configured for cooperative processing via the user journal.
You can access the following displays to work with tracking entries in any status:
Work with DG IFS Trk. Entries display (WRKDGIFSTE command)
Work with DG Obj. Trk. Entries display (WRKDGOBJTE command)
These displays provide access for viewing status and working with common problems that can occur while replicating objects identified by IFS and object tracking entries.
Held tracking entries: Status for the replicated objects is reported on the associated tracking entries. If a journal transaction is not replicated successfully, the tracking entry is placed in *HLDERR status. This indicates a problem that must be resolved.
Tracking entries can also be placed in *HLD, *HLDIGN statuses by user action These statuses are reported as ‘held for other reasons’ and also require user action.
When a tracking entry has a status of *HLD or *HLDERR, MIMIX retains log spaces so that journal entries that are being held can be released and applied to the target system. Tracking entries should not be left in these states for an extended period.
Failed recoveries: The presence of any failed recoveries for an object identified by a tracking entry is a problem that must be resolved.
Additional information: To determine if a data group has any IFS objects, data areas, or data queues configured for advanced journaling, see Determining if non-file objects are configured for user journal replication.
When working with tracking entries, especially for IFS objects, you should be aware of the information provided in Displaying long object names.