DSXchange

That is usually true, which is why the method I noted is not supported (yet will probably work).

What character sets do those numbers refer to?

While I am not sure what issue you are having, did you mean 'partitioning' instead of 'portioning' in the error message?

Check from UNIX to see if the job still has processes running, try 'ps -ef | grep {jobname}'. If not, then the job has aborted but the status hasn't been updated. The numbers displayed in the job monitor are not necessarily correct while the job is running, so the 0 records in links aren't always co...

Chances are pretty good that this code will work at V7. Do an export at V7 into .dsx format and check the version number in the header (use your favorite editor), then edit your V8 export and change the version to that of the V7 and import it at v7. If you don't get warnings or errors during the imp...

I don't see anything patently wrong in the SQL. Is there a chance that the quote_policy_link table might have uncommitted transactions at runtime? If this happens again, the quickest way to debug the issue would be to look at the 2 results and see if you can find some rule in the delta between the t...

Could you please cut-and-paste your if-then-else statement to this thread?

What method are you using in your enterprise stage, 'load' or 'upsert', that might make a bit of a difference. On the face of it, if the sequential file output is correct, then I don't see a source for the error; particularly as UTF-8 is a superset of MS1252 but the German umlaut characters are enco...

Choose your favorite UTF8 table from the internet and tell me what characters code points 0x81 and 0x8B are mapped to.

For one test run, replace your SQL in the DataStage job with hardcoded values for YIL and AY - are the results still incorrect? Again, in the monitor, check to see the row counts coming out of the DB2 stage and out of the transform stage - are they the same?

These are database errors, 42000 and 8146, you could look them up in Google or in your database documentation.

There is no reason to post duplicate threads

I'm in the same boat as Craig. Yes, have written it, but no, cannot share. This is because the code was written at a client site while the client was paying for my time; thus the code doesn't belong to me any more. While not complicated, it is a bit of work to get functioning correctly The Wiki arti...

krishna81 - I think you missed my post.

ArndW wrote:Stage -> Record Options -> Record Delimiter.

Follow Ray's suggestion, that is what is stopping the Fork() call in dsjob from successfully running.