DSXchange

This is more for documentation for other users.

I just ran into this issue and wanted to document it in case someone else ran into it.

I just found out that if you have a job that is scheduled on server 1 . If you export that job from server2 and import it onto server1 the schedule that was previously there for that job on server1 is now gone. This apparently is normal behavior on UNIX (dunno about Windows, but I assume it's the same).

So, make sure you know what your schedules are (or back up the cron) before you migrate jobs from another server.

That is all,
Tony

I would assume the same, seeing as how the Import first deletes the original job and then creates a new version (with a new internal number) when in brings in the replacement.

I knew that logically... I don't guess I ever really had anyone complain about it and had to work it out.

Thanks for the input, Craig. Long time no talk to.

Tony