×
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.
Jim,
I completely agree with you. QTEMP is a great place for temporary
objects, such as user spaces, temporary files, user indexes, etc.
However, you don't need/want to have it in your library list for such
purposes. If your code deliberately creates a temporary user space in
QTEMP, then it shouldn't be using *LIBL to access it. It should be
using QTEMP (explicitly) to access it. At least, that's my opinion.
Please read the whole thread -- I'm repeating what others have already
explained very well.
http://archive.midrange.com/midrange-l/200801/threads.html#00630
Jim Wiant wrote:
I often use QTEMP for work spaces (like user spaces or user indexes)
that hold temporary data that only applies while the job is active. It's
data that I don't want to save, so I think QTEMP is a great space since
it's automatically cleaned up.
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.
midrange.com
