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

Effective working directory without CD

When no explicit CD command runs, SPSS Statistics Server resolves relative paths in GET, SAVE, and OMS against the server process working directory, not the directory where the syntax file sits on the client. In a Production Facility job that process usually starts under the service account, so the effective directory is typically the service account home folder or the directory configured as the service startup/working directory. That is a likely explanation based on standard server behavior; the exact default depends on your SPSS version and operating system and should be treated as unverified until you check the job definition.

How the service account environment affects paths

The service account’s environment determines both the starting directory and whether the resolved path can be read or written. If the account cannot traverse a parent folder, the server may report file-not-found even when the file exists, because access denial can surface as a missing-file error. Client environment variables, mapped drives, and the submitting user’s profile are not inherited by the server process.

Configurable alignment options

Production Facility job definitions may expose a working-directory or startup-directory setting. If present, setting it to the client submission directory—or a shared directory containing the data files—aligns server-side resolution with the client. Changing that setting can affect every job that uses the same service account and may require a service restart, so test it in non-production first. The most reliable syntax-level fix is to avoid relative paths in production jobs.

Steps for this case

1. Open the failing Production Facility job definition and check whether a working directory or startup directory is specified.
2. If no directory is specified, replace relative references with absolute paths or UNC paths, for example GET FILE='C:/production/data/sales.sav'.
3. If you must keep relative syntax, insert an explicit CD command at the top of the job: CD 'C:/production/data'. Then verify subsequent GET, SAVE, and OMS references resolve relative to that folder.
4. Run the same syntax interactively under the Production Facility service account to reproduce the resolution and permission behavior, and inspect the job log for the actual error text.

Missing diagnostic detail

Does the Production Facility job definition specify an explicit working directory? If yes, use that directory as the base for relative paths or change the setting; if no, rely on absolute paths or CD because the default is the service account startup directory.

Assumption: this answer assumes SPSS Statistics Server executing Production Facility jobs as a service account. Exact defaults vary by version and platform; verify against your installation before changing service configuration.