Why we are using Control M

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
nareshketepalli
Participant
Posts: 36
Joined: Mon Jun 28, 2010 11:24 pm
Location: seepz

Why we are using Control M

Post by nareshketepalli »

Why we are using Control M insted of data stage director?

Thanks
NARESHKUMAR
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

I give up, why?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
FranklinE
Premium Member
Premium Member
Posts: 739
Joined: Tue Nov 25, 2008 2:19 pm
Location: Malvern, PA

Post by FranklinE »

In my case, because DataStage is one of about 6 different code execution platforms that have to run in a unified schedule. We have batch schedules that run from z/OS to Unix and back, Unix to Windows and back, etc.

It's easy to train an operator in Control-M and be done with it. It's much more difficult to train him in 6 different interfaces and keep him up to speed on the changes in each one.
Franklin Evans
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson

Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Ah... the wonders of an Enterprise Scheduler.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply