Source Control (was SQL is amazing )

[Frank Kolmann <Frank.Kolmann@xxxxxxxxx>]

Hi  Rob

When  set up properly a Source Control system is the ONLY way Production 
programs and files can be changed.
What is really strange is finding SQL indexes in Testing environments 
created over Production files.
I did use Implementer.  Dont recall if the version I had controlled SQL 
or perhaps I used it incorrectly.
I have no idea, but I assume Implementer has a SQL Index control?
Did not use QLMTDEVSSN , dont even know what it means.
SOX was not an excuse, but a reason to run I.T. in a way that was 
documented and properly controlled.
Why should I care about other platforms?

Frank


On 01/07/2022 6:55 am, Rob Berendt wrote:
> A source control system will only tell you the program has changed.  For example if you have a program called CRTSQLTBLS and you run that through source control change big whoop.  However if you run a SQLTBL source through proper change management, like PTC Implementer, it will track that the table has been changed.
>
> Also SOX can be used as an excuse to do a lot of strange things.  For example, those who use it as an excuse to use QLMTDEVSSN.  Really?  Where in SOX do you see that regulation?  How do you enforce that on other platforms?
>
> Rob Berendt
> -- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 
> 1600 Mail to: 7310 Innovation Blvd, Suite 104 Ft. Wayne, IN 46818 Ship 
> to: 7310 Innovation Blvd, Dock 9C Ft. Wayne, IN 46818