RE: Creating a physical AND Logical file

There was a mention of something you said about this - but I must have
missed it in going through the GLUT of emails... I don't want to run up
against the "Rob", but in every place I have worked, all applications I
have developed, any thing else I have done, putting QTEMP at the end of
the library list would break MANY things. Other than the development
scenario mentioned in another email, having QTEMP anyplace but at the
top of the USRLIBL would break nearly every application running here. 

Maybe the difference is the definition of WHY/HOW QTEMP is used at
different sites. Never having experienced any other purpose for QTEMP, I
can't speak to the other definitions. If it was me, and I had Alan's
problem, the programs would have been fixed so that the SAME NAME would
not reference two different files (at least...).

Dave

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, January 12, 2007 9:38 AM
To: Midrange Systems Technical Discussion
Subject: RE: Creating a physical AND Logical file

Perhaps it was a programming error - created the file in qtemp and
didn't bother to delete it when done.  They might have assumed that
their program was to be run in a simple batch job and it would be
automatically deleted when done..  However a belts and suspenders
approach still suggests that if you put QTEMP at the end of the library
list you reduce the possibility of this happening.  Everyone knows that
I shouldn't point a gun at someone when hunting but it doesn't stop me
from unloading the gun when crossing a fence as a safety measure.

However 

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Turnidge, Dave" <DTurnidge@xxxxxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/12/2007 10:28 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Creating a physical AND Logical file






Sounds like a programming error to me... And then the baby got thrown
out with the bathwater - instead of fixing the bathwater...

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Friday, January 12, 2007 9:22 AM
To: Midrange Systems Technical Discussion
Subject: RE: Creating a physical AND Logical file


Dave - with users signing on the first thing in the morning and not
signing off till they leave (sometimes they forget) and doing a
multitude of tasks throughout the day, creating a multitude of temporary
files form different jobs that they run, QTEMP will always be present.
Now the chances that a file created in QTEMP from a program written by
programmer Fred Bloggs has exactly the same name of a file from a
different program written by Joe Schmo  are slim, however, that being
said, I can verify that in one of my earlier positions, this has
happened three times. The first 2 times, we couldn't duplicate the
problem the user was seeing. The third time we drove over to her office
and lo and behold, the program was picking up a temporary file that had
been created in QTEMP (which was at the top of her library list) with
the same name as a PRODUCTION file in the PRODUCTION library list. At
that shop it was determined that QTEMP should be placed at the bottom of
the library list, and if a temporary file needs to used, define the
library name QTEMP as well.



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx


midrange-l-bounces@xxxxxxxxxxxx wrote on 01/12/2007 10:02:49 AM:

I guess in 35+ years I've never written ANYTHING that expected QTEMP 
to be anywhere but at the top. Currently we create application data 
areas that are created from template data areas in "production". The 
QTEMP ones are changed to match the current needs of the job. Job ends

- data areas gone. No *LIBL issue at all. If QTEMP doesn't contain 
information that is supposed to be unique to that specific job I don't

see any other purpose for it.