× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



No, I couldn't say it was INV500. But I could pretty safely say it was a program where the file was internally described, and so it would probably NOT be a BPCS program. I could then do a DSPPGMREF to find the programs that use the file and go from there.

(NOTE: I suppose technically these days it could be someone writing to a file from a data structure to an externally described file. Not sure if an uninitialized data structure would write garbage in that case.)

It depends on your circumstances, I guess. Via DSPPGMREF I know which programs update which files. I also have journaling. Between those two, it's relatively simple to determine which programs are the likely suspects. YMMV, but for me having what is in effect a warning message would be perfect - the system would continue to act as it had in the past, but would alert me to the problem so that I could find the issue. Perfect!

Joe

True, determining which files have bad data is a huge undertaking. However
once you identify the file that is corrupt determining where it got
corrupted isn't quite so simple. For example, let's say your IIM file in
BPCS had bad data. Can you then safely say "then it must be program
INV500"?

See my previous comments in this thread about tools to see where a file
gets updated.


Rob Berendt


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.