Explanation
This system tried to use a channel-to-channel (CTC) device for global resource serialization, but the CTC was disabled.
- dev
- The device number for the disabled CTC.
- HARDWARE
- There was a hardware problem in CTC dev.
- SOFTWARE
- A software problem damaged the global resource serialization control blocks that control CTC dev.
- CODE=rc
- The reason code identifies the error.
- Reason Code
- Explanation
- 01
- A software error has occurred. This code is provided for IBM® diagnostic purposes only.
- 02
- A software error has occurred. This code is provided for IBM diagnostic purposes only.
- 03
- A software error has occurred. This code is provided for IBM diagnostic purposes only.
- 05
- CTC write error.
- 06
- A software error has occurred. This code is provided for IBM diagnostic purposes only.
- 07
- CTC read error.
- 08
- A software error has occurred. This code is provided for IBM diagnostic purposes only.
- 09
- A software error has occurred. This code is provided for IBM diagnostic purposes only.
10
- Paths were temporarily lost to the device. This may be due to
a loss of light condition.
- 0B
- The CTC driver could not use the CTC because there were no paths to the device.
- 20
- A software error has occurred. This code is provided for IBM diagnostic purposes only.
- 21
- A software error has occurred. This code is provided for IBM diagnostic purposes only.
- 22
- A software error has occurred. This code is provided for IBM diagnostic purposes only.
- 23
- A software error has occurred. This code is provided for IBM diagnostic purposes only.
- 24
- A software error has occurred. This code is provided for IBM diagnostic purposes only.
- 27
- IBM internal error.
- 2C
- A software error has occurred. This code is provided for IBM diagnostic purposes only.
System action
Global resource serialization processing ignores any data it receives on CTC dev and stops sending data through CTC dev. If the error is the result of a hardware error, global resource serialization processing enters the VARY dev,OFFLINE command for the CTC. If CTC dev was in use at the time the error occurred, the global resource serialization ring might be disrupted.
The system writes messages in the system logs (SYSLOG) of all active global resource serialization systems and of any systems that are restarting or joining the global resource serialization complex. The system might write a logrec data set error record and an ABEND dump.
For return code X'10',
the device is not varied offline so that the system can detect when
paths become available again. Like other hardware errors this may
result in a ring disruption. The system will utilize the device once
the paths are restored.
Operator response
If this message is accompanied by message IOS071I indicating a missing channel and device end, then notify the system programmer.
If the message text indicates a hardware error and the reason code is X'05' or X'07', the problem might be caused by another system in the global resource serialization ring. With the reason code of X'05', the problem might be caused by the device being configured as an SCTC, which GRS cannot use. If the message text indicates a hardware error and the reason code is X'0B', the configuration might be wrong. Make sure that all required channels are varied online and that your system was initialized with the correct GRSCNF parameter.
For other occurrences of message ISG046E, contact hardware support.
After the hardware error is corrected, enter a VARY dev,ONLINE command to make the CTC enabled for use by global resource serialization.
For other reason codes, notify the system programmer.
System programmer response
If the reason code is X'05', check to see if the device is configured as a BCTC. If the device is configured as a SCTC, GRS cannot use it. If possible, try to reconfigure the device as a BCTC.
If this message is accompanied by message IOS071I indicating a missing channel and device end, check for correct specification of MIH value for the CTC device. If this value is correct, the problem is caused by a system failure of another system in the global resource serialization ring such as disabled spin loop, wait state, or machine check. Investigate the cause of the failure of the other system. If the error recurs and the program is not in error, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the logrec data set error record and the ABEND dump, if available.
Source
Global resource serialization
Module
ISGBTC
Routing code
1,10
Descriptor code
11