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

Data Files, Input Data Files, Input Data File Locations, Configuration Files

Page 298 highlights

JUST Exploration Tool Data Files Data Files Input Data Files JET uses several input data files of two main types: configuration files and architecture files. The configuration files control how the JET utility operates and the architecture files provide information on the system under test. NOTE Comments can be used in any of these files and are indicated by a # sign in front of the comment. Input Data File Locations Unless otherwise specified, JET looks for its data using a search algorithm that is valid for all scan tools. It first looks for a local ./config directory. If it is found, JET then looks for the required file in that location. If the file is not found, then JET checks to see if the SCANSW_DIR environment variable has been set. If this variable is set to the path specified in the variable, it will be used to find the file. Failing this, JET looks in the default scan file directory path for the file. Configuration Files Configuration files control the flow of execution and other processing information needed by the JET application. There are currently three configuration files: jet.cfg, cplx.ini, and board_name.map. JET Configuration File (Optional) This file contains several parameters that define JET operation. If the file is not found, then JET uses its default values. Each of the parameters described for this file may or may not be present. If they are not present, default parameters are used. This file must be located in the directory from which JET is executed and must have the name jet.cfg. The following list describes parameters supported in the JET configuration file: • Cplx_INI_File-Shows JET where to look for the cplx.ini file (this file is described below). The default for this field is the /opt/scansw/data directory. This field contains a path and file name. • Max_Msg_Retries-Specifies JET how many times to resend a command before declaring a communications error. This field is a positive integer value with a default of five. It is used only with the UDP communications protocol. • Msg_Retry_Interval-Specifies the amount of time to wait for a response to a command before timing out and resending the command. This is a positive floating point number with a default value of five seconds for UDP and 25 seconds for TCP. • Debug_Level-Sets the debug level for JET. Based on this value, different amounts of data are logged into the jet.log file. The debug level is an integer value between zero and four. • Log_File-Specifies the name of the JET log file. This field is a string specifying the path and file name of the file to use. The default is /opt/scansw/data/jet.log. 286 Appendix G

  • 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
286
Data Files
Input Data Files
JET uses several input data files of two main types: configuration files and architecture files. The
configuration files control how the JET utility operates and the architecture files provide information on the
system under test.
NOTE
Comments can be used in any of these files and are indicated by a # sign in front of the
comment.
Input Data File Locations
Unless otherwise specified, JET looks for its data using a search algorithm that is valid for all scan tools. It
first looks for a local
./config
directory. If it is found, JET then looks for the required file in that location. If
the file is not found, then JET checks to see if the
SCANSW_DIR
environment variable has been set. If this
variable is set to the path specified in the variable, it will be used to find the file. Failing this, JET looks in the
default scan file directory path for the file.
Configuration Files
Configuration files control the flow of execution and other processing information needed by the JET
application. There are currently three configuration files:
jet.cfg
,
cplx.ini
, and
board_name.map
.
JET Configuration File (Optional)
This file contains several parameters that define JET operation. If the file is not found, then JET uses its
default values. Each of the parameters described for this file may or may not be present. If they are not
present, default parameters are used.
This file must be located in the directory from which JET is executed and must have the name
jet.cfg
.
The following list describes parameters supported in the JET configuration file:
Cplx_INI_File
—Shows JET where to look for the
cplx.ini
file (this file is described below). The default
for this field is the
/opt/scansw/data
directory. This field contains a path and file name.
Max_Msg_Retries
—Specifies JET how many times to resend a command before declaring a
communications error. This field is a positive integer value with a default of five. It is used only with the
UDP communications protocol.
Msg_Retry_Interval
—Specifies the amount of time to wait for a response to a command before timing
out and resending the command. This is a positive floating point number with a default value of five
seconds for UDP and 25 seconds for TCP.
Debug_Level
—Sets the debug level for JET. Based on this value, different amounts of data are logged
into the
jet.log
file. The debug level is an integer value between zero and four.
Log_File
—Specifies the name of the JET log file. This field is a string specifying the path and file name
of the file to use. The default is
/opt/scansw/data/jet.log
.