Error running a batch file
Moderators: chulett, rschirm, roy
I have found dsjob.exe in the path D:\Program Files\Ascential\DataStage7.5 in Production.chulett wrote:PATH issue, as in the directory where dsjob lives is not in your production PATH environment variable.
I also found it present in the test.
Can I know what should I be checking other than this.
Thanks
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You need to check that the DataStage bin directory's pathname is one of those in your command search list - that is, your PATH environment variable.
Temporarily you can include it.
Ultimately you want to make the inclusion more permanent, either through Control Panel or through your login script.
Temporarily you can include it.
Code: Select all
PATH=%PATH%;"D:\Program Files\Ascential\DataStage7.5\bin"
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.
I was able to define the path which was not present
Check for the Path in command prompt. If you donot find the path where dsjob.exe is present, goto My Computer ->Properties, Advanced Tab -> Environment Variables, look for PATH under Variable and add the path=D:\Program Files\Ascential\DataStage7.5 under value.
Check for the Path in command prompt. If you donot find the path where dsjob.exe is present, goto My Computer ->Properties, Advanced Tab -> Environment Variables, look for PATH under Variable and add the path=D:\Program Files\Ascential\DataStage7.5 under value.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Control Panel, System applet, Environment command button
PATH (maybe Path) is a System variable.
Select it and edit it to include the pathname of the DataStage Engine bin directory (and of the PXEngine bin directory if you have Enterprise edition).
Tip: copy the value of PATH out of the Variable value field into, say, Notepad, edit it there, then use copy/paste to put the new value into the Variable value field after visually checking your edit.
PATH (maybe Path) is a System variable.
Select it and edit it to include the pathname of the DataStage Engine bin directory (and of the PXEngine bin directory if you have Enterprise edition).
Tip: copy the value of PATH out of the Variable value field into, say, Notepad, edit it there, then use copy/paste to put the new value into the Variable value field after visually checking your edit.
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.
[quote="ray.wurlod"]Control Panel, System applet, Environment command button
PATH (maybe Path) is a System variable.
Select it and edit it to include the pathname of the DataStage Engine [b]bin [/b]directory (and of the PXEngine [i]bin [/i]directory if you have Enterprise edition).
Tip: copy the value of PATH out of the Variable value field into, say, Notepad, edit it there, then use copy/paste to put the new value into the Variable value field after visually checking your edit.[/quote]
I have already added the pathname in PATH. But when I am running the TWS job, I am still getting the same error as I was getting before. Do I need to restart the server for this to work.
When I checked in the command prompt %path%, it gave a return as "''D:Ascential\DataStage\Engine\bin' is not recognized as aninternal or external command, operable program or batch file"
PATH (maybe Path) is a System variable.
Select it and edit it to include the pathname of the DataStage Engine [b]bin [/b]directory (and of the PXEngine [i]bin [/i]directory if you have Enterprise edition).
Tip: copy the value of PATH out of the Variable value field into, say, Notepad, edit it there, then use copy/paste to put the new value into the Variable value field after visually checking your edit.[/quote]
I have already added the pathname in PATH. But when I am running the TWS job, I am still getting the same error as I was getting before. Do I need to restart the server for this to work.
When I checked in the command prompt %path%, it gave a return as "''D:Ascential\DataStage\Engine\bin' is not recognized as aninternal or external command, operable program or batch file"
You are missing a "" in the 3rd positionshyamrai wrote:...it gave a return as "''D:Ascential\DataStage\Engine\bin'...
Last edited by ArndW on Thu Jun 28, 2007 7:05 pm, edited 1 time in total.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
![Confused :?](./images/smilies/icon_confused.gif)
To answer the question as asked, you are 'missing' any valid command that lives in the mentioned 'bin' directory.
Isn't there someone on-site there with you that is a little more 'DOS savvy' and whom could help you with this?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: