IXCH0424E

Explanation
This message is followed by IXCH0904I, which is
a table listing the maxmsg value that is too small
and where it is defined.
One or more MAXMSG specifications in
use by system system_name    are smaller than the checkowner_or_installation specification.
      MAXMSG values should be greater than or equal to this value
to       pass the check.      Message IXC0904I is issued to identify
the particular    MAXMSG value that is too small. 

In the COUPLExx parmlib member, MAXMSG values can be specified   
   on the COUPLE, CLASSDEF, PATHOUT, or PATHIN statements.  The MAXMSG
values associated with these statements can be modified   after IPL
via the SETXCF MODIFY operator command.        The SETXCF START command
can also be used to create new CLASSDEFs,   PATHOUTs, or PATHINs.If
a MAXMSG value is not explicitly coded on a statement in the     
COUPLExx parmlib member or on the SETXCF START command, a default
   value is used.       If MAXMSG is not coded on the COUPLE statement,
         the IBM® supplied default
value is used for MAXMSG.       If MAXMSG is not specified for a CLASSDEF,
the MAXMSG value is       inherited from the COUPLE MAXMSG value in
effect at the time the     CLASSDEF is defined. If MAXMSG is not specified
for a PATHOUT, the MAXMSG value is        inherited from the CLASSDEF
MAXMSG value in effect at the time       the PATHOUT is defined (the
     CLASSDEF to which the PATHOUT is assigned is used).   If MAXMSG
is not specified for a PATHIN, the MAXMSG value is         inherited
from the COUPLE MAXMSG in effect at the time the           path is
defined.    
         This check cannot determine whether a
MAXMSG value was explicitly    coded or inherited as described above.
      However, the check does understand the inheritance and assumes
      that the specification was inherited         if the MAXMSG value
of a "child" equals the MAXMSG value of its "parent".     In such
cases, the check will attempt to identify the "parent" as    the problem.

System action
The system continues processing.

Operator response
Report this problem to the system programmer.

System programmer response
         The MAXMSG values in error
were probably specified in    the COUPLEXX parmlib member, and if
so, the necessary changes        should be made there in preparation
for the next IPL.    However, the values specified in the parmlib
member could have been  modified via the SETXCF operator command after
IPL.      The check cannot determine whether such changes were made,
          so it could be possible that the parmlib values do not need
to be    changed.    Regardless, the SETXCF MODIFY command can be
used to modify the      MAXMSG values currently being used by the
system.       

Problem determination
N/A

Source
         Parallel Sysplex® (XCF)          

Module
         IXCHCSIG   

Routing code
N/A

Descriptor code
N/A

Reference Documentation
z/OS MVS Setting
Up a Sysplex
z/OS MVS System Commands