C++ routine

[DSguru2B]

Check the path of APT_COMPILER in your datastage administrator. This env. variable holds the path to your compiler.

[lak]

Check the path of APT_COMPILER in your datastage administrator. This env. variable holds the path to your compiler.

Thank you Brian..now I found the path (/usr/vacpp/bin/xlC_r) but still when I compile I am getting "No found" error please help

Thanks

-Lak

[DSguru2B]

How are you compiling it. You need to compile it by using xlC_r. Remember its case sensitive.

[lak]

How are you compiling it. You need to compile it by using xlC_r. Remember its case sensitive.

I am compiling like...

dsadm@etldev:/u01/Ascential/dev> xlC_r test.c

[lak]

How are you compiling it. You need to compile it by using xlC_r. Remember its case sensitive.

I am compiling like...

dsadm@etldev:/u01/Ascential/dev> xlC_r test.c

dsadm@etldev:/u01/Ascential/dev> xlC_r test.c
ksh: xlC_r: not found.

[DSguru2B]

Strange. Contact your system admin to get this resolved. Its in your usr/bin. You should be able to invoke it

[ray.wurlod]

APT_COMPILER is installed with a default value. It may not be correct. Check whether your machine even has a compiler installed and, if so, where it actually is. If you're trying to compile from the command line, the compiler executable's directory pathname will need to be in your PATH and any libraries it uses will need to be in your LD_LIBRARY_PATH. You may also need other environment variables set, depending upon where other components, such as header files, may be stored.

[lak]

APT_COMPILER is installed with a default value. It may not be correct. Check whether your machine even has a compiler installed and, if so, where it actually is. If you're trying to compile from the command line, the compiler executable's directory pathname will need to be in your PATH and any libraries it uses will need to be in your LD_LIBRARY_PATH. You may also need other environment variables set, depending upon where other components, such as header files, may be stored.

Thanks Ray and Brian..Now I am able to compile by usinf full path

/u01/Ascential/dev> /usr/vacpp/bin/xlC_r test.c

Thank you once again for your quick responce.

-Lak

[ray.wurlod]

/usr/vacpp/bin/xlC_r test.c should therefore be the value of APT_COMPILER environment variable.

[DSguru2B]

Without the "test.c" portion

[ray.wurlod]

the joys of copy and paste!

[rameshrr3]

Im trying to compile on similar lines
i get my compiler path using the following command

Code: Select all

>dsadmin -listenv Test | grep APT_COMPILER

Then i compile the c funtion after verifying if the complier exists

Code: Select all

>CC -c pxIFStringExists.c 

i get a file pxIFStringExists.o

I go define a new parallel routine in manager and specify the path where my object file is located.
What next? What do i do to the permissions on this object file?
Where do i place it so that my px transformer stage can use it?

Sorry if this seems like a thread hijacking.

[DSguru2B]

It is thread hi-jacking.
Thats all, once you provide the path to the object file (.o) you can use the routine inside your transformer. Make sure that your id has execute permission to the file and folder.