semi合集-English.pdf - 第1817页

SEMI E42-0704 © SEMI 1995, 2004 86 Table 12.3 RMNCreateNS Parameter Req/ Ind Rsp/ Conf Description RMNSSpec M - Target namespace specifier . NSStatus - M Information concerning the result of the requested operation. 12.4…

100%1 / 7923
SEMI E42-0704 © SEMI 1995, 2004 85
RMAgent.
RMSectionsSent Recipe attributes, recipe body, and
attributes of agent-specific section(s).
Structure composed of GenAttrSection,
BodySection, and (List of) AgentSpec_Section.
Status Error Information. Structure composed of ErrorCode and ErrorText.
12.2 Message Flow — The flow of messages defined in RMS, between the service user and the service provider, are
of two types. The first type, illustrated in Figure 12.1, applies to most namespace operations. A request message is
sent from the service user, and the namespace manager returns a response message containing the appropriate
information.
Figure 12.1
Basic Message Flow
The second type of message flow, illustrated in Figure 12.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.
The second type of message flow may be used for notifying the service user of RMNAction that individual
operations on recipes have been completed. The first type of message flow is used for all other namespace services.
Figure 12.2
Message Flow with Completion Notification
The second type of message flow may be used for notifying the service user of RMNAction that individual
operations on recipes have been completed. The first type of message flow is used for all other namespace services.
12.3 RMNCreateNS — The service user may request to create a new namespace and assign it a name (identifier).
The request shall be denied if the owner agent already has a namespace with the new name.
The parameters for RMNCreateNS are listed in Table 12.3.
SEMI E42-0704 © SEMI 1995, 2004 86
Table 12.3 RMNCreateNS
Parameter
Req/
Ind
Rsp/
Conf
Description
RMNSSpec M - Target namespace specifier.
NSStatus - M Information concerning the
result of the requested
operation.
12.4 RMNDeleteNS — The service user may request to
delete a namespace. If the namespace contains recipes,
the request shall be denied.
The parameters for RMNDeleteNS are listed in Table
12.4.
Table 12.4 RMNDeleteNS
Parameter
Req/
Ind
Rsp/
Conf
Description
RMNSSpec M - Target namespace specifier.
NSStatus - M Information concerning the
result of the requested
operation.
12.5 RMNRenameNS — The service user may request
to rename a namespace. The request shall be denied if
the owner agent already has a namespace with the new
name.
The parameters for RMNRenameNS are listed in Table
12.5.
Table 12.5 RMNRenameNS Service
Parameter
Req/
Ind
Rsp/
Conf
Description
RMNSSpec M - Target namespace specifier.
RMNewNS M M(=) New namespace name
(identifier).
NSStatus - M Information concerning the
result of the requested
operation.
12.6 RMNSpaceInquire — The service user may
request the amount of space available for recipes.
The parameters for RMNSpaceInquire are listed in
Table 12.6.
Table 12.6 RMNSpaceInquire
Parameter
Req/
Ind
Rsp/
Conf
Description
RMNSSpec M - Target namespace specifier.
RMSpace - M Amount of space available in
target namespace.
NSStatus - M Information concerning the
result of the requested
operation.
12.7 RMNRcpStatInquire — The service user may
request the current write-protection status of a recipe
and the next available numeric version for a recipe of
the same class and name.
The parameters for RMNRcpStatInquire are listed in
Table 12.7.
Table 12.7 RMNRcpStatInquire
Parameter
Req/
Ind
Rsp/
Conf
Description
RMNSSpec M - Target namespace specifier.
RMRcpStat - M Status of recipe.
RcpVersion - C Next available numeric
version. Required, except with
the specified recipe does not
exist.
NSStatus - M Information concerning the
result of the requested
operation.
12.8 RMNVersionInquire — The service user may
request the best version (highest) for a recipe with
given qualifiers of class, name, and (optionally) agent.
The parameters for RMNVersionInquire are listed in
Table 12.8.
Table 12.8 RMNVersionInquire
Parameter
Req/
Ind
Rsp/
Conf
Description
RMNSSpec M - Target namespace specifier.
RcpClass M - Qualifying recipe class.
RcpName M - Qualifying recipe name.
RMAgent C C(=) Certified agent. If omitted,
agent qualification is not
considered. If included, only
recipes for which the agent is
certified qualify.
RcpVersion - C The best available version of
the recipe. Omitted if no
qualifying recipe is found.
NSStatus - M Information concerning the
result of the requested
operation.
12.9 RMNCreate — A service user may request to
initialize a new recipe in a namespace with a body
created elsewhere. The requestor is required to supply
the attributes of the recipe body. If the requested recipe
identifier is used by a read-only recipe, the request shall
be denied.
The parameters for RMNCreate are listed in Table 12.9.
12.10 RMNUpdate — The service user requests to
replace an existing recipe body in a namespace with an
SEMI E42-0704 © SEMI 1995, 2004 87
updated body. If the requested recipe identifier is used
by a read-only recipe, the request shall be denied.
The parameters for RMNUpdate are listed in Table
12.9.
Table 12.9 RMNCreate and RMNUpdate
Parameter
Req/
Ind
Rsp/
Conf
Description
RMRcpSpec M - Recipe specifier.
(List of)
AttrSetting
M - List of recipe attributes required
for create/update.
BodySection M - Recipe body.
NSStatus - M Information concerning the
result of the requested operation.
12.11 RMNStore — The service user may request to
store a recipe in a namespace. If the recipe identifier is
already in use by a read-only recipe in the namespace,
or if the namespace has insufficient space for storing
the recipe, request shall be denied.
The parameters for RMNRetrieve are listed in Table
12.10.
Table 12.10 RMNStore
Parameter
Req/
Ind
Rsp/
Conf
Description
RMRcpSpec M - The recipe specifier.
RMSectionsCode M - Indicates which sections
sent.
RMSectionsSent M - Contents of all sections to
be sent.
NSStatus - M Information concerning the
result of the requested
operation.
12.12 RMNRetrieve — The service user may request to
receive a recipe in its entirety (including all agent-
specific datasets), the generic attributes with or without
the body but without agent-specific datasets, a
particular agent-specific dataset, or all agent-specific
datasets.
The parameters for RMNRetrieve are listed in Table
12.11.
Table 12.11 RMNRetrieve
Parameter
Req/
Ind
Rsp/
Conf
Description
RMRcpSpec M - The recipe specifier.
RMSectionsRequested M - Indicates which sections
are requested.
RMSectionsSent - M Contents of all sections
to be sent.
NSStatus - M Information concerning
the result of the
requested operation.
12.13 RMNCopy — The service user may request to
copy a recipe in a namespace to another recipe within
the same namespace. If a read-only recipe with the
specified Destination ID exists, an Access Denied error
shall be returned.
The parameters for RMNCopy are listed in Table 12.12.
12.14 RMNRename — The service user may request to
rename a recipe in a namespace if the recipe is not
write-protected. If the recipe is write-protected, then an
Access Denied error shall be returned.
The parameters for RMNRename are listed in Table
12.12.
Table 12.12 RMNCopy, RMNRename
Parameter
Req/
Ind
Rsp/
Conf
Description
RMRcpSpec M - Specifier of the recipe to be
copied or renamed (source).
RMDestRcpID M - The identifier for the recipe
to be originated (destination).
NSStatus - M Information concerning the
result of the requested
operation.
12.15 RMNAction — RMNAction is used to request the
performance of one of the following actions
(operations) on one or more recipes: delete, protect,
verify, link, unlink, certify, de-certify, download to a
specified agent, and upload from a specified agent.
Where more than one recipe is specified, operations
shall be performed on each recipe in the requested
order.
If performance of the requested action is likely to take
more time to complete than is normally allowed
between a request message and the corresponding
response, then the namespace manager should respond
with an intent to comply at the earliest opportunity
before it begins the requested operation. Immediately
following the completion of the operation on each of
the specified recipes, the manager shall send a
notification message RMNComplete to the service
requestor, providing the results of that operation
together with information concerning any errors
causing abnormal completion of the operation. Error
information is important for diagnosis and correction of
problems. Figure 12.2 in Section 12.2 shows an
example of the message flow for the download
operation performed on two recipes.
The parameter LinkID is set to a zero value in the
response if the operations have been completed and no
notifications will be sent. Otherwise, it is set to a non-