<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tt/pmc/ttpmc0100s000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Parameters (ttpmc0100s000)</Title>
		<Keyword ContextSensitive="No"><Level1>PMC</Level1>
			<Level2>parameters</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>recipient</Level1>
			<Level2>parameters</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>distributor</Level1>
			<Level2>parameters</Level2>
		</Keyword>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">You can use this session, as shown in the following figure, to maintain the parameters for the PMC module.</Paragraph>
		</AimSection>
		<GeneralSection><Paragraph class="Default">Several sessions in the PMC module require predefined data that is dependent on the environment. This data is stored in the parameter table. These parameters consist chiefly of the paths for import dumps and export dumps of solutions. If a directory does not exist, the directory is created after the user confirms.</Paragraph>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">If you do not use PMC Distributor, leave the fields in the <GUIRef href="" role="manual">Distributor</GUIRef> group box set to the default values.</Paragraph>
			</Note>
			<Figure space-and-orientation="indented-estimated"><FigIntro>The following figure shows the form of the session with the default field values:</FigIntro>
				<HTML:IMG height="354" width="691" SRC="../images/pmc_ttpmc0100s000.gif" path="/enterpriseserver/tools/tt/ttpmc" btb-count="1" btb-count2="1" btb-image-name="pmc_ttpmc0100s000.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_ttpmc0100s000.gif" ID="IDADJXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
		</GeneralSection>
		<RelatedTopics><SectionTitle>
                                 Related topics
                              </SectionTitle>
			<RelTopic><Link href="/baanerp/tt/onlinemanual/pmc_introduction" role="manual">PMC introduction</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/tt/onlinemanual/pmc_overview" role="manual">PMC overview</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/tt/onlinemanual/pmc_distributor_procedure" role="manual">PMC distributor procedure</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/tt/onlinemanual/pmc_recipient_procedure" role="manual">PMC recipient procedure</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldGroup><Title>Recipient</Title>
			<FieldHelp ID="ttpmc000.pisd"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Path for Individual Solution Dumps</Title>
				</Header>
				<FuncDesc>A directory in which individual solution dumps are placed during the scanning process at the recipient system. If a solution must be installed, the dump is read from this directory.</FuncDesc>
			</FieldHelp>
			<FieldHelp ID="ttpmc000.pund"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Path for Uninstall Dumps</Title>
				</Header>
				<FuncDesc>A directory in which dumps that are required to uninstall a solution or patch are placed. The <Link href="/baanerp/tt/pmc/ttpmc2205s000" role="session">Install Solution/Patch (ttpmc2205s000)</Link> session or the <Link href="/baanerp/tt/pmc/ttpmc2204s000" role="session">Check and Install Solutions (ttpmc2204s000)</Link> session creates these dumps. The <Link href="/baanerp/tt/pmc/ttpmc2208s000" role="session">Uninstall Solution/Patch (ttpmc2208s000)</Link> session reads the dumps from this directory.</FuncDesc>
			</FieldHelp>
		</FieldGroup>
		<FieldGroup><Title>Distributor</Title>
			<FieldHelp ID="ttpmc000.warn"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Attach components during check-out</Title>
				</Header>
				<FuncDesc>
                                    If this check box is selected, you are asked to which PMC solution a component must be linked, if a component that is not yet linked to a solution is checked out using Software Configuration Management (SCM).</FuncDesc>
			</FieldHelp>
			<FieldHelp ID="ttpmc000.idnt"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Insert PMC ident string in scripts</Title>
				</Header>
				<FuncDesc>If this check box is selected, and a <Link href="/baanerp/tt/glossary/glossary#progscript.tt" role="glossary">program script</Link> is checked out using SCM, an ident string containing the code of the solution is added to the source code of the script.</FuncDesc>
				<Note><SectionTitle>
                                       Note
                                    </SectionTitle>
					<Paragraph class="Default">This functionality is only available if the <Link href="/baanerp/tt/pmc/ttpmc0100s000#ttpmc000.warn" role="formfield">Attach components during check-out</Link> check box is also selected.</Paragraph>
				</Note>
			</FieldHelp>
			<FieldHelp ID="ttpmc000.pexp"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Path for Export Dumps</Title>
				</Header>
				<FuncDesc>A directory in which dumps are placed at the distributor side. The <Link href="/baanerp/tt/pmc/ttpmc1200s000" role="session">Export Solution/Patch (ttpmc1200s000)</Link> session places the dump in this directory. When you create a patch or collection, the individual solution dumps are read from this directory and concatenated in the patch dump, which in turn are placed in this directory.</FuncDesc>
				<Note><SectionTitle>
                                       Note
                                    </SectionTitle>
					<Paragraph class="Default">The solution file name is composed of the solution code and a constant suffix <Emphasis>.tar.gz</Emphasis>, for example, solution code 1005 becomes <Emphasis>1005.tar.gz</Emphasis>.</Paragraph>
				</Note>
				<Note><SectionTitle>
                                       Note
                                    </SectionTitle>
					<Paragraph class="Default">Collection dumps are placed in the Multilevel Export directory.</Paragraph>
				</Note>
			</FieldHelp>
			<FieldHelp ID="ttpmc000.pexm"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Path for Multi-level Export Dumps</Title>
				</Header>
				<FuncDesc>A directory in which dumps are placed at the distributor side. The <Link href="/baanerp/tt/pmc/ttpmc1202s000" role="session">Export Solution Multi-level (ttpmc1202s000)</Link> session places the dump in this directory. Exported <Link href="/baanerp/tt/glossary/glossary#100257" role="glossary">collections</Link> are also placed in this directory.</FuncDesc>
				<Note><SectionTitle>
                                       Note
                                    </SectionTitle>
					<Paragraph class="Default">The solution file name is composed of the solution code and a constant suffix <Emphasis>.tar.gz</Emphasis>. For example, solution code 1005 becomes <Emphasis>1005.tar.gz</Emphasis>.</Paragraph>
				</Note>
			</FieldHelp>
			<FieldHelp ID="ttpmc000.cpub"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Copy Published Solutions</Title>
				</Header>
				<FuncDesc>
                                    If this check box is selected, the dumps of solutions, <Link href="/baanerp/tt/glossary/glossary#100257" role="glossary">collections</Link>, or <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">patches</Link> that were marked as <Emphasis>Published</Emphasis> are copied to a separate directory immediately upon release of these dumps.</FuncDesc>
			</FieldHelp>
			<FieldHelp ID="ttpmc000.ppub"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Path for Published Solutions</Title>
				</Header>
				<FuncDesc>A directory in which dumps are placed at the distributor side when the solutions are published. This directory is a location from which you can copy the solutions, for example, to an external FTP server. Customers can connect to that FTP server to download the software updates they want to install. The <Link href="/baanerp/tt/pmc/ttpmc0100s000#ttpmc000.cpub" role="formfield">Copy Published Solutions</Link> field indicates whether or not this copy action must be carried out.</FuncDesc>
				<SimpleSection><Paragraph class="Default">Solutions are stored in separate subdirectories by base VRC.</Paragraph>
					<Paragraph class="Default">The customer part of the base VRC will be added to the solution file name. If the customer part of the base VRC is empty, the string <GUIRef href="" role="manual">stnd</GUIRef> will be added to the solution file name. Refer to the following examples:</Paragraph>
					<TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated"><THEAD><TR><TD rowspan="1" colspan="1">base VRC</TD>
								<TD rowspan="1" colspan="1">solution code</TD>
								<TD width="171" rowspan="1" colspan="1">solution file name</TD>
							</TR>
						</THEAD>
						<TBODY><TR><TD rowspan="1" colspan="1">B61_a</TD>
								<TD rowspan="1" colspan="1">1005</TD>
								<TD width="171" rowspan="1" colspan="1">1005stnd.tar.gz</TD>
							</TR>
							<TR><TD rowspan="1" colspan="1">B61L_a_Spl0</TD>
								<TD rowspan="1" colspan="1">1005</TD>
								<TD width="171" rowspan="1" colspan="1">1005Spl0.tar.gz</TD>
							</TR>
						</TBODY>
					</TABLE>
				</SimpleSection>
			</FieldHelp>
		</FieldGroup>
	</Fields>
</Session>
