RE: File update after abnormal program termination

>From: Rich Duzenbury [mailto:rduz@westernmidrange.com]
>X-message-flag: Perhaps you should consider a less virus-friendly e-mail
client.

Haha. Very funny, but not too professional. I'm sorry that you disapprove of
my choice of e-mail clients, but perhaps you care to explain your reasoning.
I'm willing to trade that SMALL loss of security for the enhanced
capabilities of Outlook.

-Walden

------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com



-----Original Message-----
Received: from linux.midrange.com (207.224.38.113 [207.224.38.113]) by
neptune.techsoftwareinc.com with SMTP (Microsoft Exchange Internet Mail
Service Version 5.5.2653.13)
        id 171VCR7C; Mon, 25 Feb 2002 19:56:50 -0500
Received: from linux.midrange.com (localhost [127.0.0.1])
        by linux.midrange.com (8.11.6/linuxconf) with ESMTP id g1Q0tM017644;
        Mon, 25 Feb 2002 18:55:22 -0600
Received: from roadwarrior.vps.com (a98.westernmidrange.com [216.248.85.98])
        by linux.midrange.com (8.11.6/linuxconf) with ESMTP id g1Q0sA016187
        for <rpg400-l@midrange.com>; Mon, 25 Feb 2002 18:54:11 -0600
Received: from roadwarrior.westernmidrange.com [127.0.0.1] by
roadwarrior.vps.com (FTGate 2, 1, 2, 1);
     Mon, 25 Feb 02 18:55:59 -0600
X-message-flag: Perhaps you should consider a less virus-friendly e-mail
client.
Message-Id: <5.1.0.14.2.20020225184245.02fb8ec0@127.0.0.1>
X-Sender: duzenbury/westernmidrange.com@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
To: rpg400-l@midrange.com
From: Rich Duzenbury <rduz@westernmidrange.com>
Subject: Re: File update after abnormal program termination
In-Reply-To: <9C0D76BA2F7AD411953000805F8541473E3FF6@RGONTSERV4>
Mime-Version: 1.0
content-transfer-encoding: 7bit
content-type: text/plain;
 charset=us-ascii;
 format=flowed
Sender: rpg400-l-admin@midrange.com
Errors-To: rpg400-l-admin@midrange.com
X-BeenThere: rpg400-l@midrange.com
X-Mailman-Version: 2.0.8
Precedence: bulk
Reply-To: rpg400-l@midrange.com
List-Help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-Post: <mailto:rpg400-l@midrange.com>
List-Subscribe: <http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>,
        <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-Id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>,
        <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>
List-Archive: <http://archive.midrange.com/rpg400-l/>
Date: Mon, 25 Feb 2002 18:55:55 -0600
From: Rich Duzenbury [mailto:rduz@westernmidrange.com]
Sent: Monday, February 25, 2002 19:56
To: rpg400-l@midrange.com
Subject: Re: File update after abnormal program termination


Bummer.  I hate when programmers do that.

Poor mans solution: I suggest you lock the record.  Then, if the job is
somehow terminated, the lock will be removed by the system.  If it's not
feasible to lock exactly that record, then create a surrogate lock file,
write the key to the record there, and then lock it.  If you can lock it,
the record is yours.  If not, another workstation has it - if all programs
are coded to use the same access method.

Whether a database field, or a real record lock is used, you still have
decide how to deal with the 'user went to lunch with a record locked'
problem.

One vendors package that I know of clears the 'in use' flag every night at
midnight.  At least then all the records are available again in the morning.

Otherwise, try journaling and commitment control.  If the transaction is
unsuccessful, the system can be set up to roll back the change to the 'in
use' flag, as well as any changes not completed by that session.


>There are programs here that update a field in a file to indicate the
>record (and other associated records that do not have this field
>updated) is in use by workstation.  Trouble is, if the job is ended
>because of external factors like the terminal being shut down or
>communications between the terminal and the controller being
>terminated, we have to manually reset this field.

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.