×
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.
Rob,
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.
In general, that's probably a good idea. But what if, for example, you have
a (CL) program that does some processing on a file. The application may want
to use that program for the QTEMP version of the file, or for an Application
library version of the file.
So, do you have two programs, one that uses *LIBL and one that qualifies
QTEMP. Or do you pass the library name to the program and use that to
qualify the library name (retrieving the object description at runtime to
resolve either QTEMP or MYLIB is just the same as using *LIBL).
What are you suggesting should be done in this sort of scenario?
*LIBL is there for a reason. Why have two versions of a program just to
stick to your rule?
Crispin.
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
