DSXchange

That seems reasonable. How did you correct it? Presumably you set the NLS_LANGUAGE for your particular connection to "ENGLISH".

Indirectly yes. If you don't specify sorting, then compiling the job will insert sort operators on each input link to the Join stage.

Data should be partitioned on at least the first join key.

It would work with either approach!

This may or may not work. Try being in the engine directory when you execute the command. cd `cat /.dshome` bin/dsadmin -domain dstagesbox:9443 -user dsadm -password ********-server engine -createproject test_project -location /data/projects/test_project/project Make sure that the location directory...

Welcome aboard. You need to get version 11.3.1 or the one after that. I'm not sure why it was omitted from 11.3.0 but it was. Feedback to IBM indicated that access to the Development Catalog (not least export and import) was required. To answer your next question, I do not believe that this will be ...

Ereplace() is not a Boolean function. It returns the new string. Therefore you need nested Ereplace() functions or, perhaps, cascaded stage variables. Ereplace(Ereplace(Ereplace(InLink.NIVA, "joejut", "F", -1, 0), "kdikkd", "F", -1, 0), "fsdidkg", &q...

Let's see - you posted this at 2:09am my time, and bumped it at 4:44am. A little patience would be no bad thing - occasionally I do sleep. Particularly after having been up at 2:30am the previous day to attend the excellent DSXchange "lunchtime" webinar! Your answer can be answered definit...

I think that the = 1 or = 2 tests may have succeeded, but the value returned by them was never transferred to the exit status of the enclosing script itself, hence the advice I tendered.

As noted, you are on a very old version. Substantial changes were made to the way QualityStage is implemented in version 8.0 and subsequently. That said, if you can preserve the scripts, you may be able to run them on another QualityStage engine, provided that any references to the local host machin...

The SQL Server implementation was all on Windows. After all, this is the only platform on which SQL Server runs.

I have done many installations over the years, on most of the popular operating systems.

Your script sets the variable OUT, but does not reflect this when exiting. All you need is to add exit $OUT at the end of your script.

If that doesn't work, try using the shell variable $? instead.

My bad - that was an alternative to try if the updates are not actually working.

So, you can probably effect some setting in the ODBC driver to affect the level of warnings that are generated, or you can use a message handler in DataStage to demote the warnings to informational messages.

Welcome aboard.

I've worked successfully with all three.

If you don't use DB2 there are some additional setup/installation steps, scripts to be run in the database to set up the metadata repository and other databases, but they are conventional and correct scripts that work out of the box.

Theoretically, Information Analyzer works just like any other Oracle client - you have to have the appropriate roles and, if you do, then you can effect queries against the tables. It's that simple. Or should be.

Try searching here for techniques for generating reports from the command line. You're using such an old version (one that is no longer supported) that I'm struggling to remember what's in it.