Virtual Hometerm Subsystem (VHS) Manual (H06.03+)

Using VHS
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3-9
How VHS Manages Messages
After you have reconfigured your Pathway system, you can restart it and your Pathway
application.
How VHS Manages Messages
The VHS process receives messages of many types from many sources. VHS
manages these types of messages:
•
OPEN messages
•
Display messages
•
Inspect prompts
•
Debug prompts
•
Application prompts
•
Reply messages (to application prompts)
The following table summarizes how VHS responds to application messages and
prompts.
Type of message VHS Action
Open message Determines the object file of the process and acts accordingly.
Display message Saves the message in the text part of an EMS event, sends the event
to the collector if configured to do so (see parameter GENERATE-
DISPLAY-EVENT), and logs the message in the primary log file.
Inspect prompt Depending on the VHSINSP file and the AUTOMATIC-INSPECT-
PROCESSING parameter, VHS handles the Inspect prompt by
sending commands found in the VHSINSP file, and creates a
saveabend file to save the application’s context and stops the
application; or, VHS lets you handle the prompt by writing to its prompt
file. VHS logs Inspect messages in its primary log file. VHS can also
send EMS events to the collector if configured to do so (see the
GENERATE-INSPECT-EVENT parameter).
Debug prompt VHS sends to Debug the D;T;S (Display;Trace;Stop) commands and
stops the application. VHS logs Debug messages in its primary log
file. VHS can also send EMS events to the collector if configured to do
so (see the GENERATE-INSPECT-EVENT parameter).
Application prompt Saves the prompt to its prompt file. The prompt can be answered via
the Prompt Browser screen. Also sends the event to the collector, if
configured to do so (see the parameter GENERATE-PROMPT-
EVENT), and logs the message.
Reply messages Sends reply messages to the application, keeps a copy of the reply in
its primary log file, removes the prompt from its prompt file, and, if
configured to do so (see the GENERATE-PROMPT-EVENT),
generates an EMS event.