Overview (TMS END command)

The TMS END command is used to indicate the end of a block of transformations to be exported to a file in PMML format--specifically, PMML 3.1 with IBM® SPSS® Statistics extensions. The exported transformations can be merged (using TMS MERGE) with a PMML model file in order to include any transformations of the raw data required to create the variables used in the model. The merged PMML file can be used to score data with scoring functions. (For more information on scoring functions, see Scoring expressions.) When you score data with a model file containing transformations, the transformations will be applied to the data before scoring. The transformations are carried out as part of the internal scoring process and have no effect on the active dataset. The TMS BEGIN command is used to indicate the beginning of the block.

Basic Specification

The basic specification for TMS END is the command name. For examples of TMS BEGIN-TMS END blocks, see the TMS BEGIN command.

Syntax Rules

  • An error occurs if the PRINT subcommand is specified more than once.
  • An error occurs if the RESULTS keyword is specified more than once.
  • Equal signs (=) shown in the syntax chart are required.
  • Subcommand names and keywords must be spelled in full.

Operations

  • TMS END will generate a warning if there is no TMS BEGIN command in effect. This condition occurs in the obvious case that there is no prior TMS BEGIN command, but will also occur if there is a TMS BEGIN command followed by a command that implicitly ends a TMS block--for instance, any statistical procedure or the EXECUTE command--followed by TMS END.
  • TMS END causes the destination file to be written, unless the associated TMS block ended implicitly (see previous bullet), thus causing the file to be written before execution of TMS END. For more information, see the Examples for the TMS BEGIN command.
  • TMS END does not cause transformations in the associated TMS block to be executed. In normal fashion, they are pending and will be executed with the next command that reads the active dataset.