4.10.3 Contents displayed as event guide information
To write event guide messages directly in an event guide information file, specify EV_GUIDE. To use event-guide message files, specify EV_FILE instead of EV_GUIDE and write the file locations.
Messages can be written in text format or HTML format. The attribute values of JP1 events can also be used as variables in messages (by prefixing the attribute value with $). For example, if you write $B.MESSAGEΔ (where Δ represents a space), JP1 event messages (B.MESSAGE) will be handled as variables, and the attribute value of the JP1 event will be displayed in the event guide message.
- Event-guide message file as a useful tool when editing
-
When event guide messages are written directly in an event guide information file (EV_GUIDE specified), each message is a single line. You cannot format the message layout by inserting linefeed codes. However, you can do so in an event-guide message file (EV_FILE specified). This is illustrated in the figure below.
Figure 4‒87: Examples of writing event guide information ![[Figure]](GRAPHICS/CS032800.GIF)
Because you can apply formatting in this way, an event-guide message file is useful when you are preparing messages in HTML format, and there is a large amount of information or you need to periodically review the message contents.
- About event guide information files:
-
See Event guide information file (jco_guide.txt) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.