Customizing or Replacing Generated Code in SAS Data Integration Studio - SAS Data Integration Studio 3.3 User's Guide - page 224

Method Description

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

For example, you can edit the code that is generated for a
transformation, save it, and then set the transformation so that
the customized code runs whenever the transformation is
executed.

Add a User-Written Code
transformation to the process
flow for a job

The User-Written Code transformation is one of the
transformations in the Process Library. Use this transformation
to perform custom tasks in for a specific process flow—tasks
that are not supported by the standard transformations and are
beyond the scope that can be managed by making a few changes
to the generated code for a single transformation.User-Written
Code transformations do not support multiple inputs or outputs.

Add a generated transformation
to the Process Library

The Transformation Generator wizard guides you through the
steps of specifying SAS code for a generated transformation.
After the transformation is saved, it is displayed in the Process
Library tree, where it is available for use in any job. Use a
generated transformation when you want to create reusable,
custom code that you can insert into the flow for any SAS Data
Integration Studio job. Unlike User-Written Code
transformations, generated transformations support multiple
inputs or outputs.

Modifying Configuration Files or SAS Start Commands

To specify SAS system options or startup options for all jobs that are executed on a
particular SAS Workspace Server, modify the config.sas file, the autoexec.sas file, or the
SAS start command for that server. Examples of these options include UTILLOC or
NOWORKINIT. For more information about SAS configuration files and SAS invocation
options, see the topics that are releated to "configuration" and "invoking SAS" in your
SAS online documentation.
One server option that is supported by SAS Data Integration Studio 3.3 or later is
the ETLS_DEBUG option. By default, SAS Data Integration Studio specifies the
MPRINT option at the start of the code that is generated for all jobs. The MPRINT
option adds messages to the log that are useful for debugging in a development
environment. However, MPRINT can make the log very large, which might not be
desirable in a production environment.
The ETLS_DEBUG option provides a way to turn off the MPRINT option for all jobs
that are executed on a particular SAS Workspace Server, without having to turn off this
option for each job. If the ETLS_DEBUG option is specified for a SAS Workspace
Server, and a job is executed on that server, the default MPRINT option is ignored.
Here is the syntax for the ETLS_DEBUG option:

%let etls_debug=0;
Note: Setting ETLS_DEBUG to any value other than 0 has one effect: MPRINT is
turned on. This might change in future releases. We suggest that you add this
assignment with a value equal to 0; otherwise, leave the statement out. ￿

CAUTION:
We strongly recommend that you do not turn off MPRINT in a development environment. ￿

See also “Setting SAS Options for Jobs and Transformations” on page 189.