semi合集-English.pdf - 第1831页

SEMI E42-0704 © SEMI 1995, 2004 100 Table 14.9 RMESelect Service Parameter Req/Ind Rsp/Conf Description RESpec M - Specifier of the recipe execu tor. (List of) RESelect M - Recipe specifiers with (optionally) one or more…

100%1 / 7923
SEMI E42-0704 © SEMI 1995, 2004 99
14.5 RMEUpload — RMEUpload retrieves a recipe from local storage and sends it to the service user.
Parameters for RMEUpload are listed in Table 14.5.
Table 14.5 RMEUpload Service
Parameter Req/Ind Rsp/Conf Description
RERcpSpec M M(=) Specifier.
RERecipe - M The execution recipe.
REStatus - M Information concerning the results of the operation.
14.6 RMERename — RMERename changes the identifier of an execution recipe through changing one or more of
its identification attributes. If the new identifier is already in use by an execution recipe, or if the recipe is currently
selected, permission to rename the recipe shall be denied.
Parameters for RMERename are listed in Table 14.6.
Table 14.6 RMERename Service
Parameter Req/Ind Rsp/Conf Description
RERcpSpec M - Specifier of the execution recipe.
REDestRcpID M M(=) The new recipe identifier.
REStatus - M Information concerning the results of the operation.
14.7 RMESpaceInquire — The service user may request the amount of space available for recipes. The parameters
for RMESpaceInquire are listed in Table 14.7.
Table 14.7 RMESpaceInquire
Parameter Req/Ind Rsp/Conf Description
RESpec M - Target recipe executor specifier.
RESpace - M Amount of space available in target namespace.
REStatus - M Information concerning the results of the requested operation.
14.8 RMEDelete — RMEDelete removes one or more recipes from local storage and frees any reusable storage area
for new recipes. If the recipe is currently selected, permission to delete the recipe shall be denied.
Parameters for RMEDelete are listed in Table 14.8.
Table 14.8 RMEDelete Service
Parameter Req/Ind Rsp/Conf Description
RESpec M - Specifier of the recipe executor.
(List of) RERcpID M C Identifier of the recipe to be deleted. Response returns identifiers of
successfully deleted recipe(s) only.
REStatus - M Information concerning the results of the operation.
14.9 RMESelect — The service user may specify one or more recipes to be selected for execution. RMESelect is the
only service of the recipe executor that allows the service user to specify more than one recipe in a single request.
Parameters for RMESelect are listed in Table 14.9.
SEMI E42-0704 © SEMI 1995, 2004 100
Table 14.9 RMESelect Service
Parameter Req/Ind Rsp/Conf Description
RESpec M - Specifier of the recipe executor.
(List of) RESelect M - Recipe specifiers with (optionally) one or more associated parameter
names/values per recipe.
REOpID C C(=) Operation ID, used where multiple confirmations may occur. May be
null or omitted where the service initiator does not request a new
service, until all confirmations for the outstanding service have been
received.
LinkID - M LinkID is set to zero if, and only if, no further completion messages
will be required.
REStatus - M Indicates the results of the operation.
14.10 RMEDeselect — The service user may deselect a recipe to prevent its re-execution.
Parameters for RMEDeselect are listed in Table 14.10.
Table 14.10 RMEDeselect Service
Parameter Req/Ind Rsp/Conf Description
RESpec M - Specifier of the recipe executor.
(List of) RERcpID M - Identifier of the recipe.
REStatus - M Information concerning the results of the operation.
14.11 RMEGetDescriptor — The service user may request the descriptors of one or more recipes.
Parameters for RMEGetDescriptor are listed in Table 14.11.
Table 14.11 RMEGetDescriptor
Parameter Req/Ind Rsp/Conf Description
RESpec M - Specifier of the recipe executor.
(List of) RERcpID M - Identifier of the recipe.
(List of) REDesc - M Requested recipe descriptor(s) in the same order as requested.
REStatus - M Information concerning the results of the operation.
14.12 RMEChange — The service provider informs an originating namespace that a permitted change has
occurred.
Parameters for RMEChange are listed in Table 14.12.
Table 14.12 RMEChange Service
Parameter Req/Ind Rsp/Conf Description
REOpID C - Operation ID, used where multiple completion messages may occur,
corresponding to the value in the original request. May be null or
omitted where the service initiator does not request a new service
using REOpID, until the confirmation for the outstanding service has
been received.
RERcpID M - Identifier of the recipe of interest. Equivalent to specifier of
corresponding managed recipe.
REChangeStatus M - State of the changed recipe.
(List of) AttrSettings C - Attributes of particular interest to the result. Varies with action.
REStatus M - Information concerning the results of the operation.
14.13 RMEComplete — The service provider notifies the service user that an action requested by the service user
has completed.
Parameters for RMEComplete are listed in Table 14.13.
SEMI E42-0704 © SEMI 1995, 2004 101
Table 14.13 RMEComplete Service
Parameter Req/Ind Rsp/Conf Description
REOpID C - Operation ID, used where multiple completion messages may occur,
corresponding to the value in the original request. May be null or
omitted where the service initiator does not request a new service
using REOpID, until the confirmation for the outstanding service has
been received.
RERcpID M - Identifier of the recipe of interest. Equivalent to specifier of
corresponding managed recipe.
REChangeStatus M - State of the changed recipe.
(List of) AttrSettings C - Attributes of particular interest to the result. Varies with action.
REStatus M - Information concerning the results of the operation.
15 Recipe Management Compliance
This section gives a centralized reference location for compliance for RMS objects. It provides references to other
sections of the standard where detailed requirements are located. This section also defines standard terminology and
documentation related to RMS compliance that can be used by agent suppliers and device manufacturers to describe
compliance with this standard.
Each object defined by RMS has both fundamental requirements and additional capabilities. Fundamental
requirements shall be met by all instances of an RMS-compliant object as specified in cited sections. Additional
capabilities consist of those features that are optional. However, for RMS compliance, where features providing the
same or similar capabilities are implemented, they shall be implemented according to RMS specifications.
Except where one or more subsections are specifically excluded, section references include all subsections of the
referenced section.
The following table format is used in this section to specify fundamental and additional (optional) capabilities.
Fundamental capabilities have a "Y" in the column labeled "Fund." Otherwise, the capability is optional.
Capability Reference Fundamental
Name of capability Sections in SEMI E42 Y or N
15.1 Areas of Compliance — There are seven areas of RMS compliance, as follows:
a. Managed Recipe
b. Recipe Namespace Management
c. Distributed Recipe Namespace Management
e. Distributed Recipe Namespace Recorder
d. Distributed Recipe Namespace Segment
f. Execution Recipe
g. Recipe Executor
15.2 Managed Recipe — This section defines RMS compliance for the managed recipe.
A managed recipe has attributes, a body, and is capable of supporting at least one agent-specific dataset. An RMS-
compliant managed recipe reflects its compliance (a) through its attributes and (b) through its structure when it is
transferred.
In some cases, a capability is represented by a single attribute. In other case, support of an additional capability
requires several attributes that are required as a set.