migration from 3.6.12 to 5.1

migration from 3.6.12 to 5.1

sorry..asking just in case...
we used to use the scheduler to 'run script' as an action after the schedule is done.
i.e. the schedule actually runs a batch file at the scheduled time, then afterwards there's jal to check that the bat ran correctly.
the import function on the new version seems to have lost all that jal that runs afterwards..i suppose because there's no option to 'run script' after a schedule anymore...
i suppose we could 'runandwait' the batch files in jal and combine all the actions into 1 jal script.
but is there an easier way to do this?

Please separate the JAL script used for post-run action into a separate job with [no schedule] schedule type. Then in the main job link it via Run Another Job action

is there anything else we should look out for during such a migration?

The only other difference is handling database connections. The database profiles in MP Edition use platform independent JDBC based connectivity drivers. Old JAL profiles use platform dependent native drivers which are still available, but the profiles for JAL are registry based and not shared with other jobs. It is decremented that you use DabasaeConnectEx in JAL jobs to avoid references to database profiles.