The extracted data written to the MXSTSxxxx files can be consumed for many possible use cases. The most common use case will be for simple Assure MIMIX replication status. The most recent records in the MXSTSxxxx files and the most recent journal MXSTSJRN records both represent the most recent Assure MIMIX status.
The IT analyst determines exactly what to accomplish with the status data. The five most common use cases for monitoring MIMIX status are listed below, along with the data that should be used in each.
- Monitoring Overall Instance Status
The STATUS field in the MXSTSINST file can be used to monitor the overall instance status. MXSTSINST provides status information on ifcRollupStatus.
- Monitoring System Managers Status
- The SYSTE00001 (systemManagerStatus) field in the MXSTSSYS file provides system manager status (A= Active, I=Inactive).
- The OVERA00002 (overallManagersStatus) field in the MXSTSSYS file provides a rollup status (1=Ok, 2=Warning, 7=Error, and so on) including system manager status and other statuses.
- Monitoring Application Groups status
The OVERA00001(overallStatus) field in the MXSTSAG file can be used to monitor the status of application groups. MXSTSAG provides status information on ifcRollupStatus.
- Monitoring Data Groups status
The OVERA00001(overallStatus) field in the MXSTSDG file can be used to monitor the status of data groups. MXSTSDG provides status information on ifcRollupStatus.
- Monitoring Audits status
For monitoring audit status, the AUDIT00001(auditsComplianceRollupStatus) and AUDIT00002(auditsComplianceStatus) fields in the MXSTSDG file provide combined audit and compliance status of the last run of each audit for the data group. MXSTSDG provides status information on IfcAuditCmplncSts and ifcRollupStatus.