DSXchange

Maybe. Where are your other classes (jar files) located?

DELETE is good but it, too, is transactional. Pour another beer down your DBA's throat.

Otherwise use stage variables in a Transformer stage to "remember" the value from the previous row, a technique that has been explained more than once on DSXchange.

That's all that's defined for the RT_... tables.

Vincent has an earlier blog about what's new in 9.1, or you can get all of that information in detail from the Information Center - the 9.1 pages have been up there for some time.

If you capture the reject in a reject link the reject link can also be populated with the error code and error text.

Why not perform an equi-join on the ID values with a Join stage and the comparison in a Transformer stage (using the Index() function) downstream of that?

For partial documentation, in a dssh environment: For discoveries, rummage around the results of a search here for DS_JOBOBJECTS.

That "solution" will still not share jobs and other engine-specific objects.

Information Server does have built-in HA capability in the services and repository tiers, but there's no way to get running jobs or connected client sessions to fail over.

If the number of fields is unknown and arbitrary, the only generic solution is to read each line as a single VarChar, parse based on a known delimiter character (could be a job parameter) and produce the output in that fashion. The output will also need to be a single VarChar in order for there to b...

Alas the structures of these tables are only partially documented. A few of us have hacked some of the structure, but definitely not completely. Do you have a colleague with UniVerse (or, at a pinch, UniData) experience? They will stand a better chance of hacking the structures. There's a lot of UV ...

When you run the installer, does it go into "add components" rather than "new installation"?

A full malware scan revealed "no issues".
A full anti-virus scan revealed "no issues".
Weird.

You need to identify (by OLETYPE) the Shared Container (view) records in DS_JOBOBJECTS. In those records the input link and output link references can be found, and you can self-join using the OBJIDNO column. To get the job name join to DS_JOBS based on DS_JOBS.JOBNO = DS_JOBOBJECTS.OBJIDNO.