The SAS Embedded Process
starts when a query is submitted using the SAS_EP function. It continues
to run until it is manually stopped or the database is shut down.
Note: Starting and stopping the
SAS Embedded Process has implications for all scoring model publishers.
Note: Manually starting and stopping
the SAS Embedded Process requires superuser permissions and must be
done from the Greenplum master node.
When
the SAS Embedded Process is installed, the ShutdownSASEP.sh and StartupSASEP.sh
scripts are installed in the following directory.
For more information
about these files, see Moving and Installing the SAS Embedded Process./path_to_sh_file/SASEPHome/bin
Use the following command
to shut down the SAS Embedded Process:
/path_to_sh_file/SASEPHome/bin/ShutdownSASEP.sh
<-quiet>When invoked from the
master node, ShutdownSASEP.sh shuts down the SAS Embedded Process
on each database node. The -verbose option
is on by default and provides a status of the shutdown operations
as they occur. You can specify the -quiet option
to suppress messages. This script should not be used as part of the
normal operation. It is designed to be used to shut down the SAS Embedded
Process prior to a database upgrade or re-install.
Use the following command
to start the SAS Embedded Process:
/path_to_sh_file/SASEPHome/bin/StartupSASEP.sh
<-quiet>When invoked from the
master node, StartupSASEP.sh manually starts the SAS Embedded Process
on each database node. The -verbose option
is on by default and provides a status of the installation as it occurs.
You can specify the -quiet option
to suppress messages. This script should not be used as part of the
normal operation. It is designed to be used to manually start the
SAS Embedded Process and only after consultation with SAS Technical
Support.
CAUTION:
The timing
option must be off for any of the .sh scripts to work.
Put \timing
off in your .psqlrc file before running these scripts.