| Miscellaneous VSC Administrator Tasks |  |
| This section describes: How to delete VSC warnings. How to copy or move VSC warnings to another verification code. How to view and cleanup the session log. How to change the VSC password. For details on the sessions mentioned below, refer to the session help. To delete VSC warnings When you verify software components, VSC generates warnings. When you solve a warning, VSC automatically removes that warning. When you accept a warning, VSC moves the warning to the Accepted Warnings list. The warnings that are not solved and the accepted warnings are not removed automatically. To cleanup your system, you can remove (a part of) these warnings. To remove warnings, you must take the following steps: Step 1. Mark warnings for removal Run the Global Delete VSC Warnings (tlvsc3200m000) session. Among other things, you can specify ranges for the verification codes, component types, packages, modules, and software components for which you want to remove the warnings. The session does not remove the warnings, but marks the warnings for removal. Global Delete VSC Warnings (tlvsc3200m000) Note: Alternatively, you can run the VSC Global Delete for the expired and not found components (tlvsc3204m000) session. This session only marks warnings that belong to software components that are expired, or do not exist anymore. These warnings are not relevant anymore, and therefore you can remove them without any problem. VSC Global Delete for the expired and not found components (tlvsc3204m000) Step 2. Remove warnings Run the Actual remove deleted warnings (tlvsc3203m000) session to remove the warnings that are marked for removal. You can specify ranges for the verification code, component type and package. Actual remove deleted warnings (tlvsc3203m000) Note: the session only removes warnings that are older than 7 days. To copy VSC warnings to another verification code You can copy VSC warnings to another verification code. This is useful, for example, when you create a new verification code for a new software release. The new release is derived from the old one. Therefore, when you run VSC for the new release, VSC also verifies components of the old release. As a result VSC generates warnings, that were already accepted in the old release, again. In this situation it is recommended to copy the (accepted) warnings of the old verification code to the new one, so that you do not have to accept all these warnings again. To copy the warnings, you must run the Copy / Move VSC Warnings to other Verification Code (tlvsc3205m000) session. You must clear the Move Warnings check box. Copy / Move VSC Warnings to other Verification Code (tlvsc3205m000) To move VSC warnings to another verification code You can also use the Copy / Move VSC Warnings to other Verification Code (tlvsc3205m000) session to move VSC warnings to another verification code. This is useful if you want to rename a verification code. You must select the Move Warnings check box. To view the session log You can run the Session Log (tlvsc4500m000) session to list the components for which you have run VSC. This session displays: When and how often the VSC run is executed for a software component. The user that initiated the VSC run. Session Log (tlvsc4500m000) To cleanup the session log It is recommended to clean the session log on a regular basis. To clean the session log, you must run the Cleanup Sessions in Session Log (tlvsc4220m000) session. You can specify ranges for the package, module, component type, and so on. Make sure that the Real Deletion check box is selected. Cleanup Sessions in Session Log (tlvsc4220m000) To change the VSC password Various VSC sessions are password protected. Each time you start one of these sessions, VSC prompts you for the VSC password. You can change this password in the Change Password VSC (tlvsc0291s000) session. Change Password VSC (tlvsc0291s000) Note During the installation the VSC password is automatically set to "vsc". It is recommended to change this password immediately after the installation. |