Using the LANSA Repository provides significant benefits to the development of all applications, but in particular to client/server applications, which are often created by a number of different developers or end user department personnel.
By using the LANSA Repository, you gain:
The Repository information is not only available to an application, but in some cases it is actually enforced. Validation rules and security access, for instance, cannot be bypassed by an application. Whether the IBM i data is manipulated by a LANSA function or a client application via LANSA Open, the data must adhere to the validation rules and security requirements defined in the Repository.
If validation rules are not met, error messages defined in the Repository are sent to the client application through LANSA Open. If a validation rule, error message or help text is changed in the Repository, none of the client applications need to be changed or recompiled. New or changed rules and help text are picked up automatically.
Files defined in LANSA are standard IBM I files, accessible to non-LANSA applications. Only the extra LANSA Repository facilities, such as validations and virtual fields, help text, multilingual translation, and so on, are available to applications developed using LANSA, or client applications accessing the IBM i data via LANSA Open.
Conversely, files maintained by non-LANSA applications can be made known to the LANSA Repository. All LANSA's Repository facilities can be added to these files and used by the client application. This will not affect the original file at all.
Re-using Repository information by a number of applications creates a need for standards to be set and a commitment to be made to the use of these standards.
Some recommended standards are:
Guidelines for field and file standard names can be found in the LANSA Application Design Guide or the LANSA for i User Guide.