IBM Tivoli NetView for z/OS, Version 6.2

Messages That Originate on the Local Processor

All WTO messages issued on a local processor pass through MPF processing on the local processor, and indicators for suppression, retention, and automation are set in its WQE.
  • If an MPFLSTxx entry exists for a message identifier:
    • Its AUTO, SUP, RET, and USEREXIT definitions are used.
    • If an entry exists but no definitions exist, the .DEFAULT entry is used.
    • If no .DEFAULT entry exists, the defaults AUTO(NO) and SUP(YES) are used.
  • If no entry exists in MPFLSTxx for the message ID:
    • The definition from the .NO_ENTRY statement is used.
    • If no .NO_ENTRY statement exists, the system defaults AUTO(YES) and SUP(NO) are used.
  • Next the message is presented to MPF exits:
    • If an MPF exit was specified for this message ID, it is processed.
    • If no MPF exit was specified but an IEAVMXIT exit routine exists, it is processed.

Then the message is broadcast on the MVS™ subsystem interface of the local processor. Each subsystem inspects the message in the order determined by the subsystem names table. JES3 must be the primary subsystem so it sees the message first.

JES3 performs MSGROUTE processing and presents the message to its exit 57 (IATUX57) and exit 69 (IATUX69)..

The NetView® program performs any Message Revision processing.

If a NetView subsystem is running on the local processor and AUTO(YES) was specified or defaulted in MPF for the message, the NetView program copies the message for automation.

After subsystem interface processing, the message goes to multiple console support on the local processor for possible display, retention, and hardcopy logging, depending on the current status of routing codes, suppression and retention indicators, the subsystem interface return code, and JES3 MSGROUTE specification.

Console support on the local processor copies the message and passes the copied message across an XCF connection to the global processor. JES3 does not alter the suppression, automation, or retention indicators of the original message in the local processor.

Console support on the global processor receives the message from an XCF connection on the local processor and processes it as follows:
  • The message is presented to MPF exits if requested by the JES3 GLOBMPF parameter.
    • If an MPF exit was specified for the message ID, the MPF exit routine is processed.
    • If no MPF exit was specified but an IEAVMXIT exit routine exists, IEAVMXIT is processed.

After subsystem interface processing, the message goes to multiple support console for possible display, retention, and hardcopy logging at the global processor, depending on the routing codes, MPF specifications, and subsystem interface return code.

Parent topic: Message Flow in a JES3 Complex

Feedback