DSXchange

The repository is a database schema and has several tables in which things are stored. To enable certain constrained queries to run faster, there are indexes maintained, for example on CATEGORY. Occasionally these can get out of date, due perhaps to contending updates. It is then that the indexes ne...

Ya hafta know that it's there first! Then you can ask the compiler its version.

That only works if aCC's directory is in your PATH.
Try

Check to see whether anyone has removed the DSParams file from your project directory on the server.

If they have, kill them.

No. If you promote the subrecord you won't get the subrecord column AND the contents of the subrecord - you can't have both.

And your Search option isn't working?

There is a search facility in the Director client. It is the tool on the toolbar with binoculars as its icon. In Director you can also disable the display of Categories all together, on the View menu. Director will take a relatively long time to refresh as it must then bring all job names in the pro...

There is a search facility in the Director client. It is the tool on the toolbar with binoculars as its icon. In Director you can also disable the display of Categories all together, on the View menu. Director will take a relatively long time to refresh as it must then bring all job names in the pro...

Insert a Nested Condition activity with a custom trigger to test the value of the relevant user variable, and to fire only if its value is greater than 0.

Search the forum for a routine that dumps a table definition. One of the available formats is a CREATE TABLE statement.

Use a Nested Condition activity (that's your IF test) immediately prior to the job activity. The custom trigger expression would be something like activity.$Counter = 2

Different records in RT_STATUSnnn have different structures. Only the first five are common to all record types. There are records for the job, for each active stage, and for each "resource".

Either is apposite. The DataStage job is probably the easier to maintain long term, particularly if the customer changes database from Oracle to something else.

Yes, you can use "ordinary" SQL syntax for an update. Auto-generated SQL will do the trick - you need to supply the key column values and the value(s) to be updated. Set the rule to "update existing rows only".