DSXchange

Create yet another group (pstest?) and chgrp everything in the test project such that they are associated with this group. Only add to the new group those users whom you wish to be able to see DataStage objects in the test project. Ideally there should be no need for anyone to be able to see them. I...

DataStage can "recognize" any date format, because it does not have any data types - everything is a character string.

It's the database servers and/or their client software (such as ODBC drivers) that grumble about date formats - not DataStage!

You may "need to know" (why?), but Ascential elects not to publish this information and reserves the right to change it at any time. In quick summary it's not file-based, it's database-based. It's definitely NOT DB2; Ascential explicitly markets itself as "database agnostic". To that end, currently,...

These statistics relate to active stages. More information is available through DSGetStageInfo in version 7 than in (your) version 5, for example DSJ.STAGESTARTTIMESTAMP, DSJ.STAGEENDTIMESTAMP and DSJ.STAGECPU. You don't really want to know about how to extract them from the Repository tables, since...

When creating a new post, the poster is prompted for "OS" to choose either UNIX or Windows.

Lately it has become clear that some have understood this to mean their client machine.

Perhaps a better prompt (and display label in the forum itself) would be "Server OS:".

One word. Micro$oft.

It would be so nice to be able to cancel the "query from hell"!

You specified that your server is on Windows, so I gave a Windows answer.

On UNIX, the odbc.ini file is accessed most easily through .odbc.ini in the $DSHOME directory. This may be a true file or may be a symbolic link. Doesn't matter, you can edit it in either case.

It's a warning rather than an error, and it's generated by the ODBC driver rather than by the database server. It means that, somewhere, a decimal value has been truncated. The apparent culprit is Dollar_Amount. The CURRENCY data type in SQL Server expects four decimal places; you have only supplied...

Control Panel > Administrative Tools > Data Sources (ODBC)

Make sure you specify System or File data sources, not User data source.

Is your load rule "insert or update" and does the target table have a primary key defined? Chances are that the first 9 rows are inserted, then the next 9 rows "update" (by overwriting). After all, you only have nine key values.

Even the routine requires knowledge about the internal architecture of DataStage that is not in the public domain.

The safer answer is a plain NO.

There are some job compilation utilities available, including the multi-job compile that now ships with DataStage.

Do you have "first line is column names" set and, if so, are the column names too large for your defined column widths?

No.

Run the job from Quality Stage Designer. You will get the same overflow blocks. It's a deficiency in your blocking or matching strategy.

No.

Parallel means parallel. They run simultaneously.

You can do what you want by creating multi-instance server jobs, and controlling those through a job sequence.