RE: [SYSTEM21] Handling locked records in RPG

[Nuno Carriço <ncarrico@xxxxxxxxxxx>]

I think you can handle that trough he file exception subroutine (INFSR), you
must define the INFDS data structrure.
The error for record locked is 01218 if I'm not mistaken.

hope this helps

Nuno

-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx
[mailto:system21-bounces@xxxxxxxxxxxx]On Behalf Of Dan Thomas
Sent: terça-feira, 29 de Abril de 2003 21:24
To: 'SYSTEM21@xxxxxxxxxxxx'
Cc: Mike Dearmond
Subject: [SYSTEM21] Handling locked records in RPG


This might not be the correct forum for this question, but...
We have a modified version of OE340 (pick notes) that runs interactively.
We are having problems when it encounters a locked OEP40 record.  The
program is bombing.  Even worse, it the previous order created despatch
notes (INP57 records), the matching INP56 record is not written because it
isn't written until the next order is read.  We didn't have this problem
with original code, but it would seem if we can simply return control to the
program indicating the OEP40 record is locked (instead of dumping after 60
seconds) we could solve this problem.  I guess the other option would be to
read each OEP40 record first in Input only mode, check for active flag and
then re-read the record I-O if it isnt.

Any help is greatly appreciated.

Dan Thomas
Director of Information Technology
MDI
4500 Progress Blvd
Louisville, KY  40218
(502) 318-1208

_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.