S2PX Architecture and Workflow

Here’s a summary of the Server-to-Parallel ('S2PX') high level workflow, boundary of responsibility, operating components, and outputs.

1. For analysis: Export legacy Server jobs as ISX files. See link.

2. Run the S2PX analysis command line tool which will produce a set of Microsoft Excel files you can analyse.

3. For conversion: Run the IBM CCMT command line tool which will upgrade your Server jobs to…

   1. remove deprecated Stages, and

   2. modify Connector Stages to use the latest version of those Connectors.

4. The CCMT tool upgrades your Jobs directly in the DataStage Repository. There is no need to export or Import DataStage files

5. Now export your legacy Server jobs as DSX files. See link.

6. Run the S2PX conversion command line tool which generates a DSX file including Parallel assets derived from the Server assets in the supplied input file.

7. The S2PX conversion process also generates a set of log files describing the assets encountered during the conversion process and what issue will require manual intervention to make your generated Parallel assets runnable.

8. A DataStage Developer will use the S2PX Analysis Spreadsheet and conversion logs to apply any required manual remediations to the generated Parallel jobs.

9. The Parallel jobs can then be deployed to a downstream environment, either manually or by using a MettleCI pipeline triggered by committing your assets to a Git repository.

10. Note that for IBM Cloud Pak for Data you can use its facilities to import legacy DataStage ISX files into its NextGen DataStage platform.

See also