DSXchange

Are you on UNIX or Windows? The post states UNIX but the term ODBC DSNs is a Windows one. The dynamic DSN cannot be done in Windows, but with a bit of effort it might be possible in UNIX by manipulating the odbc.ini or other driver files - but I don't think it would be easy.

My initial thought is that for the error row you are not multiplying by 12 as you assume, but by some other number.
Make a test copy of your job and make the output field a dfloat and write to a peek and see what value is displayed for the error row in question.

Try this solution with 2 stage variables: svWorkString Trim(In.NameString) svNumberOfSpaces dcount(svWorkString) Out.FirstName = Field(svWorkString,' ',1) Out.LastName = Field(svWorkString,' ',svNumberOfSpaces) Out.MiddleNames = Field(svWorkstring,' ',2,svNumberOfSpaces-2) If there are no middle nam...

This looks very much like an issue in your join. When you monitor your job I would wager that you are getting all of your dataset records going to the join. Is the dataset source the "right" link into an inner join?

Dataset consist of 2 components, the file "abc.ds" that you reference in jobs which is a descriptor file, then the actual data files that reside in locations specified by the APT_CONFIG file. For this reason one cannot just zip up datasets the way you envision. The names and numbers of fil...

Welcome to DSXchange, padmalavanya.

Server jobs use the lookup stage rather than a join and thus do not have a join stage.

Go to the job where you write to the dataset and see what the partitioning algorithm and key was set to in the job, the dataset inherits/uses these settings.

The APT_TRANSPORT_BLOCK_SIZE does not affect disk use, it affects the block size of data transport between stages at runtime.
What is your partitioning algorithm and key for your data set?
Try setting it to "round robin" and then your 3 part files will have almost identical sizes.

No, this is in the filter part of source sequential file stage:

Dear peep, 1. This is a forum, not an SMS telephone exchange. Please use real words and vowels since many here, including myself and yourself, are not native English speakers and communication is difficult enough with the technical nature of DataStage. 2. While most of the subject matter is freely v...

The file sizes are a result of the data that is put in them. This means that your file 0 has no records, which means that your selected partitioning algorithm isn't distributing the records evenly and you should rethink the algortihm used or the key used.

I've had the same problem before in that some mainframe FTP removes trailing spaces. In my case I used a filter in the source fixed width file stage, i.e. sed 's/[ \t]*$//' | tr -d '\x1A' | awk '{printf "%-1494s\n",$0}' - (remove 0x1A characters and then pads lines to 1494 length) This mig...

Does the SQL-Server DDL specify that the key column has "IDENTITY" set to on? If so, you may not specify that key column on writing; if not, then you need to fill that column with a value at runtime.

Before attempting a solution, you need to define exactly what you mean by "Chinese Characters". The different chinese character sets contain not only ideographs but also the classic LATIN-1 and extended ASCII characters. So first you need to know exactly which characters you want to keep. ...

Please go to your client PC where you have the DataStage clients installed, do a search for a program called "dsjob.exe" and execute the command "dsjob -help" in that directory. Alternatively, you could look at the documentation. Once you have done that and experimented with simp...