For those interested, I thought I'd share the solution we reached.

We have the Purge Task History job running each AM. We utilized this as a hook so that when this is completed it triggers the Tasks we want to run, essentially, at startup. This was done "How often do you want the Task Manager to execute this task?" to "After another task completes".

While I would love to use %ZSTART, we use a third-party application on our DB that we want to ensure our code isn't intermingled with, or inadvertently removed when the product owner decides to change dependencies of theirs within %ZSTART. Basically, we would know for certain that changes made within %ZSTART are only from that product owner.

This is a great idea as well.

While it is possible, I would ensure that it is not possible to perform the actions within Caché first. This would enhance the application's ability to work better across platforms as well. Many of the functions that users would want to use have been compiled into classes, which you can refer to the class documentation here.

Its important to note that Caché reserves system memory for itself, so external calls would rely on the system's memory less that which has been reserved for the database. In most cases, a database is set up to run on its own system (i.e. the server is optimized to run the database only). I have been in a situation where someone did not recognize this and caused the server to lock up due to consuming the remaining memory.

As far as how to do this, it would depend on your Caché version and your Operating System, but it would be done with the $ZF function, which you can read up on here.

This does not identify how consumption may be calculated; however, it does advise how we can determine how much storage a global has already consumed. I am looking for how to calculate consumption, which would help us in identifying our personal rate of consumption.

EDIT: It may be worth noting that when reviewing a global with this class the output was 0.008 for multiple tests, where ^%GSIZE provided varying bytes for each test.