Explanation
Action was taken to ensure that a system being
partitioned from the sysplex no longer has the capability to perform
I/O to devices that can be used by another active system in the sysplex.
Message IXC108I was issued when the action was initiated. This message
is issued when the results of the action are available or the action
times out.
In the message text:
- FENCE
- The action is system isolation by a system fence through coupling
facility fencing services.
- SYSTEM RESET
- The action is a SYSTEM RESET-NORMAL through the HWICMD BCPii callable
service.
- sysname
- The name of the system targeted by the action.
- SUCCESSFUL.
- The action completed successfully.
- RESULTS:
- The action resulted in the indicated return code.
- TIMED OUT.
- The action did not complete within the allotted time. Processing
continues without the result of the action.
- HWICMD
- The action resulted in the indicated HWICMD BCPii callable service
return code.
- HWMCA_EVENT_COMMAND_RESPONSE
- The action resulted in the indicated ENF68 command response return
code.
- retcode
- The hexadecimal return code from the indicated source.
- text
- One of the following:
- blank
- No additional information is provided.
- (XCFAS DOES NOT HAVE SAF AUTHORIZATION)
- XCFAS does not have SAF authorization to RESET-NORMAL the target
system.
System action
When the action was successful, partitioning can
complete and message IXC105I will be issued.
When the action
was not successful, operator intervention might be required to complete
partitioning as indicated by message IXC102A being issued, or another
action can be attempted as indicated by message IXC108I being issued.
For example, a SYSTEM RESET may be attempted after a FENCE times out.
Operator response
Look for message IXC102A.
System programmer response
If the action was not successful,
fix the problem.
Problem determination
When system isolation by a system FENCE
is not successful, each system in the sysplex should write a symptom
record. A FENCE is likely to time out for the following reasons:
- System reset, new image loaded, or partition deactivated before
fencing completed.
- No coupling facility was connected and usable by both the system
being partitioned and another active system in the sysplex.
If these reasons did not prevent the FENCE from succeeding, provide
the symptom record to the IBM® support
center for analysis.
There are many factors that could cause a SYSTEM RESET to time out. For return codes from a BCPii
callable service, see z/OS MVS Programming: Callable Services for High-Level Languages for more
information. For return codes from an ENF 68 command response, see z Systems Application Programming Interfaces for more information.
Source
Cross System Coupling Facility (SCXCF)
Module
Routing code
Descriptor code