RE: work files in qtemp

I agree that files in QTEMP can be a pain...however; in my shop we have a
product called PEEKPLUS  (from BYTWARE).  With the product, we can "Grab"
control of any job (with permission) and copy those files out of QTEMP.  It
can also see the LDA & insert other commands into the job.  It's a great
'Fire Fighting' tool.

In the CL programs, I add in the code

Rtvusrprf  grpprf(&grpprf)

chgvar &templib 'QTEMP'
If    (&grpprf = 'QPGMR') then(chgvar &templib 'MYLIB')
Crtpf  &templib/TEMPFILE
Ovrdbf  TEMPFILE  &templib/TEMPFILE
Etc.

The advantage here is that for testing I don't have to run the job
interactively to get the file.

\Vincent

 -----Original Message-----
From:   rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joel Fritz
Sent:   May 17, 2005 1:44 PM
To:     RPG programming on the AS400 / iSeries
Subject:        RE: work files in qtemp


Ooh...that's a hot button subject for me. 

I don't care for work files in QTEMP.  In production support situations
I've had to fix jobs that used an work file there that was created by a
query or some other means where the file had no source.  If you need to
recompile a program it's more work than if you at least have source, or
even better, an empty template file.  At 2 AM I like to avoid thinking.
Getting out of bed and signing on is enough. <g>

There is a good use for work files in QTEMP.  When users need to run a
report that needs a work file and more than one will be doing it at a
time it's very convenient and easier to code than adding a member with a
unique name to a file and overriding. 

If you do use QTEMP I'd advise always using a template file and doing a
CRTDUPOBJ to create an image in QTEMP.  It's even a good thing for
queries.