Overview (TMS MERGE command)

The TMS MERGE command is used to merge a PMML file containing transformations with a PMML model file containing variables whose derivations are expressed by those transformations. 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. Transformations are exported as PMML using the TMS BEGIN and TMS END commands. See the topic TMS BEGIN for more information.

Basic Specification

The basic specification is the command name followed by DESTINATION, TRANSFORMATIONS, and MODEL subcommands that contain file specifications.

Syntax Rules

  • Each subcommand can be specified only once.
  • Subcommands may be used in any order.
  • An error occurs if a keyword is specified more than once within a subcommand.
  • Equal signs (=) shown in the syntax chart are required.
  • Subcommand names and keywords must be spelled in full.

Operations

  • TMS MERGE has no effect on the active dataset. It relies completely on the information contained in the transformations and model files.
  • TMS MERGE verifies that the paths specified for the input files and destination file are valid. The destination file is unavailable to other commands until the TMS MERGE command is ended.
  • An error occurs if properties of derived variables in the transformations file do not match the properties for those same variables in the model file--for example, conflicting definitions of missing values.

Limitations

  • TMS MERGE cannot be used to merge transformations with an ensemble model.
  • TMS MERGE cannot be used to merge transformations with a model that contains splits (separate model information for each split group).