semi合集-English.pdf - 第3602页
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 “MissingTa…

SEMI E139-0705 © SEMI 2005 25
Parameter Name Form Description Where Used
PDEAttribute Enumeration
Choice of available PDE attributes. The following
values are allowed:
“name”
“gid”
“groupName”
“description”
“type”
“executable”
“maxAntecedents”
“createDate”
“createNode”
“author”
“userInfo”
“supplierInfo”
“checksum”
getPDEdirectory(),
PDEAttributeItem parameter
PDEAttributeItem
(PDEAttribute,
PDEAttributeValue)
Contains the enumerated identifier of a particular
PDE attribute and the value of that attribute.
PDEDirItem parameter
PDEAttributeName Enumeration
Choice of available PDE attributes. The following
values are allowed:
“name”
“gid”
“groupName”
“description”
“type”
“executable”
“createDate”
“createNode”
“author”
“userInfo” — supplied value matched to any
userInfo string in the PDE
“supplierInfo” — supplied value matched to any
supplierInfo string in the PDE
PDEFilter parameter
PDEAttributeValue
Depends on selected
attribute
Contains the value of the corresponding attribute in
the appropriate format.
PDEAttributeItem parameter,
PDEFilter parameter
PDEDirItem
(uid, list of
PDEAttributeItem)
Single directory entry returned by
getPDEdirectory().
getPDEdirectory()
PDEFilter
(PDEAttributeName,
operator,
PDEAttributeValue)
Set of values that define a filter on the set of PDEs
for the getPDEdirectory() service.
getPDEdirectory()
pdeRef UUID
Contains a reference to a PDE. The reference is a
UUID value that may represent a gid or a uid.
inputMap parameter,
outputMap parameter
resolution UUID
Contains the value of the uid attribute of the PDE
to which a PDE reference is resolved.
inputMap parameter,
outputMap parameter
resPDEinfo
list of (pdeRef,
resPDEstat)
Contains a list of all references to PDEs found in
the recipe structure with its corresponding status.
resolvePDE()

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()