DSXchange

Perhaps you could post your question in the correct DataStage forum, then...

Don't use operating system commands. Instead, enable the pertinent environment variables to have the player processes log their memory and timing statistics, namely APT_PM_PLAYER_MEMORY and APT_PM_PLAYER_TIMING.

In QualityStage?

Looks like BEGIN_YEAR is not a column name in the table. Use your Administrator client command window to

"Not working" means unemployed.

Can't help with the second one.

DataStage and QualityStage are the same place in version 8, therefore the answer is DS_JOBS and DS_JOBOBJECTS. Files associated with provisioned rule sets are stored in directories on the server - from memory these are subdirectories in the project directory and have "quality" in their nam...

Web Console for Information Server, in the area where you manage users. However, wasadmin needs to exist as an operating system user on the machine where the WebSphere Application Server is installed.

OK. Well, the good news is that this won't affect your operations. The bad news is that it shouldn't be happening at all - could be a bug in VERIFY.SQL. Further investigation is required. As noted, these items should - correctly - have no entry in the SQL catalog. Typically the only UniVerse table a...

As I see it you have two choices - to create triggers in the database that eventually invoke dsjob to run the DataStage job, or to have a DataStage job that polls the table in question as part of a sequence, perhaps.

May I suggest a paper-based checklist for developers? That way you have an audit trail that you've completed all required steps. Another possibility is that Designer was closed without saving changes. There's no recovery from this. That's why I never use Tools > Options to disable prompting on delet...

A final Transformer stage to add the HTML tags (at least the <tr> and <td> tags) might be feasible - although it would be like writing HTML with Notepad!

Yes, but the header has been re-written and may no longer contain the reference to the SQL catalog.

Try then see whether the VERIFY.SQL report for that "table" is still awry.