semi合集-English.pdf - 第1167页

SEMI E5-1104 © SEMI 1982, 2004 109 Stream,Function Name (Mnemonic) Direction S4,F25 Multi-block Inquire (MB14) S,H->E ,reply Description If a Stream 4 ho st-initiated message is more th an a single block in leng th, t…

100%1 / 7923
SEMI E5-1104 © SEMI 1982, 2004 108
Stream,Function Name (Mnemonic) Direction
S4,F22 Transfer Command Acknowledge (TCA) S,H<-E
Description
Equipment accepts or rejects the transfer command.
Structure
L,2
1. <TRACK> [Accepted or rejected]
2. L,n [n = # errors reported]
1. L,2
1. <ERRCODE
1
>
2. <ERRTEXT
1
>
.
.
n. L,2
1. <ERRCODE
n
>
2. <ERRTEXT
n
>
Exception
If the command is accepted, n = 0.
Stream,Function Name (Mnemonic) Direction
S4,F23 Transfer Job Alert (TJA) S,H<-E,[reply]
Description
Equipment informs the host that a transfer job milestone has been reached (e.g., job started or job complete). If complete, all
quipment resources originally reserved for the transfer have been released.
Structure
L,4
1. <TRJOBID>
2. <TRJOBNAME>
3. <TRJOBMS>
4. L,2
1. <TRACK> [success or failure]
2. L,n [n = # errors reported]
1. L,2
1. <ERRCODE
1
>
2. <ERRTEXT
1
>
.
.
n. L,2
1. <ERRCODE
n
>
2. <ERRTEXT
n
>
Exception
If the transfer job is completed successfully, n = 0.
Stream,Function Name (Mnemonic) Direction
S4,F24 Transfer Alert Acknowledge (TLA) S,H->E
Description
Acknowledge receipt of the S4,F23 message.
Structure
Header only
Exception
None
SEMI E5-1104 © SEMI 1982, 2004 109
Stream,Function Name (Mnemonic) Direction
S4,F25 Multi-block Inquire (MB14) S,H->E,reply
Description
If a Stream 4 host-initiated message is more than a single block in length, this transaction must precede the message.
Structure
L,2
1. <DATAID>
2. <DATALENGTH>
Exception
None
Stream,Function Name (Mnemonic) Direction
S4,F26 Multi-block Grant (MBG4) S,H<-E
Description
Grant (or deny) permission to send multi-block message.
Structure
<GRANT>
Exception
None
10.8.2.2 Micro Level Messages — The following messages support the equipment-to-equipment micro level
handoff of material as defined in SEMI E32.
10.8.2.2.1 The messages which support the micro level are passed directly between the equipment. For the purpose
of the communication link, one of the equipment must be designated the host and the other the equipment. The
choice is up to the implementer. Equipment which are configurable to act as either host or equipment are suggested
for ease of installation.
10.8.2.2.2 The two equipment involved in a micro level transfer assume different roles. One equipment is
designated the “Primary Transfer Partner,” and the other is the “Secondary Transfer Partner” (see SEMI E32 for
more definition). While some consistency of roles is expected, this designation is fluid and may change from one
transfer to the next. The Primary Transfer Partner has more responsibility and thus initiates messages which the
Secondary does not.
10.8.2.2.3 The selection of “Host” and “Equipment” for the communication link is not related to the fluid
relationship of Primary and Secondary Transfer Partner. However, it is the designation of Primary or Secondary
which determines the originator of certain messages. It is for this reason that the designation P = Primary and S =
Secondary Transfer Partner.
SEMI E5-1104 © SEMI 1982, 2004 110
10.8.2.2.4 Micro Level Messages
Stream,Function Name (Mnemonic) Direction
S4,F27 Handoff Ready (HR) S,P<->S
Description
Each transfer partner informs the other when they are ready to perform a specified atomic transfer. The TRLINK values from
the two partners must match. The values contained in the atomic transfer specification pertain to the sender of the message
(except where specified).
Structure
L,2
1. <EQNAME>
2. L,11 [Specification for atomic xfr]
1. <TRLINK> [Atomic transfer identifier]
2. <TRPORT> [Port to be used for transfer]
3. <TROBJNAME> [Transfer object identifier]
4. <TROBJTYPE> [Object type-what form the material is in]
5. <TRROLE> [Role in transfer-primary/secondary]
6. <TRPTNR> [Identifier of transfer partner]
7. <TRPTPORT> [Partner's Port to be Used]
8. <TRDIR> [Transfer direction-send or receive]
9. <TRTYPE> [Active or Passive]
10. <TRLOCATION> [Location to send/receive mtl]
Exception
None
S4,F28 Not Used
Stream,Function Name (Mnemonic) Direction
S4,F29 Handoff Command (HC) S,P->S
Description
Command issued by the primary to the secondary transfer partner to achieve some physical action.
Structure
L,4
1. <TRLINK> [Atomic Transfer identifier]
2. <MCINDEX> [Identified this specific Micro Cmd request]
3. <HOCMDNAME> [Requested Micro Cmd]
4. L,n [n = number of parameters]
1. L,2
1. <CPNAME
1
> [Micro Cmd parameter name]
2. <CPVAL
1
> [Micro Cmd parameter value]
.
.
n. L,2
1. <CPNAME
n
>
2. <CPVAL
n
>
Exception
N = 0 if no parameters are used.
S4,F30 Not Used