semi合集-English.pdf - 第1249页

SEMI E5-1104 © SEMI 1982, 2004 191 Stream,Function Name (Mnemonic) Direction S14,F19 Generic Se rvice Request (GSR) M,H-> E,reply Description The host request s an object to pe rform the sp e cified service with its a…

100%1 / 7923
SEMI E5-1104 © SEMI 1982, 2004 190
Stream,Function Name (Mnemonic) Direction
S14,F17 Supervised Object Action Request (SOAR) S,H<->E,reply
Description
This message is used to request a supervisor to have a supervised attached object perform an action. OBJSPEC specifies the
supervisor, and TARGETSPEC specifies the attached object.
Structure
L,4
1. <OBJSPEC>
2. <OBJCMD>
3. <TARGETSPEC>
4. L,a a = number of attribute settings
1. L,2
1. <ATTRID
1
>
2. <ATTRDATA
1
>
.
.
a. L,2
1. <ATTRID
a
>
2. <ATTRDATA
a
>
Exception
If a = 0, no attribute settings are provided.
Stream,Function Name (Mnemonic) Direction
S14,F18 Supervised Object Action Acknowledge (SOAA) M,H<->E
Description
This message is used to acknowledge the success or failure of an action requested of a supervisor.
Structure
L,2
1. L,b b = number of attributes
1. L,2
1. <ATTRID
1
>
2. <ATTRDATA
1
>
.
.
b. L,2
1. <ATTRID
b
>
2. <ATTRDATA
b
>
2. L,2
1. <OBJACK>
2. L,p p = number of errors reported
1. L,2
1. <ERRCODE
1
>
2. <ERRTEXT
1
>
.
.
p. L,2
1. <ERRCODE
p
>
2. <ERRTEXT
p
>
Exception
If b = 0, no attributes are returned. If p = 0, no errors were detected.
SEMI E5-1104 © SEMI 1982, 2004 191
Stream,Function Name (Mnemonic) Direction
S14,F19 Generic Service Request (GSR) M,H->E,reply
Description
The host requests an object to perform the specified service with its associated parameters. If multi-block, it shall be preceded
by the S14F23/F24 Multi-Block Inquire/Grant transaction. DATAID is given uniquely to each message. OPID is uniquely
specified to identify delayed completion information for time consuming service. OPID could be zero if and only if the service
cannot take a long time.
Structure
L,5
1. <DATAID>
2. <OPID>
3. <OBJSPEC>
4. <SVCNAME>
5. L,m # of parameter groups
1. L,2
1. <SPNAME
1
> service parameter 1 name
2. <SPVAL
1
> service parameter 1 value
2. L,2
1. <SPNAME
2
> service parameter 2 name
2. <SPVAL
2
> service parameter 2 value
.
.
m. L,2
1. <SPNAME
m
> service parameter m name
2. <SPVAL
m
> service parameter m value
If a specific value of SPNAME is defined to have a SPVAL defined as a LIST, it shall
always be a LIST. If the SPVAL that is associated to that specific value of SPNAME is
defined to be anything other than LIST, it will result in a format error.
Exception
A zero length list, m = 0, indicates that no parameter groups are sent with the service request. OBJSPEC can be a null length
item if no object provide the services is defined in the standards which are referred to and it is assumed that “Equipment” is
delegated and handled as if it is an object.
Notes:
1. If some service parameters are attributes of the specified object, service parameter name-value pair, that is SPNAME and
SPVAL, is actually attribute id-data pair, that is ATTRID and ATTRDATA. An example of parameter part in the message
format could be interpreted as below.
L,m
1. L,2
1. <SPNAME
1
>
2. <SPVAL
1
>
2. L,2
.
.
k. L,2
1. <ATTRID
k
>
2. <ATTRDATA
k
>
.
.
m. …
2. If SPVAL is a LIST, the items that make up that list shall take on one of the following forms: (1) a list of items with an
identical format, (2) a LIST of SPNAME, SPVAL pairs, as illustrated below. When SPVAL is actually ATTRDATA, even if it
is a LIST, it or its parts are not required to expand into lower level items if their names have not been formally named in the
corresponding SEMI standard.
A) L,2
1. <SPNAME
a
>
2. L,m
SEMI E5-1104 © SEMI 1982, 2004 192
1. <SPVAL
a1
>
2. <SPVAL
a2
>
.
.
m. <SPVAL
am
>
B) L,2
1. <SPNAME
b
>
2. L, n
1. L,2
1. <SPNAME
bl
>
2. <SPVAL
bl
>
.
.
n. L,2
1. <SPNANE
bn
>
2. <SPVAL
bn
>