|
midrange.com
CPF5032 Sender copy 30 03/06/07 10:41:06.842288
QDBSIGEX QSYS 01D6 QDBSIGEX QSYS 01D6
Message . . . . : Record 26697
member OESECTL already locked to this job.
Cause . . . . . : The record in
record format OESECR01 member number 1 of
file OESECTL in library NATLIB is
already locked to this job. Recovery . .
. : The Display Job (DSPJOB)
command can be used to display the record
locks held by the job. Wait
until record number 26697 in member OESECTL
file OESECTL in library NATLIB
becomes available. Then try your request
again. If no menus or commands
are available for you to release the lock on
the record, report the problem
(ANZPRB command). The error code is 1. If the
error code is 1, then this error
occurred in a trigger program. If the error
code is 2, then this error did
not occur in a trigger program. If the error
code is 3, then the record was
locked to another thread within this job.
Possible choices for replying to
message . . . . . . . . . . . . . . . : C
-- The request is canceled. I --
The request is ignored. Technical
description . . . . . . . . :
Message CPF5032 is sent whenever an attempt
is made by a job to get a record
for update, but the record has already been
locked to the same job by a
previous get for update. This lock will not be
released until the record is
updated, and the update option is released, the
code is 3, then the record was
locked to another thread within this job.
Possible choices for replying to
message . . . . . . . . . . . . . . . : C
-- The request is canceled. I --
The request is ignored. Technical
description . . . . . . . . :
Message CPF5032 is sent whenever an attempt
is made by a job to get a record
for update, but the record has already been
locked to the same job by a
previous get for update. This lock will not be
released until the record is
updated, and the update option is released, the
record is deleted, or the lock is
released with a release instruction. If
these menus or commands are not
available to you, there is no recovery.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of McGovern, Sean
Sent: Thursday, March 08, 2007 9:32 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Triggers 101
What error are you receiving in the joblog ?
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Turnidge, Dave
Sent: 08 March 2007 15:15
To: RPG programming on the AS400 / iSeries
Subject: Triggers 101
I am attempting to get our triggers under control and have run into what
I *think* is a problem. It has to do with record locks, and the
discussion we had recently which also included a record lock discussion,
didn't seem to answer my question.
We have an order entry program that updates/adds to file OETITLP. This
program ALSO updates a file OESECTP. OETITLP has a trigger attached that
ALSO updates OESECTP. I believe this is causing a lock issue when the
trigger attempts to update the SAME record in OESECTP that is updated by
the program.
It seems to be that a trigger should not be updating a file that is
being updated by a program that triggers the trigger. Or, maybe, the
trigger needs to be smarter and not run when the trigger is triggered by
said program.
Is there a SOP for this?
Thank you,
Dave
642-371-1163
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
