According to the documentation from Ascential, A C++ compiler is required to run Parallel extender jobs. Could somebody explain me when and how exactly this C++ compiler is used in running PX jobs. Is this installation mandatory to run these jobs?
Thanks in advance,
Srinivas.
Usage of C++ compiler to run PX jobs
Moderators: chulett, rschirm, roy
-
dlvsrinivas
- Participant
- Posts: 18
- Joined: Mon Jul 07, 2003 12:56 am
- Location: India
I don't have PX, but Ascential does require the appropriate C++ *runtime libraries* be installed for the DataStage server to run properly. Perhaps that is what the documentation is referring to, not the compiler itself.
Or perhaps it needs the compiler to generate the PX jobs, if they compile down to native code.
In either case, they seem pretty mandatory to me... [:)]
-craig
Or perhaps it needs the compiler to generate the PX jobs, if they compile down to native code.
In either case, they seem pretty mandatory to me... [:)]
-craig
My two cents..
PX uses the C compiler to compile the transform stage and 'new parallel' stages (i.e. buildop). If you don't use the transformer or buildop stage in your PX jobs, I don't think PX needs the compiler to build the job, but PX might still insist on having one there anyway.
If you run into compile-time errors with transform, you can look at the code that PX generates to encapsulate your transformer stage's functionality. If you know basic c programming, you can debug your transform from looking at this code.
I recommend that anyone who uses PX takes a look at the code that PX generates. It's a great way to see how PX is working under the covers, and it can help you understand ways to optimize your implementation of the transformer stage in PX. For instance, for a more performant transformer, you might consider using fewer stage vars b/c stage vars can add unneccessary bulk to PX-generated code.
-BP
PX uses the C compiler to compile the transform stage and 'new parallel' stages (i.e. buildop). If you don't use the transformer or buildop stage in your PX jobs, I don't think PX needs the compiler to build the job, but PX might still insist on having one there anyway.
If you run into compile-time errors with transform, you can look at the code that PX generates to encapsulate your transformer stage's functionality. If you know basic c programming, you can debug your transform from looking at this code.
I recommend that anyone who uses PX takes a look at the code that PX generates. It's a great way to see how PX is working under the covers, and it can help you understand ways to optimize your implementation of the transformer stage in PX. For instance, for a more performant transformer, you might consider using fewer stage vars b/c stage vars can add unneccessary bulk to PX-generated code.
-BP