STATUS LOG
7-5
Edition One
XC1000 Service
7.2.2 The Body
In addition to the header, all status-log entries contain a body. The body
of the entry provides more detailed information about the logged condition.
For example, CB messages or an IORB peripheral address embedded within
the body can help to identify the affected card, where a malfunction caused
the logged entry. The body of the status-log entry starts on line 00010
(Figure 7-2). The format of the body is determined by the task that logged
the entry.
7.2.3 The Input/Output Request Block
The input/output request block (IORB) contains the peripheral address, or
destination-card address, with which the CPU was communicating at the
time of the error. The destination-card address is identified in terms of a
bank, slot, and channel. Each of these is expressed as a four-bit number
(nibble). The format of the destination-card address is shown in Figure 7-3.
0100 = 0001
BANK
SLOT
CHANNEL
OFFSETS
IN LINE 00010
Figure 7-3. Destination-Card Address
in the IORB.
Not all status-log entries contain an IORB peripheral address.
When
status-log entries contain an IORB peripheral address, it can occur at
different locations in the body of the status-log entry, depending on
the status code.
However, the IORB peripheral address commonly occurs
in line 00010. To assist in interpreting a status-code entry, the location of
the IORB peripheral address, where present, is provided with each status
code described in section 7.3.
To determine the destination-card address, check the appropriate offsets
listed in the status-code description, and transpose the bytes. Using the
format shown in Figure 7-3, refer to Table 7-2 to determine the physical
card identified by the bank and slot assignment. A diagram showing
bank:slot locations of physical cards is also provided, in Figure 7-4. When
decoding port-specific entries, use Table 7-3 to cross-reference the channel
to a port.
Table 7-2 and Table 7-3 are located at the end of this chapter on a
foldout page. These tables are required throughout the chapter when
interpreting the status codes in section 7.3. Leave Table 7-2 folded
out for easy reference when using section 7.3.
SECTION 7.2
Summary of Contents for XC1000
Page 1: ...EDITION ONE XC1000 P N 101 1345 000 SERVICE MANUAL ...
Page 8: ...CONTENTS ...
Page 19: ...1 INTRODUCTION ...
Page 30: ...2 SITE PREPARATION ...
Page 60: ...3 PLATFORM INSTALLATION ...
Page 112: ...4 STARTUP AND INITIALIZATION ...
Page 177: ...5 ROUTINE MAINTENANCE ...
Page 195: ...6 TROUBLESHOOTING ...
Page 237: ...7 STATUS LOG ...
Page 297: ...STATUS LOG 7 54 Edition One XC1000 Service ...
Page 302: ...8 REPAIR AND REPLACEMENT ...
Page 380: ...9 SYSTEM UTILITIES ...
Page 424: ...10 COMPONENT DESCRIPTIONS ...
Page 465: ...11 OPTIONAL FEATURES ...
Page 485: ...12 RELEASE 1 55 UPGRADE INSTRUCTIONS ...
Page 516: ...13 RELEASE 2 X UPGRADE INSTRUCTIONS ...
Page 559: ...14 RELEASE 3 02 FCP CONVERSION INSTRUCTIONS ...
Page 603: ...15 RELEASE 3 02 ONLINE UPGRADE INSTRUCTIONS ...
Page 631: ...16 RELEASE 3 0 SYSTEM UTILITIES ...
Page 683: ...17 RELEASE 4 X FCP CONVERSION INSTRUCTIONS r P N 281 0023 002 1 of 3 ...
Page 725: ...18 RELEASE 4 X ONLINE UPGRADE INSTRUCTIONS r P N 281 0023 002 2 of 3 ...
Page 760: ...19 RELEASE 4 0 SYSTEM UTILITIES P N 281 0023 002 Part 3 of 3 r ...
Page 776: ...20 RELEASE 4 1 SYSTEM UTILITIES P N 281 0033 000 ...
Page 787: ...APPENDIXES ...