semi合集-English.pdf - 第3603页

SEMI E139-0705 © SEMI 2005 27 Parameter Name Form Description Where Used verifyDepth Enumeration Verifies the scope of the PDEs to be verified. “Single” — Only the sp ecified PDE is check ed. “All” — Verify the spec ifie…

100%1 / 7923
SEMI E139-0705 © SEMI 2005 26
Parameter Name Form Description Where Used
resPDEstat
Error
Status response for the resolvePDE() service. The
following responses are allowed:
“OK” — no problems were encountered
“MissingTargetPDE” — the targetPDE value
could not be resolved to any PDE on the
EquipmentNode.
“MissingMapPDE” — A needed PDE specified by
the inputMap could not be found on the
EquipmentNode.
“MissingReferencedPDE” — A needed PDE
could not be found on the EquipmentNode.
If more than one of these conditions applies, the
first one on this list that applies should be reported.
resPDEinfo parameter
rtsRspStat Enumeration
Status response for the requestToSendPDE()
service. The following responses are allowed:
“OK” — Indicates permission to send is granted.
“NoResources” — Indicates there are not sufficient
resources available to service this request (for
example, disk space).
“Other” — Unspecified error occurred.
requestToSendPDE()
sendRspInfo
list of (uid,
sendRspStat,
verifyRspStat)
Contains a list of all problems encountered with the
sendPDE() request. The uid value indicates which
specified PDE caused the error.
sendPDE()
sendRspStat
Error
Status response for the sendPDE() service. The
following responses are allowed:
“OK” — Indicates PDE was successfully received.
“NoResources” - Indicates there are not sufficient
resources available to receive this PDE (for
example, disk space).
“TargetMismatch” — The receiver is not
compatible with the PDE’s ExecutionTarget.
“PDElocked” – The PDE already exists and cannot
be replaced at this time.
“VerificationFailed” — The PDE failed
verification. See verifyRspStat for failure reason.
“Other” — A problem occurred that is not
described by the other enumerated values.
sendRspInfo parameter
targetPDE UUID
The uid attribute value of the PDE to be acted
upon.
verifyPDE(), resolvePDE()
tcid UUID
Identifier of a TransferContainer. This is a uuid
value.
getPDE(), getPDEheader(),
requestToSendPDE(),
sendPDE()
transferContainer Binary
Container format is left as an implementation
detail.
getPDE(), getPDEheader(),
sendPDE()
transferSize Integer
Size in bytes of the TransferContainer to be
transferred.
requestToSendPDE()
uid
UUID
Refers to a PDE by its uid attribute. deletePDE(),
getPDEheader(), getPDE(),
getRspInfo parameter,
delRspInfo parameter
PDEDirItem parameter,
verifyInfo parameter
SEMI E139-0705 © SEMI 2005 27
Parameter Name Form Description Where Used
verifyDepth Enumeration
Verifies the scope of the PDEs to be verified.
“Single” — Only the specified PDE is checked.
“All” — Verify the specified PDE, plus all PDEs it
references directly or indirectly (e.g. by the PDEs
that are referenced). It requires a check that all
required PDEparameters are supplied by each
referencing PDE. This may be used with a Master
PDE to verify all the PDEs it will need for an
activity. Note that if a PDE is referenced by
multiple other PDEs within the scope of a
verifyPDE() request, it only needs to be verified
once during this process.
verifyPDE()
verifyInfo
list of (uid,
verifyRspStat)
One value set is returned for each PDE that was
reviewed by the verification process. The uid
identifies the PDE that was found to have an error.
verifyPDE()
verifyRspStat Error
Status response for the getPDE() service. The
following values are allowed:
“OK” — Indicates successful verification of the
PDE.
“NotFound” — The specified PDE was not found.
“ChecksumFail” — The computed checksum of
the PDEheader or of the PDEbody did not match
the values in the PDE.
“SyntaxError” — The syntax of the PDE or its
body was found to be incorrect.
“ContentError” — The content of the PDE did not
match allowed values or did not follow all content
rules.
“Other” — The verification error did not match the
other enumerated categories.
verifyInfo Parameter,
sendRspStat Parameter
verifySuccess Boolean
Returns “true” if no errors were encountered
during the entire verifyPDE() operation. Otherwise
returns “false”.
verifyType
Enumeration
Specifies the type of verification to perform. The
following values are allowed:
“Checksum” — computes the checksum of each
applicable PDE and compares the value to the
checksum value contained in the PDE. It computes
the checksum of any related external PDEbodies
and compares the value to the bodyChecksum value
contained in the PDE. It also confirms that the
PDEbody is matched to the proper PDE.
“Validity” – For each PDE to be verified, ensures
that the PDE can be executed as part of a recipe
without error. This verification checks the syntax
of the PDE. It includes “Checksum” verification
plus any other criteria the equipment can provide.
Also included is a check that a compatible
ExecutionTarget exists on the equipment (if any
ExecutionTargets are specified for this PDE).
Successful verification does not guarantee the
desired process results.
verifyPDE()
SEMI E139-0705 © SEMI 2005 28
8.4.2.4 Service Message Definitions
8.4.2.4.1 This section specifies the allowable/required parameters for each service. Table 17 shows the format of
the Service Parameters tables used for this purpose.
Table 17 Service Parameters
Parameter Name Req/Ind Rsp/Cnf Comment
Name see below see below Descriptive Text
8.4.2.4.2 Each service has an initial message (Request to the sender, Indicator to the receiver, hence Req/Ind).
Services that are “Request/Response” have a return message (Response to the sender, Confirmation to the receiver,
hence Rsp/Cnf). The Req/Ind and Rsp/Cnf columns indicate in which message each parameter is to be included.
The codes from Table 18 are used in these columns to give further information.
Table 18 Req/Ind and Rsp/Cnf Codes
Code Description
M Mandatory Parameter — Must be given a valid value.
C Conditional Parameter — May be defined in some circumstances and undefined in others. Whether a value is given
may be completely optional or may depend on the value of the other parameters.
U User-Defined Parameter.
- The parameter is not used.
= (For response only) Indicates that the value of this parameter in the response must match that in the primary (if
defined).
8.4.2.5 getPDEdirectory()
8.4.2.5.1 The getPDEdirectory() service is used by the FICS to request a list of PDEs maintained by the service
provider. The requestor may supply a filter that will yield a subset of the full list of PDEs. A subset of the
PDEheader’s attributes can be reported for each returned PDE if desired.
8.4.2.5.2 When multiple PDEFilters are specified, these filters are to be AND’ed together. That is, each filter is
applied in turn with the reduced list that is output from one becoming the input for the next. Note that no
PDEDirItems are returned when no PDE’s are found that pass the filters.
8.4.2.5.3 The requestor may choose not to include PDEFilters or PDEAttributes in the request.
Table 19 getPDEdirectory() Service Parameters
Parameter Name Req/Ind Rsp/Cnf Comment
list of PDEFilter C - List of criteria for which PDEs to report. If no PDEFilters supplied, all
PDEs will be reported
list of PDEAttribute C - Lists the attributes to be returned for each PDE reported
list of PDEDirItem - C List of the PDEs on the service provider that match the provided filter.
The values of the specified attributes are included for each.
dirRspStat M Denotes any error found. If there is an error, no PDEDirItems are
returned.
8.4.2.6 deletePDE()
8.4.2.6.1 The deletePDE() service is used by the FICS to request that specified PDEs be deleted from the service
provider. The request includes a list of the PDEs to be deleted. The requestor may wish to first use the
getPDEdirectory() service to obtain a list of the available PDEs.
8.4.2.6.2 The delRspInfo lists any errors encountered by the service provider in the completion of the deletePDE()
request. All PDEs not referenced by delRspInfo shall be deleted.