IMS Log Recovery Utility (DFSULTR0) - Enhancement to add functionality to be able to close a Secondary OLDS that is OPEN when the Primary OLDS is already in CLOSED status.

IMS Log Recovery Utility was unable to be used to close a secondary OLDS dataset, preventing IMS from starting. This forced an /ERE COLDSYS on a client system.

IMS was unable to start from apparent insufficiency in IMS Log Recovery Utility being unable to close a secondary OLDS dataset independently from.

IMS could not start with this log dataset open, despite having a valid, closed primary OLDS dataset.

We would like to have some confidence that this issue can be addressed with the utility and further events where we are stuck avoided in production.

This appears to only be an issue as we were using DUAL OLDS. It is our understanding that having this is meant to make these issues with a problematic OLDS less likely, however it seems like it is adding more risk as this utility seems unable to close a secondary OLDS individually, however we still had one that was Valid that IMS was not able to use to start.

This situation occurred after the utility was run initially without the DFSOLS DD statement being included in the JCL while using DUAL logging.

It is understood this is behaving as designed, however it does not seem that a simple error such as this should leave IMS in a state that is unresolvable.

This would be a great addition to functionality to enable closing a Sec OLDS on its own as at the moment this seems to not be possible that could cause potential issues with FP data corruption and service restore delays. We don't believe you should be stuck in the occurrence of this simple mistake.