When I do this, it brings me straight back to Intersystems Cache documentation (which is where I started). To add, I have found things 'here and there' that actually work, but they are sparse and only pertain to 'simple' stuff, like this:
do ^%CD

do ^%FREECNT

do ^%D

do ^%T

Any thing related to classes and methods, that I find in the Cache documentation, simply won't work -  <Class does not exist>, <Method does not exist> and so on. I need a reference that contains 'useful' commands/classes, etc. that actually 'work'.

Thank you Rich. I will take a little time to dig into your reply.
 

Regarding non-linear, in your first reply, you stated this, when describing how Cache does lookups:

‘However once in the group the lookup is a linear function that examines every record in every block of the group to find the record being retrieved.’

You followed up with concerns about sizing issues and poor performance of Universe/Unidata, when inserting new data. In a linear system, processing time increases proportionally with the size of the data set being retrieved. Conversely, a non-linear system behaves differently: as data size grows, the processing time does not increase in a straightforward manner. Non-linear systems can become complex, and their characteristics differ from linear systems. I’m looking to better understand what you are inferring about Universe (and, its non-linear behavior) in contrast to Cache.

Thank you Rich. To clarify, you are saying that a select on Universe/ Cache is non-linear, correct? I am curious about the key/value/non-hashed/binary details. My experience has been that selects can be very time consuming on Universe/ Cache, as files grow very large. Can you expand on this part? Also, do you know what happens, at a cellular level, when you do a CREATE-FILE from TCL?