×
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.
Some other comments on QTEMP:
1. It isn't a "real" library, at least not in the sense
that QGPL is a "real" library. The differences are
normally quite transparent to HLLs, and to
properly-written applications; at the MI level and below,
they are NOT transparent. I'd go into detail, but I'm on
vacation.
2. It exists for the duration of the job. For interactive
use, that means the duration of the terminal session. It
does not get passed on to submitted batch jobs.
3. Somebody suggested that one cannot access another job's
QTEMP "without some MI." In fact, it goes well beyond
that: you can't do it without circumventing security.
4. "That's what it's there for." That is to say, QTEMP
exists specifically to provide a place to put QSYS objects
that are to be used exclusively by a single job, kept
private to that job, and are to evaporate when the job
does.
--
JHHL
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
