Unable to delete ds files

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
ramabbm
Participant
Posts: 15
Joined: Wed Nov 17, 2004 12:04 pm

Unable to delete ds files

Post by ramabbm »

Hi,

We are getting the following error, when we are trying to delete *.ds files using orchadmin command.
0509-150 Dependent module liborchgeneralaix3.so could not be loaded.
0509-022 Cannot load module liborchgeneralaix3.so.
0509-026 System error: A file or directory in the path name does not exist.
Could someone help us to resolve the above error.

Thanks
RK
aesguerra
Participant
Posts: 32
Joined: Tue Sep 09, 2003 9:45 pm

Post by aesguerra »

hi,

make sure all paths (i.e. LIB_PATH, etc) required by orchestrate have been defined.

HTH.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The shared library path may be defined (in $DSHOME/dsenv) for DataStage processes. But, if you log in as an interactive user, does your .profile file set them for you? Possibly not. You should execute the dsenv script.

Code: Select all

cd $DSHOME
. ./dsenv
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Kirtikumar
Participant
Posts: 437
Joined: Fri Oct 15, 2004 6:13 am
Location: Pune, India

Post by Kirtikumar »

Ray,

I am trying to delete the DataSet through script which uses from orchadmin.
I am getting the mentioned error. I have done
cd $DSHOME
. ./dsenv
But still getting the same error :?:

What can be the reason?
Regards,
S. Kirtikumar.
bcarlson
Premium Member
Premium Member
Posts: 772
Joined: Fri Oct 01, 2004 3:06 pm
Location: Minnesota

Post by bcarlson »

When Unix script starts, it spawns its own session. That is, it runs in its own environment. It will adopt some of the existing environment (that is accessible at the command line), but only the stuff that is exported.

For example, if I have 2 aliases (or variables or functions) - 1 is export, and 1 is not. The first will be available in the script, but the second will not.

You will need to source in the dsenv file within the script that calls orchadmin, as in the (very simple) example below:

Code: Select all

#!/usr/bin/ksh
. /opt/myAscentialDir/dsenv

ds_to_delete=$1

orchadmin rm -f ${ds_to_delete}
rc=$?

exit $rc
Please note, if $DSHOME is defined and exported in your .profile, then you could change the 2nd line of code to

Code: Select all

. ${DSHOME}/dsenv
Hope this helps,

Brad.
Post Reply