Re: QRECOVERY library and its purpose on i5/OS

The visual representation of external objects presented by the request to DSPLIB QRECOVERY, is only a subset of the objects that will be in that library. Most objects residing in that library are internal objects; i.e. they are not externalized to the user, like with the interactive sessions for the STRSQL feature.

The QRECOVERY library is [or has become] effectively little more than a place where data can be placed, where there is never any intent to backup that data. There is no supported nor documented B&R for [objects in] the QRECOVERY library. Most objects in the library are a reflection of the /now/ about activity & state of the system. The origin for that library name is from the integrated database, due to its historical /recovery/ processing which is primarily to implement COMMIT and ROLLBACK of DDL; /historical/ because recovery is long since, specific to the context in which activity is being performed. Messages like CPF3245 and CPF325E are an indication that /database recovery/ has been encountered; typically a prior activity associated with a database object has been /interrupted/ and an operation against the same database object name is prevented pending completion [effective rollback or commit] of the prior incomplete operation.

The QRECOVERY library is created fresh with any scratch install. The library is not restored as part of the operating system, nor as part of install of options nor LPP [Licensed Program Products]. The SCPF joblog of a scratch install will reflect that objects were not found. The recovery for those conditions are to create the missing object. The code that encountered the condition of missing object, would most likely infer that the IPL\install is a scratch-install, or the code can at least probably safely act in that manner, given that the current state is unknown and would be tracked from that point.

Many people confuse the QRCL library with QRECOVERY. This is especially common after a reclaim storage request, when no QRCL library was created; many times, the contents of the QRECOVERY library have been named as what the reclaim _recovered_ :-(

Regards, Chuck