Paul Gilmartin wrote:
On Tue, 18 Mar 2008 10:53:44 -0500, David Eisenberg wrote:
Yikes!
Our programmers occasionally ZAP a load module in a test load library, which is
fine. When the time comes to promote the load module into a production load
library, however, I would like our change management package to prevent the
promotion of any load module which has been zapped. I'm prepared to do that
check programmatically via an exit, if I have a reasonable way of doing it.
Extract a secure checksum (e.g. SHA-1 from ICSF) when the load
module is generated, and verify it when it is moved into the
production load library. RACF protect the following: [...]
I like RACF, but in this case it is better to use some "changeman"
package (Changeman ZMF, Endevour, etc.). In such scenario programmer
provides a *source* and team leader (whoever responsible for the code)
recompiles the code when promoting to upper environments. The roles and
datasets can be RACF-protected, however it is up to the changeman to
separater the duties and manage versions.
IMHO any other method is reinventing the wheel.
Just my $0.02
--
Radoslaw Skorupka
Lodz, Poland
--
BRE Bank SA
ul. Senatorska 18
00-950 Warszawa
www.brebank.pl
Sąd Rejonowy dla m. st. Warszawy
XII Wydział Gospodarczy Krajowego Rejestru Sądowego,
nr rejestru przedsiębiorców KRS 0000025237
NIP: 526-021-50-88
Według stanu na dzień 01.01.2008 r. kapitał zakładowy BRE Banku SA wynosi
118.642.672 złote i został w całości wpłacony.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
