DSXchange

In a job create a single Varchar column called NAME. Mark it as key. Use a UniVerse or Hashed File stage to read from DS_JOBS. Constrain so that you only get names beginning with other than "\" or "/" - these are control records, recording the existence of categories and the next available job number.

The main bottleneck will be how fast the DB2 direct write can handle the rows. You can automatically effect parallel loading into partitioned tables. 2000 rows/sec ought not to be difficult at all.

Templates are saved on the client machine, in a folder called Templates. For example C:\Program Files\Ascential\DataStage\Templates.
I suspect you lack write permission to this folder. Check.

Welcome aboard.

This particular forum exists so you can heap praise upon the cogent answers you receive from it.

You need to post your question in the forum specifically for parallel jobs.

Once there I'm sure it will be answered.

Plan how you would do it in SQL. That will suggest the number of Join stages that you will require. Join stages can be cascaded.

A lock on RT_CONFIGnnn usually indicates that someone has a Monitor open on job number nnn. This will properly prevent the job from being recompiled, which would overwrite the RT_CONFIGnnn table from which the Monitor is obtaining some of its information.

No, because it's just inaccurate. It's also inaccurate with some Decimal data types. Prefer the Orchestrate orchdbutil utility. This advice is even give in IBM training classes.

However these functions are not exposed in C++ and so are not available in parallel routines or Build stages.

Welcome aboard. :D The underlying architecture is radically different in version 8.0 and chances are that more processes, possibly on separate machines, will be involved. There is the repository database (Information Server), there is a WebSphere Application Server exposing services such as the meta...

If it's a text file, simply mark the column "contains line terminators" (scroll right in the Columns grid to find this setting).

Check the IBM web site. At the date of this post, no version of DataStage (client OR server) is supported on any Vista operating system, irrespective of the fact that it may work. Monitor the IBM web site, or have your vendor advise when one becomes available. Don't hold your breath - the first patc...

The generated SQL in an ODBC stage will be fully compliant with the grammar specified in the ODBC 3.0 standard. User-defined SQL can be anything legal for the database, as it is passed through unchanged by the driver. However, the parameter markers must correctly bind to the columns in the Columns g...

It appears that DCount() can not be used in this syntax.

Did you mean "hashed" file?