There are many opportunities to export code to a file
when you use the data preparation interface. This feature enables
administrators to review the SAS statements for a task. Some of these
tasks are starting and stopping a SAS LASR Analytic Server
instance, and loading and unloading tables. The statements in the
file can be modified and scheduled. For more information about the
LASR, OLIPHANT, and HPDS2 procedures, see the
SAS LASR
Analytic Server: Administration Guide.
Operations that enable
saving the SAS statements have an
Export Code button.
Click the
Export Code button to view the
Export
Code window. On the window, the
Export button
saves the SAS statements to the file that is specified in the
Location field
but does not submit the SAS statements for execution.
Note: The exported code does not
include information about the metadata server connection. The connection
information is often supplied in options such as METASERVER=, METAPORT=,
METAUSER=, or METAPASS=. These options are needed to run the PROC
METALIB statement that is included in jobs that register tables. The
affected jobs are the prepare data and add to data server jobs. For
information about the metadata server connection options, see
SAS Language Interfaces to Metadata.
Note: The SAS statements are saved
to a file with the credentials of the user account that is used to
run the JBoss Application Server. This user account must have Write
access to the location, and the location must be accessible from the
machine that is running JBoss.
It is also possible to configure logging so that SAS
statements are stored to a log file. Only the SAS statements that
are generated by the data preparation interface are available to be
logged. For information about enabling this feature, see
SAS Visual Analytics: Administration Guide.