We are moving from Linux Platform to Windows Platform. For one of the users, their jobs were not brought over for some reason. I ran a jobdump on Linux, modified all the data that needed to change to load on Windows (user, file paths, product line, etc). I brought the dump file over to the Windows server. I ran jobload without committing first and received no errors. I ran it again, this time with the "-c" option and all the jobs loaded fine. I logged in as that user and all the jobs were visible, I could bring them up and submit them. Some of these jobs get submitted via a process flow which was when I first had the issue that the jobs were immediately going into needs recovery with just a Stopped on Exit 1 (nothing in any of the logs and no time was logged to the job). I thought it was an issue with the process flow. I then attempted to run the job just in jobdef and received the same error. I tried some of the other jobs and none of them would run. I then created a new job, using one of the same programs as a job that wouldn't run, and it ran to a successful completion. I've never had an issue going Unix to Unix with a jobdump/jobload - but Linux to Windows seems to be an issue. Can anyone tell me what I might be doing wrong? There are hundreds of jobs and I don't want to have to create them all manually. Thanks in advance.
