| Warnings (tlvsc3100s000) |  |
| use.session.to handle warnings that VSC generates during the verification of software components. VSC generates warnings, based on the checks that are defined for the verification codes. This session plays an important role in the procedure to handle warnings. For details, refer to To handle warnings.
Fields | Description
Warning
Verification Code | The verification code for which the warning was generated.
Language | The language of the software component for which the warning was generated. This field is only filled for language-dependent components, such as forms, reports, menus and labels.
Package VRC (Version) | The version of the package VRC of the component, for which the warning was generated.
Package VRC (Release) | The release of the package VRC of the component, for which the warning was generated.
Package VRC (Customer) | The customer extension of the package VRC of the component, for which the warning was generated.
Component Type | The type of software component for which the warning was generated. For example: report, session, script, or DLL.
Component (Package) | The package code of the software component for which the warning was generated.
Component (Module) | The module code of the software component for which the warning was generated.
Component (Code) | The code that identifies the software component for which the warning was generated.
Sub Component | The subcomponent where the error occurs. Each software component type has its own types of subcomponents. Examples of subcomponents are: A form command in a form. A field in a form. An index in a table. A text field in a table. A field section in a UI script. A choice section in a UI script. And so on.
Priority | The priority of the warning: high, normal, suspicious, or low. VSC automatically assigns a priority to each generated warning: The priorities for warnings that are generated based on source analyze codes, are defined in the Source Analyze Codes (tlvsc3111m000) session. The priorities for warnings that are generated based on all other types of checks are hard coded in the VSC software.
Category | The category to which the warning belongs. The following categories exist: General Tools Consistency Application Design Application Logic Standards Text Performance Integration Runtime Export.
Script Line Number | The line number in a script where the error occurs.
Message ID | The code that uniquely identifies the message that is assigned to the warning. For example: the message ID for a warning is 5053. The corresponding message text is "Function 'sleep' is not supported by Web UI ".
Description | The text of the message that is assigned to the warning, usually followed by "=>" and a hint for an alternate implementation. For example: `Function 'sleep' is not supported by Web UI => Disable the command` `Goto statements are forbidden => while, repeat, for`
Accepted | Select this check box to accept the warning. You must enter the reason for acceptance in the Description field. Clear this check box if you want to solve the warning. For example, VSC has generated the following warning: "Possible missing break in case statement". If this break is not missing, but left out on purpose, you can select this check box and accept the warning. If this break was left out accidentally, you must clear this check box and solve the warning. For more information, refer to To handle warnings.
Description | If you select the Accepted check box to accept a warning, you must enter the reason for acceptance in this field.
Rules Information
Short Description | A short description of the error that was found by VSC. For example:
    Presence of goto statements
Description | A more detailed description of the error that was found by VSC. For example:
    The use of 'goto' statement is forbidden.

    Exception: within #defines it is allowed. Sometimes it is needed (e.g. exception handling)
Motivation | The reason why the situation indicated in the error message is not correct. For example:
    'Goto' statements reduce the readability of script code dramatically.
Possible Solution | A hint for a possible solution. For example:
    Implement structured code (early return or if-then-else statements)
Example 1
Status | The status of the displayed example. For example: "correct" or "wrong".
Example 1 | An example that can help you to understand and solve the error.
Note | A note with additional information about the example.
Example 2
Status | The status of the displayed example. For example: "correct" or "wrong".
Example 2 | An example that can help you to understand and solve the error.
Note | A note with additional information about the example.
Example 3
Status | The status of the displayed example. For example: "correct" or "wrong".
Example 3 | An example that can help you to understand and solve the error.
Note | A note with additional information about the example.
Example 4
Status | The status of the displayed example. For example: "correct" or "wrong".
Example 4 | An example that can help you to understand and solve the error.
Note | A note with additional information about the example.