Jobs Remediation

This sheet details the level of manual intervention that will be required by humans to the Parallel Jobs generated by S2PX. It derives its data from the Remediation Data sheet which you can inspect for further details.

Open

Jobs Remediation - Summary

The summary graph describes how many Server Jobs will convert to Parallel Jobs which are expected to replicate Server behaviour without problems.

In this example we can see that S2PX expects that…

• Not Required Approximately 45% of Jobs will convert to Parallel Jobs which function identically to their Server equivalents.

• Required The remaining approximately 55%, however, will require some level of manual intervention from a human before they can replicate the behaviour of their Server ancestors.

There are a number of reasons why manual intervention may be required, but is often because a Server Job uses one or more capabilities for which a direct equivalent in the DataStage Parallel engine is simply not available. In some cases the user may be required to re-interpret the original Job requirements to identify whether the compromise solution presented by S2PX will suffice, or whether further enhancement of the generated Jobs(s), using native Parallel functionality, is required.

Jobs Remediation - Details

This section describes the details of the required interventions identified in the summary graph above. The Issue requiring remediation column lists, in order of descending number of instances encountered, the S2PX Asset Query which identified the issue. The documentation for each of these Asset Queries (linked in the associated Remediation Data sheet) suggests a required course of remediation action, where one is require.

In this example we can see that the converted ISX has 183 instances (across 106 distinct Server Jobs) of the Disable Schema Reconciliation issue. In this case a remediation is likely not required but particular attention must be paid to these Jobs during Parallel Job testing.

We can also see 130 instances of a Sequential File with Backup issue across 102 distinct Server Jobs. The actual functionality of the Job itself isn’t affected but for some customers the loss of Sequential File backup functionality maybe unacceptable, and so an alternative solution (of which many are available) should be sought.

The Reserved Words in Transformer Stages issue, as a further example, is one where every instance discovered will require human intervention to resolve as these Jobs will not compile in their current form, and S2PX will not attempt to generate new variable names for your Job as the existing name is likely to encode meaning which is useful for Job developers.