semi合集-English.pdf - 第1785页

SEMI E42-0704 © SEMI 1995, 2004 54 A recipe may be syntactically and proce durally correct but, due to the di fferences bet ween different installations of agents with access to a namespace , may give different results o…

SEMI E42-0704 © SEMI 1995, 2004 53

The modify variable parameter operation consists of

adding, deleting, or modifying a specific parameter

definition to a list of definitions in

AgentSpec_LinkParam for a specific agent.

A definition is added when it is copied directly from

the LinkParam

attribute to the AgentSpec_

LinkParam

attribute without modification. A definition

shall only be added if there is currently no definition for

a parameter with the same parameter name in the

AgentSpec_LinkParam attribute.

A definition is deleted when it is completely removed

from the list of definitions in AgentSpec_

LinkParam

A definition is modified when the value or restriction

of an existing definition is replaced in

AgentSpec_LinkParam

The modify variable parameters operation is invoked

with the RMNVarPar service.

8.2.4 Recipe Authorization — Recipe authorization

operations include those that allow an authorized user

to change the value in the generic attribute Approval-

Level or the agent-specific attribute Certified.

The de-certify operation is invoked with the service

RMNAction.

8.2.4.1 Approve Recipe — Recipe management

provides two different methods of controlling how a

recipe is applied: through the generic attribute

ApprovalLevel

and through the agent-specific attribute

Certified

. The recipe's approval level (the value

contained in ApprovalLevel

) is also used to protect it

from change.

A recipe goes through different stages during its

lifecycle. After a recipe has been initially created, it

will typically go through a dynamic period while it is

tested and adjusted until it produces the desired results.

ApprovalLevel

is an unsigned integer used to designate

the different stages in a recipe's life cycle. It is set to

zero (its default value) whenever a recipe is created,

updated, or linked.

The approval operation allows an authorized user to

set ApprovalLevel

to a non-zero value. Otherwise, it

may not be set externally.

A recipe is said to be approved whenever Approval-

Level is non-zero. An example of a factory's

implementation of approval levels is given in the

appendix, Section 8.3. Figure 8.4 illustrates the recipe's

APPROVAL state. For a description of the transitions,

see Table 8.1 in Section 8.3.

Figure 8.4

Approval State Model

A subrecipe may be approved independently from any

recipes which reference it.

A linked recipe may not be approved to a level higher

than the lowest approval level of any of its subrecipes.

Therefore, all subrecipes referenced in the attribute

LinkList

of a linked recipe must be located prior to

granting an approval level other than zero. The

ApprovalLevel

attribute of the subrecipes must be

increased to a value equal to, or greater than, the

required level by an authorized user before the higher

approval level of the linked recipe is accepted.

The restriction on the approval level of the linked

recipe requires the user to purposefully change the

approval level in order to protect the entire linked

recipe set as a unit from unexpected change, as it is by

the main recipe identifier that the recipe as a whole will

be known. It should be noted that approval of a linked

recipe is not the same as approval of the individual

parts, as a subrecipe which is appropriate in one recipe

may be inappropriate in another.

The approve recipe operation is invoked with the

RMNAction service.

8.2.4.2 Certify — The certify operation sets the value

of Certified

for a specific executing agent to a non-zero

value specified by an authorized user. This operation

affects no other attributes (except the length and

timestamp attributes of the affected agent-specific

dataset).

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.

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

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,