RE: Creating a physical AND Logical file

I tend to write self-submitting CLs that will always run in batch, no
matter what. Therefore, when the job ends, QTEMP, and all of the objects
therein, are toast. In the unlikely event that an interactive
application has to create a file in QTEMP, first I do a CLRPFM, then a
MONMSG. If not found, I create it in QTEMP with no data. The file names
are specific to the program, so there won't be a conflict, and the file
doesn't have to be created more than once (just cleared after the first
round).

And QTEMP is at the top of the user part of the library list for
everyone.

Francis Lapeyre
IS Dept. Programmer/Analyst
Stewart Enterprises, Inc.
E-mail: flapeyre@xxxxxxxx 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wayne McAlpine
Sent: Friday, January 12, 2007 10:40 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Creating a physical AND Logical file

I meant deleting the temporary files (or clearing the library) once 
you're finished with them.

Turnidge, Dave wrote:

Sorry, that doesn't make any sense:  "clear QTEMP once your job has
completed". QTEMP is automatically cleared once your job has
completed... ???

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wayne McAlpine
Sent: Friday, January 12, 2007 10:29 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Creating a physical AND Logical file

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.