semi合集-English.pdf - 第1726页
SEMI E41-95 © SEM I 1995 9 EXTy pe Identif ies the ty pe of exception c o nditio n. Y RO Enumera ted: AlarmError EXM essage Text message d escribing t he abnormal situation m onitored. YR O T e x t EXEnab led In dicates …

SEMI E41-95 © SEMI 1995 8
9 POSTED Reporting disabled. NOT POSTED
10 not EXSTATE Default entry into recovery
concurrent state at initial exception
condition creation.
NOTRECOVERING
11 NOTRECOVERING “EXRecover” message received
while in the SET state and accepted.
RECOVERING Initiate requested recovery action
and execute to completion.
12 RECOVERING Recovery action completed. NOTRECOVERING Send “EX Recovery Complete”
message.
13 RECOVERING “EXRecoveryAbort” message
received.
ABORTING-
RECOVERY
Perform the abort procedure to
terminate the recovery action in
progress.
14 ABORTING-RECOVERY Abort procedure is complete. NOTRECOVERING Send “EX Recovery Complete”
message.
CLEARED — The abnormal situation related to the exception condition is either not apparent or not relevant.
SET — The abnormal situation related to the exception condition is apparent and relevant.
The exception agent should generate a collection event each time an exception condition transitions from
CLEARED to SET and another from SET to CLEARED.
NOT POSTED — The latest information on the detected abnormal situation has not yet been reported by the
exception agent. This may be transient on entering the SET state or may be because reporting is disabled. NOT
POSTED is the default state when entering the SET state.
POSTED — The latest information on the detected abnormal situation has been reported by the exception agent to
the decision authority.
Recovery — Recovery is one concurrent subset of EXSTATE. It includes the substates describing the behavior in
relation to exception condition recovery actions.
NOTRECOVERING — In the NOTRECOVERING substate, there is no recovery action in progress directly related
to the exception condition. NOTRECOVERING is the default state when an exception condition is initially created.
Recovery actions may only be initiated when the exception condition is in the SET state.
RECOVERING — A recovery action related to the exception condition is in progress when in the RECOVERING
state.
ABORTINGRECOVERY — In the ABORTINGRECOVERY substate, the abort procedure is performed to
immediately terminate the recovery action. It is the responsibility of the exception agent to cease physical activity as
quickly as possible, having achieved a safe condition.
9 Object Definitions
Exception management defines one standard object, the Exception Condition.
9.1 Exception Condition Object Definition — The exception condition is a persistent object created by the
exception agent. It provides the decision authority with reporting on, access to, and the possibility to direct
resolution of an abnormal situation detected. It also tracks progress of a requested recovery action. The exception
condition is uniquely identified by the EXID attribute.
The object attribute notation used in Table 2 is described in Conventions, Section 5.2.
Table 2 Exception Condition Attributes
Attribute Name Definition Rqmt Access Form
ObjType The object type. Y RO Text:
“EXCEPTION”
ObjID Exception agent unique identifier for the
exception condition.
YROText:
Unique with respect to the exception agent.

SEMI E41-95 © SEMI 19959
EXType Identifies the type of exception condition. Y RO Enumerated:
AlarmError
EXMessage Text message describing the abnormal
situation monitored.
YROText
EXEnabled Indicates that reporting to the decision
authority on the exception condition is
enabled.
Y RW Boolean:
TRUE – Enabled
FALSE - Disabled
EXRecActList List of possible recovery actions. N RO List of:
Text
EXStateList All concurrent sub-states of the exception
condition according to the state model in
Figure 3.
Y RO List of:
Text
EXRecoveryAction Recovery action which may be requested to
resolve the abnormal situation.
NROText
EXState A unique sub-state of the exception
condition according to the state model in
Figure 3.
YROText:
EXSTATE/CLEARED
EXSTATE/SET/NOTPOSTED
EXSTATE/SET/POSTED
EXSTATE/NOTRECOVERING
EXSTATE/RECOVERING
EXSTATE/ABORTINGRECOVERY
10 Messaging Services Detai l
This section defines the messaging services required to implement the exception management concepts. The
messages were introduced in Section 8.1. These services are independent of the messaging protocol used. They may
be mapped to SECS-II (SEMI-E5) or to other comparable protocols.
These messaging services define the messages to be used, the nature of the parameters contained within the
messages, and data type of the parameters. Not defined here is the internal structure of the actual messages as
transferred, including order of the parameters and how various data structures and data types are represented.
The service message notation used in the tables below is described in Conventions, Section 5.3.
10.1 Service List — The messages shown in Table 3 are exchanged between service-provider and service-user for
the purpose of accomplishing exception management tasks.
Table 3 Service List
Message Name Type Description
EXPost N Notification by the exception agent that the abnormal situation related to the exception
condition has been detected or significant information has changed while the situation exists.
EXCleared N Notification by the exception agent that the abnormal situation related to the exception
condition is no longer apparent or relevant.
EXRecover R Decision authority request that a particular recovery action be performed.
EXRecoveryComplete N Notification by the exception agent that a recovery action has completed.
EXRecoveryAbort R Decision authority request that a recovery action be terminated immediately.

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.