RE: Can an RPG module call another RPG module?

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
While I could quibble about this, these are good points.  And I appreciate
this effort.

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




Evan Harris <spanner@ihug.co.nz>
Sent by: rpg400-l-admin@midrange.com
12/12/2002 01:22 PM
Please respond to rpg400-l

        To:     rpg400-l@midrange.com
        cc:
        Fax to:
        Subject:        RE: Can an RPG module call another RPG module?


It ensures that source is available to recreate any production object
without recourse to another system (security in the D/R sense).

It ensures that objects are not compiled and migrated with QSECOFR or
other
adopted authority except where absolutely critical and approved.

It ensures that all programs can be scanned and checked for good security
practises (eq qualified calls to operating system commands)

It ensures that the source of the production objects can be independently
audited and checked and verified as what is actually in production.


>Again, how does keeping the source on the production machine make you
more
>secure?
>
>Rob Berendt
>--
>"They that can give up essential liberty to obtain a little temporary
>safety deserve neither liberty nor safety."
>Benjamin Franklin

_______________________________________________
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.