Previous Page

|

Next Page

Maintaining Jobs

Example: Defining a Job for which SAS/Warehouse Administrator Generates Code

Overview

This example defines a Job for which SAS/Warehouse Administrator generates the code, which means that a Process Flow is required. The Job creates one output table (a Detail Table), with one input source (an ODD).

Note:   The following explanations describe the metadata and methods used to achieve the desired results. It is assumed that the appropriate Data Warehouse Environment, Data Warehouse, Subject, Detail Table physical properties, and ODD exist.  

Adding a Job from the Data Store

In the SAS/Warehouse Administrator Explorer, position the cursor on the data store for which you want to add a Job, for example the Detail Table Customer.

Right-click and select Process. SAS/Warehouse Administrator asks you if you want to create a Job.

Select Yes. The software adds a Job (named by default for the data store), opens the Process Editor window, and displays a Job icon for the output table in the Process View.

Note:   By adding the Job using this method, the associated output table is specified automatically for the Job Process Flow, which is displayed in the Process View.  

Defining Job Properties

To update the default metadata for the Job, you can start from the Process Editor Job Hierarchy or Job List.

Position the cursor on the Job icon, click the right mouse button, and select Properties. The Job Properties window displays.

General Tab	specifies the Job name, a description, an owner, and an administrator.
Source Tab	specifies who supplies the code for the Job, which for this example is SAS/Warehouse Administrator and is the default setting.

The remaining tabs in the Job Properties window, which are for Job scheduling, are explained in the "Scheduling Jobs" chapter.

Adding an Input Source

After you have an output table specified for a Process Flow, which for this example was specified automatically, you must add its input.

Note:   SAS/Warehouse Administrator will not allow you to add an input that is invalid for a particular output table. However, some inputs might be allowed to provide for the possibility of user-written code.  

You add an input source to the Job Process Flow in the Process View:

Click the output table with the right mouse button and select Add  InputsThe Selector window displays.

In the Selector window, select the type of table you want to add as an input source, for example ODD, and then click Show to display the available ODDs.

From the displayed list, select the table that you want to specify as an input source, for example Customer, and then click OK. The input source is added to the Process Flow.

Defining Mapping Process Properties

For most output tables, a default Mapping process will appear between the output table and the input source that was added, which is illustrated in the previous display. The Mapping process maps columns from one or more input sources into one or more output tables.

You must update the default metadata in order for the Mapping process to function properly. To update the default metadata for the Mapping process, position the cursor on the Mapping icon, click the right mouse button, and select Properties. The Mapping Process Properties window displays.

For an explanation about defining the Mapping process properties, see Example: Defining Mapping Process Properties for One-to-One Mapping and Example: Defining Mapping Process Properties to Transform Data.

Editing the Load Process

A Load process (also called a Load Step) generates or retrieves code that puts data into a specified output table. The Load process is automatically included in the Process Flow that is associated with the output table. For this example, the Load process default properties do not need to be changed.

However, to update the default metadata for the Load process, position the cursor on the output table in the Process Flow.

Then, click the right mouse button, and select Edit Load Step. For this example, the Detail Table Load Process Attributes window displays.

For an explanation about editing the Load process properties, see Example: Editing Load Process Properties to Supply User-Written Code.

Previous Page

|

Next Page

|

Top of Page

Copyright © 2012 by SAS Institute Inc., Cary, NC, USA. All rights reserved.