The following table provides the format and content of the EREP record for devices of a CP that require the CCU operand on the START command:
Byte # (Dec) |
Content Description |
|||
0 |
Hexadecimal 30, indicating an Outboard record. |
|||
1 |
System-dependent operating system version. |
|||
2 |
Hexadecimal 08, indicating the time and date are as formatted by the TIME service, plus a hexadecimal 10 if at least Extended Architecture. |
|||
3 |
Hexadecimal 40, indicating a temporary error. |
|||
4 |
Hexadecimal 80, indicating that no channel path is included. |
|||
5 — 7 |
Not used. |
|||
8 — 11 |
Date in packed decimal format. |
|||
12 — 15 |
Time in packed decimal format. |
|||
16 — 23 |
CPU identification. |
|||
24 — 31 |
TDP jobname. |
|||
32 — 39 |
Channel Command Word (CCW) of the failing channel. |
|||
40 — 47 |
Channel Status Word (CSW) for 370 architecture. |
|||
48 |
Hexadecimal 03, indicating that three double words of device-dependent are available. |
|||
49 |
Not used. |
|||
50 & 51 |
Hexadecimal device number. |
|||
52 — 55 |
Hexadecimal device type, as defined to the system. |
|||
56 & 57 |
Not used. |
|||
58 & 59 |
Hexadecimal device number. |
|||
60 & 61 |
Not used. |
|||
62 & 63 |
Hexadecimal 0001, indicating the number of sense bytes present. |
|||
64 — 87 |
Device-dependent data, as follows: |
|||
|
|
Byte # (Dec) |
Content Description |
|
|
|
64 — 67 |
EBCDIC characters ‘TRDT’, identifying the product. |
|
|
|
68 |
Hexadecimal 01, indicating the current level of the device-dependent data. |
|
|
|
69 |
Hexadecimal ‘S’, indicating the Structure Protocol is being used. |
|
|
|
70 & 71 |
Hexadecimal CP number. |
|
|
|
72 — 79 |
EBCDIC TDPid. |
|
|
|
80 |
Hexadecimal I/O completion code |
|
|
|
81 — 87 |
Not used. |
|
|
|
|
|
|
88 |
Sense byte. If at least Extended Architecture, then: |
|||
|
|
Byte # (Dec) |
Content Description |
|
|
|
89 — 100 |
Extended Architecture Interrupt Response Block (IRB), which contains the failing CSW. |
|
|
|
101 — 104 |
Extended Status Word (ESW). |
|
|
|
|
|
|