DSXchange

It can be shown that UniVerse is a relational database. The fact that it can store nested relations in the same table is a bonus. You don't have to - you can design UniVerse databases to be totally first, second and third normal form designs. It's just that non first normal form yields more compact ...

To all of that I must add that DataStage uses "prepared SQL" so the original assertion, that it will do roundtrips to the database issuing the same sql over and over for each row coming from the primary link is actually false. The SQL Statement is sent when the stage starts, and the databa...

No.

That's why my earllier post was "can you try...".

Do you have Enterprise Edition? There are some useful change detection stages available in parallel jobs which, in conjunction with the Funnel stage, address all your questions. Change detection in server jobs will require either using an operating system utility such as diff or using a Merge stage ...

Export the project first. Drop project, create project and do a partial import to bring back anything you need.

RT_CONFIG is not an error; it's the base name of a set of repository tables. My guess is that you do not have full permission to the RT_CONFIGnnn table for the job that you are failing to compile. It would have been useful had you posted the exact error message. I am totally confident that RCP is no...

You can, of course, get the number of sessions from the Web Console for Information Server. This suggests that the information is stored somewhere in the XMETA database. Good luck with your detective work!

Try the dslictool command. This reports the number of CPUs for which the server is licensed and the number of client licence seats (a) in use and (b) available. The total of these should be the total of your client licence.

Oconv(@DATE, "DW") is the numeric day of week. Oconv(@DATE, "DWA") is the name of the day of the week. Oconv(@DATE, "DWB") is the abbreviated name. You can do more with formatting specifications in square brackets as part of the second argument. But this requires BASIC ...

Run-time parameter values are not part of the design time information (though parameter default values are). What precisely are you looking for?

IT people tend to think in multiples of 2, 8, 16, 512 or 1024.

Maybe the third fatal did not occur until after the 128th row (first array) had been processed?

It appears that AutoMeter is an invocation ID, and I am guessing that the message derives from DSPrepareJob() - you can't reset a job that has never been run. It may be innocuous.

Carriage return line feed?

You probably did not need to convert those explicitly at all.

Have you managed to Search DSXchange for this particular message?