ExecDOS Command

bob7027 · Post by **bob7027** » Tue Apr 16, 2013 3:38 pm

Hello All, I need your suggestion here.
i am trying to trigger the MS-DOS Batch file. Here it moves the file and add the date for the file name, when i tried this directly it is working but when i used this command through datastage, it is not working.

expected result : User_Log_Test_Mon 04-15-2013

o/p getting: User_Log_Test_0-0-0

can any one please let me know, where i am getting wrong regarding this.

Advance Thanks

ray.wurlod · Post by **ray.wurlod** » Tue Apr 16, 2013 4:22 pm

Show us the method you are using in DataStage. For example are you using a before-job subroutine to invoke ExecDOS? If so, what are you putting into the Input Value field?

chulett · Post by **chulett** » Tue Apr 16, 2013 5:59 pm

Probably a relative v. full path issue but as noted we'd need to see your syntax to have any idea what is going on.

bob7027 · Post by **bob7027** » Tue Apr 16, 2013 7:00 pm

Thank you for your reply, i used after job subroutine execDos and the input value is input file.
Thats all i used, bash file is executing perfectly but the expected output is wrong. When I ran the same commands in Cmd prompt, it is executing perfectly, but when the same executed through datastage it is giving as mentioned.

bob7027 · Post by **bob7027** » Tue Apr 16, 2013 7:02 pm

chulett wrote:Probably a relative v. full path issue but as noted we'd need to see your syntax to have any idea what is going on.

Thank you for your reply, right now I dont have syntax, but it is nor marl syntax to get the yesterday date.
I will post the systax ASAP.

I am sorry for this...

my question is do I need to keep any default date format in DS

chulett · Post by **chulett** » Tue Apr 16, 2013 7:02 pm

Changing the contents of this post since the timing was a little off.

The answer to your last question is "no". It doesn't do anything different than you would - create a DOS shell and execute the command. I mentioned the path because it is a common tripping point for people new to the product. They build something that only works when you run it from the right directory, which they always do so it always works... and then doesn't from DataStage. They don't realize that the directory it launches it from, the "current working directory", will be the Project directory of the job that is executing it.

Whatever you are doing in your batch shouldn't make any assumptions about where it is, hence my warning about relative paths. Explicitly cd to wherever you need to be. Seeing your syntax would help rule this out (or in) as the culprit.

ray.wurlod · Post by **ray.wurlod** » Tue Apr 16, 2013 11:42 pm

bob7027 wrote:bash file is executing perfectly but the expected output is wrong

You're executing a bash script using ExecDOS ?

Or do you mean a batch file?

Still waiting to see what you've put in the Input Value field.

bob7027 · Post by **bob7027** » Wed Apr 17, 2013 7:25 am

echo %DATE:/=%

set /a d= %DATE:~0,2%
set /a month=%d%

set /a d= %DATE:~5,4%
set /a year=%d%

set /a d=%DATE:~3,2%
set /a yesterday=%d% - 1

MovE "\\C\DS\DS_TEMP\BOB\TEXT_.csv"
"\\C\DS\DS_TEMP\BOB\TEXT_%month%-%yesterday%-%year%.csv"

This is the syntax I am using
which works fine when i use from the folder, but not working when using it through datastage

chulett · Post by **chulett** » Wed Apr 17, 2013 7:35 am

OK... so this is the contents of a batch file you are calling via ExecDOS, yes? And when you say "output" you're not talking about what it echoes to the screen but rather what the name of your file ends up being? Trying to understand exactly what is happening - is your file being "moved" i.e. renamed, it's just that the name isn't correct?

bob7027 · Post by **bob7027** » Wed Apr 17, 2013 7:51 am

Yes what you said is exactly correct. when it moves it should move with the file name.

output got: Text_0-0-0

expected : Text_04172013

ray.wurlod · Post by **ray.wurlod** » Wed Apr 17, 2013 2:40 pm

I still want to see what is in the Input Value field for ExecDOS.