RE: Question about opening and closing files

Much of the time the old program is "moved" to QRPLOBJ - keeping some kind of pointer in jobs that were using it. Would it work to delete the object in QRPLOBJ, forcing the jobs to find the newer version? Or would the jobs crash?

Just wondering if there is a way around this kind of thing.

Vern

-------------- Original message --------------
From: "Kesterson, Randy" <RPKesterson@xxxxxxxxxxxxxxxxxxx>

Duane,

You are absolutely correct. We do realize the old program will be used if it
fired before the compile completed. But, as you said, most of the time the
change is minor and will have little impact on immediate situations. When we
need to make a significant change, then we make everyone get out while we
replace the programs. But then, that's what you'd be doing every time if we had
to do it to the trigger itself.

Thanks for pointing that out, though.

________________________________________________________________________________
______________
Randy Kesterson, Information Services
Market Transport Services - a UTi Worldwide Company| 110 N Marine Drive |
Portland, OR 97217 | USA
rpkesterson@xxxxxxxxxxxxxxxxxxx | D +1 503.978.4353 | O +1 503.283.2405 x353 | F
+1 503.978.4392

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On
Behalf Of Christen, Duane J.
Sent: Tuesday, September 09, 2008 6:06 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Question about opening and closing files

Randy;

Hopefully you won't learn the second lesson the hard way.

When you use an "intermediate" trigger program you are setting yourself up for
some possible pain. IBM didn't set triggers up to require an exclusive lock on
the triggered file to change the trigger program just because they felt like it.

Using an intermediate trigger which then calls another program(s) to do the work
can cause some real havoc when making modifications to the called program(s).
Any job that had fired the trigger before the change will still use the old
program(s), any jobs that fire the trigger after the change will use the new
program(s).

In most cases this may not be a big problem, but if you make fundamental changes
to the trigger program(s) you could cause some major headaches.

Duane Christen