HP Integrity Superdome SX1000 User Guide, Sixth Edition - HP Integrity Superdo - Page 301

Format, Node Architecture File, Comments, Version Information, MP List Entries, MP Entries

Page 301 highlights

JUST Exploration Tool Data Files 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 non-comment field in the cplx.ini file must start with the keyword FILE_VERSION followed by the file version entered as a double. MP List Entries The first type of entry in this file list the MPs that are possible within the complex. A MP list begins with the keyword MP_List and ends with the keyword End_MP_List. Between the begin and end tags are MP entries defined as follows. MP Entries A MP entry begins with the keyword MP_ID and is followed by the MP reference number as an unsigned integer. MP_ID Node List Entries The second type of entry in this file is a list of nodes. A node list begins with the keyword Node_List and ends with the keyword End_Node_List. Between the beginning and ending tags are the node entries as defined below. Node Entries A node entry begins with the keyword Node_ID and is followed by the node type (either PROCESSOR or IO_EXPANSION), the nodes reference number, and a presence mask available boolean. If the mask available flag is TRUE then the next field is the bit in the mask representing this node, if the flag is FALSE then this field is omitted. The mask available field(s) are followed by the is host flag which indicates whether this entity is a host or not. If the host flag is FALSE then the entity to which commands destine for node are to be sent is specified along with its reference number. Node_ID [] [ ] End of file marker As with all scan files this file must end with the keyword End_Of_File. Example G-10 FILE_VERSION 4.0 Complex Architecture File MP_List MP_ID 0 End_MP_List Node_List Node_ID PROCESSOR 0 TRUE 0 FALSE MP 0 Node_ID IO_EXPANSION 8 FALSE TRUE End_Node_List End_Of_File Node Architecture File This file describes a node and contains the types of boards in each node type and a description of the scan paths in the node. This file contains a list of boards that make up the node followed by a list of paths. The path entries map the paths though the boards to the path in the node. This file can currently have one of two names: node_PROCESSOR.arc or node_IO_EXPANSION.arc. Format Comments Comments 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 must start with the keyword FILE_VERSION followed by the file version entered as a double. FILE_VERSION Appendix G 289

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332

Appendix G
JUST Exploration Tool
Data Files
289
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 non-comment field in the
cplx.ini
file must start with the keyword
FILE_VERSION
followed by the file version entered as a double.
MP List Entries
The first type of entry in this file list the MPs that are possible within the complex. A MP list begins
with the keyword
MP_List
and ends with the keyword
End_MP_List
. Between the begin and end tags are MP entries
defined as follows.
MP Entries
A MP entry begins with the keyword
MP_ID
and is followed by the MP reference number as an unsigned
integer.
MP_ID <reference number>
Node List Entries
The second type of entry in this file is a list of nodes. A node list begins with the keyword
Node_List
and ends with the keyword
End_Node_List
. Between the beginning and ending tags are the node entries as defined below.
Node Entries
A node entry begins with the keyword
Node_ID
and is followed by the node type (either
PROCESSOR
or
IO_EXPANSION
), the nodes reference number, and a presence mask available boolean. If the mask available flag is
TRUE
then the next field is the bit in the mask representing this node, if the flag is
FALSE
then this field is omitted. The mask
available field(s) are followed by the is host flag which indicates whether this entity is a host or not. If the host flag is
FALSE
then the entity to which commands destine for node are to be sent is specified along with its reference number.
Node_ID
<node type> <ref num> <mask flag> [<mask bit>] <host flag> [<entity type> <entity ref #>]
End of file marker
As with all scan files this file must end with the keyword
End_Of_File
.
Example G-10
Complex Architecture File
FILE_VERSION 4.0
MP_List
MP_ID 0
End_MP_List
Node_List
Node_ID PROCESSOR 0 TRUE 0 FALSE MP 0
Node_ID IO_EXPANSION 8 FALSE TRUE
End_Node_List
End_Of_File
Node Architecture File
This file describes a node and contains the types of boards in each node type and a description of the scan
paths in the node. This file contains a list of boards that make up the node followed by a list of paths. The
path entries map the paths though the boards to the path in the node.
This file can currently have one of two names:
node_PROCESSOR.arc
or
node_IO_EXPANSION.arc
.
Format
Comments
Comments 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 must start with the keyword
FILE_VERSION
followed by the file
version entered as a double.
FILE_VERSION <version number>