Technical data

The user program is structured as follows:
After evaluating the ANZW, to determine whether a previous job is still
active, the request is sent. If no PAFE occurs and the SEND job is
completed, the ANZW is checked to determine whether a confirmation has
been received. If this is the case, this is transferred with HDB RECEIVE to
the CPU and the parameters can be processed in the user program or
evaluated as a check. An error check has already been performed with
ANZW, PAFE and link_status.
Word DB 140 Explanation
0:
1:
2:
3:
4:
5:
6:
7:
8:
9:
KH = 0000;
KY = 000,000
KY = 011,000
KY = 000,000
KY = 000,000
KH = 0000;
KY = 000,000
KY = 000,000
KY = 000,000
KY = 000,000
***Request-Header****
com_class / user_id
service_code / no significance
no significance
no significance
****Confirmation-Header****
com_class / user_id
service_code / link_status
no significance/no significance
no significance/no significance
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
KY = 000,000
KH = 0000;
KH = 0000;
KH = 0000;
KH = 0000;
KY = 000,000
KH = 0000;
KH = 0000;
KH = 0000;
KH = 0000;
KH = 0000;
KH = 0000;
KH = 0000;
KY = 000,000
KY = 000,000
KY = 000,000
KY = ..
KY = ....
hsa / loc_add.station
station_type
baud_rate
medium_red
retry
default_sap / network_con._sap
tsl (slot-time)
tqui (modulator quiet time)
tset (set-up time)
min_tsdr (min. station delay)
max_tsdr (max. station delay)
ttr (target rotation time)
ttr (target rotation time)
g (gap_up) / in_ring_desired
in_ring_desired / physical_Layer
physical_Layer / no significance
.....
.....
Table 12.14 DB 140
Service and Diagnostics using FMA Functions B8976060/02
Volume 1 12 - 36