Glossary for Tools Add-on

	Glossary for Tools Add-on hard reference A reference from one table to another table that is defined in the data dictionary. Antonym: soft reference hard reference See: soft reference multicompany environment A collection of companies. A multicompany environment is used to limit a table sharing set to a fixed set of companies. reference type See: reference rule A criterion to measure the quality of software components. The rules used by VSC are, among other things, based on the LN Software Coding Standards (SCS), the LN Software Programming Standards (SPS), and the LN Performance Guide. Some examples of rules are: A table code must have the following structure: pp mmm s xx, where pp is the package code, mmm is the module code, s is the submodule code (only when numeric), and xx is the sequence number. A message called in a script, should not be expired. A query that performs an update must have a 'with retry' clause. Most rules are hardcoded in the VSC software. However, some rules that are used to analyze scripts are implemented as source analyze codes. rule database A database with detailed information about rules. The rule database contains: Detailed information about the rules that are implemented in VSC. Information about rules that might be added in future VSC versions. This database is intended for internal use by the LN development department only, and is therefore not delivered with the VSC software. soft reference See: hard reference soft reference A reference from one table to another table that is embedded in a program script or dll. Antonym: hard reference source analyze code A code that is used by VSC to perform user-defined checks on scripts such as UI scripts, DLLs and DALs. Each source analyze code is linked to an expression text and to a warning message. The expression text contains a search pattern, which is used to find errors. For details, refer to Source Analyze Codes. table set A set of tables that is being considered for table sharing. By using the Table Sharing Modeler tool you can simulate what happens if these tables, and only these tables, are shared. You can have two kinds of table sets: A small table set which corresponds with a specific functional requirement, for example, central purchasing. You can use this table set to find out which other tables need to be shared because of table references. An extended table set that contains not only the tables that must be shared for functional reasons, but also all other tables that must be shared for technical reasons. You can use this table set to verify the completeness of the table set. You can also use this table set to do the actual table linking. Table Sharing Modeler A tool to analyze and set up a table sharing configuration that suits the purpose of the LN user without jeopardizing the data integrity. The Table Sharing Modeler is implemented in the Table Sharing Modeler module in the Tools Add-ons package. table sharing set A proposed table sharing configuration. A table sharing set contains a collection of table sets. The table sharing set defines for each of these table sets exactly which logical companies are linked to which physical companies. verification code A code that identifies a selection of VSC checks for software components in one or more package combinations. A verification code is usually linked to one or more verification filters. verification filter A selection of VSC checks for which warnings must be generated. A verification code usually is linked to one generic verification filter and one or more specific verification filters. The generic filter defines the checks that are executed to verify all software components in all packages. Depending on the filter settings, the checks in the generic filter can generate two types of warnings: "Filtered to Handle" warnings. You must handle these warnings immediately. You must either solve or accept these filtered warnings. "Non-filtered" warnings that you do not have to handle immediately. Specific filters are used to reduce the number of "FiItered to Handle" warnings for a specific package, module or VRC. Each specific filter is derived from the generic filter, and therefore executes exactly the same checks as the generic filter. In a specific filter, you can indicate for each check whether you want to generate "FiItered to Handle" warnings or "Non-filtered" warnings. Note: you cannot disable checks, or add extra checks in a specific filter. If you select a check, which is not present in the generic filter, VSC ignores this check. Verify Software Components A utility to perform a quality check on the software components, which are developed or changed in LN. Acronym: VSC VSC See: Verify Software Components warning A message that explains an error that is found during a VSC check. Depending on the verification filter settings, VSC generates: "Filtered to Handle" warnings. You must handle these warnings immediately. You must either solve or accept these filtered warnings. "Non-filtered" warnings that you do not have to handle immediately.