Message routing during a checkpoint reconfiguration

The reason JES2 entered a checkpoint reconfiguration, the message route code, and your installation's specification of the MVS™ parameter MSCOPE= on the MVS CONSOLxx member of SYS1.PARMLIB all determine how the checkpoint reconfiguration messages are routed.

Based on reconfiguration entrance type, messages are directed as follows:

Operator initiated - the messages are directed to the console that requested the dialog
Therefore, if the MVS system to which this console is attached subsequently fails, the checkpoint reconfiguration messages might not be displayed on any console. To prevent this situation, when planning your sysplex console configuration consider the systems to which your consoles are attached. See z/OS MVS Initialization and Tuning Reference for a description of the GROUP and NAMES parameters on CNGRPxx and the ALTGRP, MSCOPE, and UD parameters on CONSOLxx. Also see z/OS MVS Planning: Operations for recommendations on how to define your consoles to be certain messages are routed as expected in a sysplex environment.
JES2 initiated - the messages are directed to consoles based on their route code(s)
The console on which reconfiguration messages appear is influenced by which member drives the checkpoint reconfiguration and your MSCOPE= specification on the CONSOLxx parmlib member. Also, if during a checkpoint reconfiguration, the driving member fails, the messages issued by the new driving member might appear on a different set of consoles based on MSCOPE= specifications.

Depending on your MSCOPE= specifications for your consoles, exception messages issued by non-driving members, such as $HASP424, might not appear on the same console on which $HASP235 and $HASP272 messages are displayed.

Messages are directed to console by route code or console ID. Additionally, some messages are also issued only to the HDRCPY log. Those issued to the HDRCPY log are useful for diagnostic purposes and allow you to follow the progress of the reconfiguration on each member during a checkpoint reconfiguration. For example, all JES2 members within the MAS issue $HASP285, $HASP233, and $HASP255 to HDRCPY.