DSXchange

UniVerse supports a WITHIN query that can do this kind of thing as well, but requires a bit of setting up.

Duplication of results can also result from improper partitioning. The Join stage requires inputs to be identically partitioned using a key-based partitioning algorithm. And sorted on at least these keys.

Only it's not always best. It's the one that will work in all circumstances.

Go back. The error is "TNS name can not be resolved". Work out why.

1. dsjob only imports executables.
2. No.

Put just mv in the Command field of the Execute Command activity.

Put the remainder of the mv command in the Parameters field of the Execute Command activity.

Cast to Integer is probably better for BIT, so that you get 1 or 0 as the result.

Fault types are documented in a late chapter (appendix?) in the UniVerse Administrators guide which you can download from the IBM U2 website. Don't have time to check right now, and it's one of the ones I have chosen not to memorize.

There's a lot less that can go wrong juggling one ball compared to juggling many! Robustness stems from an approach that uses multi-processing rather than multi-threading.

That "solution" relies upon the database vendor being able accurately to report the correct row in which the error occurs if host array processing is requested. Currently the technology does not permit this.

A bit of confusion there, grasshopper. STATUS() is a function, STATUS - without parentheses - is the statement.

Other than that, an entirely apposite response.

$DSHOME/bin/dsdlockd -p executed as superuser

How about a simple job that selects COL2 from B, and then uses user-defined SQL to DELETE FROM A WHERE COL1 = ?

If you standardize using a xxNAME Rule Set, names are identified as individual or organizational (I or O) in the Name Type (NTxxNAM) column. If you want something more graceful, then you might consider some Pattern Action Language to effect a comparison against the name classification table (xxNAME....

Normally the first candidate in this situation is the job monitor application (JobMonApp), which is a Java program that runs on the server. Its task is to collect those statistics - if it is not running (or APT_NO_JOBMON has been set) - then, no statistics.