Executing a DOS command

I_Server_Whale · Post by **I_Server_Whale** » Sat Aug 20, 2005 3:11 pm

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.

lstsaur · Post by **lstsaur** » Sat Aug 20, 2005 5:03 pm

Naveen,
I have used 'Execute Command Stage' in sequencer to execute my .bat file with the job parameters; it is working perfectly for me. What's the error message from your job? Don't just say Command Stage is not working.

elavenil · Post by **elavenil** » Sun Aug 21, 2005 2:06 am

Use Jobcontrol to call the batch file. The batch file can be executed using DSExecute function.

HTWH.

Regards
Saravanan

lstsaur · Post by **lstsaur** » Sun Aug 21, 2005 8:11 am

Hi Saravanan,
If you look the code generated for Command Stage, the DSExecute is called to excute the all the information in the .bat file.

I_Server_Whale · Post by **I_Server_Whale** » Sun Aug 21, 2005 9:02 am

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.

chulett · Post by **chulett** » Sun Aug 21, 2005 9:49 am

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.

ray.wurlod · Post by **ray.wurlod** » Mon Aug 22, 2005 5:04 pm

The 'Execute Command' stage runs fine. But nothing happens really.

What's wrong with this picture?

Does it run really fast?