A job sequence specifies the processing sequence for a set of DataStage® jobs.
In a job sequence, you can also specify such things as: How should errors
be handled? Where should e-mail notifications be sent?
A parallel job represents a DataStage parallel job. Parallel jobs
can significantly improve performance because the different stages of a job
are run concurrently rather than sequentially. There are two basic types of
parallel processing: pipeline and partitioning.
General page
- Label
- Type a name for the highlighted operator on the control flow canvas.
The canvas displays only the first 26 characters.
- Description
- Type a description to record additional information about the
highlighted operator.
Job sequence
- Job name
- Type the name of an existing DataStage job sequence.
Tip: Job
sequences can only be created using the DataStage Designer.
Names must
meet the following criteria:- Maximum length is 700 characters
- Must begin with an alphabetic character.
- Can contain alphanumeric characters and underscores.
- Project name
- Type the name of the DataStage project that contains the job sequence.
- Database server
- Type the reference name of the server where the DataStage engine runs.
Parallel Job
- Job name
- Type the name of an existing DataStage parallel job.
Tip: Parallel
jobs can only be created using the DataStage Designer.
Names must
meet the following criteria:- Maximum length is 700 characters
- Must begin with an alphabetic character.
- Can contain alphanumeric characters and underscores.
- Project name
- Type the name of the DataStage project that contains the parallel job.
- DataStage server
- Type the name of the server where the DataStage engine runs.
Diagnostics page
- Logging level
- Select the level of information detail to write to the log file:
- Info
- Writes informational messages, warnings, and errors to the log.
This value is the default.
- Warning
- Writes warnings and errors to the log.
- Error
- Writes errors to the log.
- Tracing level
- Select the type of trace output.
Tip: Because any tracing option requires additional system resources,
use tracing only when you need to debug a problem or when IBM support
representatives ask you to use it.
- None
- No output is generated. This value is the default.
- Methods
- Traces the processing flow through the methods. Use this option,
for example, when you want to determine which nodes were run in the
execution plan graph.
- Content
- Traces the SQL statements and commands that are run. This type
of trace is useful for debugging and for listing a de-parameterized
statement. You can determine the actual values that are used for a
variable in addition to the variable name.
- Both
- Traces methods and contents.
- Skip execution
- Use this property to skip the execution of individual operators
in a control flow. Select the check box or set a boolean variable
with a value of true to skip the operator when you run the
flow. The run status of the skipped operator is assumed to be successful,
and the flow continues with the next operator.
- If you use the check box to set the skip option, you can change
the @SKIPEXECUTION activity attribute in the Administration Console
after you deploy the application.
If you use a boolean
variable to define the skip option, you can change the variable value
for the application only when you start a process. This
option sets the same value for all operators using this variable.
You can use the variable assignment operator to change the variable
inside the control flow.