
Appendix H
JUST Exploration Tool
Data Files
224
A board architecture file must exist for each board part number/scan revision. Its file name has the form
brd_<board part number>_<scan revision>.arc
. This file is named using the prefix
brd_
followed by the
board name and scan revision separated by an underscore and ending with the suffix
.arc
.
Format
Comments Comments in this file are specified by placing a # character at the beginning of the line containing the
comment. End of line comments are not currently supported.
Version Information The first none comment field in the cplx.ini file must start with the keyword
FILE_VERSION
followed by the files version entered as a double.
Example H-13
Board Architecture File Version
FILE_VERSION <version number>
Board Path Entries The first series of entries in this file describe the scan paths on the board and the devices on those
paths. Each of these entries begins with the keyword Board_Path followed by the path number. The entries end with the
keyword End_Board_Path. Between the beginning and ending tags the devices on the path are defined. A device entry
begins with the keyword Device and is followed by the devices reference number, the device name, the devices reference
designator, a boolean indicating whether the device is required, and finally the devices removal order.
•
Device number—integer
•
Device name—string
•
Reference designator—string
•
Required flag—TRUE | FALSE
•
Removal order—integer
NOTE
The removal order determines which non-required devices are missing if less than the maximum number
of devices are encountered. The lower the removal order the more likely the device is missing.
Link Connection Entries Each link connection to this board needs to have an entry in this file. Link entries contain
primary and secondary link connection information. A link entry is specified as follows.
Each entry begins with the keyword
Link_Type
followed by the link type number and ends with the keyword,
End_Link_Type
. Between the begin and end are entries for Primary and Secondary link connections. A primary link
connection is the originating connection. The secondary entries are destinations for the link.
A primary link connection begins with the keyword
Primary
and ends with the keyword
End_Primary
. Between the begin
and end tags the possible connections are listed as specified below:
•
ID—Cable number of device selector number
•
lookup—Number added to look up the correct entry
•
loopback—Flag that indicates whether the connection is a loopback connection
•
type—String that indicates the type of cable being processed
•
part number—Part number of the cable as a string
•
name—String representing the name of the link cable
Secondary link connections begin with the keyword
Secondary
and end with the keyword
End_Secondary
. Connections
on a secondary link follow the same format as those of a primary link but use two less fields.
Link connections begin with the keyword
Connection
followed by the following fields.
Содержание 9000 Superdome
Страница 8: ...Contents 8 ...
Страница 9: ...9 Preface ...
Страница 21: ...21 IEC 60417 IEC 335 1 ISO 3864 IEC 617 2 International Symbols ...
Страница 22: ...22 Figure 9 Superdome Declaration of Conformity Page 1 ...
Страница 23: ...23 Figure 10 Superdome Declaration of Conformity Page 2 ...
Страница 24: ...24 ...
Страница 32: ...Chapter 1 Introduction Installation Warranty 8 ...
Страница 130: ...Chapter 4 Verifying and Booting Superdome Enabling iCOD 106 ...
Страница 146: ...Chapter 6 Troubleshooting and Installation Related Tasks Installing a PCI I O Card While the Cell is Off 122 ...
Страница 154: ...Chapter 7 No Boot Disk Superdome Installations Installing the Superdome Operating System From Available Media 130 ...
Страница 172: ...Appendix A hp Server rx2600 Support Management Station Configuring the SMS 148 ...
Страница 184: ...Appendix C Superdome LAN Interconnect Diagram 160 ...
Страница 193: ...Appendix F 169 F A180 Support Management Station ...
Страница 230: ...Appendix G Connecting Multiple SPU Cabinets Connecting Cables 206 ...
Страница 256: ...Appendix H JUST Exploration Tool Error Conditions 232 ...