>> Changed to what? What is wrong in the way SUSPEND works now?
>
> I thought that the article was clear enough.

The article describes "new invention" of Oracle. But in IB/FB SUSPEND
works this way from the beginning (i.e. more that 20 years).

> A stored procedure call in Firebird is atomic.

This statement is incorrect for selectable stored procedures (that
is, with SUSPEND inside), so the rest has no sense.

SY, SD.