Need more information and help to understand how to convert the job scheduler from CA NSM JMO to CA Workload Automation AE.
What I discovered in my environment when it was converted two years ago, was that one of the biggest challenges was the difference in handling cross-dependencies between boxes compared to the old jobsets in JMO. Filetriggers can be useful. aving different starting times in a box was also a interesting challenge, especially when all jobs should not run on every iteration. Placing jobs on autohold and then at a time set them off-hold or set them to success or even kill them can be useful. A big challenge was also converting all NSM EM-rules and stop using NSM EM and only depend on Autosys/WAAE.
Good luck in converting.
Realizing it will not necessarily be a 1:1 conversion. ;-)
and the calendars are a bit different as well. Understanding Box logic replacing application and group.
in 4.5 very much so. for R11. I think some of the differences have been removed. It's all about looking at the 2 and realizing want you need to do.
When I am assigned , I audit everything first. Then move forward.
Unfortunately your question is very broad and so understanding why you ask will help.
Are you a JMO person or an Autosys person?
To convert the JMO objects defintions (cauexpr.txt) to Autosys jil is not so difficult. There are tools to do that.
According to me, the most difficult things are:
1. No qualifier in Autosys: a daily box must end to start again. In JMO, a failed jobset can stay at tracking to be 'solved' later. So you must find a solution for daily job flows that last more than 24 hours.
2. Analyze the message-records actions in NSM Event Management to translate that in jil.
3. Scan the scripts on agents to find cautil/cawto/cawtor/caevent commands
For 2 & 3, as JMO is not event driven, most of customers add cautil commands in MRA and scripts to modify dynamically the tracking (Demand, Hold, Release, Cancel, Alter tjobparm ....)
In addition to Mathieu's reply, during such a conversation it might also be time to redesign some JMO jobflows to simplify them.
As there is no tracking file like JMO in Autosys, "Look-Back Dependencies" which are described in the CA WAAE Reference Guide can also help in some situation
Retrieving data ...