DSXchange

Thanks lstsaur,

I have configured the same in my dsenv too. The only change i did is DB@CLIINIPATH, that was added to my dsenv file and still im getting the same error.

Thanks ArndW,

As you said I checked the first log entrie and found that the LIBPATH is given correctly.

what i have is given below:

LIBPATH=/datastage/dsadm/Ascential/DataStage/Projects/scbtransdev/RT_BP3.O:/datastage/dsadm/Ascential/DataStage/DSCAPIOp:/datastage/dsadm/Ascential/DataStage/RTIOperators:/datastage/dsadm/Ascential/DataStage/DSParallel:/datastage/dsadm/Ascential/DataStage/PXEngine/user_lib:/datastage/dsadm/Ascential/DataStage/PXEngine/lib:/datastage/dsadm/Ascential/DataStage/Projects/scbtransdev/buildop:/datastage/dsadm/Ascential/DataStage/branded_odbc/lib:/datastage/dsadm/Ascential/DataStage/DSEngine/lib:/datastage/dsadm/Ascential/DataStage/DSEngine/uvdlls:/datastage/dsadm/Ascential/DataStage/DSEngine/java/jre/bin/classic:/datastage/dsadm/Ascential/DataStage/DSEngine/java/jre/bin:/datastage/dsadm/Ascential/DataStage/branded_odbc/lib:/datastage/dsadm/Ascential/DataStage/DSEngine/lib:/datastage/dsadm/Ascential/DataStage/DSEngine/uvdlls:/datastage/dsadm/Ascential/DataStage/DSEngine/java/jre/bin/classic:/datastage/dsadm/Ascential/DataStage/DSEngine/java/jre/bin::/usr/lib:/lib

Still im getting the same error, why is that so?..In the meantime Im into troubleshooting all the relavant files.

What is the value of following environment variable in the unix prompt and in your job log?

echo $DSHOME
echo $LOGIN

Is your install root or non-root?

I don't know what you have done with your libpath; the first entry, "=/datastage/dsadm/Ascential/DataStage/Projects/scbtransdev/RT_BP3.O" shouldn't be there at all!

In addition, "/Datastage/DSEngine/lib" is NOT in that libpath, which explains your error.

Thanks Arndw & balajisr

Once i put echo $DSHOME, im getting the DSEngine path and once i give echo $LOGIN im getting my login name.

I just restarted the server and again .profile configured the LIBPATH as Arndw said file and checked the issue was resolved.

Thanks a lot guys for helping in resolving the issue.