RECON data set recovery

If an I/O error occurs on a RECON data set, DBRC tries to use an available spare data set. DBRC then copies the healthy RECON data set to the spare data set, and then activates the spare data set.

When other subsystems using the failed RECON data set complete their processing, you can delete and redefine the error data set so it can be used as a spare. If, however, you want to analyze the RECON error, you should allocate new space for the RECON data set, rather than deleting and redefining it.

If DBRC cannot locate a spare data set, all currently executing jobs continue to process using the RECON data set in single mode. DBRC allows new jobs to start with only one RECON data set if you specify the STARTNEW keyword on the INIT.RECON or CHANGE.RECON command (or the DSPAPI FUNC=COMMAND COMMAND=INIT.RECON or DSPAPI FUNC=COMMAND COMMAND=CHANGE.RECON API requests).