DSXchange

Please provide exact error message. The project is recorded both in system tables on the Engine tier (DataStage) and the Repository tier (XMETA).

It is well described in the manuals, and in the on-line help. I provided a reasonably detailed answer to a similar question (albeit for version on DSXchange as recently as this week. Did you Search?

You have to do it without the expression editor open. To put it another way, right click on the red expression, not on the opened expression.

There are no spaces either side of the "=" when setting environment variable values. You also need to export the variable if you are using a Bourne shell or similar. Find examples in your dsenv script.

A good example exists in the DS_AUDIT hashed file. There are three columns that record the date/time modified, by whom modified and reason for modificiation. In the DS_AUDIT table there is one record for each repository object. Any one repository object may have been modified 0, 1 or more times. The...

For example the precursor job could simply write the count into its user status area, which the triggers from the precursor job's Job activity can interrogate directly to determine what happens next.

Re-booting the server clears shared memory, including the lock tables, the T30FILE structure, and any public shared caches for hashed files.

No documented information is available on this quesion. I used to believe that your second option was the way it works, but have no way to be certain.

Lookup stage is for small reference data sets where exact or range lookup capability is required. Duplicates of the lookup key are permitted in the stream input - each will be looked up separately. Lookup stage is also indicated if you need to access huge data sets directly from the database tables ...

It's definitely that, and it's the field called SMPL_RQSTD_IND that is your problem. Do you have a Modify stage upstream or downstream of this Data Set stage?

This really is a vague message. The issue may be in the local project repository, in which case you can verify whether entries for the job exist in DS_JOBS and in DS_JOBOBJECTS. Once you have the job number, you can also verify the existence or otherwise of all the RT_*nnn tables for that particular...

This behaviour usually occurs because the job is still receiving and logging warnings from, for example, a connected database server.

Did anyone change APT_CONDUCTOR_HOSTNAME environment variable?

It means what it says. The configuration file you are using today does not have any conductor nodes mentioned in the export node pool. This may be because you have specified APT_CONDUCTOR_HOSTNAME to be somewhere not mentioned in the configuration file. To be of much more help we would need to see t...

The Filter stage is in all 8.x versions.

Current advice from IBM is that the Transformer stage is to be preferred to the Filter or Switch stages, because the Transformer stage (nowadays) is compiled, while the other two are interpreted.