Replies

[Bill Graziano <Bill.Graziano@xxxxxxxx>]

Thanks to everyone who replied to my questions about subfile locking and
file journaling. As always, your suggestions and recommendations were very
helpful.

Sincerely,
Bill Graziano
****************************************************************************
****************************************************************************
***
> I was looking at an RPG/400 example for a subfile program which UPDATES a
> file. In the example, an "N" was placed in the H/P/N column to indicate
> that the Read statement not lock the record while the subfile was being
> loaded for display. I realize that there is no reason to lock the file
> until the update is going to be performed. However, I have also looked at
> RPGIV examples in which this was not indicated.
> 
> Is this common practice while loading subfiles before the update is
> executed?
> 
> What is the RPGIV equivalent of this example?
> 
****************************************************************************
****************************************************************************
***
 I have a file that is being written to an excessive number of times. For
example, one record should be written for each of 40 business locations.
Instead of one record, as many as 400 records are being written for some
business locations. I am trying to pin down when and by which program are
the records being written. According to my system administrator, journaling
did not help determine this. I believe that I need to add a physical file
trigger and write a trigger program. 

        I have not written any trigger programs and need some suggestions. I
have identified the file update program. What I need to know is when is this
update program being
+---
| 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
+---