|
OK good idea I will tell the manager about the cache. On Wed, May 13, 2015 at 3:50 PM, Hoteltravelfundotcom < hoteltravelfun@xxxxxxxxx> wrote: > I believe that they don't have journaling. I am working with i data but > mainly in Crystal reports. I have only writer 2-3 RPG reports in 2 years > and always in the test environment. > > On Wed, May 13, 2015 at 3:47 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> > wrote: > >> Do we take it from this that the files are not journaled? Because that >> would be the first place to look. >> >> I would also find some way to check if _only_ these records are missing. >> i.e. perhaps this is symptomatic of an ongoing problem that was never big >> enough to register before. >> >> >> Jon Paris >> >> www.partner400.com >> www.SystemiDeveloper.com >> >> On May 13, 2015, at 12:43 PM, Hoteltravelfundotcom < >> hoteltravelfun@xxxxxxxxx> wrote: >> >> > HI This is a general and long shot question. >> > >> > It seems we have lost 2 days of invoices from a particular file. >> > >> > How to research what caused this? >> > >> > Developers are the primary suspects of course or rather process of elim. >> > while most >> > devs would never do some of these I am trying to see what may have >> happened >> > and how to locate any logs of these: by all means let me know if my >> > thinking is completely >> > wrong and how it should be looked for. >> > >> > MY thinking is records get deleted by a dev if there is >> > >> > 1.any program (rpg/cl ?) that outputs to that file >> > 2. A Cpyf to that file, overlaying blanks i guess. >> > 3. command but a dltf would be halted bec logicals exist. >> > 4. Upddta. this shop uses upddta a lot, not just developers. but then it >> > has to be F23 and a lot of those. >> > >> > Thank you for any concrete info I acknowledge this is a fuzzy topic if >> this >> > is fully off topic please remove. >> > >> > Thank you, >> > Joe >> > -- >> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing >> list >> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx >> > To subscribe, unsubscribe, or change list options, >> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l >> > or email: MIDRANGE-L-request@xxxxxxxxxxxx >> > Before posting, please take a moment to review the archives >> > at http://archive.midrange.com/midrange-l. >> > >> >> -- >> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing >> list >> To post a message email: MIDRANGE-L@xxxxxxxxxxxx >> To subscribe, unsubscribe, or change list options, >> visit: http://lists.midrange.com/mailman/listinfo/midrange-l >> or email: MIDRANGE-L-request@xxxxxxxxxxxx >> Before posting, please take a moment to review the archives >> at http://archive.midrange.com/midrange-l. >> >> >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
