Using ATMCOMM › The Impact of ATMCOMM on CMS

The Impact of ATMCOMM on CMS

Running ATMCOMM has little impact on most activities at your operator console. You can still enter commands and see the results on the screen as you would if ATMCOMM were not running.

The CMS SUBCOM facility processes all commands that you enter while ATMCOMM is running, so commands are resolved just as they are under CMS. You can perform routine tasks (such as varying and attaching real devices and logging users on and off the system) without interference from ATMCOMM.

You will see a few slight differences in message and command traffic while ATMCOMM runs:

• CP messages and warnings normally generate extra blank lines, but these messages will display on a single line. Instead of including a time stamp, the messages appear as follows:

  MSG(userid) messagetext
  WNG(userid) messagetext
  

  The userid value is the user ID of the virtual machine that sent the message.

• The audible beep does not sound for messages and warnings.
• Messages sent by the CP MSG and MSGNOH commands will display on a single line and in identical formats.
• To remind you that it is active, ATMCOMM replaces the standard CMS Ready; prompt with the ATMCOMM prompt. When you enter a null line (that is, you press the ENTER key without issuing a command), the response is ATMCOMM instead of CMS.
• The CMS commands HX and HT operate under ATMCOMM just as they do under CMS. However, if you use the HX command to terminate an application, the return code generated is 100. The HX command does not terminate ATMCOMM.