|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Excellent example. Best way to compare our binding to the C programmer new to the 400. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Joe Pluta" <joepluta@PlutaBrothers.com> Sent by: rpg400-l-admin@midrange.com 12/11/2002 11:41 AM Please respond to rpg400-l To: <rpg400-l@midrange.com> cc: Fax to: Subject: RE: Can an RPG module call another RPG module? > From: alan shore > > Sorry, I sent the last e-mail before I was ready to. > The point I was trying to make was, if the modules etc are NEVER > migrated to the production area, there is no way to satisfy an > audit. (Been there, done that) If you can prove that the modules > etc were migrated to the production area, and that when they were > required again, they had been migrated back or accessed from the > production area, the auditors will be satisfied (been there done that) Do your auditors require source on the production machine? A module is no more relevant to the program object than is the source. In a completely secured environment, you would do neither compiles nor binds on the production machine, so you'd need neither the source nor the modules for auditing purposes. Think of it the same way you would a C program. You create a C program by linking together a bunch of .obj files. In a production environment, you'd never see those .obj files. My .02 _______________________________________________ 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.
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.