Asynchronous Host Sessions › Manage Asynchronous Communication › Asynchronous Console Management › Asynchronous Console Types › Message Criteria for Asynchronous Consoles

Message Criteria for Asynchronous Consoles

When processing an incoming character stream on asynchronous consoles, CA Automation Point looks for the following:

• A header to indicate that a message has started
• The text of the message
• A terminating condition or trailer to indicate that the message has ended

ASYNCH refers to the CA Automation Point asynchronous console driver. The console types in the next few sections are specific to various asynchronous formats. Specify the ASYNCH driver if none of the specific drivers apply to your console.

To the CA Automation Point console driver, a message begins with any character and continues up to the first new line (carriage return or line feed) character. If the console sees no new line character within ten seconds of receiving the last character, it releases the message text received up to this point to the CA Automation Point rules processor.

Define the console type as ASYNCH in the following situations:

• When CA Automation Point is connected to an asynchronous system such as UNIX or Linux
• When CA Automation Point is connected directly to another workstation running CA Automation Point, such as a workstation dedicated to voice processing
• When CA Automation Point is monitoring a serial printer port on a host
• When the data stream does not include escape (ESC) sequences

If an ASYNCH console receives a OpenVMS OPCOM message, each of its lines generates an individual message.

For example, suppose that the console receives the following sample message text:

%%%%%%%%%%%  OPCOM 01-JAN-1994 12:00:00:00  %%%%%%%%%%%
Message from user JOB_CONTROL
%JBC-E-SYMDEL, unexpected symbiont process termination

>TEST

CA Automation Point treats each line of message text on an ASYNCH console as a separate message and sends each message to the rules processor. Given the sample message text, CA Automation Point generates five messages; for example, the first message sent to the rules processor is:

%%%%%%%%%%%  OPCOM 01-JAN-1994 12:00:00:00  %%%%%%%%%%

In this case, the OPCOM header is a message because ASYNCH message criteria do not distinguish between headers and other parts of the incoming character stream.