SPSS Production Facility job fails with file-not-found when using relative paths

When migrating SPSS syntax from local desktop mode to a Production Facility job that runs against a Statistics Server, the same relative file references in GET, SAVE, or OMS commands may succeed locally but fail with file‑not‑found or permission errors in production. The goal is to understand how the server determines the working directory for these jobs and what factors influence path resolution when no explicit CD command is used.

What is the effective working directory for a Production Facility job when no explicit CD command is issued? How does the Production Facility service account’s environment affect the interpretation of relative paths in SPSS commands? Are there configurable options to align the server‑side working directory with the client submission directory?