semi合集-English.pdf - 第1786页
SEMI E42-0704 © SEMI 1995, 2004 55 If the value in RecipeReadOnlyLevel is zero, all recipes within the namespace are automatically write- protected , regardless of the support for the ApprovalLevel attribute . The protec…
SEMI E42-0704 © SEMI 1995, 2004 54
A recipe may be syntactically and procedurally correct
but, due to the differences between different
installations of agents with access to a namespace, may
give different results on these different installations.
Recipe certification signifies that a linked recipe
produces the desired results on a specific installation.
A recipe is considered certified for agent if the
certification-level contained in the agent-specific
attribute Certified
is non-zero. Otherwise, the recipe is
uncertified. A certified recipe is de-certified when the
certification-level is set to zero.
A recipe may be certified and de-certified only by an
authorized user. Figure 8.6 illustrates the recipe's
CERTIFICATION states. For a description of the
transitions, see Table 8.1 in Section 8.3.
Figure 8.6
Certification State Model
Recipes with variable parameters may be certified for
specific values and restrictions of some of these
variables. If so, such values are stored in the
AgentSpec_LinkParam
attribute.
Only recipes with the Linked
attribute set to TRUE
may be certified.
The certify recipe operation is invoked with the
RMNAction service.
8.2.4.3 De-certify — The de-certify operation clears
the Certified
attribute for a specific agent at the request
of an authorized user.
A recipe may need to be de-certified after major
maintenance has been performed and later re-certified
only after testing its results.
8.2.5 Recipe Protection — The namespace attribute
RecipeReadOnlyLevel is used as a threshold to govern
the level of approval required for individual recipes to
be protected. A recipe is protected when the value in
its ApprovalLevel attribute is equal to, or greater than,
RecipeReadOnlyLevel. All recipes are protected
whenever the namespace’s RecipeReadOnlyLevel
attribute is equal to zero. Figure 8.5 illustrates the
recipe's PROTECTION states. For a description of the
transitions, see Table 8.1 in Section 8.3.
Figure 8.5
Protection State Model
If the value of RecipeReadOnlyLevel
is n, then recipes
with approval levels greater than, or equal to, n are
read-only. The body of a read-only recipe may not be
changed in any way, including by over-writing or
deleting. The identifier of a read-only recipe may not be
renamed. A linked recipe that is read-only may not be
re-linked.
The recipe protect operation sets the value of
ApprovalLevel
to the value in RecipeRead
OnlyLevel
. For linked recipes with subrecipes, the
operation is denied if the resulting approval level for
the main recipe would be higher than any subrecipe, as
described in Section 8.2.4.
SEMI E42-0704 © SEMI 1995, 2004 55
If the value in RecipeReadOnlyLevel is zero, all recipes
within the namespace are automatically write-
protected, regardless of the support for the
ApprovalLevel attribute.
The protect recipe operation is invoked with the
RMNAction service.
8.2.6 Unprotect — The read-only status of a recipe
may be changed either by changing its approval level to
a value less than the value of RecipeReadOnlyLevel
or
by increasing the value in RecipeReadOnlyLevel
.
NOTE: If RecipeReadOnlyLevel is zero, all recipes are
write-protected regardless of the value in approval-
level.
A protected recipe may be changed to unprotected at
the request of an authorized user. This operation clears
the ApprovalLevel
attribute.
The unprotect recipe operation is invoked with the
RMNAction service.
8.2.7 Informational Operations — Object Services are
used to request the current value of one or more recipe
attributes and to set one or more values. Certain
attributes have restricted access and may not be set
through RMS services. These attributes are identified
as “RO” (read-only) in Tables 3.1 and 3.2 in the column
labeled “Access” in Section 3.4.2. When attributes
identified as “RW” (read-write) are set through Object
Services, the appropriate attribute length and timestamp
attributes shall be updated appropriately.
In addition to Object Services, the get descriptors
operation provides important information.
8.2.7.1 Get Recipe Descriptors — The get recipe
descriptor operation returns the descriptor of a
specified recipe: the generic descriptor, the body
descriptor, and the agent-specific descriptors of any
existing agent-specific datasets.
A recipe descriptor may be used to determine if two or
more recipes are identical or which is most recent.
The get recipe descriptors operation is invoked with the
RMNGetDescriptor service.
8.3 Recipe State Model — An existing recipe has
different states of interest to RMS. These are shown in
Figure 8.7. The Recipe Available State Model in Figure
8.7 combines the separate models for VERIFICATION,
APPROVAL, PROTECTION, LINKAGE, and
CERTIFICATION as AND substates of RECIPE
AVAILABLE.
Figure 8.7
Recipe Available State Model
These states have been discussed in previous sections and are associated with one or more of the recipe's attributes,
as follows:
VERICATION: Verified
,
APPROVAL: ApprovalLevel,
SEMI E42-0704 © SEMI 1995, 2004 56
PROTECTION: the interaction of ApprovalLevel and the namespace attribute RecipeReadOnlyLevel,
LINKAGE: Linked
, and
CERTIFICATION: Certified
.
The table of transitions is given in Table 8.1.
Table 8.1 Table of Transitions
# Current State Trigger New State Action Comment
1 (entry to Recipe
Available)
Recipe is created. Recipe Available. Initialize generic
attributes.
None.
2 (default entry to
VERIFICATION)
Recipe is created. UNVERIFIED Verified reset. Newly created recipe is
unverified.
3 UNVERIFIED Requested verification
operation is successful.
VERIFIED Set Verified to
TRUE.
Verification is performed
by the recipe executor.
4 VERIFIED Requested verification
operation, on previously
verified recipe, fails.
UNVERIFIED Reset Verified. Verification is performed
by the recipe executor.
5 VERIFIED Recipe is updated. UNVERIFIED Reset Verified. Updated recipe must be re-
verified.
6 (default entry to
LINKAGE)
Recipe is created. UNLINKED Reset Linked,
LinkList
, and
LinkParam
.
Newly created recipe is
unlinked.
7 UNLINKED Authorized user requested
link operation is successful.
LINKED Set Linked to TRUE.
Set LinkList
and
LinkParam
.
Single-part recipes set
Linked
only.
8 LINKED Recipe is updated. UNLINKED Reset Linked,
LinkList
, and
LinkParam
.
Single-part recipes set
Linked
only.
9 LINKED Recipe is re-verified. UNLINKED Reset Linked,
LinkList
, and
LinkParam
.
Single-part recipes set
Linked
only.
10 LINKED Authorized user requests the
unlink operation.
UNLINKED Reset Linked,
LinkList
, and
LinkParam
.
Single-part recipes set
Linked
only.
11 (default entry to
PROTECTION)
Recipe is created. If RecipeRead-
OnlyLevel
is zero,
new state is
PROTECTED.
Otherwise, it is
UNPROTECTED.
None. All recipes are read only
when
RecipeReadOnlyLevel
is
zero.
12 UNPROTECTED Authorized user request to
protect the recipe.
PROTECTED Set ApprovalLevel to
the value in
RecipeReadOnly-
Level.
Recipe is protected when
approval level =
RecipeReadOnlyLevel
.
13 UNPROTECTED Authorized user sets
RecipeReadOnlyLevel to
value greater than or equal
to approval level.
PROTECTED None. Recipe is protected when
approval level greater than
or equal to
RecipeReadOnlyLevel
.
14 PROTECTED Authorized user sets
approval level to a value less
than RecipeReadOnlyLevel
.
UNPROTECTED None. Recipe is unprotected when
approval level less than
RecipeReadOnlyLevel.
15 PROTECTED Authorized user sets
RecipeReadOnlyLevel to a
UNPROTECTED None. Recipe is unprotected when
approval level less than