0B5
Explanation
Basic HyperSwap® has partitioned a member out of the
SYSPLEX due to an error condition. Basic HyperSwap can
partition a system out of a sysplex for the following reasons:
- Reason 1 - User-specified policy indicates that a member failure, while a Basic HyperSwap is in progress, is to be partitioned out of the sysplex. This includes a new system joining the sysplex while a Basic HyperSwap is already in progress.
- Reason 2 - User-specified policy indicates that a new sysplex member should be partitioned if it is unable to successfully load and monitor a Basic HyperSwap configuration.
System action
XCF services are used to partition the failing member out of the sysplex. Basic HyperSwap message IOSHM0428I can result if XCF services are not available to perform the partition request.
System programmer response
Ask the operator to obtain the stand-alone dump. Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center. Provide the stand-alone dump. Review the Basic HyperSwap policy in effect at the time of the failure to ensure that the required actions were performed.
Source
Input/output supervisor (IOS)