Setting up a scheduled Migration Job with its output File Location set to write to a specific server folder, the output doesn't end up where expected — there's an LOV showing some already-configured file paths, but no obvious screen to add a new one to that list.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Check whether the Migration Job's File Location is actually set to 'OnClient' rather than a server-side location — when File Location is OnClient, the application writes the output file to the exact path entered on the CLIENT machine running the job, which can be a UNC path or a mapped network drive, as long as it's reachable from that specific client PC, not to a path on the server itself. This explains why the output doesn't appear on the server folder expected, and also why there's no dedicated screen to pre-register new server-side paths — an OnClient path is simply typed in directly rather than selected from a managed list.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions