DSXchange

About the only differentiation that I believe is relevant is the one between initial load and incremental load (meaning any subsequent load to a non-empty structure). An initial load typically processes a far larger volume of data than a subsequent load, and is unlikely to require that anything be u...

Did you create this job, or someone else? If the latter, check the permissions on RT_BP651 in the project directory.

Nowhere, really. The vendor chooses not to publish details. When a project is created several tables (implemented as hashed files) having names beginning with "DS_" are created to store the design-time components, for example DS_ROUTINES, DS_CONTAINERS. When a job is created several more tables (imp...

Yes, there are several ways. The most commonly-posted involve querying the DS_JOBOBJECTS table constraining on OLETYPE. Search the forum for details. Chuck Smith has a utility for identifying hashed files that could be adapted.

Nothing to stop you using the user status area in a parallel job. Though you will need to create a parallel routine that invokes DSSetUserStatus() - the one from the C-callable API.

HashValue = HashingAlgorithm(KeyValue)
Partition = Mod(HashValue, PartitionCount)

The hashing algorithm generates a reproducible numeric value for any given argument value. The actual algorithm is IBM's intellectual property.

Start by disabling operator combination so you can determine precisely which operator is generating the error.

Clearnly "none" is not a legal module name.
Unset the environment variable. To do this, set it up as a job parameter and make the job parameter's default value the special symbol $UNSET

What precisely do you want to accomplish? The parallel Sequential File stage can read multiple files, whether using multiple File properties or using a file pattern (wildcard). But then what?

Be more precise about where the deadlock occurs. For example, is it in the sync table or in the target table itself? What level of locking is being requested? (If multiple nodes request table-level locking you will definitely get a deadlock.)

The Lookup stage allows for conditional lookup. Your condition would be that a value "exists" (whatever that means in context). Only if the condition is true is the lookup attempted. You can capture those rows for which the condition is not met onto a reject output link from the Lookup stage. You ca...

Lookup Left outer join if failed lookup rule is Continue Inner join if failed lookup rule is Drop or Reject Merge Left outer join if mismatched master rule is set to Keep Inner join if mismatched master rule is not set to Keep However, this is only true if the master input is de-duplicated, since up...

What's supposed to be reading the other end of the pipe? Is it?

Even so, the lock will still be held, and may adversely affect re-indexing.

Your first task is to release the lock held by the defunct process.

No.