SAS Data Integration Studio 3.3- P40 pdf

Using Status Codes to Analyze Process Flows When you execute a job in SAS Data Integration Studio, a return code for each transformation in the job is captured in a macro variable.. Addi

190 Using SAS Logs to Analyze Process Flows 4 Chapter 11

Evaluating SAS Logs

The SAS logs from your process flows are an excellent resource to help you understand what is happening as the flows execute For example, when you look at the run times in the log, compare the real-time values to the CPU time (user CPU plus system CPU) For read operations, the real time and CPU time should be close For write operations, however, the real time could substantially exceed the CPU time, especially in environments that are optimized for read operations If the real time and the CPU time are not close, and they should be close in your environment, investigate what is causing the difference

If you suspect that you have a hardware issue, see A Practical Approach to Solving

Performance Problems with the SAS System, a document that is available from the

Scalability and Performance Papers page on support.sas.com (support.sas.com/rnd/ scalability/papers/)

If you determine that your hardware is properly configured, then review the SAS code Transformations generate SAS code Understanding what this code is doing is very important to insure that you do not duplicate tasks, especially SORTs, which are resource-intensive The goal is to configure the hardware so that there are no

bottlenecks, and to avoid needless I/O in the process flows

Capturing Additional SAS Options in the SAS Log

To analyze performance, we recommend that you turn on the following SAS options

so that detailed information about what the SAS tasks are doing is captured in the SAS log:

FULLSTIMER MSGLEVEL=I (this option prints additional notes pertaining to index, merge processing, sort utilities, and CEDA usage, along with the standard notes, warnings, and error messages)

SOURCE, SOURCE2 MPRINT

NOTES

To interpret the output from the FULLSTIMER option, see A Practical Approach to

Solving Performance Problems with the SAS System, a document that is available from

the Scalability and Performance Papers page on support.sas.com (support.sas.com/rnd/ scalability/papers/)

In addition, the following SAS statements will also echo useful information to the SAS log:

PROC OPTIONS OPTION=UTILLOC; run;

PROC OPTIONS GROUP=MEMORY; run;

PROC OPTIONS GROUP=PERFORMANCE; run;

LIBNAME _ALL_ LIST;

The PROC OPTIONS statement will echo SAS options and their current settings to the SAS log There are hundreds of SAS options, so if, for example, you prefer to see which value has been set to the SAS MEMORY option, you can issue the PROC OPTIONS statement with the GROUP=MEMORY parameter The same is true if you want to see only the SAS options that pertain to performance

The LIBNAME _ALL_ LIST statement will echo to the SAS log information (physical path location, engine being used, etc.) regarding each libref that is currently assigned to the SAS session This is helpful for understanding where all the work occurs during the process flow For details about setting SAS invocation options for SAS Data Integration Studio, see “Setting SAS Options for Jobs and Transformations” on page 189

Redirecting SAS Data Integration Studio’s Log to a File

The SAS log for a job provides critical information about what happened when a job was executed However, large jobs can create large logs, which can slow down SAS Data Integration Studio In order to avoid this problem, you can re-direct the SAS log to a

permanent file, then turn off the Log tab in the Process Designer window.

When you install SAS Data Integration Studio, the Configuration Wizard enables you

to set up as permanent SAS log files for each job that is executed The SAS log

filenames will contain the name of the job that created the log, plus a timestamp of when the job was executed

Alternatively, you can add the following code to the Pre and Post Process tab in

the properties window for a job:

proc printto log= path_to_log_file NEW; run;

For details about adding a pre-process to a SAS Data Integration Studio job, see

“Adding SAS Code to the Pre and Post Processing Tab” on page 225 The previous code will cause the log to be redirected to the specified file Be sure to use the appropriate host-specific syntax of the host where your job will be running when you specify this log file, and make sure that you have write access to the location where the log will be written

Viewing or Hiding the Log in SAS Data Integration Studio

The Process Designer window in SAS Data Integration Studio has a Log tab that displays the SAS log for the job in the window To display or hide the Log tab, complete

these steps:

1 From the SAS Data Integration Studio menu bar, select Tools I Options to

display the Options window

2 On the General tab, select or deselect the check box that controls whether the Log

tab is displayed in the Process Designer window

Using Status Codes to Analyze Process Flows

When you execute a job in SAS Data Integration Studio, a return code for each transformation in the job is captured in a macro variable The return code for the job is set according to the least successful transformation in the job SAS Data Integration

Studio enables you to associate a return code condition, such as Successful, with an action, such as Send Email or Abort In this way, users can specify how a return code

is handled for the job or transformation

For example, you could specify that a transformation in a process flow will abort, based on conditions that you define This can reduce the log to just the transformations leading up to the problem being investigated, making the log more manageable and eliminating inconsequential error messages For more information about status code handling, see “Monitoring the Status of Jobs” on page 103

Adding Debugging Code to a Process Flow

If you are analyzing a SAS Data Integration Studio job, and the information that is provided by logging options and status codes is not enough, consider the following methods for adding debugging code to the process flow

192 Analyzing Transformation Output Tables 4 Chapter 11

Table 11.2 Methods for Adding Custom Debugging Code

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) 4

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

C:\>"C:\Program Files\SAS\SAS 9.1\sas.exe"

-work "C:\Documents and Settings\sasapb\My Documents\My SAS Files\My SAS Work Folder" -noworkinit

-noworkterm

This redirects the generated Work files in the folder My SAS Work Folder

To create a permanent SAS Work library in the z/OS environment, edit your JCL

statements and change the WORK DD statement to a permanent MVS data set For

example:

//STEP1 EXEC SDSSAS9,REGION=50M

//* changing work lib definition to a permanent data set

//SDSSAS9.WORK DD DSN=userid.somethin.sasdata,DISP=OLD

//* other file defs

//INFILE DD

CAUTION:

If you redirect Work files to a permanent library, you must manually delete these files to

avoid running out of disk space. 4

Using a Transformation’s Property Window to Redirect Output Files

The default name for a transformation’s output table is a two-level name that

specifies the Work libref and a generated member name, such as work.W54KFYQY The

Processtab in the property windows for some SAS Data Integration Studio

transformations has a Data Location button that enables you to specify the name and

location of the output table for that transformation Note that this location can be a

SAS library or RDBMS library This has the added benefit of providing users the ability

to specify which output tables they want to retain and allow the rest to be deleted by

default Users can use this scheme as a methodology for checkpoints by writing specific

output tables to disk when needed

Note: If you want to save a transformation output table to a library other than the

SAS User library, replace the default name for the output table with a two-level name 4

If you refer to an output table with a single-level name (for example, employee),

instead of a two-level name (for example, work.employee), SAS automatically sends the

output table into the User library, which defaults to the Work library However, this

default behavior can be changed by any SAS user Through the USER= system option,

a SAS user can redirect the User library to a different library If the USER= system

option is set, single-level tables are stored in the User library, which has been

redirected to a different library, instead of to the Work library

Adding a List Data Transformation to the Process Flow

In SAS Data Integration Studio, you can use the List Data transformation to print

the contents of an output table from the previous transformation in an process flow

Add the List Data transformation after any transformation whose output table is of

interest to you

The List Data transformation uses the PRINT procedure to produce output Any

options associated with that procedure can be added from the Options tab in the

transformation’s property window By default, output goes to the Output tab in the

Process Designer window Output can also be directed to an HTML file For large data,

customize this transformation to print just a subset of the data For details, see

“Limiting a Transformation’s Input” on page 188

194 Analyzing Transformation Output Tables 4 Chapter 11

Adding a User Written Code Transformation to the Process Flow

You can add a User Written Code transformation to the end of a process flow that would move or copy some of the data sets in the Work library to a permanent library For example, assume that there are three tables in the Work library (test1, test2, and test3) The following code moves all three tables from the Work library to a permanent library named PERMLIB and then deletes them from the Work library

libname permlib base

"C:\Documents and Settings\ramich\My Documents\My SAS Files\9.1";

proc copy move

in = work out = permlib;

select test1 test2 test3;

run;

For information about User Written Code transformations, see “Adding a User-Written Code Transformation to the Process Flow for a Job” on page 227