Let us know how we can help
Sales & Pricing
Speak to a rep about your business needs
Help & Support
See our product support options
General inquiries and locations
Contact us
Control-M + Micro Focus
Your Micro Focus workflow starts before a JCL job stream ever executes — and it can fail when something upstream breaks. An MFBSIJCL submission can wait on required application data. A JES batch initiator can be unavailable when the overnight processing window starts. Control-M orchestrates the full chain: managed file arrival, COBOL preprocessing, Micro Focus JCL execution, and downstream database reconciliation.
common workflow issues
Does this sound like your week?
These aren’t edge cases. They’re the normal operating conditions for teams running Micro Focus JCL workloads across multiple tools. Here’s how Control-M handles each one.
UPSTREAM DEPENDENCY
The JCL is ready. The overnight input file still isn’t.
Control-M holds Micro Focus execution until the required upstream transfer or job completes, then submits the JCL through MFBSIJCL. Cross-platform dependencies replace disconnected schedules, preventing processing from starting against missing or incomplete inputs.
JCL FAILURE RECOVERY
STEP4 abended at 2:13 a.m. Reprocessing everything wastes the window.
Control-M captures the Micro Focus job result and supports rerunning a JCL job stream from and to defined steps or PROCs. Operations can recover the failed processing segment instead of automatically repeating the entire job stream.
SLA RISK
JES processing is running late. Downstream reconciliation has a hard deadline.
Control-M connects the Micro Focus job to the broader service SLA, monitors dependencies and execution progress, and surfaces predicted delays before the business deadline is missed. Operations sees the end-to-end service risk, not an isolated batch status.
OUTPUT TROUBLESHOOTING
The JCL ended. Now operations needs the SYSOUT to explain why.
Control-M adds Micro Focus SYSOUT to the job output and centralizes job status, results, and output in the monitoring environment. Operators can investigate the failed execution without treating the JCL workload as a disconnected scheduling island.
RESOURCE CONTENTION
Multiple critical JCL streams hit the same processing window at once
Control-M applies advanced scheduling criteria, resource pools, lock resources, and dependencies around Micro Focus execution. Teams can coordinate competing workloads and shared resources as part of the enterprise schedule instead of relying on independent batch timing.
INTEGRATION FACTS
Control‑M + Micro Focus
|
Platform & OS coverage |
UNIX/Linux · Windows · Micro Focus JES · Micro Focus Enterprise Server environments |
|
Job types supported |
Micro Focus Linux jobs · Micro Focus Windows jobs · JCL job streams · step/PROC reruns · SYSOUT capture |
|
SLA monitoring & alerting |
SLA job attachment · service-level monitoring · predictive SLA delay detection · automated alerts · dependency-aware escalation |
|
Audit trail & access controls |
secure connection profiles · centralized Micro Focus credentials · job status and results · SYSOUT capture · execution history · role-based Control-M access |
end-to-end orchestration
One production workflow. Every tool in the stack.
Control-M orchestrates workflows across Micro Focus, managed file transfers, databases, REST APIs, enterprise applications, and cloud services in a single job flow — with dependency tracking, SLA visibility, and automated recovery across all of them.
- Cross-tool dependency: managed file transfer → Micro Focus JCL → database reconciliation → reporting
- Data-aware triggers: file arrival, upstream job completion, API event, database process completion
|
Micro Focus |
JCL execution · JES integration · status monitoring · SYSOUT capture · step/PROC rerun |
|
Managed File Transfer |
secure file delivery · file arrival detection · workflow initiation · transfer monitoring |
|
Databases |
SQL execution · stored procedures · status-based dependencies · downstream processing |
|
REST APIs & Web Services |
API invocation · response monitoring · conditional execution · workflow coordination |
|
Enterprise applications |
batch coordination · cross-application dependencies · schedule alignment · completion tracking |
|
Cloud services |
hybrid workflow coordination · dependency management · application workflow integration · centralized monitoring |
MONITOR WORKFLOWS
Monitor Micro Focus JCL execution in one place
Micro Focus exposes execution inside its own environment, but enterprise operations often depend on jobs running before and after each JCL stream. Control-M provides centralized monitoring across Micro Focus and the surrounding workflow so operators can investigate problems in context:
-
JCL execution status
-
Job results and SYSOUT
-
Upstream and downstream dependencies
-
Runtime and execution history
-
End-to-end workflow visibility
SLA ASSURANCE
Keep Micro Focus batch services on schedule
A successful JCL submission does not guarantee the end-to-end business service will finish on time. Control-M connects Micro Focus execution to upstream and downstream dependencies, monitors SLA risk, and coordinates recovery so operations can protect critical processing windows:
-
SLA job attachment
-
Predictive SLA risk visibility
-
Cross-platform dependency tracking
-
Step-level JCL restart
-
Automated operational alerts
Documentation
Bring order to complex workflows
Learn how Control-M helps teams orchestrate complex processes with greater visibility, coordination, and control.
