Re: QTEMP in LIBL (Was Re: OVRDBF problem or maybe it i searly Alzheimer's

Doesn't sound like a plausable reason to me. 
How are you going to end up with a rogue object in Qtemp? I think there is a
greater chance of somone putting a rouge in Qsys or Qgpl. But I could be
wrong.

Duane Christen

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Alan G. Campin
Sent: Wednesday, July 12, 2006 2:27 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] QTEMP in LIBL (Was Re: OVRDBF problem or maybe it
isearly Alzheimer's

This brings up a question I have wondered about.

I also always thought that QTEMP should be at the top of the user

portion 

of the library list.  What is the logic for placing it at the end of

the

list instead of the beginning?

I suspect this discussion should be in Midrange-L but here goes. 

I always thought that it should be at the top too until recently
discussing issue with my boss and he brought up point that having at the
top introduces security risks. Someone can place a rogue object in the
QTEMP and it gets found instead of the real object. 

The solution is to keep the QTEMP in the bottom of the list and to
always reference the QTEMP explicitly.