DSXchange

If they are pathed, then yes. Otherwise, you'd need to worry about the VOC entry as well. And I wouldn't worry about changing the column names, columns are referenced by their internal position number, not name. So any time you reference a hashed file, you can call the columns whatever you like.

You can automatically 'validate' XML as long as you have an xsd for them. While the stages support that, I find doing it from the command line a better practice, a more robust solution. As to 'validating' flat files, you'd have to explain what kind of validations you'd need to perform.

Actually you're doing CDD or Change Data Detection, not CDC. Why not just do as Vince posted? Read your landed data as one long delimited string, use calls to Field() to pull out the individual key fields and then one or more Field() calls can pull out everything else (whichever are contiguous) and ...

Seems like this is why you've asked about the RowMerger stage. One thought... perhaps array notation would be more managable and would get you the Value Marks automatically. Use ArrayName<-1> to push an element onto the end of the array in a loop. And if you end up needing a different delimiter, the...

ps. There's no need to "set" them, that's handled in the generated code, something you could check out if you are curious in the RT_BPnnn directory for your job. So just reference them in your "reject" links. Oh, and rejected means not only "didn't go down" but "di...

When I click Constraints, Expression Editor Context Help ("..." button), Link Variables, Outputs..., I see what looks to be a global REJECTED variable, and individual link REJECTED variables. If there is a way to set the REJECTED variables without having a Reject link (Reject Row box tick...

Ok, back in bottle now.

greggknight wrote:output captures the return code of the script

Actually, that 'Output' variable captures whatever is sent to stdout by the script, which is why they 'echo $flag'. The one they named ReturnCode captures the return code.

OK... so (bare bones) an "ls <pattern> |wc -l" perhaps, inside a loop, until it returns something other than zero.

ps. While "*.*" means any file on Windows, it certain does not on UNIX - that means 'any file with a dot in it'.

Interesting... thanks for posting that.

each time i run the job file name must be updated with system date and time. Does this mean you'll be appending to a file and want to rename it as well each time, or do you just mean each new file must have a current timestamp as part of its name? :? :idea: Not the first time someone has asked this...

What does the routine need to do? Wait for how long? And then exit when files found? Or return the number of files? A list of file names?

Any of this can be done with O/S commands and DSExecute. Or all in a shell script you call.

What I'd suggest is running the script in 'debug' mode like so: Cmd = 'sh -x /abc/test7.sh /home/test/xyz.csv' and then logging the Output variable. Then you should be able to see where it is going wrong.

You'd have to be a wee bit more specific about what an 'uneven result' means.

Right, because a search would reveal no definitive answers posted as to what it means. Involve your official support provider. Post any results you get.