| # Solutions (ttpmc1100m000) Use this session to maintain solutions. The scope of this session covers the life cycle of a solution from the solution's creation to the solution's release. In this session, you can maintain the basic data of a solution. You can use this session to change the status of a solution manually under certain conditions. Note Check out and check in is not restricted to the Current Package VRC. You can check out or check in all components for which you are authorized. For check out you need the following authorizations: VRC authorization Module authorization Language authorization Authorization for components of which you are not the developer. These authorizations are specified in the Developer Authorizations Template. For check in the same authorizations are required. You can only check in components that were checked out by yourself. The check out and check in functionality displays a message with the number of components for which you are not authorized. 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. 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. Solution Code A unique identification of the solution in a base VRC. The solution code has the following characteristics: Datatype: alpha-numerical string. Maximum length: 14 characters. Forbidden characters: All characters that have a special meaning in UNIX, such as $, *, and so on. If you specify a forbidden character, the code will not be accepted. Obsolete Solution This check box identifies a solution as an obsolete solution. 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. Patch If the solution is also part of a patch, the patch code appears in this field. Published If this check box is selected, the solution is published immediately upon release. If a solution is published, the solution is copied to the directory specified in the Path for Published Solutions field in the Parameters (ttpmc0100s000) session. Note If the Copy Published Solutions check box in the Parameters (ttpmc0100s000) session is cleared, the solution cannot be published, regardless of the selection of the current check box. Text If this check box is selected, a text appears with additional information. Click Text to add, read, or change the text. Patch The code of the patch to which a solution can be linked. Note To select a patch for this field, you must start the current session from the appropriate menu of the Patches (ttpmc1501m000) session. Defects by solution Starts the Defects by Solution (ttpmc1110m000) session. Print Solution/Patch Starts the Print Solution/Patch (ttpmc1400m000) session. Print Maintenance History Starts the Print Maintenance History (ttpmc1460m000) session. Print Dependencies (Multi-level) Starts the Print Dependencies (Multilevel) (ttpmc1440m000) session. Components by solution Starts the Components by Solution (ttpmc1520m000) session. Check-in Check-out Dependencies Starts the Dependencies (ttpmc1140m000) session. Generate Dependencies Starts the Generate Dependencies (ttpmc1240s000) session and sets the status to Dependencies Defined. Validate Solution Starts the Validate Solution (ttpmc1404s000) session. This option validates a solution before the real export. It checks, for example, if components are available, or if components are not compiled in debug mode, and so on. Link Solution to Patch Links the solution to the patch that appears in the Patch field. This option is only available if the Patch field displays a patch that is not yet released. The solutions you want to link must be released. This option is only available if you start the current session from the appropriate menu of the Patches (ttpmc1501m000) session. A solution can only be part of one patch. Remove Solution from Patch Removes the solution from the patch that appears in the Patch field. This option is only available if the Patch field displays a patch that is not yet released. To select a patch, you must start the current session from the appropriate menu of the Patches (ttpmc1501m000) session. Export solution Starts the Export Solution/Patch (ttpmc1200s000) session. This option is only available if the Status of the solution is Dependencies Defined. Note that the session that starts has no user interface, and that the solution is exported immediately. Export Solution Multi Level Starts the Export Solution Multi-level (ttpmc1202s000) session. This option is only available if the Status of the solution is Released. Note that the session that starts has no user interface, and that the solution is exported immediately. Maintenance History Starts the Maintenance History (ttpmc1560m000) session. Change Current Package VRC of User Starts the Change Current Package VRC of User (ttadv0140s000) session. |