DSXchange

They are internal executables used when DataStage/SQL DDL statements (such as CREATE SCHEMA, CREATE TABLE, etc.) are used. They are not for you to use; their syntax is not documented anywhere,

More efficient is (I assume this expression is in a job sequence; Oconv() is not available in parallel jobs but is available in job sequences.

Change your needs. Import it using the Manager or Designer client.

Some pressure must be applied to IBM to run the classes - especially the advanced class - so we can learn what the expected answers are (rather than the answers we have learned through experience). The certification and advanced class were developed together. I've been on a waitlist for one class fo...

We kill that process(7623) through root. Aarrggh! Did you check to see whether pid 7362 had any child processes before you killed it? Killing a parent can turn a nohup child into a zombie, and they're almost impossible to get rid of without re-booting UNIX. And killing a process does not, at least ...

I disagree. Given that there's a huge mindset change, having some guidance (maybe a transition class, maybe something else) is far more value than trying to learn out of what are, in reality, just reference manuals for those who have a fundamental understanding of what they're doing.

It will return the original string. If 0 is used as the the argument in Substrings(), it is replaced with 1. It's also documented thus in the DataStage BASIC manual.

The original error also mentioned that a file had been created in the &PH& directory in your project (on the server). Is there any useful diagnostic information in that file?

Nothing, not even Chuck's utility, can save you if you use job parameters for table names. You must - necessarily - learn only that "some table was used in this job".

Scroll right in the Columns grid. You will find a setting called something like "contains terminators" that may help.

It's usually a UNIX kernel parameter named something like NPROC. But the name varies on different UNIXes.

That code basically looks OK. Error messages usually appear ahead of the code. Are you SURE you haven't left anything out?

Welcome aboard :D
Failure to connect via OLEDB is almost always a connection string that's deficient in some way. What error codes/messages are generated?

In job 1 and job 2 checking "allow write cache" will help. In jobs 3, 4 and 5 enabling pre-load to memory will help. Don't worry about competition for reading. If you do, then investigate the use of public link caching or even shared caching (read dsdskche.pdf). Thus, as far as the hashed file is co...

There are many possible solutions depending on your definition of "corrected". What characters do you want to preserve, and what characters do you want to discard?