DSXchange

No-one can help you while you still have operator combination in effect.

The answer is no. The maximum permitted value of MAXKEYSIZE (my error earlier, it's not MAXKEYLENGTH) is nowhere near 20000. From the manual: Specifies the maximum number of characters for a primary key. It must be any multiple of 64 between 256 and 2048. The full record ID is stored in the record l...

Premium membership is not expensive; it's less than 30c (Rs12) per day. Revenue from premium memberships is totally devoted to helping to defray the hosting and bandwidth costs incurred by DSXchange. And you get to be able to read the entire contents of premium posters' contributions, among other b...

But, because there is a space ahead of your AM/PM designator, you need a variation, as I posted in my original answer, which is a complete solution. Do purchase premium membership. Revenue from premium membership is totally devoted to helping to defray the hosting and bandwidth costs incurred by DSX...

Right click on the output link and choose "Change to Reject" from the pop-up menu.

The main difference is that they are different tools that serve different purposes. Visual Source Safe is a source code control system; you have probably already noticed that DataStage uses a graphical paradigm, so does not have any source code per se (not counting routines and transforms). Version ...

You need to look in the record schema - either in the generated OSH or in the score - to see the C-style data types reported. Clearly string[n] corresponds to the SQL data type Char(n) while string[max=n] corresponds to the SQL data type VarChar(n). When these are ustring it means that NLS is enable...

Well, record 0 is the first line. Would you like to check the actual file?

You don't. Not without accessing the log itself (which is a database table, so that might mean SQL or other commands that can read individual entries) and reformatting the heck out of what you get back.

Yes, but... Do you have the skills to restore the hashed file to a separate location, create a VOC pointer to it there, and use SQL to inspect it?

Overwriting a hashed file with one of a different structure on backup media is a Bad Idea, and can lead to corruption.

Try checking your "first line is column headings" setting.

Your assumption is invalid. The default, as installed, has two nodes.

Integers do not have leading zeroes. Integers are stored in a binary format. If you want leading zeroes then your target field needs to be a string. In that case an appropriate expression to use is something like

Change the format to one acceptable to SQL Server, particularly CCYY-MM-DD HH:MM:SS or CCYY-MM-DD HH:MM:SS.sss Split the input into date and time. Use Iconv() and Oconv() functions to reorganize both, then concatenate with a space between. Oconv(Iconv(Field(InLink.TheString," "...

The correct terminology is hashed file, not "hash" file.

Are there any warnings in your job log?

What is the MAXKEYLENGTH setting for hashed files at your installation? (The default is 768, which would definitely rule out 20000-character keys.)