Re: SQL history lost moving to new i

[CRPence <CRPbottle@xxxxxxxxx>]

  The library QRECOVERY is not part of B&R; explicitly excluded. 
The term "recovery" in the name is a reference to "recovery objects" 
which implement database related [for both non &] commit capable 
activity.  The chosen location of QRECOVERY for storage of the 
internal objects is a reflection that the STRSQL sessions are not 
intended to migrate to a new system, only exist [and probably be 
functional] on the same disk at an upgraded release.

  I gave an explanation of the library here:
http://archive.midrange.com/midrange-l/200803/msg01307.html

  If sav/rst could be effected for those internal objects, then one 
would have to be extremely careful to avoid restoring anything but 
the internal SQL session objects to avoid reflecting the current 
/recovery status/ of the saved-from system at the restored-to system 
for which any restore activity into that library causing problems 
would surely only be supported under a paid ConsultLine contract.

Regards, Chuck

Buck wrote:
> We moved to a new E4A a few weeks ago and everything went
> swimmingly. Even the spooled files got restored to the new
> machine.  Today, one of the developers tried STRSQL and
> discovered all her saved SQL statements are gone.  Stupidly, I
> tried the same thing and found mine are gone too.
>
> I say stupidly because I am well aware that they are stored in
> QRECOVERY and are accessible-ish via DMPSYSOBJ ISQLST* QRECOVERY
> TYPE(19) SUBTYPE(EE) I didn't think to dump the objects before
> accessing them and apparently on first touch they get reset.
>
> My question: How can I restore them so I can use DMPSYSOBJ?