Some actions that can be selected on the
Status Handling tab require server setup, as described
in the following table.
Prerequisites for Status Handling Actions
|
|
|
Any action that sends
e-mail.
|
E-mail must be enabled
for the SAS Workspace Server that executes the job that includes the
action. For more information, administrators should see the section
called "Add or Modify E-Mail Settings for SAS Application Servers"
in the SAS Intelligence Platform: Application Server Administration
Guide.
|
|
|
SAS Foundation Services
must be installed, and the Event Broker Service must be properly configured
for the software that receives the events. For more information, see
the documentation for SAS Foundation Services and for the software
that receives the events.
|
|
|
The Custom action enables
you to call SAS code to provide user-defined status handling for a
job or transformation. Examples include SAS code that is added to
the Precode and Postcode tab in a job or
transformation, or a macro in a SAS Autocall library. The SAS code
must have valid SAS syntax based on the location it is being called
from.
If you call a macro
in a SAS Autocall library, the SAS Application Server that executes
the job must be able to access the relevant Autocall library. For
details about making Autocall macro libraries available to SAS Data
Integration Studio, see the “Administering SAS Data Integration
Studio” chapter in the SAS Intelligence Platform:
Desktop Application Administration Guide.
|
Any action that requires
a libref
|
The libref must be assigned
before the job or transformation executes. To assign a library within
SAS Data Integration Studio, you can select the Precode
and Postcode tab in the properties window for the job
or transformation and then specify a SAS LIBNAME statement in the Precode area.
To assign a library
outside of SAS Data Integration Studio, you can pre-assign the library
to the SAS Application Server that is used to execute the job. Some
tasks that are associated with pre-assigning a SAS library must be
done outside of SAS Data Integration Studio or SAS Management Console.
For details, see the “Assigning Libraries” chapter in SAS Intelligence Platform: Data Administration Guide.
|
Note: If an action requires you
to specify a physical path, then use relative paths for portability.