DSXchange

In addition to what Vincent said, make sure that you get your stewards lined up early in the process. It's far easier to begin with good governance practices than to try to retro-fit them.

I'm going to guess that the single quote character isn't well handled when the drill-down query is constructed. Maybe it's something like That is, that you've uncovered a bug.

What does your offical support provider say?

If you want to capture the values file name that was used in the job run after the job has been run (or even while it is running), simply review the "run starting" event in the job log, either using the Director client, the dsjob command, or the DataStage API.

Capture it from where? You're trying to set up the job run request, so clearly you can't expect to capture it from the job itself. The point of values files is that you have different sets of default values for the parameters in the Parameter Set for different circumstances (for example for each env...

A segmentation violation fault indicates an attempt to access a memory address that the process does not own. The two examples I cited are common causes of segmentation violations in database stage types. I note that you did not address my second scenario in your investigation. Trying to insert (for...

Alas there's no user-facing mechanism for getting the rating figure.

But that's far less important than updating the home page and the list of version numbers.

It's perfectly clear. What we've all been trying to tell you is there is no reliable way to split the file AFTER it has been compressed. You must split either before or during compression. If you split during compression you run the risk that an XML element may be split across file boundaries. If th...

Are you perhaps sending NULL into a column that is defined to be NOT NULL ? Or sending too many characters into a VARCHAR2 column?

What is a good average number of points per post on DSXchange?

I wonder how many enthusiastic individuals they catch with "prior to doing the above, do this" not appearing until after the pertinent instructions!

IBM wrote:Note: prior to modification backup the original file and rename it.

Welcome aboard.

I'd say that, if your system is running satisfactorily as it is, and you seem to have sufficient headroom for all planned expansion, then leave well alone.

I'm assuming here that all non-DS work is also submitted via whatever grid management software you use.

Use seven stage variables. It's easier to manage.

For a more arbitrary solution, you may be able to devise a solution that uses Transformer stage looping.

But I'd still advocate doing this task in SQL, not in DataStage.

There is a "catalog" (a table called UV_SCHEMAS) on the DataStage instance. That alone should suffice to allow the ODBC driver to connect. On a Windows server you may need to configure domain versus local user but, since you're on UNIX, this step is not needed. So it's time to be specific ...

While it's possible to do it in DataStage (using stage variables to "remember"), I'd argue that this kind of report is in the ambit of business intelligence tools (or simple database queries).

Do you have the ODBC driver for UniVerse?