|
So what's the problem? Meaning does it stay stuck on the CHAIN forever?
If so, did you add a default wait time to either the file description or
the OVRDBF? (Is there a F spec keyword for that yet? or better yet a
chain extender?)
Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin
MWalter@xxxxxxxxxxxxxxx
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
10/24/2003 10:42 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
To
rpg400-l@xxxxxxxxxxxx
cc
Subject
Record Lock Problem
I'm having a problem trapping a record lock in a sub-procedure. Here is my
code:
dow 1 = 1;
chain(e) (sfitem:sfitwh) Itemblmc;
if ib_fileStatus = 1218;
reportLock(status:reply);
select;
when reply = 'R';
iter;
when reply = 'C';
stkcnt = 2;
msgDta = 'Could not load Cartons Per Pallet.';
sendMessage();
unlock(e) Itemasa;
unlock(e) Mbb2cps0;
return *off;
endsl;
endif;
leave;
enddo;
This code is in a sub-procedure.
Here is the Fspec and D spec:
FItembl UF E K Disk prefix(ib_) infds(ib_status)
Dib_status DS
D ib_fileStatus 11 15s 0
This is in the mainline code. I've tried Monitor, On-Error 1218. I've
tried %error and now the INFDS. None of the techniques trap the record
lock.
Thanks,
Mark
Mark D. Walter
Senior Programmer/Analyst
CCX, Inc.
mwalter@xxxxxxxxxx
http://www.ccxinc.com
_______________________________________________
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.