| | Patches (ttpmc1501m000)Use this session to maintain patches. 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. Export VRC The physical VRC from which components that belong to a PMC
solution must be exported at the PMC distributor side. Each base VRC has an export VRC linked, so components for
different products are exported from different physical VRCs. Base VRC Combination A Base VRC combination is defined at the PMC distributor
side and consists of a set of related base VRCs. A base VRC combination
controls the creation of co-requisites between base VRCs. You can only define
co-requisites between base VRCs that are part of the same base VRC combination.
Base VRC combinations prevent the unwanted creation of co-requisites between
base VRCs. Patch Description The description of the patch. New Base VRC This field is only applicable for Feature Packs. If this check box is selected, the base VRC is a Feature Pack; otherwise, the batch VRC is a patch. Patch Sequence Number The patch sequence number. You can only enter a value for
Feature Packs. For each new Feature Pack, you must increase the number by
one. 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.
Published If this check box is selected, the patch is
published. | |