Using ATMCOMM › Using ATMCOMM to Intercept Operator Messages

Using ATMCOMM to Intercept Operator Messages

You can use ATMCOMM to intercept messages from OPERATOR and make these messages eligible for routing to other systems in your complex using CA MIC. You are not required to run ATMCOMM at your site, although it is recommended. If you do not run ATMCOMM, unsolicited messages displayed to the operator will not be available to other systems.

ATMCOMM sends a duplicate of each message displayed at the screen of the operator to CA MIC, which may then route the message to other systems in the complex. ATMCOMM also sends information about each message, such as the origin of the message and the type of message (for example, MESSAGE, WARNING, or CPCONIO).

ATMCOMM communication with CA MIC is strictly one way; messages are sent to CA MIC but never received from it.

ATMCOMM is a shell program that operates in cooperation with CMS without interfering with normal CMS functions. With ATMCOMM running, the operator can issue CP and CMS commands, use XEDIT, execute REXX or EXEC2 programs, and perform all other routine functions, just as if ATMCOMM were not running.

Note: If the IUCV link between ATMCOMM and CA MIC is down, buffers that would normally be sent to CA MIM are discarded. No messages for this link are queued or saved while the link is down.