|
- Description:
- For each path check that there is a MAXMSG of at least the
indicated minimum value specified by or inherited from the COUPLExx,
transport class definition, or path definition.
- Reason for check:
- It is recommended for availability that there is a minimum
MAXMSG value of 2000 for each transport class.
- z/OS® releases the check
applies to:
- z/OS V1R4 and later.
- Parameters accepted:
- The minimum MAXMSG value for transport classes. (must be
an integer in the range of 1 to 999999
- User override of IBM® values:
- The following shows the default keywords for the check, which
you can override on either a POLICY statement in the HZSPRMxx parmlib
member or on a MODIFY command. This statement may be copied and modified
to override the check defaults:
UPDATE CHECK(IBMXCF,XCF_DEFAULT_MAXMSG)
SEVERITY(LOW) INTERVAL(024:00) DATE('date_of_the_change')
PARM('2000')
REASON('Your reason for making the update.')
- Reference:
- For more information, see z/OS MVS Setting Up a Sysplex.
- Messages:
- This check issues the following exception messages:
See the IXCH messages in z/OS MVS System Messages, Vol 10 (IXC-IZP).
- SECLABEL recommended for MLS users:
- SYSLOW
|