The persistent access path maintenance job is included in the summary of processes whose status is reported in the Target DB column on the Work with Data Groups display. When all other processes reported in this column are active but access path maintenance is enabled and does not have at least one active job, Partial status is displayed.
In detailed status for a data group, status for access path maintenance is displayed in the AP Maint field on the merged view and database views 1 and 2 when the APMNT policy is enabled. The following status values are possible:
A (Active) - One or more access path maintenance jobs exist.
I (Inactive) - No access path maintenance jobs exist. The APMNT policy is enabled.
U (Unknown) - An unknown error occurred.
Error status
The number of logical (LF) and physical (PF) files that have access path maintenance failures for a data group is included in the number of errors specified in the DB Errors column on the Work with Data Groups display. Option 12 (Files needing attention) provides access to detailed information for the file entries associated with replication errors and access path maintenance errors.
Only replication errors appear on the initial view of the Work with DG File Entries display. Therefore, you must use F10 multiple times to see the view showing the AP Maint. Status column. The value in this column identifies status of access path maintenance processing for the file identified by the data group file entry. The APMNT policy in effect determines whether the database apply process can optimize access path maintenance.
If an access path maintenance error exists for a physical file or a logical file that is identified by a data group file entry, the error status is *FAILED. If an access path maintenance error exists on a logical file which does not have a data group file entry, the error status *FAILEDLF is reported on the file entry for its associated physical file.Therefore, a file entry for a physical file may have errors for itself and for multiple associated logical files which are not identified by file entries. When this scenario occurs, the *FAILED status takes precedence for the PF is displayed, and when resolved, the *FAILEDLF status will be displayed.
When one of the files included in a join logical is not associated with a file entry and an access path maintenance error occurs, all of the file entries associated with the join logical are tracked as errors if they are not already in error. The error cannot be reported on the join files that are not represented by file entries.
|
Value |
Description |
|---|---|
|
*AVAILABLE |
The file is eligible for access path maintenance. The policy in effect allows the database apply process to temporarily delay access path maintenance for the file on the target system. |
|
*DISABLED |
Access path maintenance is disabled by the policy in effect. |
|
*FAILED |
Access path maintenance failed for the file. The failure occurred while resetting access path maintenance for the file from delayed (*DLY) to immediate (*IMMED). |
|
*FAILEDLF |
Access path maintenance failed for a logical file associated with the file. The failure occurred while resetting access path maintenance for the logical file from delayed (*DLY) to immediate (*IMMED). |
|
*NOTALW |
MIMIX cannot perform access path maintenance for the file because the operating system does not allow it. |