Limits of OMS Selection Granularity in SPSS Statistics

Direct answer

A narrow OMS selection such as TYPE='TABLE' SUBTYPE='PIVOT' routes only the pivot-table object. Procedure titles, headings, footnotes, notes, and warnings are separate Viewer objects, so they are omitted. The routed table therefore lacks its explanatory context. If the destination is a dataset, SPSS flattens the table into cases and adds bookkeeping variables such as Command_ and Subtype_, which downstream consumers must filter or use to reconstruct the original layout.

Likely explanation versus confirmed facts

Likely explanation: OMS evaluates each output object independently against the TYPE and SUBTYPE filter. Text objects do not carry the table's subtype, so a table-only request excludes them even when they appear immediately above or below the table in the Viewer.

Confirmed facts: OMS captures only output generated after the OMS command starts; pre-existing Viewer output is never routed. Subtype names and destination behavior vary across SPSS Statistics versions. Dataset destinations lose the pivot table's visual layout and multi-level headers.

Steps for this case

1. Run OMSINFO to confirm the exact TYPE and SUBTYPE labels for the procedures you plan to route.
2. Create a second OMS request scoped to the same COMMANDS filter, selecting only the text objects you need—typically headings, notes, and warnings—rather than an unfiltered TEXTS selection.
3. Route both requests to separate dataset destinations, or use OXML if you want headings, notes, warnings, and the pivot table in one structured file.
4. Close both requests with OMSEND, then inspect the destination file for Command_ and Subtype_ to link tables to their associated text records.

Illustrative syntax scope

OMS
  /SELECT TABLES
  /IF COMMANDS=['FREQUENCIES'] SUBTYPES=['PIVOT']
  /DESTINATION FORMAT=SAV OUTFILE='routed_tables.sav'.

OMS
  /SELECT TEXTS
  /IF COMMANDS=['FREQUENCIES']
  /DESTINATION FORMAT=SAV OUTFILE='routed_context.sav'.

* procedure runs here *

OMSEND.

The /IF keywords above are version-dependent. Verify them with OMSINFO before using the syntax in production.

Missing diagnostic detail

Are you writing routed output to a dataset (SAV) or to OXML? This determines whether you align two dataset files using bookkeeping variables or extract context from a single OXML hierarchy.

Verification

• Run a small test job that produces a table with a known heading, note, and warning, then apply the narrow selection and inspect the destination file to confirm which objects are missing.
• Compare the Viewer outline tree against OXML output to verify that headings, notes, and warnings are preserved.
• Open the routed dataset and check Command_ and Subtype_ to ensure they can reliably link tables to associated text records.