Re: QTEMP not in library list

vhamberg wrote:

Scott's comment was about whether QTEMP should be in the library list - not whether to use it for temporary objects. You've responded with saying he says NOT to use QTEMP at all. He did not say that.

Vern:

Right on.

I keep getting the uneasy feeling that there's an unspoken belief floating around that QTEMP must be in the job's library list in order to use it.

However, the simple fact is that QTEMP exists in each job regardless of its being in the library list or not. Also, QTEMP can be used for (temporary) objects regardless of its being in the library list or not. It is only that _unqualified_ references use the library list that the issue makes much difference.

The confusions that have come out of this thread are... confusing. I'm not sure what it says about "general practices". Scott's statements seem supported by the ways that the thread has gone.

Writing for a software house affects how these types of issues are perceived. We never know what environment our programs might run within. And we can't easily 'force' our preconceived notions about 'best practices' on a customer.

It's something of a trick to recognize when I'm coding according to what "I" think is best and then to discard that technique because it simply might not work on an unfamiliar system.

I once ran across a customer who didn't use the QSTRUPPGM system value. THAT threw a nasty little twist into an installation routine! (But I learned a LOT along the way about what that system value really did.)

Tom Liotta