Optimizing Process Flows - SAS Data Integration Studio 3.3 User's Guide - page 192

Table 11.2 Methods for Adding Custom Debugging Code

Method Documentation

Replace the generated code for a
transformation with user-written
code.

“Replacing the Generated Code for a Transformation with
User-Written Code” on page 226.

Add a User-Written Code
transformation to the process
flow.

“Adding a User-Written Code Transformation to the Process
Flow for a Job” on page 227.

Add a generated transformation
to the process flow.

“Adding a Generated Transformation to the Process Library” on
page 228.

Custom code can direct information to the log or to alternate destinations such as
external files, tables. Possible uses include tests of frequency counts dumping out SAS
macro variable settings, or listing the runtime values of system options.

Analyzing Transformation Output Tables
Most transformations in a SAS Data Integration Studio job create at least one output
table and store that table in the Work library on the SAS Workspace Server that
executes the job. The output table for each transformation becomes the input to the
next transformation in the process flow. All output tables are deleted when the job is
finished or the current server session ends.
If a job is not producing the expected output, or if you suspect that something is
wrong with a particular transformation, you can view the output tables for the
transformations in the job to verify that each transformation is creating the expected
output. The next sections describe how to view a transformation's output table from the
Process Designer window, and how to preserve output tables so that you can view their
contents by other means.

Note: In addition to being useful when analyzing process flows, output tables can be
preserved to determine how much disk space they require, or to restart an process flow
after it has failed at a particular step (transformation). ￿

Viewing the Output Table for a Transformation
See “View Data in a Transformation's Temporary Output Table” on page 111.

Setting SAS Options to Preserve Intermediate Files for Batch Jobs
When SAS Data Integration Studio jobs are executed in batch mode, a number of
SAS options can be used to preserve intermediate files in the Work library. These
system options can be set as described in “Setting SAS Options for Jobs and
Transformations” on page 189.
Use the NOWORKINIT system option to prevent SAS from erasing existing Work
files on invocation. Use the NOWORKTERM system option to prevent SAS from
erasing existing Work files on termination.
For example, to create a permanent SAS Work library in UNIX and PC
environments, you can start the SAS Workspace Server with the WORK option to
redirect the Work files to a permanent Work library. The NOWORKINIT and
NOWORKTERM options must be included.