Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Please recommend an approach to achieving familiarity, fluency, and eventually expertise in Control-M. The immediate problem domain is "potent stakeholders have urged the migration of a zoo of hundreds of cron jobs, some quite elderly, to Control-M," and the immediate platform is Solaris.

share|improve this question

closed as off-topic by masegaloeh, kasperd, joeqwerty, Katherine Villyard, Nathan C Apr 17 '15 at 15:46

This question appears to be off-topic. The users who voted to close gave this specific reason:

If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 1 down vote accepted

I don't know how the job scheduler on Control-M works, but it is quite easy to fake a Control-M environment for testing an app. It has shell script scaffolding on unix and batch files on Windows.

I found it quite easy to emulate Control-M for the purposes of testing offline running of a job. This was achieved by taking one of its template scripts and modifying it. It took about half a day to get working - mainly tracing back through its other scripts to find the origin of some of the variables.

I'm guessing the the job scheduler's bark is probably worse than its bite. The scripts should give you some insight into how it handles error conditions.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.