...
DSX – The older Information Server export format that supports a subset of all current Information Server asset types.
This format is also available 7-bit encoding in which any ASCII character above DEL (127) is encoded as
\nnnwherennnis the relevant character’s ASCII number.
XML (referred to in the DataStage documentation as ‘Legacy XML')
ISX – A compressed XML (binary) based format which supports all Information Server asset types.
...
For DataStage Jobs, the DSX and ISX formats allow you to choose whether you want your export to include Job design information only, encoded-binary executable information, or both.
...
When you choose to create an export incorporating only Job design information then that file will need to be re-compiled in any target project into which it is subsequently imported.
...
Each format occupies varying amounts of disk space, with the design-only ISX format occupying the least. By way of example here is a set of exports (of a simple 3-stage Parallel Job) using various formats, order by increasing file size:
...
You’ll see that the ISX design-only format occupies the least space.
...
Why does MettleCI use DSX files?
...
The format in which DataStage artefacts are stored in Git only matters to a customer when they want to do something with
Does the re-compilation of jobs in each environment compromise good deployment governance
File Contents
Treat the export as opaque
...
You won’t be relying on traditional test-based diffing techniques to identify the changes between code versions.
The Future
DataStage NextGen
MettleCI uses the 'default' ISX format (1) which contains a single version of the job which can be exported and imported without imposing restrictions about the tooling which ca be used.
...