Introduction

When S2PX encounters Server Routine names it takes the following approach:

1. Look for an appropriately-named mapping in the mapping section of the s2px.yml file and substitute the Server function name for the defined Parallel expression. This expression may include one or more references to new Parallel functions, defined in the s2px.yml file's libraries section.

2. If a mapping is not found then the Server function name is retained, unaltered, in the generated Parallel job, and S2PX assumes that an identically-name Parallel function is available. A set of new Parallel functions to support this behaviour, and which are named after Server functions, is suppled by IBM’s recent Fix Packs.

Generated Parallel Function Definitions

Where a custom Parallel function is defined in your s2px.yml file's libraries section then S2PX will create a Parallel Routine asset in your DataStage project which will provide DataStage’s interface into that external function.

...

Due to the dependency on the apt_util classes (logmsg, errlog and errind) the generated files need to be linked against the appropriate liborch<arch>.so file (where <arch> is the relevant host architecture. e.g. liborchx86_64.so) which is located in /opt/IBM/InformationServer/Server/PXEngine/lib .

Compiling Your Custom Parallel Routines

A detailed description of how you can compile your custom Parallel Routines, ready for use by DataStage, can be found here.