× 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: duplicate record Id's in multi user environment
  • From: "paul cunnane" <paul@xxxxxxxxxxx>
  • Date: Thu, 12 Oct 2000 09:41:01 +0100

Simple answer: a separate `next record ID' file.  The SQLRPGLE program reads
the one and only record in this file, increments the record ID and updates.
Because a record lock is held between the read and the update, there is no
way for two users to get the same record ID.

If you have more than one file requiring unique record IDs, the `next record
ID' file can have multiple records, keyed by file name.

--
Paul

> What would be the best way to assign unique record Id's in a multi user
> environment? Since, we have about ten users who add records to same file
> almost at same time. Chances are high that more than one user try to add a
> record at same time. The file should only have unique record Id's.
>
> Our users access this file through a client server application
> (power builder). The client server application calls a stored procedure
> written in SQLRPGLE to add the records to file.


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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 ...

Replies:

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.