semi合集-English.pdf - 第3459页

SEMI E134-0305 © SEMI 2004, 2005 12 the date and tim e at which the plan was installed on the equipment. definedBy The identity of the consumer that defined the DC P. Text, equal to a valid identifier for the consumer th…

100%1 / 7923
SEMI E134-0305 © SEMI 2004, 2005 11
9.1.2.2 DefinePlan — Upon receiving this request, the equipment shall first verify that the consumer has sufficient
privilege (see Section 10) to define a new DCP. If so, the equipment shall then validate the plan name for
uniqueness and all referenced events, exceptions, parameters, and trace reports for existence and correctness. The
equipment shall place no a-priori limitation on the number of plans that can be defined.
9.1.2.2.1 Any hard limitations imposed by constraints on available storage capacity shall be documented by the
equipment supplier. If such limitations are encountered at runtime, the equipment shall return an equipment-defined
error indicating that the DCP was not successfully defined, and a human-readable description of the reason. The
mechanism for supporting such errors shall be fully specified in implementation mappings provided for this
specification.
9.1.2.2.2 If there are any issues with the submitted plan, the equipment shall return a description of all problems
detected with the plan (see Section 9.1.2.2.6 for a description of possible DCP definition problems), and the plan
shall not be defined on the equipment.
9.1.2.2.3 If there are no issues with the submitted plan, the equipment shall record the date and time at which the
plan definition was submitted and the id of the consumer that submitted the plan. The equipment shall store this
information and the plan definition in non-volatile storage. It shall thereafter be legal for DCP requests to refer to
the submitted plan by its id field.
9.1.2.2.4 DefinePlan Operation Arguments
Table 6 DefinePlan Argument Definitions
Argument Description Kind Form
newPlan The definition of a new DCP. in Structured data, of type DataCollectionPlan,
described in Section 11.1.2 .
planDefined An acknowledgement that the new DCP
definition was well-formed, correct, and
supportable.
out Structured data, of type DCPDefined, described in
Section 9.1.2.2.4 .
error The consumer submitting the DCP does
not have sufficient privilege to define
DCPs.
error Structured data, of type UnauthorizedOperation,
described in Section 9.1.2.2.5 .
error The DCP definition is invalid. error Structured data, of type InvalidPlan, described in
Section 9.1.2.2.6 .
planI d
timeDef ined
definedBy
DCPDefin ed
Figure 7
DCP Defined Class
9.1.2.2.5 DCPDefined — This class describes a DCP that has been successfully defined on the equipment.
9.1.2.2.5.1 DCPDefined Attribute Definition Table
Table 7 DCPDefined Attribute Definition
Attribute Name Definition Form
planId Identifies a defined DCP. Text, equal to the ‘id’ attribute of the
DataCollectionPlan defined on the equipment.
timeDefined The date and time at which the DCP was originally
defined.
Text, formatted according to Section 14.5 For built-in
plans (see Section 11.1.2.1), this field shall be equal to
SEMI E134-0305 © SEMI 2004, 2005 12
the date and time at which the plan was installed on
the equipment.
definedBy The identity of the consumer that defined the DCP. Text, equal to a valid identifier for the consumer that
took the action (see Limitations, Section 3.1.2). For
built-in plans (see Section 11.1.2.1 ), this field shall be
a URN of the form “urn:semi-org:equipment”. The
valid values to use for this attribute to identify
consumers shall be specified by any adjunct document
defining a technical binding for this specification.
des cript ion
requiredPrivilege
Unauthoriz edOperation
Figure 8
UnauthorizedOperation Error
9.1.2.2.6 UnauthorizedOperation — This class describes an authorization error associated with a specific operation.
9.1.2.2.6.1 UnauthorizedOperation Attribute Definition Table
Table 8 UnauthorizedOperation Attribute Definition
Attribute Name Definition Form
description A description of the error Text, including the name of the operation and a
description of any important context associated with
the original request.
requiredPrivilege The name of the privilege that is required for the
operation
Text, equal to a valid privilege name or identifier (see
Section 10 ) defined on the equipment that the
consumer must possess in order to execute the
operation. The valid values to use for this attribute
shall be specified by any adjunct document defining a
technical binding for this specification.
SEMI E134-0305 © SEMI 2004, 2005 13
sourceId
eventId
invalidSourceId
invalidEventId
notProduc edBySource
isDuplicate
InvalidEventRequest
sourceId
ex cept ionId
severity
invalidSourceId
invalidExceptionId
invalidSeverity
notProduc edBySource
isDuplicate
InvalidExceptionRequest
sourceId
paramet erName
invalidSourceId
invalidParameterName
notProduc edBySource
invalidContext
InvalidParameterRequest
traceId
duplicateI d
InvalidTraceRequest
sourceId
itemId
invalidStartTrigger
invalidEventTrigger
invalidExc ept ionStat e
invalidSourceId
invalidItemId
notProduc edBySource
isDuplicate
InvalidTrigger
needs Start Trigger
needs StopTrigger
InvalidCycle
planId
desc ription
InvalidPlan
1
invalidEv ents
0..*
1
inv alidExceptions 0. . *
1
inv alidParamet ers
0..*
1
invalidTriggers 0..*
1
inv alidT raceRequest s
0.. *
1
inv alidCycle
0..1
1
duplicat ePlanI d 0. .1
DCPDefined
validI nt erval
InvalidInterval
1
invalidInterval 0..1
1
invalidParamet ers
0..*
Figure 9
InvalidPlan Error
9.1.2.2.7 InvalidPlan — This class provides an overall description of all errors detected with a submitted DCP.
9.1.2.2.7.1 InvalidPlan Attribute Definition Table
Table 9 InvalidPlan Attribute Definition
Attribute Name Definition Form
planId The identifier of the invalid DCP. Text, equal to the ‘id’ attribute of the submitted
DataCollectionPlan.
description A human-readable description of why the
DCP was rejected.
Text.