AutoSys Job not waiting for script to complete

view full story

http://www.unix.com – I'm not sure if this is the right place to post this issue...but here goes... I am converting a set of windows jobs from Control-M to AutoSys r11.3. The same command line is being executed in both systems. The Control-M job runs to compltion in about 1.5 hours, waiting for the entire batch script to complete before an exit code is returned. When the same command line is executed in AutoSys...the script is kicked off, but the AutoSys job completes in under 60 seconds. The customer verifies that the backup that was kicked off IS actually running, but for some reason...the AutoSys job is n (HowTos)