RE: QTEMP not in library list

["Crispin" <cbates@xxxxxxxxxxx>]

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.