Re: Trigger blocks our AS400 applications
- From: "caura" <caura@xxxxxxxxxxxxxxxx>
- Date: Sun, 16 Jul 2006 04:56:04 GMT
Dieter,
the trigger is a simple RPGLE pgm.
(created with actgrp(*caller).
On the trigger I didn't even specify a locklevel *All.
It gets the record parm and writes a logfile containing some controlefields
(user/timestamp/...) plus the recordstring.
We changed the trigger pgm to a simple CLLE that just sends a message.
Same behaviour.
I too suppose it's a bug and we did contact IBM.
They said it was a highlevel issue for them,
but since then we didn't hear from them
(the only thing they have sent back was a msg with a description of the
problem
and the question wether they had well understood the problem)
So I'm looking for alternatives - if there would be any -.
PS: last PTF in the DB2 GroupPTFs is SI14558 (dd 13/03/2005)
luc
"Dieter Bender" <dieter.bender@xxxxxxxxxxx> schreef in bericht
news:aemfh2-eg6.ln1@xxxxxxxxxxxxxxxxxxxxxx
Hi,read
you didn't specify how you did create your trigger exactly, but even a
trigger with lock level *all would allow concurrent reads. the behaviourread-trigger.
seems to me to be a bug. What Group PTF level do you have for the database
(ptf sf99502)?
Dieter Bender
news.wplus.ne wrote:
Hi,
We need to log every access on a specific (main)-file of our system.
(not our choice, but a demand of a business partner)
The only way to accomplish this, that we know of, is using a
So we did some tests (V5R2).
If an application takes a record in Update-lock (non exclusive lock)
during a transaction,
and at the same time there is a (read)-Trigger actif,
no Query, Read, ODBC or whatever can read the File beyond that record.
=> CPF5027 "Record in use" ,errorcode = 2
job ####/user/$$$$$$$ was not waiting on a lock held by this job
If I remove the trigger, everything works as expected.
The indicated job is the one that has read the record for update.
"This job" did not take any lock.
Even worse, with not any used record (not in update nor in read),
if we want to access the file using a Join Logical file ,
the Read instruction blocks before any read has been done .
=> MCH3601, pointer not set in QSYS/QDBGETKY
RMVPFTRG and all reads work fine again ...
If I want to access the file (FLI) via a simple Query and a record has
been taken for update in another session
"runqry qry(*NONE) qryfile(FLI)" I get the error QRY5050 .
Commitment control with lock level *ALL is active .
The read-trigger apparently changes the commitlevel to *ALL ,
as for me, there is not any reason to do so.
Is there another way to log all accesses on a file (without affecting
other files in the database)
Is there any circumvention for this misbehaviour of the triggerlogic?
luc
.
- Follow-Ups:
- Re: Trigger blocks our AS400 applications
- From: Dieter Bender
- Re: Trigger blocks our AS400 applications
- From: Dieter Bender
- Re: Trigger blocks our AS400 applications
- Prev by Date: Re: Digital Signature and iSeries?
- Next by Date: Re: Trigger blocks our AS400 applications
- Previous by thread: Re: Digital Signature and iSeries?
- Next by thread: Re: Trigger blocks our AS400 applications
- Index(es):
Relevant Pages
|
