|
Dave, It's not that hard to write a "simple" change control system. You need a database to track who has what checked out, a wrapped around cpyf to check source members in and out, and a wrapped around crtdupobj (assuming single system) or savrst (multi-system) for promotions. Now, in fairness, even this "simple" system will take you a while to build and get correct, and it sure won't have all the bells and whistles of commercial systems, but it may due. However, since you also state that you are "Interested to hear especially from any financial institutions" I wonder what your internal (or external) auditors would have to say about any change control that is less that production-quality. Also, unfettered access to production data, source and object could cause problems for compliance with GLBA, SOX and numerous state data security regulations. -Walden ------------ Walden H Leverich III President & CEO Tech Software (516) 627-3800 x11 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
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.