DSXchange

No, because that's not how Round Robin partitioning works. In any case, what happens if the failure occurs half way through a Data Set?

Range lookups also compile to transform operators.

I'd suggest that you need to get a compiler licence.

Welcome aboard.

The short answer is "No".

You have to design in a mechanism to "remember" which rows were inserted if you don't want to query the target.

True. But the solution is still straightforward using DataStage BASIC (for example in the BASIC Transformer stage). Convert the words into a dynamic array, take the leftmost character of each element, then delete the dynamic array delimiters. Convert(@FM, "", Substrings(Convert(" &quo...

Does your shared library search list include all the parent directories of the shared libraries mentioned? Are the permissions on these libraries set correctly?

The easiest way to find out is to look at the score for that job.

Then, maybe, you can report your findings back to us.

CAPITALS is a Transform that encapsulates Oconv(%Arg1%, "MCT")

Use BASIC Transformer stage and Oconv(InLink.TheString, "MCT")

Using three Lookup stages is the correct approach, not least because it works.

When you use a range lookup the Lookup stage compiles to a transform operator and, as you noticed, gets finicky about what's able to be used (re-used) as a lookup key.

Or you could simply change the NLS locale, particularly the TIME category.

You need to test (for example with dnsping or similar) that the name can be resolved using DNS. If it can't a temporary fix is to put the actual hostname and IP address into /etc/hosts file.

mikva2012 wrote:what will be the impact if will run the cleanup_abandoned_locks.sh script from Unix command line.

Abandoned locks will be cleaned up. However, a lock held by another DataStage client is not an abandoned lock.

I do this a lot when updating values files of Parameter Sets. One approach is to overwrite the file entirely, using a Sequential File stage. That's the way I normally do it, particularly when the number of parameters in the Parameter Set is small. The other is to use a Hashed File stage in a server ...

@ABORT.CODE is only set by server/sequence jobs. However, this is the final message. You need to show us earlier errors from the job log, which is where the cause is reported. These errors might even be reported in the log of a job called from a Job activity in your sequence.

If you have IS Administrator role, log in to the Web Console for Information Server, open the list of active sessions and disconnect the session that owns the log (the session ID is in the "locked" message). The lock will be cleared immediately.