Page 1 of 1
dsjob command not working
Posted: Tue Jun 17, 2008 3:47 pm
by marbar
Hello,
I was running some dsjob commands (-linkinfo, -stageinfo, etc.) from the /bin directory
when I performed a bad copy/paste into the command line (last good command was a dsjob -report).
I got a whole list of command rejected errors messages.
Now when I try to run a dsjob command all I get is the /bin> prompt and no execution.
I cannot explain this behaviour so any help would be much appreciated...
(and I promise will try to loose some weight from my fingers
) .
Thanks
Posted: Tue Jun 17, 2008 4:51 pm
by ray.wurlod
Welcome aboard. As a general rule we can not do anything useful with "not working" - it's too vague. We need to see the precise error messages that are generated.
Posted: Tue Jun 17, 2008 5:13 pm
by chulett
Can you explain what this "bad copy/paste" was all about? Have you destroyed / overwritten any of the bin components?
Posted: Wed Jun 18, 2008 12:10 am
by marbar
Ray,
Here is the what I am doing:
apux19::/appl/asudtstg/Ascential/DataStage/DSEngine> . ./dsenv
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine> cd bin
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine/bin> dsjob -lprojects
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine/bin>
The result of the dsjob command is this last line, just a prompt, no error messages. And there are 20 projects in the DSEngine/projects directory.
This is on our DEV box. The same sequence of commands on our PROD box gives the list of projects.
Craig,
Everything was working fine. I had run several dsjob commands with different options and they were all working fine. Then I ran a dsjob -report command. After that I was going to select a section of that command with the mouse and right click to paste it in the command line when I actually selected the -report command plus its the whole result and pasted it into the command line and executed it. For each line I pasted I got an invalid command message so I did not think much of it and went on to try again.
From that moment on any variation of the dsjob command is just coming back with the prompt. No messages.
I got everybody out of the server and stopped/restarted it to no avail.
I was thinking about overlaying the DEV dsjob file with the PROD one to test the file corruption theory. But if that got corrupted then the whole bin directory could have been affected...
Posted: Wed Jun 18, 2008 12:35 am
by ray.wurlod
Try:
Code: Select all
apux19::/appl/asudtstg/Ascential/DataStage/DSEngine> . ./dsenv
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine> bin/dsjob -server apux19 -lprojects
Posted: Wed Jun 18, 2008 12:39 am
by ArndW
Could your "dsjob" executable have been corrupted? Can you still run jobs?
Posted: Wed Jun 18, 2008 12:44 am
by ray.wurlod
Surely that would generate at least some error message!
Posted: Wed Jun 18, 2008 5:43 am
by chulett
Apparently not.
I'm assuming that, at the very least, dsjob was hosed up by your actions. Simple enough to check. Compare the output of these commands from DEV and PROD:
Code: Select all
cd $DSHOME/bin
file dsjob
ls -l dsjob
And then - as noted - if dsjob was affected, what else might have been?
Posted: Wed Jun 18, 2008 6:02 am
by ArndW
Ray, I think if you have an executable and make it length 0 by mistake (i.e. bad copy) then you can execute it and get no error.
Posted: Wed Jun 18, 2008 10:16 am
by marbar
Ray,
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine> . ./dsenv
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine> bin/dsjob -server apux19 -lprojects
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine>
Same behaviour.
Craig,
FROM PROD:
apux165::/data51/app/asudtstg/Ascential/DataStage/DSEngine/bin> file dsjob
dsjob: ELF 32-bit MSB executable SPARC Version 1, dynamically linked, not stripped
apux165::/data51/app/asudtstg/Ascential/DataStage/DSEngine/bin> ls -l dsjob
-rwxr-xr-x 1 asudtstg datastage 146876 Feb 20 2007 dsjob
FROM DEV:
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine/bin> file dsjob
dsjob: empty file
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine/bin> ls -l dsjob
-rwxr-xr-x 1 asudtstg datastage 0 Jun 17 12:56 dsjob
I compared the DEV /bin content with the PROD /bin content and the only file that is different in size in dsjob (143KB on PROD side, 0 on DEV). It is also the only file that got updated on 6/17/08.
Do you think I can safely copy the PROD file onto the DEV one?
Thanks
Posted: Wed Jun 18, 2008 10:17 am
by marbar
Ray,
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine> . ./dsenv
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine> bin/dsjob -server apux19 -lprojects
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine>
Same behaviour.
Craig,
FROM PROD:
apux165::/data51/app/asudtstg/Ascential/DataStage/DSEngine/bin> file dsjob
dsjob: ELF 32-bit MSB executable SPARC Version 1, dynamically linked, not stripped
apux165::/data51/app/asudtstg/Ascential/DataStage/DSEngine/bin> ls -l dsjob
-rwxr-xr-x 1 asudtstg datastage 146876 Feb 20 2007 dsjob
FROM DEV:
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine/bin> file dsjob
dsjob: empty file
apux19:ASUPMDEV:/appl/asudtstg/Ascential/DataStage/DSEngine/bin> ls -l dsjob
-rwxr-xr-x 1 asudtstg datastage 0 Jun 17 12:56 dsjob
I compared the DEV /bin content with the PROD /bin content and the only file that is different in size in dsjob (143KB on PROD side, 0 on DEV). It is also the only file that got updated on 6/17/08.
Do you think I can safely copy the PROD file onto the DEV one?
Thanks
Posted: Wed Jun 18, 2008 10:19 am
by chulett
Yes.
Posted: Wed Jun 18, 2008 10:27 am
by ArndW
Hehe, looks like the 0 length guess was good. I've done that before, by mixing source and target directions in those tricky UNIX commands.
At least 0 length executables are easy to debug...
Posted: Wed Jun 18, 2008 10:31 am
by marbar
Thank you all for your help.