OSBlog implementation for logging errors, diagnostic logging, and event logging.

OSBlog Interface	OSBlog extension interface to the VXIlog interface.
OSBlogInit	Global platform initialization of OSBlog
OSBlogShutDown	Global platform shutdown of Log
OSBlogCreateResource	Create a new log service handle
OSBlogDestroyResource	Destroy the interface and free internal resources

OSBlog is an implementation of the VXIlog interface for logging. The OSBlogInterface extends the VXIlogInterface to support enabling/disabling messages on an individual tag basis without requiring a recompile for use by consumers of the diagnostic log. Diagnostic( ) is highly efficient for cases when the tag is disabled: in other words, the lookup for seeing if a tag (an integer) is enabled should be done using a simple array or some other extremely low-overhead mechanism. OSBlog provides a way to enable/disable tags on-the-fly (without needing to restart the software).

Across all streams, OSBlog is responsible for automatically supplying the following information for end consumer use:

• timestamp
• (Error only) error key/values, the error number, and the supplied module name.
• (Diagnostic only) tag number, and the supplied subtag name
• (Event only) key/values pairs to log in the event

  Each OpenVXI component provides an XML error file which integrators can choose to us (or rewrite) to map error numbers and error key/values to error text. An XSLT transform can do this in an error viewer.

Alphabetic index Hierarchy of classes