%let indconn = server=yourserver user=youruserid password=yourpwd database=yourdb schema=yourschema serveruserid=yourserveruserid;
specifies the DB2 user name (also called the user ID) that is used to connect to the database.
specifies the password that is associated with your DB2 user ID.
| Tip | Use only PASSWORD=, PASS=, or PW= for the password argument. PWD= is not supported and causes an error. |
specifies the DB2 database that contains the tables and views that you want to access.
| Requirement | The scoring model functions are created as Unicode functions.
If the database is not a Unicode database, then the alternate collating
sequence must be configured to use identity_16bit.
|
specifies the DB2 server name or the IP address of the server host.
| Restriction | This argument is required when using function-based scoring. It is not used if you use the SAS Embedded Process. |
| Requirement | The name must be consistent with how the host name was cached when SFTP server was run from the command window. If the full server name was cached, you must use the full server name in the SERVER argument. If the short server name was cached, you must use the short server name. For example, if the long name, disk3295.unx.comp.com, is used when SFTP was run, then server=disk3295.unx.comp.com must be specified. If the short name, disk3295, was used, then server=disk3295 must be specified. For more information about running the SFTP command, see “DB2 Installation and Configuration Steps” in the SAS In-Database Products: Administrator’s Guide. |
specifies the schema name for the database.
| Default | If you do not specify a value for the SCHEMA argument, the value of the USER argument is used as the schema name. |
specifies the user ID for SAS SFTP and enables you to access the machine on which you have installed the DB2 database.
| Default | If you do not specify a value for the SERVERUSERID argument, the value of the USER argument is used as the user ID for SAS SFTP. |
| Restriction | This argument is not used if you use the SAS Embedded Process. |
| Note | The person who installed and configured the SSH software can provide the SERVERUSERID (SFTP user ID) and the private key that need to be added to the pageant.exe (Windows) or SSH agent (UNIX). In order for the SFTP process to be successful, Pageant must be running on Windows and the SSH agent must be running on UNIX. |
specifies the directory where the scoring model program, the properties file, and the format catalog are located.
| Requirement | You must use a fully qualified pathname. |
| Interaction | If you do not use the default directory that is created by SAS Enterprise Miner, you must specify the DATASTEP=, XML=, and (if needed) FMTCAT= arguments. |
| See | Special Characters in Directory Names |
specifies the name that is prepended to each output function to ensure that each scoring function name is unique on the DB2 database. If you use the SAS Embedded Process, the model name is the primary index field in the model table.
| Restriction | The scoring function name is a combination of the model and output variable names. A scoring function name cannot exceed 128 characters. For more information, see Scoring Function Names. |
| Requirement | If you use scoring functions, the model name must be a valid SAS name that is 10 characters or fewer. If you use the SAS Embedded Process, the model name can be up to 128 characters. For more information about valid SAS names, see the topic on rules for words and names in SAS Language Reference: Concepts. |
| Interaction | Only the EM_ output variables are published as DB2 scoring functions. For more information about the EM_ output variables, see Fixed Variable Names and Scoring Function Names. |
specifies whether scoring functions or scoring files are created. MECHANISM= can have one of the following values:
specifies that scoring functions are created.
| See | Using Scoring Functions to Run Scoring Models |
specifies that scoring files are created.
| Requirement | If you specify MECHANISM=EP, you must also specify the MODELTABLE= argument. |
| Note | The SAS Embedded Process might require a later release of DB2 than function-based scoring. For more information, see the SAS Foundation system requirements documentation for your operating environment. |
| See | Using the SAS Embedded Process to Run Scoring Models |
| Default | STATIC |
specifies the name of the model table where the scoring files are published.
| Default | sas_model_table |
| Restriction | This argument is valid only when using the SAS Embedded Process. |
| Requirement | The name of the model table must be the same as the name specified in the %INDB2_CREATE_MODELTABLE macro. For more information, see the MODELTABLE argument in %INDB2_CREATE_MODELTABLE Macro Syntax. |
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. |
| 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. |
specifies the name of the properties XML file that was created by the SAS Enterprise Miner Score Code Export node.
| Default | score.xml |
| Restrictions | Only XML files that are produced by the SAS Enterprise Miner Score Code Export node can be used. |
| If you use scoring functions to run scoring models, the maximum number of output variables is 128. If you use the SAS Embedded Process, the maximum depends on the page size of the database tablespace. For a 4K page size database, the limit is 500. If you have it configured for any of the larger page sizes (8K, 16K, 32K), then the limit is 1012. | |
| 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. |
specifies the name of a DB2 database to which the scoring functions and formats or the scoring files are published.
| Requirements | The scoring model functions are created as Unicode functions.
If the database is not a Unicode database, then the alternate collating
sequence must be configured to use identity_16bit.
|
| If you use the SAS Embedded Process, the name of the database must be the same as the database specified in the %INDB2_CREATE_MODELTABLE macro. For more information, see the DATABASE argument in %INDB2_CREATE_MODELTABLE Macro Syntax. | |
| Interaction | The database that is specified by the DATABASE argument takes precedence over the database that you specify in the INDCONN macro variable. For more information, see %INDB2_PUBLISH_MODEL Macro Run Process. |
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.
| Restriction | Only format catalog files that are produced by the SAS Enterprise Miner Score Code Export node can be used. |
| 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. |
specifies one of the following actions that the macro performs:
creates new functions or files.
overwrites the current functions or files, if functions or files by the same name are already registered.
causes all functions or files for this model to be dropped from the DB2 database.
| Default | CREATE |
| Tip | If the function or file has been previously defined and you specify ACTION=CREATE, you receive warning messages from DB2. If the function or file has been previously defined and you specify ACTION=REPLACE, no warnings are issued. |
specifies whether the running code is isolated in a separate process in the DB2 database so that a program fault does not cause the database to stop.
| Default | FENCED |
| Restriction | This argument is valid only when using the scoring functions. It has no effect if you specify MECHANISM=EP. |
| Tip | After the SAS scoring functions are validated in fenced mode, you can republish them in unfenced mode. You might see a performance advantage when you run in unfenced mode. |
| See | Modes of Operation |
specifies the initial wait time in seconds for SAS SFTP to parse the responses and complete the SFTP -batchfile process.
| Default | 15 seconds |
| Restriction | This argument is valid only when using the scoring functions. It has no effect if you specify MECHANISM=EP. |
| Interactions | The INITIAL_WAIT= argument works in conjunction with the FTPTIMEOUT= argument. Initially, SAS SFTP waits the amount of time specified by the INITIAL_WAIT= argument. If the SFTP -batchfile process is not complete after the initial wait time, retries occur until the wait time is equal to or greater than the time-out value specified by the FTPTIMEOUT= argument. All retries double the previous wait time. SAS SFTP fails after the time-out value is reached or exceeded, and an error message is written to the SAS log. |
| For example, assume that you use the default values. The initial wait time is 15 seconds. The first retry waits for 30 seconds. The second retry waits for 60 seconds. The third retry waits for 120 seconds. This is the default time-out value. So, the default initial wait time and time-out values enable four possible tries: the initial try plus three retries. | |
| See | FTPTIMEOUT= argument |
specifies the time-out value in seconds if SAS SFTP fails to transfer the files.
| Default | 120 seconds |
| Restriction | This argument is valid only when using the scoring functions. It has no effect if you specify MECHANISM=EP. |
| Interactions | The FTPTIMEOUT= argument works in conjunction with the INITIAL_WAIT= argument. Initially, SAS SFTP waits the amount of time specified by the INITIAL_WAIT= argument. If the SFTP -batchfile process is not complete after the initial wait time, retries occur until the wait time is equal to or greater than the time-out value specified by the FTPTIMEOUT= argument. All retries double the previous wait time. SAS SFTP fails after the time-out value is reached or exceeded and an error message is written to the SAS log. |
| For example, assume that you use the default values. The initial wait time is 15 seconds. The first retry waits for 30 seconds. The second retry waits for 60 seconds. The third retry waits for 120 seconds. This is the default time-out value. So the default initial wait time and time-out values enable four possible tries: the initial try plus three retries. | |
| Tip | Use this argument to control how long SAS SFTP waits to complete a file transfer before timing out. A time-out failure could indicate a network or key authentication problem. |
| See | INITIAL_WAIT= argument |
specifies a directory that contains diagnostic files.
| Tip | This argument is useful when testing your scoring models. |
| See | Special Characters in Directory Names |