| Table of Contents |
|---|
...
This sheet provides a high-level overview of the level of support S2PX will provide for converting your DataStage solution’s particular set of stage types.
  | Supported Server Jobs - SummaryThe percentage of jobs in the supplied ISX file that contain…
A description of which stages are currently supported and which are still in the planning stage is available here. Number of unsupported Stages by StatusA colour-coded breakdown of the number of
UniVerse Data Access stage of which 16 instances were encountered.Unsupported Jobs - DetailsLists the individual Jobs containing
Find_Untraced_Jobs_DB2 is the Jobs which will require the greatest attention due to it containing 6 instances of unsupported stages. The exact names and types of these stages are described in the associated Support Data spreadsheet. |
...
This sheet details the level of manual intervention that will be required by humans to the Parallel Jobs generated by S2PX.
...
Jobs Remediation - SummaryThe 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…
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 - DetailsThis 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 a likely to encode meaning which is useful for Job developers. |
...
(This summary sheet derives is data from the Function Data sheet which you can inspect for further details.)
  | Job Function Calls - SummaryThe Summary graph at the top identifies the proportion of Server Jobs which use function calls which are expected to work without further intervention (because an identically-named Parallel equivalent function already exists) and those which are expected to require some level of human involvement. In the example here we see…
Function or Routine Name - DetailsThe table below lists all function calls which S2PX doesn’t understand, and for which some level of manual conversion will be required. This table of functions names, ordered by descending number of distinct calls, also details the number of distinct Jobs from which calls originate. |
...
(This summary sheet derives is data from the Connector Migration Data sheet which you can inspect for further details.)
  | Jobs requiring Connector MigrationPercentage of jobs involving Connectors (a component that provides data connectivity and integration for external data sources, such as relational databases or messaging software) that are classified as legacy components and need migration using IBM’s Connector Migration Tool ('CCMT') solution. Stage Types requiring Connector MigrationA breakdown of the number of stages requiring conversion by stage type, ordered (left-to-right) by descending number of instances discovered in your ISX file. Jobs requiring Connector MigrationA table of Jobs along with the number of stages on each job requiring migration, order by descending number of stages requiring migration. |
...
 | Prevalence of Hashed Files in Jobs - SummaryThe Summary graph at the top simply identifies the proportion of Jobs which make use of one or more Hashed Files stages. Jobs are categories as simply
Hashed File Usage Patterns - SummaryThe next summary graph identifies, for each Hashed File reference, whether that reference is…
Hashed File Instances per Job - DetailsA list which breaks out the Hashed File Usage patterns summary above by Job, ordered by descending frequency of usage. |
...