You are not logged in.
You can indeed create a job on one Operating System, then deploy it and execute it on a different OS.
To achieve this task, simply follow the steps below:
1. Export a job on current Operating System.
2. Import the job onto the other Operating System.
3. Make some change if you need and run it.
However, if the job contains input/output components, the input/output paths should be changed to match the different Operating System.
Let's say, you want to migrate a job from Windows to Linux.
We advise you to use the context parameter to store the output path so that you can easily change the path once the job is imported to the other OS.
For example, add a variable myfileoutput1 with default value: F:/tmp/myfileoutput1.txt when working on Windows . Perform the export/import tasks to deploy your job onto Linuw. When you have deployed the job, change the default context parameter value of myfileoutput1to: /usr/tmp/myfileoutput1.txt as you are now on Linux.
You can define a context variable and set the value if you start the script. To get the file over systems boundaries you can use for example the "ftp-component".
I hope this is the information you search for.