|
Hector - I can only speak for my experiences in the midrange world. I've worked for 6 companies that program on IBM equipment and 1 company that programmed on Unix (VMS). The size of the departments using IBM I was in ranged from 2 developers to 8 developers - all fairly small shops. None of them used any kind of change management or source control. The VMS shop had 30+ developers - they used PCVS and a home-grown package. I've been on a quest on here and other newsgroups and other listserves trying to find an affordable solution to control source revisions (package wide), change management (source-by-source level), and revision documentation. So far, most packages are either WAY too expensive or they're lacking in documenting changes. If you find something - PLEASE, PLEASE, PLEASE give me a yell. Thanks in advance - David Schopp WISDM Team Leader Computers Unlimited 2407 Montana Ave Billings, MT 59101 v:406.255.9500 f:406.255.9693 "Hector Sanchez" <hsanchez@driscollchildrens.org> wrote in message scfb824a.069@driscollchildrens.org">news:scfb824a.069@driscollchildrens.org... I work for a Children's Hospital in South Texas. We are a pretty small shop as far as the AS/400 goes. 3 programmers and 2 operators. I used to work for our Electric Utility and in a much bigger shop. None of the Programmers/Analyst had Security Rights to Change Live Objects, Source Code or Files. Everything was done in Test and we had someone in charge of Change Control to move everything over once we got the proper signatures. Recently we had an I/S audit and the auditors are requiring us to use some form of Change Control. The other 2 programmers are very much against this and so far we have avoided doing such. So my question is this, are most 400 shops small and dont do Change Control, or are we unique in not doing so? Hector Sanchez _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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.