A software reclone uses the rules within the Replication Criteria List (RCL) to determine which objects on the source node are replicated. Replicated objects which can not be restored over and any objects that depend on those replicated objects are deleted from the copy node. Then all replicated objects are saved from the source node and restored on the copy node, ensuring that all replicated objects are identical between the two nodes. The system environment (operating system, licensed products, applications, and other non-replicated objects) of the copy node is unchanged.
A software reclone can be used if the nodes are configured using internal storage or external storage without FlashCopy® or replication services. A software reclone might also be preferred if the source and copy nodes have significantly diverged in their non-replicated objects, the products they have installed, the level of the operating system fixes, or the operating system release level. A software reclone is also an option to return to active replication in the event that a node is marked permanently suspended due to main store loss. A software reclone will ensure that all replicated objects are equivalent while not replacing non-replicated objects or system objects on the copy node.
A software reclone is done on an IASP basis. Unlike hardware reclone, it is possible to perform a software reclone on SYSBAS while leaving any database IASPs intact. It is also possible to perform a software reclone on only a database IASP. If SYSBAS and database IASPs all must be recloned, separate software reclones for each must be initiated.