|
What does your job log show you, anything? DSPJOBLOG and hit F10 to display all and scroll down. The first thing I could think that would cause a record not to be written would be duplicate keys. Second would be library list issues. Third would be commitment control. Fourth would be program logic. Fifth would be bug in RPG. Regards, Jim Langston -----Original Message----- From: Andrew Goade [mailto:agoade@hubgroup.com] For the records it doesn't write normally, it writes them in Debug. Basically, I have a record, let's say it's record 123. I make a table change to 123, and it flows through my process. However, my record doesn't write to my file. Now, I put my process in debug. Again I make a change to 123. When I break at the write and F10 through it, the record now appears in my file. Now let's say that I enddbg and make a change to record 456. It flows through my process and writes to my file. This is not dependant on debug. It will happen this way before or after I start/stop debug.
As an Amazon Associate we earn from qualifying purchases.
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.