semi合集-English.pdf - 第1250页

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 >…

100%1 / 7923
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
>
SEMI E5-1104 © SEMI 1982, 2004 193
Stream,Function Name (Mnemonic) Direction
S14,F20 Generic Service Acknowledge (GSA) M,H<-E
Description
The equipment acknowledges requested service or reports any error(s). If the service is accepted and completed at once, (i.e.
SVCACK = 0) then, the required parameters for the response are listed within this message. If the service is accepted but the
performance of the service takes a relatively longer time due to some physical reason, (i.e. SVCACK = 4) then, the service
response will be sent with the required parameters when the service is completed (see S14,F21/F22). The determination as to
whether a delayed response is acceptable is dependent upon the implementation. LINKID is set to a non-zero value if and only i
f
additional completion reports will be sent. The data items are mapped to the service response parameter list of the applied object
service. Parameters that apply to the list are described in the standard that defines the application of the service.
Structure
L,4
1. <SVCACK>
2. <LINKID>
3. L,n # 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
.
.
n. L,2
1. <SPNAME
n
> service parameter n name
2. <SPVAL
n
> service parameter n value
4. L,2
1. <SVCACK>
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 p = 0, no errors were detected. If n = 0 parameters are returned. SVCACK is specified twice in the above structure for
backward compatibility with the previous structure of this message, and for consistency with other stream 14 reply messages.
The values of both SVCACK data items in this structure must be equal. The above message structure (L,4) is the preferred
structure for this message and must be used for new implementations. The following message structure (L,3) is included for
compatibility with previous implementations and must not be used for new implementations.
Structure:
L,3
1. <SVCACK>
2. <LINKID>
3. L,n # 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
.
.
n. L,2
1. <SPNAME
n
> service parameter n name
2. <SPVAL
n
> service parameter n value