Maintaining Processes

Example: Defining User Exit Process Properties

This example defines the User Exit process properties to specify the location of user-written code, which for this example transforms data from the input source before it is loaded into the output table.

For an example about adding a User-Exit process, see Example: Adding a User Exit Process to a Process Flow.

Note: The following explanation describes the metadata and methods used to achieve the desired results. It is assumed that the appropriate Data Warehouse Environment, Data Warehouse, Subject, data stores, Job, and Process Flow exist. [cautionend]

Defining User Exit Properties

In a Job Process Flow, a User Exit process can be added either below the output table or above the input source as appropriate. For this example, the User Exit process was added above the input source as shown in the following Process Flow:

[untitled graphic]

In the Job Process Flow, position the cursor on the User Exit process icon, click the right mouse button, and select Properties. The User Exit Process Attributes window displays.

General Tab	specifies a name, a description, an owner, and an administrator for the User Exit process.
Source Code Tab	specifies that the source code for the process is supplied by user-written code, which is required for a User Exit, and specifies the name of the SAS library that contains the code. The catalog entry name must be either SOURCE or SCL. Click Edit to open an editing window where you can enter, view, or update the specified code. User-written code can supplement the code that SAS/Warehouse Administrator generates or it can completely replace the code generated by SAS/Warehouse Administrator. Here is an example of code for a User Exit process:
Execution Tab	specifies the host on which you want to run the User Exit process, which for this example is the local host.
Output Data Tab	specifies the name and location of the intermediate work table(s) if output is produced by the User Exit process.
Options Tab	specifies options for generating the source code for the process. For this example, both options are selected, which is the default setting. The options available on this tab are Generate Access Code (ex. signon, libname) before step allows you to control whether SAS/Warehouse Administrator generates the code to access the preceding objects, such as sign on code, and the LIBNAME statement. If selected, SAS/Warehouse Administrator generates the code that is required to load or run the current object or process and the code that is required to access the objects or processes that precede the current one. It assumes that code has already been generated or is already in place to load or run the objects or processes that precede the current one. Set &SYSLAST macro variable at end of step allows you to control whether SAS/Warehouse Administrator generates code that sets the &SYSLAST macro variable to the name of the last table that was created or updated.

Top of Page