| Update VRC's (ttpmc2140m000) |  |
| use.session.to maintain the update VRCs. This session registers the update VRCs to which solutions can be connected. You can also link update VRCs to a VRC combination. For the Infor Enterprise Server (Tools) package no update VRC is used. Solutions for the Tools package are imported in the standard Tools VRC. You still must make the Tools VRC known in PMC. If a solution is connected to the update VRC, you cannot: Delete the update VRC. Change the base VRC of the update VRC. The following figure shows the form of the session: Related topics PMC introduction PMC overview PMC recipient procedure
Fields | Description
Package For Determining Derivation Structure | The package that is used as basis for the VRC derivation structure. Use the package with the most extensive structure.
Update VRC | A physical VRC at the PMC recipient side in which updates are installed. Every update VRC has a base VRC linked.
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. Note Do not connect a base VRC for the standard to an update VRC of a localization, or vice versa.
VRC Combination | A VRC Combination is defined at the PMC recipient side and consists of a set of related Update VRCs. The VRC Combination will guarantee that, if required, the related update VRCs are updated simultaneously at the PMC recipient side. In this way, you can avoid compatibility problems between related update VRCs. For example, if you use the standard application and you also have an extension installed, you will have two update VRCs defined. If a co-requisite dependency is defined between a standard solution and a solution for the extension, PMC installs both solutions in one run if you linked the update VRCs for both standard and extension in one VRC combination.
Commands | Description
Generate Update VRC structure | Starts the Generate Update VRC structure (ttpmc2240s000) session.
Delete Update VRC Structure | Starts the Delete Update VRC Structure (ttpmc2241s000) session. Use this session to delete an update VRC structure that is generated by the Generate Update VRC structure (ttpmc2240s000) session.
Patches by Update VRC | Starts the Process Patches (ttpmc2102m000) session.
Solutions by Update VRC | Starts the Process Solutions (ttpmc2101m000) session.
History Base VRCs | Starts the History Base VRCs (ttpmc2541m000) session.
Print Solution/Patch by Update VRC | Starts the Print Solution/Patch by Update VRC (ttpmc2401m000) session.
Print Dependencies by Update VRC (Multi-level) | Starts the Print Dependencies by Update VRC (Multi-level) (ttpmc2440m000) session.
Print Solution/Patch History | Starts the Print Solution/Patch History (ttpmc2460m000) session.
Compare Installed Solutions | Starts the Compare Installed Solutions (ttpmc2405s000) session.
Print Solution/Patch | Starts the Print Solution/Patch (ttpmc1400m000) session.