×
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.
After reading these I've come to this belief - Unqualified references to
objects in QTEMP should never be in production code.
If you mean QTEMP/MYWSSESS for a file, then say QTEMP/MYWSSESS. Don't
assume that the only copy of MYWSSESS is in QTEMP, or, that QTEMP is at
the head of the library list.
If you mean myprodlib/MYWSSESS for a file name then it's ok to use the
library list, and, if you have to have QTEMP in your library list, then
put it at the bottom. You could do what many vendors do and access a data
area that says what the name of your file library is and qualify your file
openings with that. (Pros and cons to that.)
If you want to inject a library above production to test a program, or
file, then that should only be done under tight conditions where you put
that library higher in the library list only for the brief time of
testing.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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
