MIMIX will track both the current and historical status of secure communications
based on connection attempts.
- Current - Status of the current communication mode for the system. This status reflects the result of the most recent secure communication attempt involving this system.
- Historical – Status reflects the ‘worst case’ current status that has occurred since the last time the Historical status was reset using WRKSYS option 17. When the historical status changes to non-optimal, a notification will be created that alerts you and activate any subscriptions. This notification is intended to alert you if communication returns to a non-secure connection or if an effort to securely connect fails completely.
When MIMIX reports the current or historical communication mode, the possible values have
the following result:
- The value *SECURED indicates that communications were secured.
- The value *UNSECURED indicatesthat communications were unsecured and that secured communications were not requested.
- The value *UNSECWARN indicates that communications were run as Unsecured because an attempt to run as Secured failed. The Communication mode (CMNMODE) policy allows for Unsecured communications when secure connections fail.
- The value *FAILED indicates that secure communication failed, and unsecure communications were not allowed by policy.
- The value *UNKNOWN indicates the status cannot be determined due to an error or communication issue.
Resetting the historical communication status
Do the following from the management system:
- From the MIMIX Intermediate Main Menu, select option 2 (Work with Systems) and press Enter. You can optionally use the Work with Systems (WRKSYS) command.
- The Work with Systems display appears. Type 17 (Reset hist. comm.
status) to reset the historical communication mode status of the selected
system definition and press Enter.Note: The jobs running with unsecure communications must be restarted to ensure they are using secure connections.