Comment/Note during Runtime

Another option is to log the messages as user events in the Sequence of Events log (alarm history). That way it is saved automatically by both alarm servers and can be viewed on the alarm history page. You use the SOEEventAdd() function to write a message. You're supposed to be able to specify an alarm tag name as well to associate it with that alarm, but I haven't tried that.

SOEEventAdd(TimestampCurrent(), sMessage, "");

Another option is to log the messages as user events in the Sequence of Events log (alarm history). That way it is saved automatically by both alarm servers and can be viewed on the alarm history page. You use the SOEEventAdd() function to write a message. You're supposed to be able to specify an alarm tag name as well to associate it with that alarm, but I haven't tried that.

SOEEventAdd(TimestampCurrent(), sMessage, "");

Ah, I like this option. I'll try it out.

Andy

Just be aware that pulling specific alarms out of the SOE journal can be very slow (depending on how many alarms your system is generating per day).

Also be aware that the SOE journal will get archived at some point, so long term operator notes will disappear at some point.
I also had trouble creating an SOE entry without having an alarm configured; could've been just me though...
We have a note system based on the SOE entry functionality and I am seriously thinking of scrapping it for something that's more useful.

Also, you would have a limited string length, much like a tag.

You can make SOE entries without an alarm as per Eric's suggestion, however I question the usefulness as they are then not tied to the equipment.