DSXchange

Right, because you've always got the MKS Toolkit to fall back on with a Windows server and was part of the reason why I said you'd be better off sticking with UNIX commands. Seems to me it is more problematical getting a fully pathed filename from a dir command which is trivial with ls. Just surpris...

You should wait for more smarter peoples to comment but I'm thinking you might want to double your T30FILE setting. Odd that it just hangs, though.

No warnings of any kind are logged when this happens? Nothing that mentions anything like T30FILE perhaps?

You're right, errors are reported from those 'combo' actions when the second action fails. And while the first action must also 'fail' for the second to be triggered, that first failure is silent, not logged. The issue here is determining what it didn't like about the update. Typically that means it...

Right, those square brackets are the substring operators and they take start position and length as parameters.

You're certain your DataStage server is on a Windows box? And you're not actually including the "<code>" tags you keep using here, are you?

If it's everyone then the first question is moot. However, you'll find it on the Tools/Options menu.

It's not a problem to provide more details or distinguish your question, just don't start a new post simply to do that.

Simple has nothing to do with it. Out of curiosity, what is your refresh interval in the Director? Is everyone seeing this or just you?

Something wrong with this post? Let's stick to one place to discuss this, please.

"dir" is a DOS command similar to "ls" in UNIX and the /b means "bare format". Open a "cmd" window and type "dir /?" for the syntax. Or google.

And why is that?

You really haven't given us all that much to go on, btw. How about that job design?

'Running continuously' when a database is involved generally means locking issues. Has your DBA monitored these sessions for you?

How many times are you going to post this?

Not true. No 'concatenation' will occur but it will process all of the files one after the other without that pesky looping job sequencer.

For DOS, you want to look into dir with the /b option but you're better off sticking with UNIX commands.