Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

(This summary sheet derives is data from the Function Data sheet which you can inspect for further details.)

Job Function Calls - Summary

The 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…

  • BUILD-IN Just over 50% of Jobs feature one or more function calls of which all are natively supported in target DataStage environment (v11.7.1.3 SP4 or greater).

  • REQUIES MAPPING Slightly less than 50% percent, however, have no Parallel equivalent - either because they are IBM-supplied DataStage Server functions for which no Parallel version exists, or because they are custom functions you have coded yourself in DataStage Basic. In this case you will need to configure S2PX with one or more custom routine mappings.

Function or Routine Name - Details

The 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.

  • No labels