The ROR LOG file is used for recording different kinds of events (errors, debug messages, etc.) that are generated by registry processes. You may control event recording via parameters in the ROR REGISTRY PARAMETERS file. Look for additional information in the RORLOG and RORERR routines. A permanent screen (the ^DD(798.7,0,"SCR") node) restricts access to records of this file. Only users with the security key(s) for any defined registry (or those with the ROR VA IRM security key) can access records of the file. If you want the changes in the security keys allocation to have an effect immediately, you should rebuild the "ACL" cross-reference of the .01 field of the SECURITY KEY multiple of the ROR REGISTRY PARAMETERS file (#798.1). See the description of the cross-reference for more details.
DESCRIPTION: This multiple contains a list of the registries that were processed. Events recorded in the log are associated with these registries.
Records of this multiple are indexed by the "ARD" index (whole file). So, it is possible to get a list of log files associated with the particular registry.
This multiple contains all messages recorded in the log.
TECHNICAL DESCR:
Every call of the LOG^RORLOG procedure adds a new record to this multiple. The $$OPEN^RORLOG and CLOSE^RORLOG entry points can also call the LOG^RORLOG automatically to add a header and footer to the log.