Limits of OMS Selection Granularity in SPSS Statistics

Goal

To route only specific output types (e.g., pivot tables) from a SPSS job to a file while preserving enough contextual information for later interpretation.

Constraints & Uncertainty

OMS captures only output generated after the OMS request begins, so pre‑existing tables in the Viewer are never routed. The OMS command allows selecting by TYPE and SUBTYPE, but narrowing the selection can drop surrounding headings, notes, and warnings that are often essential for understanding the routed tables. Additionally, routed pivot tables become data files that include bookkeeping variables such as Command_ and Subtype_, which may need filtering for downstream use.

Unresolved Questions

1. When a narrow OMS selection (e.g., only TYPE='TABLE' with SUBTYPE='PIVOT') is used, what contextual information is omitted, and how does this affect the interpretability of the routed table?
2. Is there a recommended strategy for including necessary contextual output (headings, notes, warnings) when routing specific output types without overwhelming the routed file with unrelated information?