Comments on: Update duplicate record in rpgle

By: nasrunisar

nasrunisar — Fri, 27 Jul 2012 12:33:45 +0000

Thank you very much Tom, Got DB Rrn during each read operation thru INFDS and written into subfile ‘H’idden field (HRRN) and for update, used Chain with HRRN and update working fine. And for delete, pointer at *start setll and the file processed within Dow Not %EOF and compared delete screen fields with file fields, and the matching record deleted. Everything works fine till now as far as write, update and delete is concern. Now got some validations to perform. Once again I thank you vey much for your quick response.

By: TomLiotta

TomLiotta — Thu, 26 Jul 2012 21:47:51 +0000

Subfile Rrn and PF Rrn is not matching…

The subfile RRN is not the same as the PF RRN unless your program logic makes them the same.

You must retrieve the PF RRN (DB_RRN) from the device-specific-feedback area at the time the PF record is retrieved. You would store each DB_RRN in a ‘H’idden subfile field so your program knows which PF record to access later.

Tom

By: nasrunisar

nasrunisar — Thu, 26 Jul 2012 13:05:32 +0000

Subfile Rrn and PF Rrn is not matching while comparing after deleting any record, therefore giving errror update without prior input operation. Could any one suggest how to solve this issue.?

By: philpl1jb

philpl1jb — Wed, 25 Jul 2012 03:12:23 +0000

And that means putting the original field value into a hidden field or the relative record # into a hidden field.
Also you can change the Chain to a SETLL and read until all fields match the original values… then you have the record you want to update…unless someone else updates it before you get to it.

By: graybeard52

graybeard52 — Wed, 25 Jul 2012 00:30:43 +0000

Another option is to use SQL to update the record using criteria that makes it unique.

By: nasrunisar

nasrunisar — Tue, 24 Jul 2012 04:28:00 +0000

Thank you Tom and all, its updating correctly thru RRN.

By: TomLiotta

TomLiotta — Mon, 23 Jul 2012 21:52:53 +0000

Since there are no unique fields between the 3rd and 4th records except for F6, you would need all six fields as your key for any LF that you create. A possible better choice would be to grab the RRN of each row and store it as a ‘H’idden field in the subfile. When you are ready to update, use the RRN to CHAIN to the PF record, and update that record. Tom

By: Splat

Splat — Mon, 23 Jul 2012 14:48:18 +0000

This is why I use logical views for display sequencing and physical RRN for updating.

By: nasrunisar

nasrunisar — Mon, 23 Jul 2012 13:10:36 +0000

Thank you Charlie,
1. Create a new LF where the key would be unique. = In this option what would be my key fields. Are the same field1, 2 and 3 will be the key fields?
2. In the hidden fields only the record will be available right? Could you please send me some sample code?