If you are upgrading from a previous release, follow the instructions in Upgrading from a Previous Version before installing the in-database deployment package.
Install the SAS formats library and the binary files.

For more information, see Installing the SAS Formats Library and Binary Files .
Install the SAS Embedded Process.

For more information, see Installing the SAS Embedded Process.
Run the %INDGP_PUBLISH_COMPILEUDF macro if you want to publish formats or use scoring functions to run a scoring model. Run the %INDGP_PUBLISH_COMPILEUDF_EP macro if you want to use the SAS Embedded Process to run a scoring model or other SAS software that requires it.

For more information, see Running the %INDGP_PUBLISH_COMPILEUDF Macro or Running the %INDGP_PUBLISH_COMPILEUDF_EP Macro.
If you plan to use SAS Model Manager with the SAS Scoring Accelerator for in-database scoring, perform the additional configuration tasks provided in Configuring SAS Model Manager.

Note: If you are installing the SAS High-Performance Analytics environment, there are additional steps to be performed after you install the SAS Embedded Process. For more information, see SAS High-Performance Analytics Infrastructure: Installation and Configuration Guide.

Upgrading from a Previous Version

Upgrading the 9.3 SAS Formats Library and SAS Embedded Process

To upgrade from the SAS 9.3 version, follow these steps:

Delete the full-path-to-pkglibdir/SAS directory that contains the SAS Formats Library and the SAS Embedded Process.
Note: You can use the following command to determine the full-path-to-pkglibdir directory.
```
pg_config --pkglibdir
```
If you did not perform the Greenplum install, you cannot run the pg_config --pkglibdir command. The pg_config --pkglibdir command must be run by the person who performed the Greenplum installation.
CAUTION:

If you delete the SAS directory, all the scoring models that you published using scoring functions and all user-defined formats that you published are deleted.

If you previously published scoring models using scoring functions or if you previously published user-defined formats, you must republish your scoring models and formats. If you used the SAS Embedded Process to publish scoring models, the scoring models are not deleted.

It is a best practice to delete the SAS directory when you upgrade from a previous version. Doing so ensures that you get the latest version of both the SAS Formats Library and the SAS Embedded Process.
Continue the installation instructions in Installing the SAS Formats Library and Binary Files .

Upgrading the 9.4 SAS Formats Library and SAS Embedded Process

To upgrade from the SAS 9.4 version, follow these steps. If you upgrade or install the SAS Formats Library and the SAS Embedded Process in this manner, you do not delete any scoring models or formats that were previously published.

Log on to the Greenplum master node as a superuser.
Run the UninstallSASEPFiles.sh file.
```
./UninstallSASEPFiles.sh
```
This script stops the SAS Embedded Process on each database host node. The script deletes the /SAS/SASTKInDatabaseServerForGreenplum directory and all its contents from each database host node.

Before the fourth maintenance release of SAS 9.4 (November 2016), the UninstallSASEPFiles.sh file is in the path_to_sh_file directory where you copied the tkindbsrv self-extracting archive file.

Starting with the fourth maintenance release of SAS 9.4 (November 2016) and later, the UninstallSASEPFiles.sh file is in the path_to_sh_file/SASEPHome/bin directory.

CAUTION:

The timing option must be off for the UninstallSASEPFiles.sh scripts to work.

Put \timing off in your .psqlrc file before running this script.
Move to the directory where the SAS Formats Library is installed.

The directory path is full-path-to-pkglibdir/SAS/.
Note: You can use the following command to determine the full-path-to-pkglibdir directory.
```
pg_config --pkglibdir
```
If you did not perform the Greenplum install, you cannot run the pg_config --pkglibdir command. The pg_config --pkglibdir command must be run by the person who performed the Greenplum install.
Delete the libjazxfbrs.so and sas_compileudf.so files.
In addition to deleting the libjazxfbrs.so and sas_compileudf.so files on the master node, you must log on to each host node and delete the files on these nodes.
Continue the installation instructions in Installing the SAS Formats Library and Binary Files .

Installing the SAS Formats Library and Binary Files

Move and Install the SAS Formats Library and Binary Files

The SAS formats library and the binary files for the publishing macros are contained in a self-extracting archive file. The self-extracting archive file is located in the SAS-installation-directory/SASFormatsLibraryforGreenplum/3.1/GreenplumonLinux64/ directory.

To move and unpack the self-extracting archive file, follow these steps:

Using a method of your choice, transfer the accelgplmfmt-3.1-n_lax.sh file to your Greenplum master node. n is a number that indicates the latest version of the file. If this is the initial installation, n has a value of 1. Each time you reinstall or upgrade, n is incremented by 1.

The file does not have to be downloaded to a specific location. However, you should note where the file is downloaded so that it can be executed at a later time.
After the accelgplmfmt-3.1-n_lax.sh has been transferred, log on to the Greenplum master node as a superuser.
Move to the directory where the self-extracting archive file was downloaded.
Use the following command at the UNIX prompt to unpack the self-extracting archive file:
```
./accelgplmfmt-3.1-n_lax.sh
```
Note: If you receive a “permissions denied” message, check the permissions on the accelgplmfmt-3.1-n_lax.sh file. This file must have EXECUTE permissions to run.
After the script runs and the files are unpacked, the content of the target directories should look similar to these where path_to_sh_file is the location to which you copied the self-extracting archive file.
```
/path_to_sh_file/SAS/SASFormatsLibraryForGreenplum/3.1-1/bin/
    InstallAccelGplmFmt.sh
/path_to_sh_file/SAS/SASFormatsLibraryForGreenplum/3.1-1/bin/
    CopySASFiles.sh 
/path_to_sh_file/SAS/SASFormatsLibraryForGreenplum/3.1-1/lib/
    SAS_CompileUDF.so
/path_to_sh_file/SAS/SASFormatsLibraryForGreenplum/3.1-1/lib/
    libjazxfbrs.so 
```
Use the following command to place the files in Greenplum:
```
./path_to_sh_file/SAS/SASFormatsLibraryForGreenplum/3.1-1/bin/
    CopySASFiles.sh
```
CAUTION:

The timing option must be off for the CopySASFiles.sh script to work.

Put \timing off in your .psqlrc file before running this script.

This command replaces all previous versions of the libjazxfbrs.so file.

All the SAS object files are stored under full-path-to-pkglibdir/SAS. The files are copied to the master node and each of the segment nodes.
Note: You can use the following command to determine the full-path-to-pkglibdir directory:
```
pg_config --pkglibdir
```
If you did not perform the Greenplum install, you cannot run the pg_config --pkglibdir command. The pg_config --pkglibdir command must be run by the person who performed the Greenplum install.
Note: If you add new nodes at a later date, you must copy all the binary files to the new nodes. For more information, see Step 6.
(Optional) If you add new nodes to the Greenplum master node after the initial installation of the SAS formats library and publishing macro, you must copy all the binaries in the full-path-to-pkglibdir/SAS directory to the new nodes using a method of your choice such as scp /SAS. The binary files include SAS_CompileUDF.so, libjazxfbrs.so, and the binary files for the already published functions.

Installing the SAS Embedded Process

Unzipping the SAS Embedded Process for Greenplum

The SAS Embedded Process is contained in a self-extracting archive file named sepcoregplm-12.00000-1.sh. This file is contained in a ZIP file that is put in your SAS Software Depot directory. You need this file if you want to run your scoring model.

To unzip the SAS Embedded Process file for Greenplum, follow these steps:

Create a new temporary directory on your client machine such as /sasep. The new directory is referred to as EPZipDir throughout this section.
Navigate to the YourSASDepot/standalone_installs directory. This directory was created when you created your SAS Software Depot.
Locate the en_sasexe.zip file. The en_sasexe.zip file is located in the YourSASDepot/standalone_installs/SAS_Core_Embedded_Process_Package_for_Greenplum/12_0/Greenplum_on_Linux_x64/ directory.

The sepcoregplm-12.00000-1.sh file is included in this ZIP file.
Copy the en_sasexe.zip file to your EPZipDir temporary directory on the client machine.
```
cp en_sasexe.zip /EPZipDir
```
Navigate to your EPZipDir temporary directory and unzip en_sasexe.zip.

After the file is unzipped, a sasexe directory is created in the same location as the en_sasexe.zip file. The self-extracting archive file is in the /EPZipDir/sasexe directory.

Moving and Installing the SAS Embedded Process

The SAS Embedded Process is contained in a self-extracting archive file named sepcoregplm-12.00000-1.sh.

To move and unpack the self-extracting archive file, follow these steps:

Using a method of your choice, transfer the sepcoregplm-12.00000-1.sh file to your Greenplum master node. This directory is referred to as the path_to_sh_file.

The file does not have to be downloaded to a specific location. However, you need to note where it is downloaded so that it can be executed at a later time.
After the sepcoregplm-12.00000-1.sh has been transferred, log on to the Greenplum master node as a superuser.
Move to the directory where the self-extracting archive file was downloaded.
Change permissions on the file to enable you to execute the script.
```
chmod 755 -r sepcoregplm-12.00000-1.sh
```
Use the following command at the UNIX prompt to unpack the self-extracting archive file.
```
./sepcoregplm-12.00000-1.sh
```
After the script runs and the files are unpacked, the contents of the target directories should look similar to these. path_to_sh_file is the location to which you copied the self-extracting archive file in Step 1.
```
/path_to_sh_file/SASEPHome/bin
/path_to_sh_file/SASEPHome/misc
/path_to_sh_file/SASEPHome/sasexe
/path_to_sh_file/SASEPHome/utilities
```
The path_to_sh_file/SASEPHome/bin/ directory contains several scripts:
```
/path_to_sh_file/SASEPHome/bin/InstallSASEPFiles.sh
/path_to_sh_file/SASEPHome/bin/UninstallSASEPFiles.sh
/path_to_sh_file/SASEPHome/bin/StartupSASEP.sh
/path_to_sh_file/SASEPHome/bin/ShutdownSASEP.sh
/path_to_sh_file/SASEPHome/bin/ShowSASEPStatus.sh
```
The InstallSASEPFiles.sh file installs the SAS Embedded Process. The next step explains how to run this file. The StartupSASEP.sh and ShutdownSASEP.sh files enable you to manually start and stop the SAS Embedded Process. For more information about running these two files, see Controlling the SAS Embedded Process.

The UninstallSASEPFiles.sh file uninstalls the SAS Embedded Process. The ShowEPFilesStatus.sh file shows the status of the SAS Embedded Process on each host.
Use the following commands at the UNIX prompt to install the SAS Embedded Process to the master node and all host nodes.

The InstallSASEPFiles.sh file must be run from the /path_to_sh_file/SASEPHome/bin/ directory.
```
cd /path_to_sh_file/SASEPHome/bin
./InstallSASEPFiles.sh <-quiet>
```
CAUTION:

The timing option must be off for the InstallSASEPFiles.sh script to work.

Put \timing off in your .psqlrc file before running this script.

Note: -verbose is on by default and enables you to see all messages that are generated during the installation process. Specify -quiet to suppress messages.

The installation also creates a full-path-to-pkglibdir/SASEPHome/ directory. This directory is created on the master node and each host node.

The installation also copies the SAS directories and files from Step 4 across every node.
The contents of the full-path-to-pkglibdir/SASEPHome directory should look similar to these.
```
full-path-to-pkglibdir/SASEPHome/bin
full-path-to-pkglibdir/SASEPHome/misc
full-path-to-pkglibdir/SASEPHome/sasexe
full-path-to-pkglibdir/SASEPHome/utilities
```
Note: You can use the following command to determine the full-path-to-pkglibdir directory:
```
pg_config --pkglibdir
```
If you did not perform the Greenplum install, you cannot run the pg_config --pkglibdir command. The pg_config --pkglibdir command must be run by the person who performed the Greenplum install.
This is an example of the SAS Embedded Process install location:
```
usr/local/greenplum-db-4.2.6.1/lib/postgresql/SASEPHome
```

Running the %INDGP_PUBLISH_COMPILEUDF Macro

Overview of the %INDGP_PUBLISH_COMPILEUDF Macro

Use the %INDGP_PUBLISH_COMPILEUDF macro if you want to use scoring functions to run scoring models.

Note: Use the %INDGP_PUBLISH_COMPILEUDF_EP macro if you need to use the SAS Embedded Process. For more information, see Running the %INDGP_PUBLISH_COMPILEUDF_EP Macro.

The %INDGP_PUBLISH_COMPILEUDF macro publishes the following functions to the SASLIB schema in a Greenplum database:

SAS_COMPILEUDF function

This function facilitates the %INDGP_PUBLISH_FORMATS format publishing macro and the %INDGP_PUBLISH_MODEL scoring publishing macro. The SAS_COMPILEUDF function performs the following tasks:
- compiles the format and scoring model source files into object files. This compilation occurs through the SQL interface using an appropriate compiler for the system.
- links with the SAS formats library.
- copies the object files to the full-path-to-pkglibdir/SAS directory. All the SAS object files are stored under full-path-to-pkglibdir/SAS.
  
  Note: You can use the following command to determine the full-path-to-pkglibdir directory:
  pg_config --pkglibdir
  If you did not perform the Greenplum install, you cannot run the pg_config --pkglibdir command. The pg_config --pkglibdir command must be run by the person who performed the Greenplum install.
Three utility functions that are used when the scoring publishing macro transfers source files from the client to the host:
- SAS_COPYUDF function
  
  This function copies the shared libraries to the full-path-to-pkglibdir/SAS path on the whole database array including the master and all segments.
- SAS_DIRECTORYUDF function
  
  This function creates and removes a temporary directory that holds the source files on the server.
- SAS_DEHEXUDF function
  
  This function converts the files from hexadecimal back to text after the files are exported on the host.

You have to run the %INDGP_PUBLISH_COMPILEUDF macro only one time in each database.

Note: The SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions must be published before you run the %INDGP_PUBLISH_FORMATS or the %INDGP_PUBLISH_MODEL macro. Otherwise, these macros fail.

Note: To publish the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions, you must have superuser permissions to create and execute these functions in the SASLIB schema and in the specified database.

%INDGP_PUBLISH_COMPILEUDF Macro Run Process

To run the %INDGP_PUBLISH_COMPILEUDF macro, follow these steps:

Note: To publish the SAS_COMPILEUDF function, you must have superuser permissions to create and execute this function in the SASLIB schema and in the specified database.

Create a SASLIB schema in the database where the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions are published.

You must use “SASLIB” as the schema name for Greenplum in-database processing to work correctly.

You specify that database in the DATABASE argument of the %INDGP_PUBLISH_COMPILEUDF macro. For more information, see %INDGP_PUBLISH_COMPILEUDF Macro Syntax.

The SASLIB schema contains the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions.
Start SAS 9.4 and submit the following command in the Enhanced Editor or Program Editor:
```
%let indconn = user=youruserid password=yourpwd dsn=yourdsn;
/* You can use server=yourserver database=yourdb instead of dsn=yourdsn */
```
For more information, see the INDCONN Macro Variable.
Run the %INDGP_PUBLISH_COMPILEUDF macro.

For more information, see %INDGP_PUBLISH_COMPILEUDF Macro Syntax.

You can verify that the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions have been published successfully. For more information, see Validating the Publishing of the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF Functions.

INDCONN Macro Variable

The INDCONN macro variable provides the credentials to make a connection to Greenplum. You must specify the user, password, and either the DSN or server and database information to access the machine on which you have installed the Greenplum database. You must assign the INDCONN macro variable before the %INDGP_PUBLISH_COMPILEUDF macro is invoked.

The value of the INDCONN macro variable for the %INDGP_PUBLISH_COMPILEUDF macro has one of these formats:

USER=<'>userid<'> PASSWORD=<'>password<'> DSN=<'>dsnname<'>
<PORT=<'>port-number<'>>

USER=<'>userid<'> PASSWORD=<'>password<'> SERVER=<'>server<'>
DATABASE=<'>database<'> <PORT=<'>port-number<'>>

USER=<'>userid<'>

specifies the Greenplum user name (also called the user ID) that is used to connect to the database. If the user name contains spaces or nonalphanumeric characters, enclose the user name in quotation marks.

PASSWORD=<'>password<'>

specifies the password that is associated with your Greenplum user ID. If the password contains spaces or nonalphabetic characters, enclose the password in quotation marks.

Tip	Use only PASSWORD=, PASS=, or PW= for the password argument. PWD= is not supported and causes an error.

DSN=<'>datasource<'>

specifies the configured Greenplum ODBC data source to which you want to connect. If the DSN name contains spaces or nonalphabetic characters, enclose the DSN name in quotation marks.

Requirement

You must specify either the DSN= argument or the SERVER= and DATABASE= arguments in the INDCONN macro variable.

SERVER=<'>server<'>

specifies the Greenplum server name or the IP address of the server host. If the server name contains spaces or nonalphanumeric characters, enclose the server name in quotation marks.

Requirement

You must specify either the DSN= argument or the SERVER= and DATABASE= arguments in the INDCONN macro variable.

DATABASE=<'>database<'>

specifies the Greenplum database that contains the tables and views that you want to access. If the database name contains spaces or nonalphanumeric characters, enclose the database name in quotation marks.

Requirement

You must specify either the DSN= argument or the SERVER= and DATABASE= arguments in the INDCONN macro variable.

PORT=<'>port-number<'>

specifies the psql port number.

Default	5432
Requirement	The server-side installer uses psql, and psql default port is 5432. If you want to use another port, you must have the UNIX or database administrator change the psql port.

Note: The SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions are published to the SASLIB schema in the specified database. The SASLIB schema must be created before publishing the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions.

%INDGP_PUBLISH_COMPILEUDF Macro Syntax

%INDGP_PUBLISH_COMPILEUDF

(OBJPATH=full-path-to-pkglibdir/SAS
<, DATABASE=database-name>
<, ACTION=CREATE | REPLACE | DROP>
<, OUTDIR=diagnostic-output-directory>
);

Arguments

OBJPATH=full-path-to-pkglibdir/SAS

specifies the parent directory where all the object files are stored.

Tip

The full-path-to-pkglibdir directory was created during installation of the InstallAccelGplmFmt.sh self-extracting archive file. You can use the following command to determine the full-path-to-pkglibdir directory:

pg_config --pkglibdir

If you did not perform the Greenplum install, you cannot run the

pg_config
                                    --pkglibdir

command. The pg_config --pkglibdir command must be run by the person who performed the Greenplum install.

DATABASE=database-name

specifies the name of a Greenplum database to which the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions are published.

Restriction

If you specify DSN= in the INDCONN macro variable, do not use the DATABASE argument.

ACTION=CREATE | REPLACE | DROP

specifies that the macro performs one of the following actions:

CREATE

creates a new SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF function.

REPLACE

overwrites the current SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions, if a function by the same name is already registered, or creates a new SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF function if one is not registered.

Requirement

If you are upgrading the SAS Formats Library, run the %INDGP_PUBLISH_COMPILEUDF macro with ACTION=REPLACE. The CopySASFiles.sh install script replaces existing versions of most files. However, you need to replace the existing SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions after you run the CopySASFiles.sh install script. For more information, see Upgrading from a Previous Version and Move and Install the SAS Formats Library and Binary Files.

DROP

causes the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions to be dropped from the Greenplum database.

Default	CREATE
Tip	If the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions were published previously and you specify ACTION=CREATE, you receive warning messages that the functions already exist and you are prompted to use REPLACE. If the SAS_COMPILEUDF, SAS_COPYUDF, SAS_DIRECTORYUDF, and SAS_DEHEXUDF functions were published previously and you specify ACTION=REPLACE, no warnings are issued.

OUTDIR=diagnostic-output-directory

specifies a directory that contains diagnostic files.

Tip	Files that are produced include an event log that contains detailed information about the success or failure of the publishing process.

Running the %INDGP_PUBLISH_COMPILEUDF_EP Macro

Overview of the %INDGP_PUBLISH_COMPILEUDF_EP Macro

Use the %INDGP_PUBLISH_COMPILEUDF_EP macro if you want to use the SAS Embedded Process to run scoring models or other SAS software that requires it.

Note: Use the %INDGP_PUBLISH_COMPILEUDF macro if you want to use scoring functions to run scoring models. For more information, see Running the %INDGP_PUBLISH_COMPILEUDF Macro.

The %INDGP_PUBLISH_COMPILEUDF_EP macro registers the SAS_EP table functions in the database.

You have to run the %INDGP_PUBLISH_COMPILEUDF_EP macro only one time in each database where scoring models are published.

The %INDGP_PUBLISH_COMPILEUDF_EP macro must be run before you use the SAS_EP function in an SQL query.

Note: To publish the SAS_EP function, you must have superuser permissions to create and execute this function in the specified schema and database.

%INDGP_PUBLISH_COMPILEUDF_EP Macro Run Process

To run the %INDGP_PUBLISH_COMPILEUDF_EP macro, follow these steps:

Note: To publish the SAS_EP function, you must have superuser permissions to create and execute this function in the specified schema and database.

Create a schema in the database where the SAS_EP function is published.

Note: You must publish the SAS_EP function to a schema that is in your schema search path.

You specify the schema and database in the INDCONN macro variable. For more information, see INDCONN Macro Variable.
Start SAS 9.4 and submit the following command in the Enhanced Editor or Program Editor:
```
%let indconn = user=youruserid password=yourpwd dsn=yourdsn <schema=yourschema>;
/* You can use server=yourserver database=yourdb instead of dsn=yourdsn */
```
For more information, see the INDCONN Macro Variable.
Run the %INDGP_PUBLISH_COMPILEUDF_EP macro. For more information, see %INDGP_PUBLISH_COMPILEUDF_EP Macro Syntax.

You can verify that the SAS_EP function has been published successfully. For more information, see Validating the Publishing of the SAS_EP Function.

INDCONN Macro Variable

The value of the INDCONN macro variable for the %INDGP_PUBLISH_COMPILEUDF_EP macro has one of these formats:

USER=<'>userid<'> PASSWORD=<'>password<'> DSN=<'>dsnname <'>
<SCHEMA=<'>schema<'>> <PORT=<'>port-number<'>>

USER=<'>userid<'> PASSWORD=<'>password<'> SERVER=<'>server<'>
DATABASE=<'>database<'> <SCHEMA=<'>schema<'>>
<PORT=<'>port-number<'>>

USER=<'>userid<'>

PASSWORD=<'>password<'>

specifies the password that is associated with your Greenplum user ID. If the password contains spaces or nonalphabetic characters, enclose the password in quotation marks.

Tip	Use only PASSWORD=, PASS=, or PW= for the password argument. PWD= is not supported and causes an error.

DSN=<'>datasource<'>

specifies the configured Greenplum ODBC data source to which you want to connect. If the DSN name contains spaces or nonalphabetic characters, enclose the DSN name in quotation marks.

Requirement

You must specify either the DSN= argument or the SERVER= and DATABASE= arguments in the INDCONN macro variable.

SERVER=<'>server<'>

specifies the Greenplum server name or the IP address of the server host. If the server name contains spaces or nonalphanumeric characters, enclose the server name in quotation marks.

Requirement

You must specify either the DSN= argument or the SERVER= and DATABASE= arguments in the INDCONN macro variable.

DATABASE=<'>database<'>

Requirement

You must specify either the DSN= argument or the SERVER= and DATABASE= arguments in the INDCONN macro variable.

SCHEMA=<'>schema<'>

specifies the name of the schema where the SAS_EP function is defined.

Default	SASLIB
Requirements	You must create the schema in the database before you run the %INDGP_PUBLISH_COMPILEUDF_EP macro.
Requirements	You must publish the SAS_EP function to a schema that is in your schema search path.

PORT=<'>port-number<'>

specifies the psql port number.

Default	5432
Requirement	The server-side installer uses psql, and psql default port is 5432. If you want to use another port, you must have the UNIX or database administrator change the psql port.

%INDGP_PUBLISH_COMPILEUDF_EP Macro Syntax

%INDGP_PUBLISH_COMPILEUDF_EP

(<OBJPATH=full-path-to-pkglibdir/SAS>
<, DATABASE=database-name>
<, ACTION=CREATE | REPLACE | DROP>
<, OUTDIR=diagnostic-output-directory>
);

Arguments

OBJPATH=full-path-to-pkglibdir/SAS

specifies the parent directory where all the object files are stored.

Tip

The full-path-to-pkglibdir directory was created during installation of the InstallSASEP.sh self-extracting archive file. You can use the following command to determine the full-path-to-pkglibdir directory:

pg_config --pkglibdir

If you did not perform the Greenplum install, you cannot run the

pg_config
                                    --pkglibdir

command. The pg_config --pkglibdir command must be run by the person who performed the Greenplum install.

DATABASE=database-name

specifies the name of a Greenplum database where the SAS_EP function is defined.

Restriction

If you specify DSN= in the INDCONN macro variable, do not use the DATABASE argument.

ACTION=CREATE | REPLACE | DROP

specifies that the macro performs one of the following actions:

CREATE

creates a new SAS_EP function.

REPLACE

overwrites the current SAS_EP function, if a function by the same name is already registered, or creates a new SAS_EP function if one is not registered.

Requirement

If you are upgrading the SAS Embedded Process, run the %INDGP_PUBLISH_COMPILEUDF_EP macro with ACTION=REPLACE. The InstallSASEPFiles.sh install script replaces existing versions of most files. However, you need to replace the existing SAS_EP function after you run the InstallSASEPFiles.sh install script. For more information, see Upgrading from a Previous Version and Moving and Installing the SAS Embedded Process.

DROP

causes the SAS_EP function to be dropped from the Greenplum database.

Default	CREATE
Tip	If the SAS_EP function was defined previously and you specify ACTION=CREATE, you receive warning messages that the functions already exist and you are prompted to use REPLACE. If the SAS_EP function was defined previously and you specify ACTION=REPLACE, no warnings are issued.

OUTDIR=diagnostic-output-directory

specifies a directory that contains diagnostic files.

Tip	Files that are produced include an event log that contains detailed information about the success or failure of the publishing process.

Last updated: February 9, 2017