Troubleshooting › Cross-system Message Processing Problems › Message Traffic from External Systems not Displayed on the Local Console

Message Traffic from External Systems not Displayed on the Local Console

Try these possible solutions:

• Enter D C,* and F MIM,D COLLECT from the local collecting console. Compare the attributes of the local console with the information in the
  D COLLECT output.
• Verify that console names/IDs match and the correct target systems are specified. Verify that no exclusion criterion is specified.

  Note: Review D GCMF OPT=ALL on the WTO originating system and the local D COLLECT output.

• Verify that CA MIC is synchronized on all systems
  (F MIM,D SYSTEMS).

CA MIC reissues imported unsolicited WTOs from external systems as GCM/xxxxx on the local system, instead of the typical message ID (for example, IEF233A is changed to GCM/xxxxx). This is done so CA MIC can differentiate between one of its own imported messages versus a WTO that originated on the local system. CA MIC then converts it back to the original message text.

WARNINGS!

• Do not allow MPF to suppress messages that begin with GCM/. If so, then these messages will never appear on the target consoles. Also, do not allow automation packages to act on these messages because unpredictable results may occur.
• Check for CA MIC exits, for example, F MIM,D EXIT. Check the message on the syslog of the originating system. If the LOGONLY bit (00000200) is set, then CA MIC will not route this message (unless SET GCMF CAPTURELOG=YES is specified).

The following are some more possible solutions:

• Check the route codes on the message. Be sure they match the route codes that you are using on the COLLECT command.
• Check the suppression bits (00000004,00000001,00000005). If the message is suppressed on the originating system, then CA MIC will not route this message to external systems.
• If the message is issued as a command response (NR, MR in the syslog), then CA MIC will not route this message.