semi合集-English.pdf - 第1728页

SEMI E41-95 © SEM I 1995 11 10.3.2 EXC leared — Notification tha t an abnormal situation is no lo nger apparent or relevant, as is described in Section 8.1, is communicated us ing the EXCleared service. Table 6 EXCleare …

100%1 / 7923
SEMI E41-95 © SEMI 1995 10
10.2 Parameter Dictionary
Table 4 Parameter Dictionary
Parameter Name Definition Form: Possible Values
ErrorCode Contains the code for the specific error found. Enumerated:
EXRecover:
Parameters improperly specified
Insufficient parameters specified
Recovery action currently invalid
Busy with another recovery
Currently unable to perform the recovery
EXRecoveryAbort:
Parameters improperly specified
Insufficient parameters specified
No active recovery action
EXRecoveryComplete:
FailedRecovery aborted
ErrorText Text in support of the error code. Text
EXAck Indicates whether the request was successful or the activity
completed normally.
Boolean:
TRUE – Successful
FALSE – Unsuccessful
EXID Persistent exception condition identifier. Text:
Unique with respect to the exception agent.
EXMessage Message describing the situation related to an exception
condition.
Text
EXRecovery Identifies a recovery action associated with an exception
condition.
Text
EXRecoveryStatus Reports the acceptance or rejection of a requested recovery
action and whether completion was normal.
Structure composed of:
EXAck
(List of) Status
EXType Identifies the type of exception condition. Enumerated:
Alarm
Error
Status Reports any errors found. Structure composed of:
ErrorCode
ErrorText
Timestamp Event date and time. Text
yyyymmddhhmmsscc
10.3 Service Detail — Tables 5 through 9 define the parameters for each service. Parameters have additional detail
which is defined in the parameter dictionary, Table 4.
10.3.1 EXPost — Detection of abnormal situations by the exception agent is communicated using the EXPost
service, as described in Section 8.1. This notification is also used to communicate any significant changes in
exception condition information while its state is SET.
Table 5 EXPost Service Detail
Parameter Req/Ind Comment
Timestamp M
EXID M Identifies the exception condition which has detected the abnormal situation.
EXType M
EXMessage M
(List of) EXRecovery C List of possible recovery actions. Not available for alarms.
SEMI E41-95 © SEMI 199511
10.3.2 EXCleared — Notification that an abnormal situation is no longer apparent or relevant, as is described in
Section 8.1, is communicated using the EXCleared service.
Table 6 EXCleared Service Detail
Parameter Req/Ind Comment
Timestamp M
EXID M Identifies the exception condition which has detected the abnormal situation.
EXType M
EXMessage M
10.3.3 EXRecover — Recovery action requests, described in Section 8.1, are communicated using the EXRecover
service. The recovery action services are not available for alarms.
Table 7 EXRecover Service Detail
Parameter Req/Ind Rsp/Cnf Comment
EXID M - Identifies the exception condition on which to perform the recovery action.
EXRecovery M - The particular recovery action being requested.
EXRecoveryStatus - M
10.3.4 EXRecoveryComplete — Notification of recovery action completion by the exception agent is
communicated using the EXRecoveryComplete service. Recovery action completion, which is described in Section
8.1, is not directly linked to clearing the exception condition state, and successful completion indicates only that the
operation performed completed normally.
Table 8 EXRecoveryComplete Service Detail
Parameter Req/Ind Comment
Timestamp M
EXID M Identifies the exception condition on which the recovery action was performed.
EXRecoveryStatus M
10.3.5 EXRecoveryAbort — Recovery action abort, described in Section 8.1 is communicated using the
EXRecoveryAbort service.
Table 9 EXRecoveryAbort Service Detail
Parameter Req/Ind Rsp/Cnf Comment
EXID M - Identifies the exception condition on which the recovery action is being performed.
EXRecoveryStatus - M
10.4 Fundamental Requirements — Exception management defines the standard services available to achieve
exception condition-based exception handling and error recovery in equipment.
All exception agent implementations shall support the fundamental requirements. This standard provides for two
aspects of fundamental requirements: exception reporting and interactive exception handling. It is possible to
support only exception reporting in systems which do not require interactive exception handling. Interactive
exception handling requires that exception reporting be supported.
10.4.1 Exception Reporting — The fundamental requirements of the exception agent for exception reporting are
based on maintaining the decision authority updated on the exception conditions it is interested in. These are listed
below.
• Detect and report the occurrence of significant abnormal situations by setting the related exception condition,
and posting it if reporting is enabled.
SEMI E41-95 © SEMI 1995 12
• Detect and report that an abnormal situation is no
longer apparent or relevant by clearing the related
exception condition and reporting it if enabled.
• Provide for enabling and disabling reporting on
each exception condition.
• Maintain the data of exception condition attributes
indicated in Table 2.
• Reject requests for capabilities not supported (such
as recovery actions).
10.4.2 Interactive Exception Handling — The
fundamental requirements of the exception agent for
interactive exception handling extend the exception
reporting to allow the decision authority to request
recovery actions to be performed to resolve abnormal
situations. These are listed below.
• Support all exception reporting fundamental
requirements specified above.
• Supply a list of valid recovery actions for an
exception condition when posting.
• Execute a requested recovery action for an
exception condition if the requested recovery
action is currently valid. The exception agent may
support only a single recovery action to be in
progress at a time and reject all other recovery
action requests for other exception conditions
while it is busy.
• Report the completion of the recovery action.
• Support Abort of the recovery action at all times,
immediately ceasing recovery activity and
terminating the recovery action.
• Reject requests with incomplete or invalid
parameters.
• Reject requests for capabilities not supported.
Optional capabilities defined or enabled in this standard
include the following:
• Support for multiple concurrent recovery actions.
The standard allows only one recovery action in
progress for each exception condition.
• Adjust the exception condition message and the
valid recovery action list as appropriate during the
error recovery, and post the changes if reporting is
enabled.
The services are defined with mechanisms to reject
unsupported services and options should they be
requested. This improves robustness and enables
sophisticated service-users to adjust its requests to the
capabilities of the particular exception agent.
NOTICE: These standards do not purport to address
safety issues, if any, associated with their use. It is the
responsibility of the user of these standards to establish
appropriate safety and health practices and determine
the applicability of regulatory limitations prior to use.
SEMI makes no warranties or representations as to the
suitability of the standards set forth herein for any
particular application. The determination of the
suitability of the standard is solely the responsibility of
the user. Users are cautioned to refer to manufacturer’s
instructions, product labels, product data sheets, and
other relevant literature respecting any materials
mentioned herein. These standards are subject to
change without notice.
The user’s attention is called to the possibility that
compliance with this standard may require use of
copyrighted material or of an invention covered by
patent rights. By publication of this standard, SEMI
takes no position respecting the validity of any patent
rights or copyrights asserted in connection with any
item mentioned in this standard. Users of this standard
are expressly advised that determination of any such
patent rights or copyrights, and the risk of infringement
of such rights, are entirely their own responsibility.
Copyright by SEMI® (Semiconductor Equipment and Materials
International), 3081 Zanker Road, San Jose, CA 95134. Reproduction o
f
the contents in whole or in part is forbidden without express written
consent of SEMI.