DSXchange

The very point I made at the end of my first post in this thread.

Hang on a minute. The DSU. prefix indicates that it's a Routine - you should be able to see it in your Repository. However the message suggests that it's not there. Can you see it in another project? If so you can export it from there (if read-only object export is enabled) and import it into the pr...

There is not.

There is a Red Book called QualityStage Methodologies, Standardization and Matching

In version 7 the only possible normal lookup you can do with a Lookup stage is an equality lookup (an exact match is required). You might contemplate using a sparse lookup that includes a LIKE condition in user-defined SQL. But it won't be fast.

The limit is set in the uvconfig file parameter T30FILE. This is the maximum number of dynamic hashed files that can be open at the same time. It is a system-wide limit.

DataStage ships with an ODBC driver for SQL Server. Use that.

What you propose won't work. The project directory contains objects that are part of a database instance, and there need to be system table entries that describe them. The right way is export/import. This does not, of course, synchronize hashed files. You can use format.conv to export/import these, ...

That the keys aren't what you believe them to be is the only explanation.

Perhaps they have trailing space characters. Can you see these keys with View Data?

What partitioning do you already have? Is the DB2 table partitioned?

Try using ODBC standard grammar (not Oracle specific) to specify the joins. SELECT DISTINCT A.SAMPLE_DTTM SAMPLE_DTTM,A.DTTM_SEQ_ID DTTM_SEQ_ID,A.HOUR HOUR,A.TIME_FRAME TIME_FRAME, B.LOAD_DATE LOAD_DATE,B.SAMPLE_DTTM SAMPLE_DTTM2 FROM TSTKPI.RMS_SRCDATA B LEFT OUTER JOIN TSTKPI.TIME_PERIOD A ON B.SA...

I second Mike's "Nope". At best you'd be guessing, unless you have some other kind of document that displays the record layout. But do it properly; insist upon correct technical documentation (that is, a COBOL copybook). That it takes time is not your fault - they should have provided it up front. D...

... and I did specify how you can get a server Transformer stage into a parallel job as well as talking about the BASIC Transformer stage.

That's the second field, returned as a nested function in the Left() function in my solution. Premium membership is not expensive, at less than 30c per day, and helps to fund the hosting and bandwidth charges incurred by DSXchange. Among other benefits premium membership allows you to read the entir...

Probably. Do you use the same operating system user ID and password as the one that the DataStage process uses? Maybe your environment variable setting (from .profile) is different to DataStage's (from dsenv).

Since I pointed out the difference between BASIC Transformer and server Transformer in my post, how can you claim that I said they're the same?!!

Premium membership is inexpensive, at less than 30c (Rs12) per day, and helps to fund the hosting and bandwidth costs incurred by DSXchange.com.