The following operating modes are available:
Attended mode
An operator is on duty. You can optionally have an automation database respond to messages and execute actions.
In attended mode, pattern matching can be on or off. You specify whether the default for pattern matching is on or off during the installation of the OMKEY background run.
Casual mode
An operator is nearby who can respond to an audio or visual alarm. Much of the interaction between the operator and the system is automated by a CP-AMS database handling console messages. The system issues an alarm if one of the following conditions occurs:
The system console receives a read-and-reply message, but CP-AMS does not find a match in the active database. For example, a user on a terminal sends a message (using a @MSG,W statement) asking a question and waits for a reply.
The system console receives a read-alert message, but CP-AMS does not find a match for it in the active database.
A user run terminates abnormally, but CP-AMS does not find a match (for a message of the form run-id ERROR FIN, run-id FAC ERROR FIN, or run-id ABORT FIN) in the active CP-AMS database (the UALM option of the OM keyin must be set).
Unattended mode
No operator is present. Devices such as tape drives and printers can be shut down. Unattended mode includes the casual mode functions. As an option, CP-AMS aborts any nonprivileged user program that issues a read-and-reply message (except a @MSG,W message) that does not match a pattern in the active database. (A nonprivileged program does not have the COM$PRV privilege.)
In addition, if CP-AMS does not find a match in the active database for a read-and-reply message generated with the @MSG,W statement, CP-AMS automatically issues a rejection response to the message.
No distinct dividing lines exist between attended, casual, and unattended modes of operation. CP-AMS can respond differently to a console message depending on which mode the system is currently in. These features allow you to tailor message actions and application initialization to define attended, casual, and unattended modes to match your site requirements.
Your site controls the amount of operator intervention. The extent to which the system can run without any operator intervention depends on the nature of the applications in use.