Managing Cross-System Message Traffic › Selecting Message Sources

Selecting Message Sources

Messages can be collected from the CA VM:Operator or from any other virtual machine. CA MIC can intercept messages from the following sources:

• CP messages and warnings directed to the MIMGR service machine using the CP MESSAGE (MSG), the CP MSGNOH, and the CP WARNING (WNG) commands.

  To enable CA MIC to intercept CP messages and warnings directed to MIMGR, issue these commands on the MIMGR user ID:

  SET MSG IUCV
  SET WNG IUCV
  

  When CA MIC is intercepting CP messages and warnings on the MIMGR user ID, you will notice a slight difference in the way they appear at the MIMGR console.

  CP messages and warnings are displayed on a single line without a time stamp, as shown here:

  MSG(userid) messagetext
  WNG(userid) messagetext
  

  Also, there is no difference in format for messages sent by the CP MSG and MSGNOH commands.

• SCIF traffic received at the MIMGR service machine, due to designating the MIMGR service machine as a secondary user to another user ID.

  The Single Console Image Facility (SCIF) allows a secondary user to observe and control a disconnected virtual machine. All console messages from the disconnected virtual machine are forwarded to the secondary user. To define MIMGR as the secondary user for a specific virtual machine, use the CONSOLE control statement in the z/VM directory.

• Messages forwarded to the MIMGR service machine by ATMCOMM. ATMCOMM is used to capture operator console information and forward console messages (through IUCV) to the MIMGR service machine. ATMCOMM runs as a CMS nucleus extension on the OPERATOR user ID (or any user ID you select). For more information about ATMCOMM, see the chapter "Using ATMCOMM."