Re: Creating a physical AND Logical file

[Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx>]

I agree.  It also makes good sense to clear QTEMP once your job has 
completed.  One thing that has not been mentioned is that if you run the 
job in batch, there is no possibility of the files stepping on each 
other.

Turnidge, Dave wrote:
> 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.