In contrast with status codes (which indicate success or failure within a specific Rendezvous call), asynchronous advisory messages notify programs of events that occur
outside of the program’s direct flow of control—for example, the program is processing inbound messages too slowly, causing the daemon’s message queue to overflow.
For example, the subject _RV.*.SYSTEM.> matches all advisories related to communications. Programs can also listen more selectively for specific advisories, as appropriate.
Some platforms do not support the concept of stderr, or support it only in limited cases. When
stderr is not supported, error and warning messages are lost unless the program explicitly listens for them. For example, Microsoft Windows operating systems do support
stderr, but only in console-based applications; they do not support it in GUI (window-based) programs.