DSXchange

Forget the row counts on the link - these might not be updated for a number of reasons.

Is the job running to completion? Are the lookups working? Enable player process row counts and get the row counts into the log file.

PRECISION <> EXACTNUMERIC

PRECISION is a statement that can be inluded in a BASIC routine.
EXACTNUMERIC is a configuration directive in uvconfig

They are related by the fact that PRECISION must be less than EXACTNUMERIC but it remains the case that PRECISION must also be less than 15.

Try the Orchestrate Administration manual.

Create a new job.
Copy the DATA.30 file from that job's RT_CONFIGnnnn to the jobs that are exhibiting the problem.
Then try re-compiling those jobs.

That's at best a workaround. If 8.0 is causing deadlocks in the Repository I, for one, want to know how, where and why so that I can avoid the situation. Please ask your support provider to stay with it. Having to run scripts to clear deadlocks is not my idea of a professional application.

StartLoop activity supports two kinds of loop: a counted loop and a "list of things" loop. Investigate more thoroughly.

We are not discussing scale. We are discussing an artifact of working in a data-typeless environment, where decimal numbers are rounded to PRECISION decimal places following any arithmetic operation (originally so that display columns are not too wide). For most currency operations, PRECISION 4 is f...

There's no tab, but there IS an available property to add.

Welcome aboard. :D

Get "them" to send you a valid CSV file. The CSV rules stipulate the same number of fields in each row.

If you can't get that, read each row as a single VarChar and parse it yourself, perhaps in a Transformer stage, perhaps in a Column Import stage.

In particular, is there a leading \x00 character?

I do know. It can not be done.

RCP is only ever about pass-through columns. Anything you want to derive or constrained must be named explicitly.

You might contemplate building the constraint expression as or containing a job parameter.

That - along with the coding exercise itself - should tell you something about the amount of work that is involved.

It's time to manage expectations better.

Can you run two jobs in succession, one with Delete, the other with Insert, using the same keys?

1. Someone executed dsdlockd -p command.

2. The deadlock daemon on waking found defunct processes and initiated a cleanup.

3. Someone (whose pid is given) started the deadlock daemon, maybe from DEADLOCK.MENU, maybe from the command line. If pid = 1 this was the auto-start on re-boot.

You don't need administrator access. All you need is read/write access to the DSParams file for project-defaults set in the Administrator client, and read/write access to the job log to set for a particular job.