semi合集-English.pdf - 第1229页
SEMI E5-1104 © SEMI 1982, 2004 171 Stream,Function Name (Mnemonic) Direction S13,F0 Abort Transaction (S13F0) S,H< ->E Description Same form as S1,F 0. Structure Exception Stream,Function Name (Mnemonic) Direction …

SEMI E5-1104 © SEMI 1982, 2004 170
10.17.2.9.3 The size of the secondary message may be
less because of limited resources in the sending system.
10.17.2.9.4 For data sets with Discrete records, the for-
mat of each item is either ASCII (format 20) or binary
(format 10). There is no requirement that all records be
in the same format, but mixed record formats are not
encouraged. Items with ASCII format should have only
data characters. Characters which the sending system
uses for control information (e.g., newline for a record
terminator) should not appear. If an application finds it
necessary to include these characters, then format 10, or
Stream should be used.
10.17.2.10 CLOSE Transaction — This transaction ter-
minates a data transfer and frees the Handle for future
use. The primary message is sent by the receiving sys-
tem and contains only the Handle. The sending system
responds with a secondary message which has a return
code.
10.17.2.10.1 The return code is one of the following:
OK.
ERROR: No open Data Set (i.e., incorrect Handle).
ERROR: Pending Transaction.
10.17.2.11 Sending a Data Set — Writing a data set is
performed by requesting that the receiving system read
it. The sending system initiates the SEND transaction
to request that a data set be read. The receiving system
is expected to perform the OPEN, READ, and CLOSE
transactions to transfer the data set if it accepts the
request. The time between the secondary message of
the SEND and the primary message of the OPEN
depends on the application.
10.17.2.12 The SEND Transaction — The primary
message sent from the sending system to the receiving
system contains the Data Set Name.
10.17.2.12.1 The secondary message contains the Data
Set Name and a return code which is one of the follow-
ing:
OK.
ERROR: Unknown Data Set Name.
ERROR: Try later (i.e., the system is busy).
10.17.2.13 Error Recovery — The receiving system
may crash while a data set is open but no READ trans-
action is pending. The sending system will not be able
to tell that this has happened because there is no time-
out value defined between READ transactions. When
the receiving system is restarted it may have forgotten
which data sets were open. States in the two systems
are now inconsistent.
10.17.2.14 RESET Transaction — The RESET transac-
tion offers a way to resynchronize the two systems.
When one system issues the primary message of the
RESET transaction, it is informing the other system that
any data sets which may have been open are to be
closed. This applies to all data sets open between both
systems. It is not necessary to issue CLOSE transac-
tions for each individual data set because the RESET
transaction is a global close.
10.17.2.15 Any equipment which uses Stream 13 must
issue the RESET transaction as part of its initialization
or bootstrap procedure. A host system must issue a
RESET to equipment which uses Stream 13 during the
initialization for that equipment.
10.17.2.16 SECS-II Protocol Definition —
Figure 11
shows the state diagram for the sending system while a
data set is being transferred. Each circle shows a possi-
ble state of the sending system. The names of these
states are for reference only. They are not meant to
suggest an implementation. The arrows show transi-
tions due to SECS-II messages received or sent by the
sending system.
10.17.2.16.1 In the initial state (Idle) handle X is not
open. The states marked with an asterisk are those in
which a transaction is outstanding. If the sending sys-
tem receives any primary message from the receiving
system with handle X during the time it is in these
states, then the secondary message for that transaction
will contain the “Pending Transaction” error code, but
the original transaction for handle X will not be
affected. Some states, especially the error states, may
take zero time in some implementations. In these cases,
the “Pending Transaction” error code would not be
returned from those states.
10.17.3 Formatted Data Sets — Formatted data sets
are data sets transferred in a standard format. Stream
13 provides a method for transferring data sets in a
table format. A table has both attributes and content.
The attributes of the table provide information about the
data set as a whole, such as the date and time that it was
last modified, its size, etc. The content of the table
consists of column headers and rows. A row is an
ordered list of table elements. A column refers to all
table elements at a specific position within all rows,
where each column is identified by a corresponding text
string as a column header. The table elements in the 1st
column position are used as an identifier for the row.

SEMI E5-1104 © SEMI 1982, 2004 171
Stream,Function Name (Mnemonic) Direction
S13,F0 Abort Transaction (S13F0) S,H<->E
Description
Same form as S1,F0.
Structure
Exception
Stream,Function Name (Mnemonic) Direction
S13,F1 Send Data Set Send (DSSS) S,H<->E,reply
Description
Sent by the sending system to request that the other system read a dataset.
Structure
L,1
1. <DSNAME>
Exception
None
Stream,Function Name (Mnemonic) Direction
S13,F2 Send Data Set Acknowledge (DSSA) S,H<->E
Description
Sent by the receiving system in response to Send Data Set Send.
1. <DSNAME>
2. <ACKC13>
Structure
Exception
The possible ACKC13 codes for this message are:
0 = O.K.
1 = ERROR:Try later.
2 = ERROR:Unknown Data Set Name.
Stream,Function Name (Mnemonic) Direction
S13,F3 Open Data Set Request (DSOR) S,H<->E,reply
Description
Sent by the receiving system to open a data set for reading.
Structure
L,3
1. <HANDLE>
2. <DSNAME>
3. <CKPNT>
Exception
None

SEMI E5-1104 © SEMI 1982, 2004 172
Stream,Function Name (Mnemonic) Direction
S13,F4 Open Data Set Data (DSOD) S,H<->E
Description
Sent by the sending system in response to Open Data Set Request.
Structure
L,5
1. <HANDLE>
2. <DSNAME>
3. <ACKC13>
4. <RTYPE>
5. <RECLEN>
Exception
The possible ACKC13 codes for this message are:
0 = O.K.
1 = ERROR:Try later.
2 = ERROR:Unknown Data Set Name.
3 = ERROR:Illegal Checkpoint value.
4 = ERROR:Too many open Data Sets.
5 = ERROR:Data set open too many times.
9 = ERROR:Handle in Use.
10 = ERROR:Pending Transaction.
Stream,Function Name (Mnemonic) Direction
S13,F5 Read Data Set Request (DSRR) S,H<->E,reply
Description
Sent by the receiving system to read data from an open data set.
Structure
L,2
1. <HANDLE>
2. <READLN>
Exception
None