Re: Record locking

Could It be that the record does exist and you need to "..update.."  the "D"
status field back to an "A" status or whatever?  Maybe your program is deleting
(removing) the record when you exit the program, thus when you go back into the
program it will let you re-add it okay.  Also make sure your file DDS is not
..excluding.. the D records.





|--------+----------------------->
|        |          "Quazy"      |
|        |          <quazy@SoftHo|
|        |          me.net>      |
|        |                       |
|        |          05/31/2000   |
|        |          09:25 AM     |
|        |          Please       |
|        |          respond to   |
|        |          RPG400-L     |
|        |                       |
|--------+----------------------->
  >--------------------------------------------------------|
  |                                                        |
  |       To:     RPG400-L@midrange.com                    |
  |       cc:     (bcc: Darlene H Bryant/Banpharm)         |
  |       Subject:     Re: Record locking                  |
  >--------------------------------------------------------|






No the chain that locks up is trying to check to see if the record is in
existence with the deleted flag, and if it is there it does a update and if
it is not then I do a write.   Everything works fine if I delete the record
and then exit the program, and then go back in and recreate it.    The
problem is when I delete the record and then recreate the record without
exiting the program.


----- Original Message -----
From: "Jim Langston" <jlangston@conexfreight.com>
To: <RPG400-L@midrange.com>
Sent: Tuesday, May 30, 2000 5:14 PM
Subject: Re: Record locking


> It seems to me that you are trying to add a record that already exists.
If you
> do not delete the record, as you state, but just turn on a Record Deleted
type
> flag (we do the same thing in one of our files) then the record is still
there.  If
> you are not allowing duplicate keys, and the user "recreates it" then
arent' they
> creating a duplicate record?  And you would then be getting an error when
the
> duplicate record key was attempted to be written.
>
> I think what you actually want to do, is just change the Deleted Record
field back
> to not deleted and Update the record, not Write it.
>
> Regards,
>
> Jim Langston
>
> Quazy wrote:
>
> > I have a program that when a user deletes a record it just marks the
record for delete, that way all the data is all still there if we need to
get it back.   But if a user decides they did not want to delete the record
and recreates it before they exit that portion of the app they cant because
the record is still locked.   I have tried using the unlck command and I
have tried closing the file and opening it back up again but nothing seems
to work.   the lock gets hung up on a chain command.       Am I just doing
this wrong or what, any suggestions would be greatly appreciated.   Thanks
Chris
>
> +---
> | 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
> +---
>

+---
| 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
+---



+---
| 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
+---