%INDSP_PUBLISH_MODEL Macro Syntax

Note: The %INDSP_PUBLISH_MODEL and the %INDSP_RUN_MODEL must be run from sessions that use the same encoding or locale.
%INDSP_PUBLISH_MODEL
( MODELNAME=name, INPUTDIR=input-directory-path
<, DATASTEP=score-program-filename>
<, XML=xml-filename>
<, FMTCAT=format-catalog-filename | libref.format-catalog-filename>
<, ACTION=CREATE | REPLACE | DROP>
);
Arguments

MODELNAME=name

specifies the name that is prepended to the SPD Server tables that are created after the %INDSP_PUBLISH_MODEL macro runs.

Requirement The model name cannot exceed ten characters and must be a valid SAS name. For more information about valid SAS names, see the topic on rules for words and names in SAS Language Reference: Concepts.
Tip After the model is published, two SPD Server tables are created in the INDCONN domain: modelname_ARGS and modelname_PKG. If you have user-defined formats in the model, an additional table, modelname_FMT, is created.

INPUTDIR=input-directory-path

specifies the directory where the scoring model program, the properties file, and the format catalog are located.

This is the directory that is created by the SAS Enterprise Miner Score Code Export node. This directory contains the score.sas file, the score.xml file, and (if user-defined formats were used) the format catalog.
Restriction You must use a fully qualified pathname.
See Special Characters in Directory Names

DATASTEP=score-program-filename

specifies the name of the scoring model program file that was created by using the SAS Enterprise Miner Score Code Export node.

Default score.sas
Restriction Only DATA step programs that are produced by the SAS Enterprise Miner Score Code Export node can be used.
Requirement The scoring model program file must be located in the INPUTDIR directory.
Interaction If you use the default score.sas file that is created by the SAS Enterprise Miner Score Code Export node, you do not need to specify the DATASTEP= argument.

XML=xml-filename

specifies the name of the properties XML file that was created by the SAS Enterprise Miner Score Code Export node.

Default score.xml
Restriction Only XML files that are produced by the SAS Enterprise Miner Score Code Export node can be used.
Requirement The properties XML file must be located in the INPUTDIR directory.
Interaction If you use the default score.xml file that is created by the SAS Enterprise Miner Score Code Export node, you do not need to specify the XML= argument.

FMTCAT=format-catalog-filename | libref.format-catalog-filename

specifies the name of the format catalog file that contains all user-defined formats that were created by the FORMAT procedure and that are referenced in the DATA step scoring model program.

Default FORMATS
Restriction Only format catalog files that are produced by the SAS Enterprise Miner Score Code Export node can be used.
Requirement If the catalog is specified as a one-level name, it is expected to be found in the same location as the scoring model program (score.sas) and the scoring model XML file (score.xml). If the catalog is specified as a two-level name (libref.format-catalog-name), the catalog is expected to be found using the two-level name.
Interactions If you use the default format catalog that is created by the SAS Enterprise Miner Score Code Export node, you do not need to specify the FMTCAT= argument.
If you do not use the default catalog name (FORMATS) or the default library (WORK or LIBRARY) when you create user-defined formats, you must use the FMTSEARCH system option to specify the location of the format catalog. For more information, see PROC FORMAT in the Base SAS Procedures Guide.

ACTION=CREATE | REPLACE | DROP

specifies one of the following actions that the macro performs:

CREATE

creates a new model.

Note If the model by the same name exists, an error occurs.

REPLACE

overwrites the current model, if a model with the same name is already registered.

Note If the current model does not exist, an error occurs.

DROP

causes the model to be deleted.

Notes If you specify ACTION=DROP, the modelname_ARGS, modelname_PKG, modelname_THR, and if created, modelname_FMT tables are also deleted.
If the model does not exist, an error occurs.
Default CREATE