SCON

SCON's architecture centered on consolidating console messages from multiple MVS images into a single 3270 session. The key components included message capture modules, a consolidation engine, and a 3270 presentation layer. Configuration files defined the MVS images to monitor and the rules for message filtering.

SCON lacked standard APIs, relying on its 3270 interface. It used z/OS security mechanisms for authentication and access control. Competing products like IBM Z ChatOps offer REST APIs for integration and enhanced automation.

SCON's administrative interface was through configuration files, defining message consolidation parameters. Monitoring capabilities focused on providing a consolidated view of system events to aid in problem determination. SCON is no longer supported, and organizations should consider migrating to alternatives like BMC AMI Ops Automation or IntelliMagic Vision for z/OS.

Migration involves re-architecting monitoring workflows to leverage the capabilities of the new platform. The absence of APIs in SCON necessitates a different integration approach with modern monitoring ecosystems.