DSXchange

It's works !

But on "Execute Command Activity", I have not found a similar command DOS (cd myfiles) to put before for /F "delims=" %A in ('dir /b *.csv') do if %~zA LSS 1024 del "%~dpnxA" in DataStage

Do you mean what goes in the 'Command' v. 'Parameters' boxes in the Execute Command stage? Shouldn't really matter, put the whole thing in either one. If you really need something, try using CMD as the Command.

Hi,
My JOB :




In the first stage "Execute Command", the command is cd MYDIRECTORY , it's works

In the second stage, the command is for /F "delims=" %A in ('dir /b *.csv') do if %~zA LSS 250 del "%~dpnxA" but it doesn't work.

Errors :
- Command for /F "delims=" %A in ('dir /b *.csv') do if %~zA LSS 250 del "%~dpnxA" did not finish OK, reply = '1'
- delims was unexpected at this time.

What is strange, is that it works with "cmd.exe".

Please need backup.

The CD command does not "carry through" - you need both commands in a single Execute Command activity with either a ";" or a "&&" between them.

I try with one "Execute Command" :

cd MYDIRECTORY ; or && for /F "delims=" %A in ('dir /b *.csv') do if %~zA LSS 250 del "%~dpnxA"

It doesn't work.


This command /F "delims=" %A in ('dir /b *.csv') do if %~zA LSS 250 del "%~dpnxA" doesn't work on DataStage why?

DataStage unlike "delims" and "dir"

Show us the detailed contents of the log message where the command is executed, specifically the actual command it ran. DataStage is notorious for stripping quotes, perhaps that is what is going on.

Write a batch file where you do everything that needs to be done - cd, check the size and delete - then use ERRORLEVEL to see if it succeeded. Run the .bat file in the Execute Command stage.

ps. Long overdue move just made to the General forum since nothing here is specific to either job type.

When I stated

ray wurlod wrote:either a ";" or a "&&" between them

I did not intend for you to put ; OR %% between the two commands. I meant you to put ; between the two commands, or to put && between the two commands. That's why the word "either" was there.

Never mind the fact that && is valid for UNIX, not DOS.

But in Windows MKS is there!!

Ray

That mean from DS 9.1 none of the unix commands won't work??

You mean the MKS Toolkit and AFAIK you wouldn't have it if you have a Server only license, which I believe is the case here. And for 9.1 I think that they will all still be there but will be implemented differently under the covers. At least that's the impression I got from what Ray has posted so far on the subject.

chulett wrote:You mean the MKS Toolkit

Yes you are right. I haven't realize when i post my comment.

chulett wrote:Never mind the fact that && is valid for UNIX, not DOS.

&& is valid for DOS.
See, for example, Conditional Execution - Conditional Execution Based on Result of Previous Command in DOS Script Snippets.

OK then... well, never mind. I know what it means just don't recall ever seeing it used in the DOS world. Live and learn.