DSXchange

That's a lot of Quatloos, back in the day I could get a thrall for a mere 2000Qt's . I think I'll not wager on this one...

"later" means after a while? How much memory does your workstation have?

Your database allows nVarChar(36) and that won't fit into your jobs nvarchar(6). Correct your column width in your job to match that of the data.

You are probably reading a .csv file, not an excel spreadsheet. could you post a sample line or three?

This happens when your PC runs out of memory. Close windows and/or the datastage application and restart your session.

Even though DS Server does not restrict you from misusing job column metadata it is always best to act as if it would and use column definitions that approximate the data; that way if you were to write to a database you can avoid error messages upon insert and update.

DataStage has no builtin PDF writing stage. But you could always call a conversion tool from an after-job routine or from a job sequence to perform this PDF creation.

You should always use realistic numbers, particularly for non-strings; but in Server you can put "Hello There" into a VarChar(3) field and it would still be stored correctly.

All I can say is "hair of the dog..."

Convert('. ','.','Hi. There World') will result in "Hi.ThereWorld".

Hashed files only have one internal datatype, namely a string. Length specifications are informational only, thus all 3 hashed files you mentioned will be identical.

CHAR fields will be padded with blanks in DS and written/read with blanks.

A report of *what* information? Basically, if it is a DataStage report you can always print it to a PDF document.

DataStage itself has no pdf output, but various tools exist to print to pdf files or to create pdf files. What contents do you want in the PDF?

When the records go down the reject link DataStage adds the SQL error number - what number do you get there, that might go far in tracking down the problem.