DSXchange

What is this "filename.txt" of which you speak? Where do it come from?

just4geeks wrote:We would like to use 64 bit hash files to avoid size limitation.

Where exactly are you having any file size issues? You've marked this as 'Parallel' and parallel jobs don't use hashed files like Server jobs do. Is this so you can have ginormous job logs?

Open up the dsx file with your editor of choice and see if the job is in there once or twice...

You get 32 character output from an MD5 checksum and it is indeed hexidecimal.

With a script and plain old command line ftp.

What "that" are you begging to differ on?

If you mean my "easily solved" comment, that was strictly regarding your inability to see Premium Content.

OK, we understand blink errors. How about my other question, when are the copies being made - while jobs are running?

Can we get some details on what "log file corruption" means here? What logs and are they doing this file copying from a live, up and running system?

In other words, inadvertent sub-string matches.

Split to your own post.

Well, there you go. My point still stands, though - it can't be used to transfer multiple files from one location to another, if that is the need here. It can, however, read multiple files into a single input stream.

chandra.shekhar, that particular problem is easily solved. Provided, checksums of no two strings should be equal Checksums in no way guarantee uniqueness across large data volumes. Anyone that uses them in that fashion or with that expectation is asking for problems in my opinion. As noted, checksum...

Does this have anything whatsoever to do with DataStage?

bff is some kind of "backup format file" and the other two something to do with security, apparently.

That's the biggest disconnect sometimes with the FTP stage - it is metadata driven and streams a record through it one at a time as if you were reading or writing to a file. It's not equivalent to what the ftp function does, which is just stream bytes / characters from one location to another and al...

The stage does not support wildcards. One solution might be to dynamically generate the DDMMYYYY part based on the current date, pass it in as a parameter and use the parameter in the stage.