DSXchange

nicolas2143 wrote:Does any stage exist in DS USS, which allows to realize this operation?

DS USS uses the same stages as the Parallel canvas but enables you to shift the workload onto the mainframe.

srekant wrote: 1)Is it possible to run parallel jobs on win2003

ArndW wrote:Yes, you can run Px on 2003.

But not using DS 7.5.1.A

I disagree. If the dll was missing then the job would not compile and this message looks like a runtime error. The last message is "The specified module could not be found" which normally means that the function within the dll cannot be loaded. This implies that either the dll was not buil...

External routines don't use the object file ( *.obj) on a windows system.

On windows systems you to compile either a *.lib (library file) or a *.dll (dynamic library file)

Is this a library or dynamic routine?
How did you compile the routine? (commands?)
Have you set the retrun datatypes correctly in the PxRoutine definition in the DataStage designer?
Have you done this before on Unix?

Does this job work at runtime?

unresolved external symbol "char *"

What arguments and return types have you configured within the parallel routine definition? - Do these match with the return types definied within the DLL?

You can compile the transformer directly on the Z/os from the command line. (DataStage can generate you a script) You can then see how long that part of the compile takes and what difference tweeks on the mainframe make.

(check the options on the remote tab for generating deployment scripts)

Eric, The compiler is available coz when i compiled the c Code from Command Line This does not mean that DataStage can find the compiler. Did you have only Studio .NET installed Before you installed DataStage? You other post has problems with Unknown compiler and linking Options (i.e. -Wc++) - Why ...

maffan76 wrote:

Code: Select all

##I TBLD 000000 15:58:50(006) <main_program> Error when checking composite operator: Output from subprocess: Compiler "cl" not found.

The problem is that no compiler is avaliable to DataStage.

Do you have visual studio 6 also installed?

D:\Ascential\DataStage\PXEngine\include\apt_util\basicstring.h(89) : error C2039: 'ostream' : is not a member of 'operator``global namespace'''

That error sounds like the .NET compiler is not being used???

Why would a C routine on Windows be any different from the same C routine on UNIX? The routine code may be the same, but to create a windows DLL you will require a different function decleration and sometimes different include definitions. This is due to the way the windows platform uses a DLL at r...

Have you moved this job to a different platform? (recompile job)

Does the job contain PX routines? (move routine 'c' code - recompile routine then recompile job)

Do you want to build static or dynamic libraries?

For static libraries you need to compile a *.lib file
for dynamic libraries you need to build a *.dll file

How you generate these depend on your choice of using command line 'nmake' or the Visual Studio .net application.

maffan76from subprocess: Compiler "cl" not found.

Did you have a compiler installed before you installed DataStage?
The error would imply that datastage cannot find a compiler.