| Page: | 1 | 2 | 3 |
|---|
The following messages are generated by the KDB when error conditions occur.
SYNTAX ERROR | ||
| Cause: | Syntax error in the command specification. | |
| Action: | Correct the command syntax and reexecute. | |
ADDRESS ERROR | ||
| Cause: | 1. Address field is missing. | |
| 2. Address specified in the address field cannot be accessed | ||
| 3. Address specifications in the trap and DAS commands are not within the 4-byte boundary. | ||
| Action: | Correct the address specification and reexecute. | |
PROCESS NOT FOUND | ||
| Cause: | 1. PID process specified is not found. | |
| 2. proc entry specified has not been used. | ||
| 3. Process specified is not found. | ||
| Action: | Correct the process specification and reexecute. | |
TASK NOT FOUND | ||
| Cause: | The TID task specified is not found. | |
| Action: | Correct the task specification and reexecute. | |
SYMBOL NOT FOUND | ||
| Cause: | Symbol name specified is not queued as symbol information. | |
| Action: | Correct the symbol name and reexecute. | |
| Home |
|---|
I/O ERROR | ||
| Cause: | I/O error is detected in the input/output device. | |
| Action: | Remove the error and reexecute. | |
OLD VALUE UNMATCH | ||
| Cause: | The specified OLD VALUE in the P command is not consistent with the actual value. | |
| Action: | Correct the value and reexecute. | |
LENGTH ERROR | ||
| Cause: | 1. Error in specifying the length field in D command. | |
| 2. Length of OLD VALUE and NEW VALUE in the P command are not consistent. | ||
| Action: | Correct length or value and reexecute. | |
TOO MANY TRAPS | ||
| Cause: | 1. There are already 64 traps set. | |
| 2. No area is available for storing multicommand. | ||
| Action: | Remove unwanted traps and reexecute. | |
NOT YET CPU READY | ||
| Cause: | Command execution is not possible because the CPU is not yet activated. | |
| Action: | Activate the CPU and reexecute. | |
REGISTER NOT EXIST | ||
| Cause: | Reference to register cannot be completed. | |
| Action: | Activate CPU and reexecute. | |
ILLEGAL ADDRESS TYPE | ||
| Cause: | The address type specified is incorrect. | |
| Action: | Correct the address type and reexecute. | |
| Home |
|---|
TRAP IS ALREADY SET | ||
| Cause: | A trap is already set in the address. | |
| Action: | Change the trap address or remove the trap at the specified address and reexecute. | |
CANCEL | ||
| Cause: | Command processing is canceled halfway. This message indicates that command processing was interrupted by an attention key. | |
| Action: | Reexecute. | |
ILLEGAL XMU#/PARTITION# | ||
| Cause: | 1. The specified XMU virtual disk device number or partition number is incorrect. | |
| 2. Dump data already exists in the XMU virtual disk device or partition with the specified number. | ||
| Action: | Correct the device number or partition number and reexecute. | |
| If the result of executing the command is normal, the message EXECUTED is displayed. |
| Home |
|---|
| Contents | Previous Chapter | Index |