semi合集-English.pdf - 第1829页

SEMI E42-0704 © SEMI 1995, 2004 98 The second type of message flow may be used for notifyin g the service user of RMEDnldV er, RMEVerify, and RMESelect that i ndividual o perations on recipes have been completed. A third…

100%1 / 7923
SEMI E42-0704 © SEMI 1995, 2004 97
Parameter Definition Form
RERecipe Execution recipe. Structure composed of REAttrSection, BodySection.
RESelect Recipe specifier with option
parameter setting.
(List of) Structure composed of RERcpSpec and (list
of) RESelectParam.
RESelectParam Variable parameter name and initial
value.
Structure composed of REParamName and
REParamSetting.
RESpace Amount of available storage, in
bytes.
Unsigned integer.
RESpec The specifier of the recipe executor. Formatted text.
REStatus Information regarding the success or
failure of the request.
Structure composed of REAck and (List of) Status.
REVerData Information concerning a
successfully verified recipe.
Structure composed of RcpExtRef, RcpParameters,
RcpEstRunTime (optional), RcpVerificationID
(optional), and (where applicable) RcpDerivedID.
REVerID Contents of VerificationID attribute. Text.
Status Error information. Structure composed of Error Code and ErrorText.
a. A recipe specifier may reference a recipe that is in a namespace and not in the recipe executor’s storage.
14.2 Message Flow — The flow of messages defined in RMS, between the service user and the service provider,
are of three types. The first type, illustrated in Figure 14.1, is the most common and applies to all recipe executor
operations except for cases of RMEDnldVer, RMEVerify, and RMESelect. A request message is sent from the
service user, and the recipe executor returns a response message containing the appropriate information. All
activities that occur as a result of the request are completed before the response message is sent.
Figure 14.1
Basic Message Flow
The second type of message flow, illustrated in Figure 14.2, is used for messages that specify an operation to be
performed that may require more time for completion than is allowed between a request and a response. In this case,
the response to the request indicates an intent to complete the operation rather than actual completion. The operation
is then performed on each of the specified recipes in turn, until each operation has completed, either successfully or
with errors. Any errors that occurred are reported in the completion message.
Figure 14.2
Message Flow with Completion Notification
SEMI E42-0704 © SEMI 1995, 2004 98
The second type of message flow may be used for notifying the service user of RMEDnldVer, RMEVerify, and
RMESelect that individual operations on recipes have been completed.
A third type of message flow consists of a single notification message, shown in Figure 11.3, sent by the recipe
executor to inform the originating namespace of a new or changed execution recipe. (See Section 11.2.10.)
Figure 14.3
Change Notification Message Flow
14.3 RMEDnldVer — The service user may request the recipe executor to download and verify an execution recipe.
All unverified downloaded recipes are verified automatically. The service user may optionally specify a forced
overwrite of any pre-existing unselected recipe with the same identifier. A currently selected recipe shall not be
overwritten. If forced overwrite is not specified and a recipe with the same identifier is already in storage, the
request to download is denied and the recipe is discarded.
If the recipe executor performs a verification of the downloaded recipe, and if the verification is successful, then it
shall return the information provided by the conditional parameters.
Parameters for RMEDnldVer are listed in Table 14.3.
Table 14.3 RMEDnldVer Service
Parameter Req/Ind Rsp/Conf Description
RERcpSpec M - Destination specifier of the execution recipe.
REOWCode M - Indicates if a forced overwrite is requested.
RERecipe M - The execution recipe.
REVerData - C Information concerning the successfully verified recipe. Omitted if
recipe has no external references or fails verification.
REStatus - M Information concerning the results of the operation.
14.4 RMEVerify — The service user may request the recipe executor to verify an execution recipe. If the
verification is successful, then it shall return the information provided by the conditional parameters.
Parameters for RMEVerify are listed in Table 14.4.
Table 14.4 RMEVerify Service
Parameter Req/Ind Rsp/Conf Description
RESpec M - Specifier of the target recipe executor.
(List of) RERcpID M - Identifier of the 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.
(List of) REVerData - C Information concerning the successfully verified recipe. Omitted if
recipe has no external references or fails verification.
REStatus - M Information concerning the results of the operation.
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.