IMS Queue Control Facility

The architecture of IMS Queue Control Facility centers around three primary components: the Queue Monitor, the Requeue Processor, and the Offload Manager. The Queue Monitor continuously tracks queue activity, collecting metrics such as message counts and queue depths. The Requeue Processor is activated during IMS cold starts to handle messages that were in-flight during the outage, ensuring no data loss.

The Offload Manager automates the process of moving messages from active queues to offload datasets based on predefined thresholds. Communication between these components occurs through internal z/OS mechanisms and IMS APIs. Configuration is managed via control statements and parameter datasets, which define thresholds, requeuing criteria, and logging levels.

The ISPF interface provides a central point for monitoring and management. The product integrates with the z/OS security infrastructure, leveraging RACF or similar systems for access control. The product does not use a database for persistent storage; it relies on IMS queues and datasets.

Network requirements are minimal, as the product primarily interacts with IMS and z/OS components on the same system. The product does not expose any external APIs.