Hi,
Looping through them all SQLGetDiagRec() would be the way forward as far as I can see.
The output of dbcc log (as with other dbcc commands) will be sent in what we call 'EED' tokens which are used to send errors and warnings. You would need to iterate through these.
OdbcInfoMessageEventArgs would be the class to use from a .NET application.
This should work on any supported ASE\ODBC version.
Cheers,
Simon