× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: ALCOBJ and OPEN occurs?
  • From: "Bob Crothers" <bob@xxxxxxxxxxxxxx>
  • Date: Sun, 8 Nov 1998 15:02:54 -0500

Tim,

Actually, the suggestion about write a little rpg pgm that will read
the transaction file, write the record to the other file and then
delete the record from the transaction file is probably the best idea
that has been given so far.

It is both simple & safe.

Doing a copy and then clear (via CLRPFM or SQL) without an exclusive
lock on the file would cause problems of the worst kind.  Every once in
a while, when the timing is just perfect, you would loose a record.
These kind of problems are the hardest to find.

Bob

-----Original Message-----
From: Tim Truax <truax@usaor.net>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Sunday, November 08, 1998 2:35 PM
Subject: Re: ALCOBJ and OPEN occurs?


>Bob,
>This statement is correct, I checked the Softcopy book (DB2 for OS/400
Database
>Programming) and the CLRPFM does the exclusive lock automatically, but
the CPYF
>with *ADD doesn't do any lock from what I have read.  If used
improperly this
>could be the trouble.
>Thanks to all for the GREAT answers.
>
>
>Bob Crothers wrote:
>
>> Note that in your CLP, you will have to do an explicit alcobj
because I
>> don't think CPYF automatically does one.  But CLRPFM does.  So if
the
>> CPYF runs and you add a record before the CLRPFM, that record is
gone.
>>
>> Bob
>
>--
>Tok2YaLatR!
>Tim & Dana Truax and ... Caleb 5 yrs!
>
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator:
david@midrange.com
>+---
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.