When you say “handshake”, are you referring to dependencies (in/out conditions)?
I would work the phases where the dependents are grouped together in the migration. If that is not possible, you need something in between to sync the two with conditions.
Without knowing your environment and what systems you have available, it makes suggestions difficult, but there is always a way. You would certainly be working with no support… meaning you’d be supporting yourself. (Assuming BMC has not provided any solution).
We have a similar situation here, two scheduling tools that can not share conditions (long story, but we’re almost completely on Control-M now).
We created a process where jobs on one scheduler will send information (via email) that lands in a directory on a certain machine. A trigger of the file arriving executes a script to update the scheduling db with the appropriate condition (to add or remove a dependency).
There are some risks in this process where as email is vital for batch initiation and control. (email has become vital to the business regardless, so this is minor issue as any problems will be address quickly). Also the box or filesystem that receives the incoming information has issues, it could affect SLA’s.
Bottom-line… you add complexity which inherits risk.
You may also want to check with the Control-M user group on yahoo.com called “control-x” which you can find at this address:
http://tech.groups.yahoo.com/group/Control-X/
