How do I install the Control M skill?

Run npx skillmds@latest add joogy06/control-m in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Control M safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Control M?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Control M free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Control M?

joogy06 (@joogy06) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Control M by joogy06 — Agent Skill

Name: Control M
Author: joogy06

Control M

Use when working with BMC Control-M workload automation — server and agent administration, job definition (OS/Script/File Transfer/Database/Application Integrator/Web Services), scheduling (calendars, time zones, cyclic jobs), flow management (conditions, resources, quantitative/control resources), Automation API (jobs-as-code JSON, ctm CLI), monitoring and alerts (Control-M Web, viewpoints), SLA management, role-based access (admin/developer/operator roles), and RHEL agent deployment. Covers Control-M 9.0.21+ and Helix Control-M (SaaS).

joogy06 1f277f6 4 files · 37.2 KB Updated Sep 17, 2026

File contents

BMC Control-M Workload Automation

Covers Control-M 9.0.21+ (on-premises) and Helix Control-M (SaaS). Organized by role: Admin, Developer, Operator/User.

Reference Files

Detailed code examples, patterns, and configuration are in the reference files below. Read the relevant file when working on that area.

File	Covers
admin-role.md	server/agent administration, configuration, security, integrations, and infrastructure management
developer-role.md	job definition (OS/Script/File Transfer/Database/Application Integrator), scheduling, flow management, SLA management, and Automation API
operator-reference.md	operator/user tasks (monitoring, active jobs, troubleshooting, batch operations) and quick reference

Anti-Patterns

Anti-Pattern	Why It Fails	Correct Approach
Hardcoding paths and server names in job definitions	Jobs break when migrated between environments (dev/test/prod); maintenance requires editing every job	Use Control-M variables, AutoEdit substitution, and connection profiles for environment-specific values
Creating linear chains of 50+ jobs without sub-folders	Impossible to monitor, debug, or restart mid-chain; a single failure blocks the entire sequence	Break into logical sub-folders with condition-based dependencies; use Smart Folders for grouping
Setting no timeout or unrealistically long timeouts on jobs	Hung jobs hold resources indefinitely; downstream jobs wait forever; batch windows get missed	Set realistic timeouts based on historical runtime + buffer; configure alerts for jobs exceeding threshold
Running all batch jobs under a single service account	No auditability; a credential change breaks everything; violates least-privilege principle	Use dedicated service accounts per application or job group; rotate credentials on schedule
Skipping calendar validation when scheduling across time zones	Jobs fire at wrong times; DST transitions cause double-runs or missed runs	Use Control-M calendar objects with explicit timezone settings; test scheduling across DST boundaries

Related Skills

Domain	Skill
RHEL system administration	`rhel-server-admin`
Database administration on RHEL	`rhel-databases`
Docker/Podman on RHEL	`rhel-docker-host`
Monitoring (Prometheus/Grafana)	`rhel-monitoring`
CI/CD pipelines	`docker-cicd`

---name: control-mdescription: Use when working with BMC Control-M workload automation — server and agent administration, job definition (OS/Script/File Transfer/Database/Application Integrator/Web Services), scheduling (calendars, time zones, cyclic jobs), flow management (conditions, resources, quantitative/control resources), Automation API (jobs-as-code JSON, ctm CLI), monitoring and alerts (Control-M Web, viewpoints), SLA management, role-based access (admin/developer/operator roles), and RHEL agent deployment. Covers Control-M 9.0.21+ and Helix Control-M (SaaS).---# BMC Control-M Workload AutomationCovers Control-M 9.0.21+ (on-premises) and Helix Control-M (SaaS). Organized by role: Admin, Developer, Operator/User.<HARD-RULE>Always use conditions (In/Out) for job dependencies, never rely on scheduling time alone — time-based sequencing breaks when upstream jobs run late.</HARD-RULE><HARD-RULE>Never modify active (ordered) jobs in production without hold/free — in-flight changes cause unpredictable behavior.</HARD-RULE><HARD-RULE>Always use the Automation API (jobs-as-code) for version-controlled job definitions — manual GUI changes create configuration drift that is impossible to audit.</HARD-RULE><HARD-RULE>Never grant admin/full role to developer accounts — Control-M role separation exists to prevent accidental production job modifications.</HARD-RULE>---## Reference FilesDetailed code examples, patterns, and configuration are in the reference files below. Read the relevant file when working on that area.| File | Covers ||---|---|| [admin-role.md](admin-role.md) | server/agent administration, configuration, security, integrations, and infrastructure management || [developer-role.md](developer-role.md) | job definition (OS/Script/File Transfer/Database/Application Integrator), scheduling, flow management, SLA management, and Automation API || [operator-reference.md](operator-reference.md) | operator/user tasks (monitoring, active jobs, troubleshooting, batch operations) and quick reference |---## Anti-Patterns| Anti-Pattern | Why It Fails | Correct Approach ||---|---|---|| Hardcoding paths and server names in job definitions | Jobs break when migrated between environments (dev/test/prod); maintenance requires editing every job | Use Control-M variables, AutoEdit substitution, and connection profiles for environment-specific values || Creating linear chains of 50+ jobs without sub-folders | Impossible to monitor, debug, or restart mid-chain; a single failure blocks the entire sequence | Break into logical sub-folders with condition-based dependencies; use Smart Folders for grouping || Setting no timeout or unrealistically long timeouts on jobs | Hung jobs hold resources indefinitely; downstream jobs wait forever; batch windows get missed | Set realistic timeouts based on historical runtime + buffer; configure alerts for jobs exceeding threshold || Running all batch jobs under a single service account | No auditability; a credential change breaks everything; violates least-privilege principle | Use dedicated service accounts per application or job group; rotate credentials on schedule || Skipping calendar validation when scheduling across time zones | Jobs fire at wrong times; DST transitions cause double-runs or missed runs | Use Control-M calendar objects with explicit timezone settings; test scheduling across DST boundaries |---## Related Skills| Domain | Skill ||---|---|| RHEL system administration | `rhel-server-admin` || Database administration on RHEL | `rhel-databases` || Docker/Podman on RHEL | `rhel-docker-host` || Monitoring (Prometheus/Grafana) | `rhel-monitoring` || CI/CD pipelines | `docker-cicd` |

Frequently asked questions