DSXchange

key_column

Ring any bells?

I am not aware of any function call in the API. However, in DSVERSION.H (in DSINCLUDE) there is the declaration EQU DSFullVersionStr TO "7.5.1.35" that's fairly reliable. Lots of other version stuff in there too. The following you might also find interesting. It's from DSR_ESRPROPS.H (agai...

Look at the aborted job's "started" message in the log to determine with what parameter values it was started. Are these the same as for a manual run? Under what identity do DataStage jobs run? Do they have the same id (and therefore the same permissions) as for manual runs?

The T30FILE configuration parameter sets the number of slots ("rows") in a table in shared memory in which the current settings for each open dynamic (Type 30) hashed file resides. The table contains the following columns displayed by ANALYZE.SHM -d Slot # Slot number in table, beginning at 0 Inode ...

The metadata (table definition) that you imported from the CSV file will define how the Sequential File stage will automartically split each row into its correct columns. The metadata that you imported from the Oracle table will specify the columns that exist in the Oracle table. You map from the on...

As a subquery following the EXISTS, in user-defined SQL. But somewhere, somehow, you'll need to pass some value to include in the WHERE clause of the sub-query. It's this that you mark as Key in DataStage. In a reference lookup, "Key" refers to the search key, not necessarily to the primary key (unl...

You are out of synchronization. Delete all the hashed files. Delete all VOC entries that refer to them. Delete all operating system objects that participate in them. Then go again and all will be well.

PWD is an environment variable. It contains the pathname of your working directory. In most cases it can usefully be set to "." (current directory).

"Orchestrate" is the operating environment, in much the same way that "UNIX" or "PL/SQL" are operating environments. They have no real visibility.

Check that you really do have MAZDA MX-5 MX5 as a row in the lookup table (not MAZDA MX-3 MX5). Check also that there are no trailing spaces causing the lookup to fail.

For sufficiently large amounts of unsorted data the Aggregator stage can run out of memory.

What key are you using for the lookup? if its only 1234 - note that all of these have 1234 - then the first one found is returned. You need more specific information for this kind of lookup.

Keep going. What query follows EXISTS?

That's a good way to think of it. If the source records are at a particular level (say 01) then the subrecord fields will be at a lower level (say 02) on the output of the Make Subrecord stage.

Ray, These routines needs to execute in both job control and PX Transformer. If I write server routine we can not use those routines in PX transformer. I wrote PX routines which are working in PX Transformer and I want to use same routines in job control section of PX job. Thanks, Yoganand And I su...

And, as Arnd noted earlier, converting twice also yields wrong results. That's why the mapping has to be specified correctly everywhere in the processing chain.