Transaction vs Rununit

Discussion created by ca.portal.admin on Feb 3, 2006
Latest reply on Feb 3, 2006 by ca.portal.admin

IDMS/SQL introduces the notion of transaction. A transaction may control
1 or more rununits.

Let's explain an example with more than 1 rununit.

Your ADS dialog accesses the SQL DB (RU1) and IDMS/SQL detects a
discrepancy between the Access Module and the Catalog.

IDMS/SQL will start a new ru (RU2) in an attempt to rebuild a new AM on
the catalog.

In this situation we have 2 RUNUNITS (1 on the USER SQL DB & 1 on the
CATALOG) under the control of 1 TRANSACTION for integrity purpose

All internals freak (like YVA) are free to comment on this, of course.


Philippe Jacqmin

IDMS (Data Base & Transaction Server)
WT 20/8 zone 1
+32 (0)2 222 93 52

Philippe.P.Jacqmin at
<> or philippe.jacqmin at

Dexia Bank disclaimer :

IDMS Public Discussion Forum


Re: Transaction vs Rununit
"I do not wish to get in to long discussions on this subject but I beg to

Since R12 CA stopped using 'run unit' and replaced it with

Examples are
1) Journal report 8 new refers to transaction id and not run unit id.
2) When something is backed out you get Transaction-ID nnnnnn has been
Rolled Out!

The example quoted is, I would say, a TASK with two TRANSACTIONS.

I have a DC program that issues 2 bind run units for different databases
and when it abends I get
Transaction-ID 84341 has been Rolled Out!
Transaction-ID 84342 has been Rolled Out!

So again one TASK with two transactions.

Must admit I find the terminology confusing may be if some one in CA
monitors the list they could clarify all this.

Best Regards to all

Pete Charles