DSXchange

Anything that works is feasible.

It's not actually a bad design. But think about inserting some Sort stages ahead of each Aggregator stage - the second one can specify "don't sort (already sorted)" and thereby introduce some efficiency to the design.

So what?

BASIC functions do not work in the C++ environment of parallel jobs.

If you want to write your own C++ equivalent of DSGetStageInfo() as a parallel routine - and you prefer such an inefficient approach - then there is a C-callable DataStage API that offers a DSGetStageInfo() function.

Look for the log and bad files on the scratch disk for the fourth-named node in your configuration file.

WHY won't you do what I asked and post the result?

JOB_NAME is not a column in the DS_JOBS table.
Use NAME as the column name in the WHERE clause.
Remember to use a trailing semi-colon on all DataStage/SQL statements.

Which of the given solutions was your resolution?

There's nothing in the manuals to say that the Modify stage does not handle NLS-mapped characters. It handles ustring, so one must assume that it can handle NLS-mapped characters. The NLS maps ensure that all characters are mapped to Unicode (ustring), so it ought to work. What does your support pro...

You can set the user ID to run scheduled jobs in the Administrator client, on the Schedule tab (for Windows-based servers only). This overrides the default which, as you have discovered, is NTAUTHORITY\SYSTEM.

That's correct, Distributed files are also known as Type 27 (which is even more mysterious). There's no really useful documentation about Distributed files in the DataStage documentation; however the UniVerse User's Guide provides comprehensive coverage.

Welcome aboard. :D The easiest solution is to let the DB2 stage generate the SQL. You just provide the connectivity/authorization information, the table name and the column name(s), deliver the values into those columns within your job design, and whether you want to insert, update or some combinati...

I can only advise you to experiment with changing the Thai map at the stage level. Perhaps at the stage that is reading the data, perhaps in the stage that is writing the data. If you can not get the Modify stage to work in an NLS setting, you may need to switch to a Transformer stage, and use the N...

That is the one if you're on version 7.0. There are more recent Orchestrate manuals for version 7.5. I guess you could try substituting orch75 for orch70 in the pathname, but no guarantees. Hassle your support provider some more.

How did you propose to get it from DSGetStageInfo()?!! Is the source a Sequential File? If so you can use the Row Number Column property to yield the row number from the file - even if you are reading multiple files or using multiple readers per node. Presumably - because you've never said - the val...

I wrote:Add a reject link to the Lookup stage so that you can see exactly what values were sought.

What happened when you tried that? What value was in the date column that you used for a key, and subsequently was sent to the reject link?

1. Click the Code button. 2. Draw your "ASCII art" picture. 3. Click the Code button again, to close the Code tags. 4. Click Preview. 5. Edit your "ASCII art" so that it looks better, then click Preview. 6. Repeat step 5 until the "ASCII art" looks like you want it to. 7. Click Submit. -----> Aggrea...

Where do the "weird words" come out?

What NLS map is in force?

Try it without using Thai characters just for a test, to isolate the problem to the handling of the Thai characters.