| | Validate Patch (ttpmc1401s000)You must validate a patch or Feature Pack before you can
export the patch or Feature Pack by means of the Export Solution/Patch (ttpmc1200s000) session. The validation performs these actions: - Checks whether the dumps of the solutions are present in the Path for Export Dumps directory 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, which can only be the case if the solution was
exported.
- Checks if any solution in the patch has a post-requisite dependency relation with another solution,
and whether the other solution is also present in the patch.
- If any solution in the patch has a co-requisite relation with another solution, whether the
other solution is present in another patch, and a co-requisite relation is defined between the current
patch and the other patch.
For Feature Packs, the validation performs these additional
checks: - The patch header must be present.
- The installable unit key name and the version of the base VRC
must be present.
- The prerequisite to the preceding Feature Pack must be
defined.
- All solutions created in the previous Feature Pack must exist
as obsolete solutions in this Feature Pack.
If you export a patch or Feature Pack, the current session
starts automatically. If any of the checks fails, the export stops. You can
also run this session manually from the appropriate menu of the Patches (ttpmc1501m000) session. 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. 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.
New Base VRC If this check box is selected, the patch is a
Feature Pack. | |