|
I have to echo Mark's sentiments here. There have been three times over the last year where near-disaster (at least in terms of time spent tracking down a problem) was averted by being able to see exactly that information on a module. You might say that proper object management would prevent these issues, but sometimes things happen (especially during upgrades and disaster recovery) where this information is great to have. Joe
From: Mark S. Waterbury "WARNING, WARNING, DANGER WILL ROBINSON!" (arms flailing wildly) Please note that when you put source code in the IFS, you lose one of the most important features of OS/400, IMHO, that *PGMs and *MODULEs carry with them the name of the source file, library and member name and date/time stamp for the primary source member from which they were created. That feature has "saved" many companies in identifying the "correct" source for objects in "production" use. No other platforms have this feature built-in -- it is unique to i5/OS and OS/400, to my knowledge. IBM mainframe customers license expensive ISV products to add this functionality to the operating system.
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.