To configure VSCBefore you can start using VSC, you must complete some tasks. Step 1. Install VSC Before you can use VSC, you must generate the basic VSC settings.
The session executes the following actions:
Step 2. Change the VSC password The VSC password is used to limit the access to various administrative VSC sessions. The end-user sessions are not password protected. During the installation the VSC password is automatically set to "vsc". It is recommended to change this password immediately after the installation. To change the VSC password:
Step 3. Optional - Maintain the coding standards The LN Software Coding Standards (SCS) is a set of standards that define how each software component type must be coded. When you install VSC, these standards are generated in your LN environment. You can maintain these standards via the Coding Standards (tlvsc1150m000) session. Use this session only if you want to modify or extend the standards that were generated during the installation. For example, if you want to add new coding standard for a new type of session that you developed. Step 4. Optional - Create additional verification codes During the installation of VSC, one base verification code is generated. Optionally, you can add additional verification codes, for example if you want to perform additional checks, or if you want to test software components that belong to different package combinations. You can add verification codes in the Verification Codes (tlvsc1500m000) session. Step 5. Optional - Link additional package combinations to the
verification code(s) During the installation of VSC, one package combination is linked to the base verification code. To perform checks on components in other package combinations, you can link additional package combinations to the base verification code. To link package combinations to a verification code:
Note: You can also start the Package Combinations vs Verification Codes (tlvsc1501m000) session directly from the menu browser. Step 6. Define Verification Filter(s) During the installation of VSC, one generic verification filter is linked to the base verification code. This 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:
Optionally, you can define one or more specific verification filters. You can use a specific filter 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. Define a specific verification filter To add a specific filter to a verification code:
For more information, refer to the online session help. Note: You can also start the Verification Filters (tlvsc2510m000) session directly from the menu browser. Step 7. Define Source Analyze Codes You can link one or more source analyze codes to a verification filter. Source analyze codes are used 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. To create a source analyze code:
Note: For more information, refer to Source Analyze Codes. Step 8. Link Source Analyze Codes to the generic verification
filter To make sure that the checks defined in a source analyze code's expression are executed, you must link the source analyze code to the generic verification filter. To link source analyze codes to the generic verification filter:
Step 9. Optional: Modify Source Analyze Codes for specific
verification filters The source analyze codes that are enabled for the generic verification filter, are also executed for all specific verification filters. In a specific filter, you can indicate for each source analyze code whether you want to generate:
To specify that VSC must generate "Non-filtered" warnings:
Note: you cannot add extra source analyze codes in a specific filter. If you select an analyze code, which is not enabled in the generic filter, VSC ignores this analyze code.
| |||