DSXchange

You probably need a Split Vector stage. Check out the stages in the Restructure folder.

Investigate your logic - see if you can eliminate any of the sorts. As Arnd noted, using a Sort stage to avoid re-sorting is often useful.

You don't need Trim() on Char columns - they would simply be padded immediately afterwards. All you need to extract the 30 characters from source into target columns is substring. I believe this will even handle 0x00 but, if it doesn't, a simple If..Then..Else for that column would probably be able ...

The error arises from the Iconv() function. Whatever the format of your date is, it is not understood by "D" as a conversion, which expects the date format of your locale (had you provided your location I could probably be more specific about that). Try Iconv(FM_FLEETS_HASH_FILE.START_DT,&...

Search out the parallel version of Ereplace() that was posted on DSXchange. Use this instead of Convert() which, as Arnd noted, only operates on one character.

It may be that your last line in the file lacks a record delimiter character.

That's why EOF was unexpectedly encountered.

No, with one exception.

Most of the QualityStage stages are for parallel jobs only.

Server jobs invoke QualityStage in a different way, through the QualityStage Legacy stage. This requires qsrtmngr to be running and can only invoke version 7 QualityStage jobs.

Moderator: please move to Enterprise Edition (parallel) forum

There is nothing in the original question to warrant its being posted in the SOA forum.

Find out what error code -911 is in DB2.

At least one of the lines generated by your external source program has contained an insufficient number of commas (record delimiters). You have specified comma as the record delimiter character.

Welcome aboard. The Transformer does look the same, initially. One obvious difference is that you won't be able to connect a second (reference) input to a parallel Transformer stage. Just as with the server Transformer stage, you don't get to see the tabs until you open the stage properties. Either ...

Do a regular lookup against lookup_codes.txt. Outputs from the Lookup stage contain: (0) the found country code (1) the source lookup code, which is passed through a Column Generator stage to replace it with "XX" These two outputs then run into a Funnel stage to return them to a single str...

Reading from a table you've just created? Why not just use a Row Generator stage in a job, or the same SELECT with which you would have populated the table in your Stored Procedure? That is, is creating the table really necessary? I suspect not.

It is not possible in a single parallel job. You would need two jobs.

The host name is not valid, or the host is not responding.

Resolve this problem first.