UDR

Oninit's engineering line for reusable Informix DataBlade / UDR tooling — infrastructure built once, in C, that any UDR project can adopt rather than reinvent.

Every Informix shop writing C UDRs eventually needs the same handful of things: a way to see what a UDR is actually doing in production without guessing, a way to move data in and out of TimeSeries objects efficiently, a way to talk to the engine's own catalogs instead of working around them. Each sub-project under UDR answers one of those needs, built and verified against a real, live Informix instance — not just compiled and assumed to work.

ONI UDR Debug

A generic, reusable diagnostic subsystem for C UDR code — one shared, structured record of what your UDRs did, without mi_trace()'s silent failure modes.

Why a separate engineering line

These aren't one-off scripts for a single customer. They're written to be dropped into any Informix UDR project: no dependency on a particular schema, no assumptions about what else is running in the instance, and no behavior that only works until someone else's UDR shares the same connection or the same VP. Each sub-project is verified the same way — against a real, running IDS instance, not just a compiler.

What's here now

ONI UDR Debug — available now. A PER_SYSTEM-shared circular message queue, SQL-level admin surface, and disk-failure-resilient flushing, usable by any C UDR that links it in.