In normal operations, unconfirmed entries are automatically handled by the RJ link monitors.
However, there is a scenario where you may end up with a backlog of unconfirmed entries that can prevent you from starting or ending an RJ link. This problem can occur when all of the following are true:
The data group is not switchable or you do not want to switch it
A link failure on an RJ link that is configured for synchronous delivery leaves unconfirmed entries
The RJ link monitors are not active, either because you are not using them or they failed as a result of a bad link
To recover from this situation, you should run the Verify Communications Link (VFYCMNLNK) command to assist you in determining what may by wrong and why the RJ link will not start.
If you are using an independent ASP, check the transfer definition to ensure the correct database name has been specified.
You also need to end the remote journal link from the target system. Ending the link from the target system is a restriction of the IBM remote journal function.