User Answers

I am sorry, I started to look around on the other Help options and I found my answer. 

Humm, just noticed that the (so called) relevant articles really have nothing to do with my question.

Thank you both for your answer.

Unfortunately, I cannot click on or acknowledge both answers, what a shame, it would be nice to have that capability.

Thank you every body, with sdk 64 bit and JAVA_HOME variable created it works!

%Status or %Library.Status provides a number of useful capabilities.

Following is documentation from the %Library.Status Class.

The %Status data type class is used to represent an error status code.

Many of the methods provided by the Caché Class Library return error status information using the %Status data type. The include file, %occStatus.INC, contains several macro definitions that are useful in testing the value of an error code in %Status format.

These macros include:

I started this post and I appreciate everyone who contributed.

However, I see that the phrase "Extent Query" used a number of times.

I must admit that I really do not know its meaning.

Will someone help me understand the meanings and ramifications of "Extent Query"?

Perhaps I missed the post, but has any engineers weighed-in on the planning of Objects and SQL? 

Was SQL part of the mix from the start?

One very important point is that SQL is easier to read and modify than Cache.

So maybe not in run time efficiency, but the advantage is to SQL for speed of changes.

One thought I had, I am not sure if it applies.

I assume that the Object processing code is more developed than the SQL processing code.

Assuming that holds, can we say that future SQL processing code has more to gain than future Object processing code?

If that is true, then going with SQL in the mix seems like the correct way to go.