DSXchange

If the export includes executables, then it is not necessary to compile in the project into which the components were imported. Equally, it is not wrong to do so. Validating jobs is the preferred way to verify connectivity; parameter defaults may be changed in Director if desired without the need to...

Look in RT_BP2311/JOB.1396960201.DT.1465440079.TRANS1 and check the code either side of line number 107 to see what might have happened. In particular look for a reference to a subroutine whose name begins with "$". (You may have overlooked this earlier.)

The three dots are part of the syntax. The job name is preceded (in the DS_AUDIT key) by a class identifier. The three dots are the wildcard in RetrieVe query language pattern matching. Or use the SQL that I posted earlier.

Why do you believe asking the same question in a different thread will get a different answer?

Versions earlier than 5.2 had to write their own job control code. Nowadays we have job sequences which, when compiled, create job control code. Therefore the need to write your own should be almost non-existent; though you may encounter sites where there is some "from the old days" that needs to be...

U hasn't logged in for quite a few months. Don't hold your breath waiting for U to explain how to start any DS job from another.

No. but it's easy to do from a Routine activity.

Look on the Format tab. The delimiter you've specified is not the one actually used in the file. DataStage is still looking for the on you've specified. Alternatively you've hit a hard-coded limit of one million bytes that the import operator is allowed to scan without finding a delimiter. If you ne...

Start at this page for the full set. Heed Craig's advice.

Or you can use the Administrator client Command window. DataStage/SQL is one of the two query languages available. Or you can use the RetrieVe query language, as Ken suggested. To view the table definition of a hashed file the command is LIST.DICT (for which you will also need a VOC pointer to the h...

So cast as BigInt rather than Integer. BigInt is an eight-byte signed integer.

So cast as BigInt rather than Integer. BigInt is an eight-byte signed integer.

What it is you think you can't do? Is it a query builder, or the ability to view the data in the hashed file? Certainly you can do the latter with the data browser.

That most recent message is about not being able to find the error message text in the "resource" file. It's unrelated to the earlier problem, and probably solved by setting the indicated environment variable to the location of the resource file (probably DS_RESENU for US English).

The reason is that that would be a "blocking operation" - a passive stage can not open its output(s) until its input has closed. Blocking operations interfere with (prevent) pipeline parallelism and are therefore banned.