DSjob command issue
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 17
- Joined: Thu Jan 15, 2015 5:21 am
- Location: India
DSjob command issue
We are trying to invoke a job using dsjob command inside a script. But we are getting the following error when we run the script.
line 9: .: ./dsjob: cannot execute binary file
Please help us.
line 9: .: ./dsjob: cannot execute binary file
Please help us.
-
- Participant
- Posts: 17
- Joined: Thu Jan 15, 2015 5:21 am
- Location: India
Never mind the whole 'relative path' thing, while fine advice that's obviously not the issue here. Your error is an odd one and generally indicates a compatibility issue - say you bring over the command from another version of UNIX or one compiled with the 'wrong' compiler for the current O/S you could see something like that.
Can you run dsjob from the command line outside your script?
Can you run dsjob from the command line outside your script?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
are you able to log in to the command line with dsadm and execute this:
(after sourcing dsenv of course)
$DSHOME/bin/dsjob -lprojects
That will at least tell you if it's the engine or something specific to your project (like if you imported jobs with executables from a different OS) as was mentioned.
(after sourcing dsenv of course)
$DSHOME/bin/dsjob -lprojects
That will at least tell you if it's the engine or something specific to your project (like if you imported jobs with executables from a different OS) as was mentioned.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 17
- Joined: Thu Jan 15, 2015 5:21 am
- Location: India
Thank you all for the suggestions.
Please find the script that we are using
#!/bin/bash
. /opt/IBM/InformationServer/Server/DSEngine/dsenv
cd /
cd /opt/IBM/InformationServer/Server/DSEngine/bin/
pwd
. dsjob -run TEST TEST
Since our login ID's doesn't belong to dsadm group , we are executing the script from datastage job. In th datastage job log we could see USER=dsadm.
But we are getting the below error in datastage log
Reply=126
Output from command ====>
/opt/IBM/InformationServer/Server/DSEngine/bin
line 7: .: ./dsjob: cannot execute binary file
Thanks,
Mani
Please find the script that we are using
#!/bin/bash
. /opt/IBM/InformationServer/Server/DSEngine/dsenv
cd /
cd /opt/IBM/InformationServer/Server/DSEngine/bin/
pwd
. dsjob -run TEST TEST
Since our login ID's doesn't belong to dsadm group , we are executing the script from datastage job. In th datastage job log we could see USER=dsadm.
But we are getting the below error in datastage log
Reply=126
Output from command ====>
/opt/IBM/InformationServer/Server/DSEngine/bin
line 7: .: ./dsjob: cannot execute binary file
Thanks,
Mani
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Try changing it to
Please also verify permissions on the dsjob executable file.
Code: Select all
. ./dsjob -run TEST TEST
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 17
- Joined: Thu Jan 15, 2015 5:21 am
- Location: India
-
- Participant
- Posts: 17
- Joined: Thu Jan 15, 2015 5:21 am
- Location: India
Have you tried running it manually from the command line as requested? If you still get that error, involve support. If it won't even run from the command line (should give you a basic usage error) then it's corrupt or otherwise invalid.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Try "./dsjob -run TEST TEST". You don't want to do a Dot Space Dot Slash.ray.wurlod wrote:Try changing it toCode: Select all
. ./dsjob -run TEST TEST
Code: Select all
#!/bin/bash
. /opt/IBM/InformationServer/Server/DSEngine/dsenv
#make sure you are in your personal home
cd
#don't play in the engine path
#cd /opt/IBM/InformationServer/Server/DSEngine/bin/
pwd
#$DSHOME set in dsenv
$DSHOME/bin/dsjob -run TEST TEST