ESP → Control-M
Migrating to Control-M from ESP.
Concept-by-concept
What changes, what stays the same.
Three paths, one destination
Engagement shaped to your team. Methodology comes from BMC.
- Advisory. Your team leads. We coach your conversion-rule design in the Control-M Self Conversion Tool, review outputs, and stay close through validation and cutover.
- Blended — where most engagements run. Your team owns the parts where you want to stay close. Our ESP-experienced team owns the parts where deep Control-M expertise pays off. The line moves as the project moves.
- Comprehensive. We run the conversion end to end using the Control-M Conversion Tool, while your team stays focused on day-to-day operations.
What the assessment looks like
Sample WayPoint output.
- Illustrative output · ESP → Control-M
What drives the work
Scope and timeline are confirmed in the assessment.
Frequently asked
ESP → Control-M questions.
Will Control-M for z/OS handle our JCL the way ESP does?
Control-M for z/OS submits standard JCL and integrates with the same mainframe submission services ESP does. JCL is preserved verbatim during conversion in nearly all cases. Where ESP-specific syntax appears inside JCL — typically symbolic substitutions — the conversion translates them into Control-M Auto-Edit Variables.
What happens to RACF / ACF2 / Top Secret mappings?
Mainframe security mapping is signed off by the customer’s mainframe security team in the assessment phase. Control-M for z/OS supports the same integrations ESP supports. The translation is mechanical, but the sign-off is not optional — the security team owns it.
Can we run ESP and Control-M in parallel during cutover?
Yes. For mainframe environments specifically, parallel test routinely extends to four to six weeks to capture full month-end and quarter-end coverage before cutover.