A cacheStart trap indicates that the Cache instance
has been started.

A cacheProcessFail trap indicates that a process has abnormally
exited Cache due to an access violation. Check the console log
of the instance for further details.

A generic trap that can be used by Cache applications to generate alerts
via SNMP. See the %Monitor.Alert.External class method for details about
how this can be used. It includes the name of the application, a severity
code, and a text description of the event.

A cacheECPTroubleDSrv trap indicates that a connection to this 
ECP Data Server for a Cache database has encountered a serious 
communication problem. Check the console log of the instance
for further details

A cacheECPTroubleASrv trap indicates that a connection from this 
ECP Application Server to a remote Cache database has encountered a serious 
communication problem. Check the console log of the instance
for further details

A cacheAuditLost trap indicates that system has failed to record
an Audit event. The most likely cause is a problem with space for
the Audit database, and requires operator asssitance.

A cacheDaemonFail trap indicates that one of the major Cache
system processes (or 'daemons') has encountered an unhandled
error and the process has died. 
OBSOLETE - now sent as cacheLoggedError.

A cacheLoggedError trap indicates that a 'severe' error has been
logged in the Cache console log. The trap will include the error
message as defined in cacheSysErrorMsg.

A cacheLicenseExceed trap indicates that a request for a license 
has exceeded the number licenses currently available or allowed.

A cacheDCPNetError trap indicates that a DCP client has detected a 
communications outage, and indicated a <NETWORK> error for all
pending transmissions.

A cacheStop trap indicates that the Cache instance
is in the process of shutting down.

A cacheDBExpand trap indicates the successful expansion of a
Cache database.

A cacheDBOutOfSpace trap indicates that there is a potential
problem in the future expansion of a Cache database. The database
is approaching its maximum size or the disk is nearly full.

A cacheDBStatusChange trap indicates that the read/write 
status of a Cache database has been changed.

A cacheDBAccessFail trap indicates that an error occurred trying
to access a Cache database, this my be either read or write
access. It includes the Cache error code for the failed access,
either DATABASE or DISKHARD.

A cacheWriteDemonStop trap indicates that the Write Demon
of a Cache instance has stalled.

A cacheWDPanic trap indicates that the Write Demon for a Cache
instance has entered 'panic' mode. That is the Write Demon
is out of buffers and must write database blocks directly to disk
without first commiting them to the Write Image Journal file.

A cacheLockTableFull trap indicates that the lock table for
a Cache instance is full, causing subsequent Locks to fail.