RE: work files in qtemp

Larry,
        Count me in as well
Bob Anderson
IT Guy
Kent Sporting Goods Inc.
New London OH
Ph: 419-929-7021 x315
Fax: 419-929-1380

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On
Behalf Of Larry Ducie
Sent: Tuesday, May 17, 2005 5:22 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: work files in qtemp


Hi Vincent,

<snip>
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.
</snip>

You wouldn't believe how easy it is to get hold of another job's QTEMP
objects. In fact you wouldn't believe how easy it is to get hold of another
job completely! A while back somebody told me you couldn't see/manipulate
objects in another job's QTEMP. Well that's a red rag to any programming
bull. :-)

By the end of the day I'd written three VERY simple CL commands (and a
couple of processing programs in RPG) that allowed me to take control of any
job in the system and then force it to issue any commands I sent it. (I had
some fun sending naughty break messages to one of my colleagues, from the
interactive job of another of my colleagues! Ooh the look on their faces!!!
Or sending a program call command and watching their faces as a screen
appeared!!!)

On a practical note...

Once, at 3am I got a call about an overnight finance batch job falling over
- a RPG program was trying to use a LF that should be in QTEMP (scoped over
the PF there). Normally that's unfixable - have you ever tried to create a
LF in another job's QTEMP, and scoping it over the PF there? BIG smile from
me, cancelled back to the CL, copied the LF into QTEMP of the batch job,
retried the call - 5 minutes later I was back in bed.

The commands I wrote are:
STRJOBCMD - here you specify the job you want to take control of.
SNDJOBCMD - here you send a command to that job. You can send as many as you
want.
ENDJOBCMD - here you release control.

I still use them when servicing a batch job and debugging it. If I get to a
point where I want to see what's in a file in QTEMP I simply send a command
to CPYF it into a production library. I can even amend the data and cpyf
(*replace) it back again. All this while sitting on a break point! Boy does
that make life easier.

Anybody who wants the source are most welcome. I'll even post the whole lot
on the list if it's something that might be of use to people - but believe
me, there is nothing to these programs.

Larry Ducie


--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.11.11 - Release Date: 5/16/2005

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 266.11.12 - Release Date: 5/17/2005