Académique Documents
Professionnel Documents
Culture Documents
DataStage EE Basics
Creating a Job
Where We are
MODULE 01 Introduction to DataStage
MODULE 02 DataStage Installation on Windows Platform
MODULE 03 Features of DataStage Clients
MODULE 04 Creating a Job
MODULE 05 Accessing Sequential Data
MODULE 06 Combining Data
MODULE 07 Splitting Data
MODULE 08 Transforming Data
MODULE 09 Sorting and Aggregating Data
MODULE 10 Accessing Relational Data
MODULE 11 Job Control
MODULE 12 Architecture and Parallelism Concepts
Module 04
Creating a Job
Attaching to a Project
1. Analyze the source data and what stage we can use to extract the
source data
Job Parameters
Go to Job Properties
Use parameters defined in Project Level: User defined
parameters in environment variable. Default value can be hard
coded or retrieved at runtime [$PROJDEF]
Create Job- level parameters
Parameters can be passed from a sequence. Value defined in
higher level takes precedence
Run Job
Short description of
the Job
Job Parameters
Parameter name
Parameter
Parameter prompt to default value
be seen at run time
Parameter type
Project level
parameters
Job level
parameters
Add new
environment variable
Compile/Validate/Run
Compiling a Job:
• creates the OSH script for the Job
• C++ code for the transformers
Validating a Job:
• performs connectivity check and authentication
• Basically does everything except process rows. It opens any required files and
connect to data sources.
• Prepares SQL and captures any return message referring to syntax errors from
database
• It is not necessary to validate a job every time you change its design. If the
change does not affect any passive stage, then re-validating it won't really
prove anything. Missing property values will be picked up when the job is
compiled.
• Validation is useful on initial deployment.
Q&A