The WindowsEventLog class allows the Rexx programmer to write an event record to any of the Windows event logs.
However, the event record that is written is restricted and not that useful because of the way the Event Log service works on Windows. The Event Log service needs a message file to function correctly.
For instance a Rexx programmer could now produce this:
The description for Event ID ( 100 ) in Source ( Application2 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: First String, Second String.
However if a simple message resource was added to the resources compiled into one of the DLLs shipped in the Windows distributions and the installation set up the correct registry entry, the Rexx programmer would be able to use the WindowsEventLog to write a message that looked more like:
First String, Second String
Of course, I assume that the programmer would write an event record more like:
The myRexx program could not find its data file and was forced to close.
The compiled message resource would be smaller than an icon resource so it would add practically nothing to size of the DLL and would make the WindowsEventLog class much more useful.