| # Validate Collection (ttpmc1402s000) Use this session to validate a collection. A collection must be validated before the Export Collection (ttpmc1210s000) session can export the collection. The validation performs these actions: Checks whether the dumps of the solutions are present in the Path for Export Dumps directory that is specified in the Parameters (ttpmc0100s000) session. The dumps of the solutions are placed in this directory when the solutions are exported individually, which you can do through the Export Solution/Patch (ttpmc1200s000) session. Checks whether the status of the solutions is Released. Checks if any solution in the collection has a post-requisite relation with another solution, or a co-requisite relation with another solution in the same base VRC, and whether the solution with which this relation exists is also part of the collection. If you export a collection, the Validate Collection session starts automatically. If any of the checks fails, the export stops. You can also use the Validate Collection session manually from the appropriate menu of the Collections (ttpmc1503m000) session. Related topics PMC introduction PMC overview PMC distributor procedure Base VRC A means in PMC to identify products in a unique way. Updates at the distributor side are provided with the base VRC identifier. A base VRC can contain the code of the physical VRC in which the related master product is installed, for example, B61_a, but can also be a code not related to a physical VRC, for example, 7.6_a_tt. At the recipient side, every update VRC is linked to a base VRC identifier. The installation process checks if the base VRC identifier of the update matches with the base VRC identifier of the update VRC. If not, you cannot install the update in that update VRC. Collection Code A unique identification of the collection in the base VRC. Collection Status The following statuses describe the progress of the maintenance of solutions, Collections, and patches. To keep the descriptions readable, only solutions are described. However, in each case, collections and patches are intended as well, unless explicitly excepted. The status of the solution is only used at the distributor side. A history of status changes is recorded in the Maintenance History table. To distinguish maintained solutions at the distributor side from imported solutions at the recipient side, the status is cleared when the solution is imported. This also applies to patches, but not to collections. The reason is that a collection is not known as such at the recipient side. Only the solutions contained in the collection are known at the recipient side. In progress The initial status of the solution upon creation. Dependencies defined The dependencies between the various solutions are defined, and the solution is ready to be exported. You must select this status manually, because you might want to create dependencies that cannot be created automatically. Exported The solution is exported. The system handles this status. You cannot set the status manually. However, you can set a solution with the status Exported back to In Progress, Solved, Completed, or Dependencies Defined. If you change anything in an exported solution, the status is always set back to Dependencies Defined, and you must export the solution again. Before you can release a solution, the status must be Exported. Released The solution is released, which means that the solution is frozen. You can no longer change anything in the solution. To release a solution, you must change the status from Exported to Released, and you must save the solution with this status. Validate Validates the collection. |