1.3.4 Controlling Repository Content

While the benefits of a centralized Repository are clear, there is also a responsibility to control the contents to avoid the unexpected consequences of a change. For example, a new field validation rule will affect every function which accesses that field. If a field description is changed, it potentially impacts every screen that displays that field.

In order to maintain the integrity of the repository's contents, formal procedures for changes should be set up in advance:

• Define and publish site standards so that all developers understand how the maintenance of the repository will be done.

• Enforce development procedures by using LANSA security to limit access to specific development options such as creating fields or tables.

• Control and limit the access to the repository definitions so that changes are made in a controlled fashion and are being evaluated before they are made.

• Use the LANSA for i impact analysis tool or the Visual LANSA Repository Find to review how a change will affect your application.

When developing in a client/server distributed development environment, you may have multiple copies of the repository. In this case, it becomes even more important that proper procedures and standards are enforced.