DSXchange

Webdings?

You are correct (at least as far as I know); DSWaitForJob interrogates the RT_STATUSnnn table for the job. This table sometimes does not get updated - which is why killed jobs sometimes appear to retain a "Running" state forever. However, if the job status shows as "Finished", then one of the active...

Can't be done. Go with the parameter.

Should be do-able. Your custom stage will need to refer to the reference file/table, of course. And you will need to come up with a convention for naming the schema file and getting this into the job(s). Main problem is that, if you need to do any transformation, you must make reference to a specifi...

... and provided that row #1 is directed to output link #1; not prevented by the constraint expression.

Depending on the data type of the target column, the leading zeroes may well be stripped by the database server anyway.

The Repository is a database. You can only access it via queries or programmatically. Note, however, that the vendor deliberately does not publish full details of the Repository database structure, so that you're limited in what you can retrieve with queries. For some reason the presentation has bec...

As well as being defined in the Administrator, $LOGFILE_DIR must also be added to the job as a job parameter. Click the Add Environment Variable command button on the Parameters page to achieve this.

Try selecting View > Refresh.
Chances are that your first attempt deleted the categories successfully but the client did not auto-refresh.

The limiting factor on key size is the number of characters in the key, rather than the number of columns in the key. By default this limit is 768 characters. It can be tuned in uvconfig. There are substantial implications in increasing it, however, for example GROUP.SIZE 1 may no longer be appropri...

The limiting factor on key size is the number of characters in the key, rather than the number of columns in the key. By default this limit is 768 characters. It can be tuned in uvconfig. There are substantial implications in increasing it, however, for example GROUP.SIZE 1 may no longer be appropri...

No data are moved from the server to the client or vice versa. Metadata are moved, usually only sufficient to populate the current window - that is, a trivial amount. Some other things, such as creating/using templates and compiling job sequences (for the XML portion) also use the client but, again,...

3 lakh * 50 bytes = 1.5MB only. You definitely don't need 64-bit addressing.

You have version 7.5x2, which is parallel-capable. The main thing is that the design process is a very different mindset. In Informatica you're used to a bottom-up design strategy - start with the details and build the structure (maps and the like) on those. In DataStage it's top-down - start with t...

Take the time to construct and test a connector. Then you have a re-usable component that you'll never need to configure again - just add to jobs as required.