Hi All,
I need to execute a DOS batch file. Currently, I'm doing it in a 'Before Job Subroutine', the job here extracts data from ODBC to text file. But I want to execute this batch file as a different job.
How can I include just the batch file in an empty(new) job without anything else? All this job does is execute the batch file.
I tried used 'Execute Command Stage' in sequencer. But it is not executing the DOS command.
I don't know why. Any help is very much appreciated.
Thanks much,
Naveen.
Executing a DOS command
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
Hi lstsaur,
I'm not getting any error message. The 'Execute Command' stage runs fine. But nothing happens really. I mean the SQL script is not run, which is supposed to, through the batch file.
Should I use the 'Command Stage' instead of the 'Execute Command' Stage? May be I should. I'll try that and let you know.
FYI, the batch gets executed when included in the 'Before JOb Subroutine'.
I'll get back to you after trying the 'command stage'.
Thanks a lot for your response.
Naveen.
I'm not getting any error message. The 'Execute Command' stage runs fine. But nothing happens really. I mean the SQL script is not run, which is supposed to, through the batch file.
Should I use the 'Command Stage' instead of the 'Execute Command' Stage? May be I should. I'll try that and let you know.
FYI, the batch gets executed when included in the 'Before JOb Subroutine'.
I'll get back to you after trying the 'command stage'.
Thanks a lot for your response.
Naveen.
You need to look in the log of the Sequencer job to see what happened with the Execute Command Stage. Usually you need to double-click on it to see all of the gory details. The job won't error when there is a problem running your command... well unless you have triggers to handle that and the command actually reports back errors.
If 'nothing happens' I would guess that you are not giving the full path of the batch file in the stage and it can't find it to run it. Again, that should be recorded in the log.
If 'nothing happens' I would guess that you are not giving the full path of the batch file in the stage and it can't find it to run it. Again, that should be recorded in the log.
-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: