DSXchange

This is a message that the osh is wrong in some way.

Why are you trying to write in Osh?
Why don't you create your job using the Designer?

kool_cons wrote:or else need to compile the jobs and run the sequence. this is all has to be done in unix.

You can't compile jobs from a Unix script.

permissions?

I think you need to preload java in your shell script.
Look at your dsenv file for the entry LD_PRELOAD.
Try getting your shell script to add this environment variable before it calls and java components.

Does it contain a BASIC Transformer?

To build just an object file for a routine you don't need to run the linker. If you wish to build a library file for a routine then you will need to use the linker (and thus the options). I think the referenced compiler for AIX is xlC_r ? Just to be sure - each time you rebuild the object file you s...

In your 'c' code you haven't declared the function return type.
[ i.e int AddNumber( int a, int b) }

When building the object file, did you use:
CompilerOptions = -+ -O -g
LinkerOptions = -G -qmkshrobj=1000

Have you declared the arguments in the PX routine definition?

I assume you PX routine definition has the Object type = 'Object'.
(Not Library) if so:

Have you tried using the examples from your DataStage Install media?
Which Platform and compiler options have you used?

I think to clear the job with the Invocation ID from the director you would have to recompile the origianal job. (without InvocationID)

You must exprt the custom stage from the machine it was created and import it to the new machine before the jobs that rely on this stage will work.

Have you tried waiting a short while before killing the job?
If you kill the job to quick the messages won't have found there way to the director log before the kill signal throws away your error logging.

s_rkhan wrote: Are there any specific runtime C++ libraries that are required for Linux machines.

You just need to check that you are using the correct version of Linux and compiler. What version of Linux do you run and which compiler is installed?

/usr/lib is definitely not enough. You also need the DataStage lib directory, the branded ODBC drivers' lib directory, any other operating system library directories and, in particular, the directory containing the "missing" V0S1_testjobtrans_Transformer_1.so. You need to adjust LD_LIBRAR...

I first though is that FMT is a server function and thus not avaliable in a parallel job.

kumar_s wrote:Is there any way we can refresh OSH so that it takes the current configuration of the job.

If your using a parallel transformer in the job try using the "Force Compile" Option when you re-compile the job.