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

JUST Exploration Tool Error Conditions Error Conditions When errors are detected during update, several things can happen. If the error is detected at the complex level, an error is written to the complex.cfg file, but the complex data will not be present in the file. If an error is detected at the node level, the node configuration file will contain an error message and no data will be present. If an error is detected at the board level, an error message is placed in the node configuration file for the board. This message prevents JUST from loading the file but does not affect any other board or path data in the file. If an error is detected at the scan path level, the path entry in the file will contain an error message that prevents JUST from loading the file, but no other path data is affected. In any of these cases, a jet.err file is created and an entry for the node is added to it. If an error occurs at the node level, the nodes entry is not placed in the complex.cfg file. If an error is detected during link processing, a message is placed in the flex.mte file for certain error types. Due to the fact that the flex.mte file is complex wide, JET may encounter errors when testing a single node with other nodes in the complex powered off. This is a valid test condition. Therefore, link errors due to destination nodes not being present are dropped and a jet.log entry is made, but no error is entered into the flex.mte file. 298 Appendix G