DFS4764A ONLINE CHANGE COMMIT PHASE 2 FAILED, SO IMS IS STUCK IN AN ONLINE CHANGE STATE
Explanation
An error occurred during online change commit phase 2. The error might be a result of an internal error. The IMS system can neither commit the online change nor abort it.
System action
The /MODIFY command is rejected. IMS is stuck in an online change state. Resources that were deactivated for the online change remain inactive.
Output destination
The system console.User response
- Issue the /DISPLAY MODIFY MODS command and save the output.
- Produce an IMS dump.
- Save the X'22' and X'70' log records.
- Contact IBM and provide the documentations: the output of the /DISPLAY MODIFY MODS command, the system dumps, and the X'22 and X'70' log records.
- Use the /CHE FREEZE command to shut down IMS and then restart IMS. If that doesn't work, cancel IMS and perform an emergency restart.
It is likely that some of the resource changes did not take effect if the commit phase 2 internal error occurred before those resources could be changed and log a X'22' log record. You can use the /DISPLAY command for the resources that are named in the /DISPLAY MODIFY MODS command output before IMS shut down to determine whether some of the changes did not take effect.
If all changes took effect, the output of the /DISPLAY command includes the newly added resources, omits the deleted resources, and shows the new values of the changed resources.
If some of the changes did not take effect, you can retry the online change that failed or perform an IMS cold start from the current libraries.