Re: QRECOVERY library -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

I live and die by it sometimes.

In fact, I learned a while back that you have multiple levels of SQL history. I use that a lot, to the point where I have a standard procedure I do once every week or two (if I remember) to cycle through all the levels and save them into separate source members. Hmmm... that sounds like a good topic for a Tech Tip over at MC Press. :)

Joe,

I reference my SQL history often.
Once a 3rd party vendor was on our system via a WEBEX, and they accidently cleared my SQL history.
Argh.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Tuesday, December 19, 2017 6:04 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: QRECOVERY library

Thanks for this, Paul.

It seems (to me) to be an odd choice to store the SQL history in a "temporary" library. I suppose you could make an argument either way, but that looks like something you might want to have after a system crash and recovery.

Anyway, I'll put that on my "what I learned in 2017" list. :)

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.