On this page
DataStage
Prepare DataStage inputs for a data estate, collect the relevant dependencies, and verify the scope represented in Understand.
modernAIze supports DataStage as a data estate source platform. Export the jobs and related definitions needed to explain the selected output. DSX carries job design information for investigating stages, links, and processing. A screenshot of the job canvas cannot provide that material.
Inputs to prepare
DataStage DSX exports in .dsx files, supplied directly or in a ZIP containing the relevant export files.
Native assets and what to collect
| Asset | Material to supply | What it contributes |
|---|---|---|
| Job design | .dsx export | Stages, links, connectors, and job properties |
| Stage and link definitions | Included DSX definitions | Column metadata, derivations, and movement between stages |
| Sequence job | Its DSX definition | Job ordering, activities, triggers, and control context |
| Job parameters and parameter sets | Relevant exported definitions and approved value context | Values that specialize the job for the intended run |
| Connector SQL | SQL properties carried by the export | Queries and writes associated with connected systems |
A DSX file can contain several jobs and related definitions. Count the objects inside the export when reviewing scope; one uploaded file need not mean one job. An ISX package is not the DSX input format described here.
How to collect the inputs
Use DataStage’s native export facilities to obtain a DSX export of the selected
jobs and their required definitions. Supply .dsx directly or package the export
files in a ZIP. The route is a native product export; it does not require a
separate modernAIze collection program.
Check whether called routines or external commands are actually defined in the export. If they are only referenced, record their owner and obtain the relevant behavioral evidence separately. Preserve parameter context without including connection passwords.
Prepare the source
- Identify the jobs and sequences that produce the selected output.
- Collect their DSX exports, including the relevant shared definitions and parameter context.
- Preserve the export contents and names so the source owner can reconcile them with the original jobs.
- List external routines, commands, or upstream jobs that the export references but does not supply.
Investigate the analysis
Follow links between stages to understand how data enters, changes, and leaves the job. Investigate transformer logic, field derivations, lookups, and branch conditions where they affect the assessment. Use sequence context when several jobs cooperate to produce the output.
Start with Briefing for the system-level explanation, then use the appropriate Landscape view and available Detail links to investigate the relevant processing. Keep the question tied to the supplied source revision.
Example review question
The following example is synthetic.
For monthly revenue, locate the job preparing order values and the stages responsible for conversion and monthly aggregation. Check whether a sequence runs a separate exchange-rate preparation job first.
Verify the scope
Compare the intended job list with the represented processing and its relationships. If an external routine or prerequisite job affects the result, obtain its source or record the dependency for specialist review. A job export alone does not establish the behavior of an external command.