Interestingly enough, that information is available via TEST DBLOG. I presume you want this for a production system, not a system being developed. If it is a development system, then TEST DBLOG would be the way to go.
For a production system, well, probably not pretty. Of course, if the system is “small enough” (whatever that means, probably only a small number (couple of hundred) of Adabas calls per execution) you could probably still use DBLOG.
Maybe a proposed Change Enhancement. When running a LARGE production system, keep, say, the last 100 Adabas calls.