Re: Source Control (was:Can an RPG module call another RPG module?)

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
About the same guarantee that you have if the source is on the production
machine - none.  Oops, just reread your email.  Now I see the 'secured
from development team'.  I would compare the source date and time with the

DSPPGM PGM(ROUTINES/SRVPGM) DETAIL(*MODULE)
same as anyone.  Just in case your security isn't as tight as you think it
is.  And actually we had a tool that would compare these from our
source/production machine that we internally wrote.

However you could secure the source library on the development machine.
And then the only way to access it would be with your change management
software.  For example, you might have the following libraries on your
development machine:  PRODUCTION, TEST, ROB.  And then your change
management software would allow you to check something out to ROB, modify
it and test it there.  Then you could promote it to TEST.  Then promote it
to PRODUCTION, then promote it to your live system.  Other than securing
the PRODUCTION library (yet) on your DEVELOPMENT machine here, this is how
we do it with our Turnover software.  And you can control who can promote.
 I know there are some Turnover lurkers.  Perhaps they can comment if
their system has passed the stringent requirements of the banking
industry.  Silence shouldn't be considered an admission of failure,
perhaps just an underling fearing to make a corporate statement.

While this seems like an extensive set of libraries.  It might be useful
if, for instance, you want to QC it in the TEST environment before
promoting it to PRODUCTION on the development machine.  And your QC might
be someone else.

And Turnover will flag things that have been changed outside of Turnover.
For example, someone did a CHGPGM to USRPRF(*OWNER), or CHGPRTF..., or
some other thing.  We find this helpful instead of having to remember
multiple things like:  Oops, I have to compile this printer file with this
option to get it right.  Turnover remembers that.  Many others have
written their own MAKE tool.  The only problem we have with this feature
is that many SQL programs are modified by the OS themselves.  Something
about storing optimization in the program object itself when the program
is run.  This can numb you to some mods.

Do you have a tool which checks for missing and/or changed source?  And
hopefully run it before the backups of the source on your production
machine go out of rotation?

Alan,  part of our communication here may be because this last email,
while sent hours before some of my others, has arrived later.  Now, I have
been tagging my email to this list with a trace to see where the hangup
is.  David is pretty sure it is on my end.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"alan shore" <SHOREA@dime.com>
Sent by: rpg400-l-admin@midrange.com
12/13/2002 09:34 AM
Please respond to rpg400-l

        To:     <rpg400-l@midrange.com>
        cc:
        Fax to:
        Subject:        Re: Source Control (was:Can an RPG module call
another RPG     module?)


Rob -
Okay - my turn to aks a question. If the source is NOT migrated to the
production area, and secured from the development team, that means the
source resides on the development area. If a request is made to enhance
XYZ, what guarantee do you have/make that source XYZ has NOT been changed
for what ever reason since the executable has been migrated to the
Production region?
>>> <rob@dekko.com> 12/12/02 02:29PM >>>
This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Don,

I understand the argument in your second paragraph.  What I can't accept,
blindly, is that keeping my source on my production machine makes it more
secure.  Granted, having it both on the production and development machine
is shaky at best.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Fisher, Don" <Dfisher@roomstoreeast.com>
Sent by: rpg400-l-admin@midrange.com
12/12/2002 01:12 PM
Please respond to rpg400-l

        To:     "'rpg400-l@midrange.com'" <rpg400-l@midrange.com>
        cc:
        Fax to:
        Subject:        Source Control (was:Can an RPG module call another
RPG module?)


I believe the operative word in the requirement is "application", as
opposed
to "operating system".  I also imagine the requirement only applies to
applications used directly to manipulate financial information, which
would
exempt PC type applications.

By the way, you can argue the merits of the procedures all you want, but
government agencies are notoriously close-minded about disagreements. Once
they have a procedure in place, it stays that way because the time it
takes
to approve changes is measured on a geologic scale.

Donald R. Fisher, III
Project Manager
The Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@roomstoreeast.com

<clip>
>Hence the bank I work for REQUIRES that any vendors supply the sources
etc
with the application.
<clip>
Wow, how did you get IBM to give you the source for OS/400?  And
Microsoft,
too, for Windows?  Pretty Cool.
<clip>
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.