DSXchange

I don't know why the code isn't visible to you, your user type is marked as "premium".

Here is quickie BASIC routine which does what you want: ArgCopy = Arg1 WordCount = DCOUNT(ArgCopy," ") GroupCounter = 1 Ans = "" TempString = FIELD(ArgCopy," ",1) FOR i = 2 TO WordCount Word = FIELD(ArgCopy," ",i) IF (LEN(TempString)+Len(Word) > 15) THEN Ans :...

It isn't so trivial, as you need to parse by words. This logic is not terribly difficult to solve in a small BASIC routine and called from either a server job directly or via a BASIC Transform stage in a parallel job. Preferable is a server job.

This looks like a perfect example of where DataStage 8.7 with loops inside transform stages can be of some use. What version are you running?

The thread isn't closed, just post your questions to it until sich time as you can mark it as resolved. Perhaps later this after Craig will wander by and he can delete this thread.

As long as you keep the password in encrypted fields so that they are not easily visible then you've done as much as possible. I like to keep such passwords as encrypted project-level environment variables.

How many characters have you defined in the string and how many are in the string causing the error message?

Then you should post on that original thread instead of opening a new one.

The module "ccora11g.dll" must be present and in the path on the DataStage server machine, not the client.
On my 8.7 version the dll is in the directory "D:\Program Files\IBM\InformationServer\Server\DSComponents\bin" on the server.

You posted the exact same question on this thread yesterday. Why open another thread?

Which image had a dataset with an input and output? My sample just has a copy stage to convert the reject dataset from the database write to a reference link used by the dummy lookup.

That is quite strange behaviour indeed. If you write to your table then capture the display the value to a file for a known string, i.e. "ABC" then do an od -x on just the first character shown, what is the value? We need to know the expected value of the first character "A" and ...

I suggested dropping a nonexistant column in the OP's modify stage as a route to solving the problem. As you noted, the warning message would need to be deprecated. But with that approach, the OP could have added a field that would get dropped in the modify, or done a "{col}={col}" where &...

I did explain, but perhaps that part of the message was in the premium content portion. When using NLS there is a difference between string size when the table is defined as character rather than byte sized.

It would seem that your job definition for one of the columns isn't big enough to fit the actual data. Compare your metadata in the actual table with what you have in the job. When I see "nls" in the error message I wonder if you might have declared the table with "bytes" rather ...